- This topic has 5 replies, 3 voices, and was last updated 12 years, 1 month ago by
.
-
Posts
-
Today I moved a site from HostGator to GoDaddy (usually it's the other way around). It's also the first time I've moved a site I built with Genesis. When I installed it on GoDaddy, all kinds of errors came up, all to do with the WP Super Cache plugin that now installs with Genesis. It appears that WP Super Cache uses absolute directory paths rather than relative ones and that was causing the issue. It was looking for a public_html directory (like on HostGator). GoDaddy has no such animal.
My fix:
I deactivated the WP Super Cache plugin. Re-ran a backup with BackupBuddy and moved the new backup to the new hosting account. Worked like a charm, no errors. I have not reactivated the WP Super Cache plugin because the site seems fast enough already. I don't anticipate any problems reactivating it.
In case anyone else has future problems with BackupBuddy and genesis, I thought I'd post this. Happy coding and Happy new year!
The WP Super Cache plugin doesn't install with Genesis. That's something your host does. I've heard about so much trouble with that caching plugin lately...
You're right. I just checked the zip files for Genesis and the Magazine theme. Why would HostGator install a plugin "for me"? That seems very intrusive. Now I don't feel bad at all about getting rid of it. Honestly, I didn't notice any difference with it. And it certainly makes sense now why it didn't transfer well to GoDaddy. What other issues have you heard with this plugin? I know I had problems actually clearing the cache. It never seemed to do it when I wanted it.
HostGator was doing that to me for a while, too. Not anymore, though. I agree - I don't like that idea!
Maybe I'm thinking of a different plugin, but there was a vulnerability with one of the caching plugins. Google "w3 total cache vulnerability" to read about it. I think I heard they've resolved it, though.
You can read Frederick Towne's response to the vulnerability here. It's now fixed in the WP repo version. At some level the vulnerability is really based on an insecure setup to begin with, so if your WP installation had good security before, this would not have been a vulnerability. What Frederick did in this update is to close the vulnerability for those who have insecure setups and to better hash certain info in the unlikely event someone might gain access to your DB cache.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
- The topic ‘Backupbuddy plugin issue with Genesis’ is closed to new replies.