Desi Matlock

So… WordFence? Doing that already. Hoping to continue to have a second line of defense… Anyone have any other alternatives they’ve started using? How about at the server level? (I have numerous clients with an aversion to JetPack for site speed reasons.)

If you’ll notice, the document root is defined TWICE, I’m guessing someone goofed in the ready backup plugin code and now the plugin inserts the document root TWICE.

I have the exact same problem (document root repeats in this exact error message) across all 12 sites I’ve installed Ready Backup to. Can’t get it to back up to ANYTHING but DropBox…

How to fix would be a more useful response. And no, updating did not repair the problem. Deleting, and then reinstalling from a fresh copy off the wordpress plugin repository also did NOT repair the problem. It’s an unfixed bug, guys.

Since then, I’ve verified it’s not plugin compatibility issues.

Same issue. I have also sent an email via the provided contact form.

Yes.

Yes, agreed. Amazingly unprofessional. I am a paying customer and they do not respond!

Where can I get real help from other users? I inherited two other webmaster’s wp e-commerce installs, and upgraded them to GoldCart for merchant gateway purposes. Big mistake.

And these clients don’t want to change carts…

Any sort of banding together of those of us who’ve solved our own issues? Places where solutions to some of these hacks are found?

In addition to that, tax applies incorrectly, and Google Checkout cannot be gotten working no matter what settings are applied.

Not Working for me either.

Thanks, Yoast. I’ll try SEO Data Transporter and making sure all instances are at latest build and get back here with more data.

Anyone else seeing the file when they view source or open it in a text editor rather than through the browser?

Actually – if you view the source on the empty page that shows up, I’ll bet the sitemap’s there. I “found” the sitemap when I opened up the blank sitemap, and viewed source. It was all there, as pretty as can be. I think it’s an issue with the XSL file…

Why not just upgrade to 3.x?

Yup. Me neither. But not in every case. Just in three cases.

Disabling Twitter tools worked for me – on three separate client installs on unique servers.

I would really appreciate someone helping me with this. I’ve tried to understand it and can’t find another post that covers it. If I’m wrong, please let me know.