When clicking on any block with Theme Devel enabled, the vars will not load. Instead it returns an alert dialog with result code 200. Installed latest devel version available as of today and still has the issue. I disabled all other modules except for Core modules and still has this error. Attach is a copy of the alert dialog. AJAX functionality in other modules, such as Views, works fine.

CommentFileSizeAuthor
response.txt243.92 KBrory_o

Comments

rory_o’s picture

rory_o commented

Just discovered that having 'Display theme log' enabled in the Devel Themer settings pane causes this to happen.

ultimike’s picture

ultimike
Primary language English
Location Florida, USA
commented

I was not able to reproduce this issue - I started with a fresh install of Drupal 7.0, and am using the -dev version of Theme Developer as well as Devel 7.x-1.0. I am able to click on any block and have the proper info appear.

Have you tried it with Devel 1.0?

-mike

Anonymous’s picture

Anonymous (not verified) commented

I have this exact problem - whether or not 'Display theme log' is checked.

Using Devel 7x-1.0, Theme Developer 7.x-1.x-dev

I am using it to work on a subtheme of Omega (XHTML).

3rdLOF’s picture

3rdLOF commented

same here.

ansorg’s picture

ansorg commented

I run into this also. It happend after I switched to a theme that I was working on. Turned out to be an error in a template file: the HTML Source of the rendered pages started with <php instead of a proper HTML tag or <!DOCTYPE . After fixing this the AJAX call did work again. Cause for the corrupt HTML was an error in template.php. If this file contains nothing but a opening php tag <?php it needs to have one line break at the end.

So, if having this issue: look at the generated HTML of your pages or look directly at the response body of the actual AJAX call. It needs to be valid XML

One more: View Source in Firefox did not show the misplaced php characters at the beginning of the file, only View Source in IE 9 did reveal it.

kenneth.venken’s picture

kenneth.venken commented
Status: Active » Closed (works as designed)

Closing because of comment #5. If you're still getting this Ajax error and your template files are error free, feel free to reopen this issue.