Small bug that I've noticed when making changes to a view display. When you are adding or modifying any setting for a display, and you click the override button, it closes the settings box. It saves the overridden status, but is rather annoying. In D6, clicking on the override button overrode the default display, but kept the settings box open so you could make or continue to make changes. With this you have to add or modify a setting, click override, then click on that setting to then make changes.
I am using the 7x-dev April 30th versions of both Drupal7 and Views.
Comments
Comment #1
dawehnerThis could be caused by the same bug as http://drupal.org/node/734062
The function views_ui_ajax_form looks a bit different in d7, perhaps there as something missported.
Comment #2
bojanz commentedHere's a comparison of the mentioned function between the 6.x-3.x and 7.x-3.x version.
The called functons would probably need to be compared too, since I didn't feel very enlightened after reading the diff ;)
Comment #3
dawehnerI hoped fixing re_render would do it, but at no level.
So what's the problem:
The code should look like this:
Currently it's $form_state['submitted'].
The problem is that $output is not empty when you click "update" on the filter. So the item form never do a redirect, so you don't come back to the main form.
Views in d6 hat this fapi part:
This is used by d6 views to have a empty output.
So from my perspective we have to simulate rerender in views_ajax_form_wrapper or find a way to do this with d7 fapi and write everything that it does work as expected.
But this is really not trivial
You better shouldn't have two not equal fapi's and mixed ajax frameworks.
Comment #4
dawehnerPuh.
Now this patch allows to use views without js :) But there are some type problems with js enabled.
Comment #5
dawehnerI think http://drupal.org/node/626732 has the same problem.
Comment #6
bojanz commentedApplied the patch.
Clicking "Expose" or "Hide" gives me the above mentioned type errors, looking like this:
The offending part is this:
In this case $output is a html string, hence the error.
I tried placing "$output = array();" above the offending line, but that just caused the links/buttons to go dead.
So, views_ajax_form_wrapper() needs some more loving...
Tried it with JS disabled, clicked around what's interesting is that even with JS off, the exposed form settings validation doesn't work.
Comment #7
dawehnerI should have written this in my comment. That's exact the problem where i stopped.
I think this stops the validation.
Comment #8
dawehnerI commited this part
This has nothing todo with the central problem.
Comment #9
dawehnerThere is hope in the darkest times :)
Comment #10
dawehnerOne's this issue is fixed the test for views_exposed_form should not fail anymore.
Comment #11
dawehnerYE...EAH!
Based on some magic this issue is now solved.