table is undraggable when view is exported to code

definitely needs review

I have replicated this problem on 6.x.3.2-beta-5 and the latest 6.x.3.2-dev -- when I export a view using DraggableViews to code, I have to go in and change the style plugin and change it back or change a setting for the style plugin. Based on very minimal debugging, it appears the that the draggable views info is not properly attaching to the view in this scenario.

I can reliably reproduce this as well. I have to edit any setting within the view, save it (so that it's in the database and not just cached by views from the exported code) and finally clear my sites cache to get the view operating. I've seen this in 6.x-3.2-beta5 as well as 6.x-3.x-dev. Unfortunately I don't think I'll get anytime within the next few weeks to look into this.

1) There is nothing showing up except the submit-button?
2) ..or does everything show up except the drag handles?

Presuming this issue is (1) I suppose this is a duplicate of #541130: Theme registery issues

Ok now I understand. This isn't a duplicate of #541130: Theme registery issues.
I've never tried before to export a draggable view to code (without saving the view to the database). DraggableViews denied rendering all tabledrag-stuff when the view doesn't have a vid. Once you hit the submit button everything is fine.

With the attached patch I consequently use the view-name instead of the vid. So also non-saved (..to code exported) views are supported. The database columns changed, so update.php must be called. The update script ports all vid's to the appropriate view-names.

Greetings,
sevi

EDIT: Patch already committed to DRUPAL-6--3 branch (see latest dev version)

Since this patch is already part of the recommended DRUPAL-6--3-2 version I'll set the status to fixed. Open a new issue if needed.