GoDaddy Managed WordPress uses a layer of server-level caching, which probably doesn’t clear when you make changes via SFTP. Generally, such things only clear when a POST request is sent to the database (whenever something is changed via the Dashboard).
(If I recall correctly, their managed WordPress plan comes with a plugin which clears the cache, but I could be wrong.)
If you’re with GoDaddy Managed WordPress Hosting, they claim that their plans come with “Award-winning 24/7 support” and I highly recommend getting in touch with them for details on how their caching system works and how to clear it.
I looked through their Managed WordPress support docs right now, but could only find one which confirmed that they do cache everything for you, and nothing on how to clear that cache.
Thread Starter
jefftg
(@jefftg)
Thank you James, I’ve always liked their support while getting involved in this business and I will be giving them another call. The woman who suggested the hosting package gave me her email but I guess she’s too busy or something. 😉
You’re welcome, good luck with them! 🙂
I’ve just found the answer to this (was looking myself!)… there’s a button on the toolbar at the top of the Dashboard that says ‘Flush Cache’ – aha!
The “Flush Cache” button _doesn’t_ work for me. Anyone have any other ideas?
I’ll call GoDaddy and ask them.
So, here’s what they said.
Even with pressing the ‘Flush Cache’ button, it will take up to 15 minutes to see the change.
If you add this to the URL you’re viewing, you’ll see the change faster: “/?nopass=1”
Example: http://domain.com/?nopass=1
BUT, even with that, the change is taking up to 30 seconds to propagate. Not a big delay, unless you’re making dozens of changes every few minutes. I guess you shouldn’t develop directly on GoDaddy, using the WordPress Managed Hosting package.
I told them it’s a problem for me, although for a more serious developer with their own local testing server, it’s probably not a big deal. I’ll consider this before I recommend a client to them.
