Just updated to the latest Views Dev and now there are "Apply" buttons on all my blocks that use Views. They don't actually do anything, but just sit there but they are visible to everyone. They appear at the top left of each Block.
Just updated to the latest Views Dev and now there are "Apply" buttons on all my blocks that use Views. They don't actually do anything, but just sit there but they are visible to everyone. They appear at the top left of each Block.
Comments
Comment #1
gustav commentedSubscribing. I have the same problem.
Comment #2
Jeremy Toaster commentedWhen you click on these "apply" buttons you get
"An error occurred at /views/ajax" and the little blue spinners sit there and spin and nothing happens.
jeremy
Comment #3
Jeremy Toaster commentedwarning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'views_ajax' was given in /Library/WebServer/Documents/mysite/www/includes/menu.inc on line 346.
This just showed up after hitting those apply buttons a few times and navigating to another section of the site afterwards.
Comment #4
merlinofchaos commentedThe extraneous apply button is fixed in -dev. Note that Jeremy's issue is a dup of http://drupal.org/node/288101 and is a related issue but I'm keeping that one over on that issue.
Comment #5
Jeremy Toaster commentedThe latest DEV I can find is AUG 20, but when I install it, it says it is AUG 19 and the tarball updater is not showing any newer releases.
Comment #6
merlinofchaos commentedI only just checked it in; it can take up to 12 hours for the automatic tarball to be made. I believe it happens at midnight GMT and noon GMT, so it should've been rolled 20 minutes ago now.
Comment #7
Jeremy Toaster commentedSeems to be fixed now.
Thanks a lot.
jeremy
Comment #8
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #9
Anonymous (not verified) commentedNope.
Iiiiiiiiiiiiiiiiiiittttt's baaaaaaaaack
Views filter opening in a different block in IE than it should?
Comment #10
dawehnerSorry but this is a different problem. Read the issue carefully.
Comment #11
merlinofchaos commentedAlso if you think it's the same problem, don't re-open an issue. Working the same problem in 2 issues helps who, exactly? Not the maintainers and not the people with issues and not the people trying to figure out what's going on.
Comment #12
Anonymous (not verified) commentedI found this is issue afterwards, and referenced to the other issue. Forgot to reference back. Still trying to fix this, as it caught me offguard on a live site. But I should not re-open a issue cue and use a different one even if it is the same problem?
It's been a long day, and I am still nowhere solving this issue. So my apologies, if it got posted wrong. Just trying to help someone running into the same problem.
And sick and tired of having to put my site offline every so many days because another bug in Drupal crops up on live, and not in testing.