Hello,

I was using Draggableviews 6.x-3.1 on my site (running drupal 6.10) and everything was working perfectly. When I updated to 6.x-3.2-beta2 and went to view a page that had a draggable view on it (as configured through views 2) I now get the following error:

Fatal error: Call to a member function get_form_element() on a non-object in /usr/local/4admin/apache/vhosts/mysite.com/httpdocs/drupal/sites/default/modules/draggableviews/draggableviews_theme.inc on line 156

Similarly, when I go to the frontpage of my site now I find the following error messages at the top:

* Draggableviews: Handler could not be found.

* warning: Invalid argument supplied for foreach() in /usr/local/4admin/apache/vhosts/mysite.com/httpdocs/drupal/sites/default/modules/draggableviews/draggableviews.inc on line 368.

* warning: Invalid argument supplied for foreach() in /usr/local/4admin/apache/vhosts/mysite.com/httpdocs/drupal/sites/default/modules/draggableviews/draggableviews.inc on line 656.

When I did the module update I updated it along with a few other modules and then ran update.php once and it said that it successfully added a table as required by draggable views and no errors were logged during the creation of the table. The module, along with DraggableViews CCK Implementation module are enabled.

I'm not quite sure what happened, where to start troubleshooting or even if I've given you enough information to figure out whats going on, but my site is heavily reliant on the Draggableviews module, so hopefully its something thats correctable.

Thanks!

Comments

sevi’s picture

sevi commented

What I can say for sure is that you have to update the draggableviews settings. Since CCK-handler isn't the default implementation anymore you have to choose it explicitly from the list of available handlers (at the part with the order fields).

dkane’s picture

dkane commented

Thad did the trick. Thanks! I just changed the handler to from "Native" to "CCK" under the draggableviews setting and it all is back and working.

What is the difference then between the "Native" and "CCK" and why would I use "Native", since it seems to break everything...

Thanks again sevi

sevi’s picture

sevi commented
Status: Active » Fixed

True, based on your description "Native" seems to be very useless :) But actually this isn't the case :)
"Native" handler saves the values to a database table. So you don't have no bearing on where the data gets saved. If you don't really need CCK (and all its overhead) you should use "Native" handler because of performance issues.
To use the "Native" handler use the fields "Draggableviews: Value #1", etc. that came with the beta version instead of the CCK fields. These fields can be reused for each view.

I'll rewrite the documentation soon.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.