After searching the site for anything I could find, I found that the specific browser used can affect how pages load and are displayed, so I tried using Firefox instead of the normal IE.
This resulted in all pages loading well in Firefox, but many pages still won't load properly in IE.
This is a test installation, with absolutely ZERO content, a few extra modules installed, and on a server where other scripts are working fine in both IE & FF.
I can see absolutely nothing in the source code for the affected pages that would account for the problems. Is there something in the PHP code that makes IE users wait for pages? I saw a module called "IE Destroyer" - does this mean that Drupal refuses to work with 85% of the internet community?
I really love the flexibility and features that Drupal has to offer, but if 85% of my audience will have these problems, I can't use it.
What's the solution here?
Thanks.
Comments
Most browser issues are
Most browser issues are related to CSS or Javascript quirks in IE6 and some other browsers. The core release of Drupal is compatible with all browsers to the best of my knowledge. When developing a CSS theme, it can be a nightmare for the developer to ensure cross browser compatibility and IE6 gets the worse wrap for standards compliance.
The IE Destroyer module, is a simply a module for those who have had enough of ensuring compatibility with a browser they deem to be inferior, regardless of it's market share. I believe it simply detects the browser you are using and if it is IE, it recommends that you download FF. An extension of the Spread Firefox mission.
If you are sure that your theme is cross browser compliant, then this module is not needed.
It is not likely that the issues you are having will be related to the PHP, as PHP is a server side script - Only the generated output is made available to the browser.
Your issues sounds like something that is more to do with content caching - this is controlled by your server, your Drupal install, or your ISP.
So how can I fix the problem?
None of my other scripts have the same issue, so content caching by server or ISP doesn't seem to make any sense. I don't know how Drupal would be doing it's content caching, but it seems to treat IE and FF differently for one reason or another.
For reference, I'm using the bluemarine theme that came with Drupal itself.
How do I get the same performance for my IE users that is currently being experienced in FF?
- Alan Tutt
http://www.PowerKeysPub.com
- Alan Tutt
Exceptional Personal Development for Exceptional People
http://www.PowerKeysPub.com
Seems to be connected to the "checklist" module
Earlier today, I installed a fresh copy of Drupal and noticed that the speed issues were not a problem. This led me to test which of the added modules may be at fault, so I deactivated all of my added modules on the main installation (where I did have the problem) and found that the speed issue had disappeared.
From there, I added a couple of module at a time, checking for the speed issue at each step. When I found the problem, I deactivated first one, then the other module to see which one caused the issue. When I reached the "checklist" module, activating it slowed down certain pages (such as create page and access control).
Just to make sure it wasn't the number of modules activated, I added a few others and found that the speed issue did not return, even with all other modules activated, so at this point, it appears that there is something about the "checklist" module that is causing the problem with IE.
What's confusing is that the many of the pages that are slowed down in IE don't seem to access this module at all, except for the access control page and the modules page.
Does anyone have any idea why the checklist module would create this situation?
- Alan Tutt
http://www.PowerKeysPub.com
- Alan Tutt
Exceptional Personal Development for Exceptional People
http://www.PowerKeysPub.com