A view without lang prefix, when setup to have attachment with lang prefix works nicely. But when there is lang prefix its stops working. This is when AJAX is enabled, when disabled it works ok.
A view without lang prefix, when setup to have attachment with lang prefix works nicely. But when there is lang prefix its stops working. This is when AJAX is enabled, when disabled it works ok.
Comments
Comment #1
dawehnerWhich version of views do you really use? 2.9 is the default selection so this is likely not the case.
Comment #2
Marko B commentedHad 2.9 before now its 2.12 in fact, but problem is the same.
A year ago someone posted similar problem here on #10 http://drupal.org/node/729098
Also i would mention that default language is not english. Dont know if this makes a problem for ajax.
Comment #3
Marko B commentedI am getting further into investigation of this. So i opened ajax.inc and got to debuging.
What I realize is that when using path like
"en/shops-overview" when i click on some summary value i always get first value, if it is Glossary i get "A" all the time, when using "shops-overview" i get normal letters in argument, i got to this with dpm($_REQUEST['view_args'] ); in views_ajax() function.
Also dpm($_REQUEST['view_path'] keeps getting path thats without parametars, guessing thats why its always the first letter(def. value i guess).
Comment #4
Marko B commentedMaybe this should be put into i18n module?! or i18n views module. Dont know where the problem occurs.
What i found out is that function views_ajax() { gets wrong path and argument but dont know how to trace from where does this argument and path come from, any help?!
Comment #5
JulienThomas commentedGood afternoon.
It may an already solved issue due to the dates but you can find an appropriate fix here: http://drupal.org/node/1803758
Best regards,
Julien Thomas.
Comment #6
chris matthews commentedThe Drupal 6 branch is no longer supported, please check with the D6LTS project if you need further support. For more information as to why this issue was closed, please see issue #3030347: Plan to clean process issue queue