Environment: D6.10, Views 2.3 and then Views 2.4, firefox 3, php 4.4.7
Issue: I turned on clean urls. I cleared cache. I went to edit a block view. When I click on any of the options (e.g., node: title), I get an error popup (see screen shot attached). I disable clean urls and it works fine. Then, I tried enabling clean urls and creating a new view (thinking maybe the view created originally with clean urls disabled was part of the problem). Nope. Still get the same issue.
History: I just upgraded from D4 where I never turned on clean urls. I have used views 2.1 on another D6 site but the clean urls was on from the start and did not have this issue. I assume there is some type of legacy data issue floating around in my db but I don't know how to clear it. Help!
| Comment | File | Size | Author |
|---|---|---|---|
| views_admin_4-8-09.jpg | 76.45 KB | idcm |
Comments
Comment #1
idcm commentedMore details.
I just ran a test on my new D6 test site (versus the upgraded site I reference above). No problem occurred. I really need my upgraded site to work so any ideas on how to resolve would be appreciated ASAP.
thanks
Cindy
Comment #2
dave reidTry navigating to http://yoursite/admin/build/views/ajax/display/WebD2/block_1/block_description and check what the output is.
Comment #3
merlinofchaos commentedAlso try looking in the php error log and seeing if there is a php error causing a problem.
Comment #4
idcm commentedI went in, turned clean urls back on, went to the address you said and got the following.
{ "display": "\x3cform action=\"/admin/build/views/ajax/display/WebD2/block_1/block_description\" accept-charset=\"UTF-8\" method=\"post\" id=\"views-ui-edit-display-form\"\x3e\n\x3cdiv\x3e\x3cdiv class=\"form-item\" id=\"edit-block-description-wrapper\"\x3e\n \x3cinput type=\"text\" maxlength=\"128\" name=\"block_description\" id=\"edit-block-description\" size=\"60\" value=\"\" class=\"form-text\" /\x3e\n \x3cdiv class=\"description\"\x3eThis will appear as the name of this block in administer \x3e\x3e site building \x3e\x3e blocks.\x3c/div\x3e\n\x3c/div\x3e\n\x3cdiv class=\"clear-block\"\x3e\x3cdiv class=\"form-buttons\"\x3e\x3cinput type=\"submit\" name=\"op\" id=\"edit-submit\" value=\"Update\" class=\"form-submit\" /\x3e\n\x3cinput type=\"submit\" name=\"op\" id=\"edit-cancel\" value=\"Cancel\" class=\"form-submit\" /\x3e\n\x3c/div\x3e\x3c/div\x3e\x3cinput type=\"hidden\" name=\"form_build_id\" id=\"form-b132c791bef80301419827ffa2d0c07f\" value=\"form-b132c791bef80301419827ffa2d0c07f\" /\x3e\n\x3cinput type=\"hidden\" name=\"form_token\" id=\"edit-views-ui-edit-display-form-form-token\" value=\"932b018cc6fc0b235039fed8afa47179\" /\x3e\n\x3cinput type=\"hidden\" name=\"form_id\" id=\"edit-views-ui-edit-display-form\" value=\"views_ui_edit_display_form\" /\x3e\n\n\x3c/div\x3e\x3c/form\x3e\n", "title": "Block: Block admin description", "url": "http://cindymccourt.com/admin/build/views/ajax/display/WebD2/block_1/blo...", "js": null, "hilite": ".views-item-block-1-block-description" }
Comment #5
idcm commentedNothing shows in the "recent log entries"
Comment #6
idcm commentedI don't know why it is working now but I have a hunch. The following is my guess and maybe you smart programmers will understand.
I was using the amadou them for both front and back end. Every time I switched to clean urls, views had the issue I described. Long story short, I changed my admin theme to garland from amadou. I turned on the clean urls. I test the views function again - it worked.
Amadou doesn't have a test. I am wondering if the test sets some variable in the drupal db that was missing before. In other words, clean urls was only partially enabled and views needed the test to run first.
Anyway, that's all I can guess.
Comment #7
esmerel commentedComment #8
dawehnerEnable php logs on your php ini. There should be errors, which are critical to solve this issue
Comment #9
idcm commentedI have a vague recollection of this issue but am experiencing similar issues with a new 6.17 install. They are intermittent but I have my logs on. I will catch the next occurrence and post the results.
Comment #10
esmerel commentedFor now, I'm going to close this since there's been no updates in more than 30 days. This is definitely one of those cases where I can reasonably see a new issue referring back to this one if the problem is repeatable in later versions.
Comment #11
idcm commentedI see I forgot to report back. I am so sorry. If memory serves, the issue was a mod_security issue on the server. the server guys tweaked the settings and I am fine now.