Since beta 5, vdt works wonderfully with regular, non-ajax views, but only ajax views show up on the settings page. For a non-ajax view this requires creating a view, making it ajax, adjusting its vdt settings, then returning the view to be non-ajax.

It would be great if non-ajax views just showed up in the vdt settings to begin with. Also, the documentation should be updated to indicate that non-ajax views are supported.

Comments

jordanmagnuson’s picture

jordanmagnuson commented
Title: Update vdt settings page to show non-ajax views » Update vdt to allow tabs on non-ajax views

My mistake -- once the drupal cache is cleared, vdt tabs are removed from non-ajax views, even though vdt can now work with those views. To fix this, the check at line 308 of viewsdisplaytabs.module:

if (_viewsdisplaytabs_supported_view($view)) {

should simply be removed. After removing that check, vdt can be used just fine with non-ajax views.

jordanmagnuson’s picture

jordanmagnuson commented
Category: bug » feature
Status: Active » Needs review

Changing status to needs review.

jordanmagnuson’s picture

jordanmagnuson commented
Status: Needs review » Needs work

After further testing, it seems a bit more needs to be done to properly implement this for non-ajax views. Currently if I turn ajax off, but have vdt on, vdt removes ajax from my view's exposed filters (autocomplete when filtering by tags, for example). Using views 6.x-3.x-dev.

gooddesignusa’s picture

gooddesignusa commented

Subscribing.
If ajax was not required I think i would be able to use this with a gmap view

solipsist’s picture

solipsist commented

If you disable AJAX for your view, Views will not depend on AJAX at all why auto completion et c won't work.

The issue with VDT still requiring AJAX for the settings page is fixed and committed since a while back.

Have you tried the latest development release?