Accessibilty module breaks Javascript
| Project: | Accessibility |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | jabba_29 |
| Status: | by design |
Jump to:
I enabled your module and then put in the common.inc updates. It seemed to work temporarily, but when I went back to see the site in a normal browser the site was broken.
The error that appeared was as follows:
XML Parsing Error: not well-formed
Location: http://www.espinozaenergy.com/
Line Number 154, Column 290: Store Management
I understand that somehow this is referring to some problem with its interaction with the blockbar module, however I don't have the blockbar module block enabled in the mobile theme, only in the normal theme. I am not sure why the accessibility module is interfering with the content of the default theme, but for some reason it is. I turned off the accessibility module and the problem went away.

#1
To expand the test I turned off the blockbar module, at which point the error goes away, but the flash banner on the front of my site disappears. I turn off the accessibility module and the flash comes back. Very weird. This could be related to the way that the module affects javascript. I have a link to a javascript page in the header that is required in order to make the flash work and so does the Blockbar module. I am guessing that there is some kind of error which interferes with Javascript.
#2
To answer your first point:
The error is self explanatory. As it states many times in the documentation:
Code must be well-formed or it will break. The problem lies with HTML code.
To override this, check the "Override xHTML mime type" check-box.
Second point:
If you are serving your pages as Application/xhtml+xml then certain things don't work, such as document.write.
See this example.
To get the deprecated JavaScript to work, see the solution to point one.
Not sure why/if the accessibility module is "interfering with the content of the default theme" accept that it will still sent http header info irrelevant of whether you are using a selected theme or not.