edelen

You may be able to fix this by the following:

1. Deactivate and delete any installed XML sitemap-building plugin (other than the Yoast plugin).

2. Deactivate the Yoast plugin.

3. Delete existing XML sitemap files, both normal and GZIPed.

4. Reactivate the Yoast plugin.

5. Use the Yoast plugin to create the XML sitemap.

The sitemap should now create normally and the error should go away.

I initially had this same problem because the Google XML sitemaps plugin was installed. Even deactivating it did not work. Following the procedure above corrected the problem.

Broke my site and made a mess. Complained about all the files in the transfer queue no matter what I did. Disabled. Boo!

And what is with the new trailing slash nonsense on the disk caching? My pages end in .html and I don’t want to change that.

I ran my site through the W3C HTML validator and the plugin threw a ton of invalid XHTML errors. Isn’t it supposed to be XHTML valid?

Thanks.

micropat,

While I certainly appreciate your support, I’ve chosen AddThis, as it has no problems with my current configuration.

Turns out that CSprites for WordPress was the offending plugin, though I don’t know how to get around this, as using sprite graphics enables my site to load much faster.

Any ideas? That’s a popular plugin, so I can’t be the only one who has run into this.

Same problem here. Tried deleting the MIME type call, but that did nothing.

Sorry, Esmi. Wasn’t really trying to post a job. Just looking for other people’s experiences with some companies. Where would something like that go if not here?

Retried the MySQL sata file import and it worked the second time around. Turns out that the something got mangled in the database file during the first import. I never would have tracked it down, but by chance I ran a file comparison and noted the difference.

Still, this does not answer the elusive question about WordPress’s export/import feature: Does it maintain threading info when exporting?

I tried the updated Kubrick also: no go.

esmi,

Thanks for the response.

I’ve used some of the best-known WordPress 2.7+-compatible themes out there, including a few of the theme frameworks like Thematic and Buffet, and the threading won’t work. And I know those work right of the box, no tweaking needed. ??

centepines,

The problem was that the PHP.INI file did not have enough time allocated to allow the script to complete. Increasing the max timeout limit (by a factor of 10) made the difference.

Anyone?

bump?

@leip11, et al.

Disable Gears, restart Firefox, flush the cache (private data), then restart Firefox a second time.

If that doesn’t work, try starting Firefox in its Safe Mode, which doesn’t load any add-ons. If the Visual Editor loads, then the problem is due to another add-on. If not, you can try some of the other suggestions people have posted in this and other forums posts discussing this issue.