Firstly, many thanks for all the effort that is going into this module. It is very very appreciated.
I have discovered a bug with drupal 6.10, Internet Explorer and xmlsitemap 6.x-1.x-dev. I'm not exactly sure what the actual message refers to. Maybe a timeout issue, not sure?
The error does not happen all the time, but more often that not does happen when i visit pages after clearing the IE cache.
I got this error about 6 times in a row, and then it went away. On another occasion, when i did finally get the page to display, some right side block content was missing or corrupt. I had the main menu here, so it main navigation difficult. I clicked on a top menu to get to another page and then on the side menu to take me back to the page, and again it was corrupt. Clearing the cache in IE, seems to fix the problem sometimes.
The error doesn't appear to happen with Firefox.
Is this a known issue? I seem to remember an earlier issue with timeouts in a version 5 release.
Once again many thanks for this module.
Peter
Comments
Comment #1
avpadernoIf the blocks on the right side were corrupted, then it's not a bug of any project modules, which don't output any blocks, nor they change any block.
Comment #2
Anonymous (not verified) commentedSounds to me that it is an environment issue and server limits are being reached. You should research your log files and if PHP or MySQL isn't logging then you need to turn that on.
Comment #3
rodenp commentedThis error happens only when i activate the XML Sitemap modules, and goes away when i inactivate it.
Why does the issue only happen with IE?
I spoke with my hosting company and they inform me that there is no load issues with my server. Also they suggested that my site looks fine and no errors are being logged.
Let me also rephrase what i wrote before, about pages being corrupt. Corrupt is not a good term, what would be more accurate is that block content on the page is not fully rendered.
Anyway, after all this i struck upon the idea of increasing the value of the php directive max_execution_time, and this seems to have resolved the problem. Looks like IE is much slower than Firefox in rendering pages. I will monitor the site over the next few days.
cheers
Peter
Comment #4
rodenp commented