RW Classic 9.5.0: RW is publishing obsolete versions of my files to my ISP server. Everything looks correct in the RW previews, but not on my site. I have completely cleared the site files on the server and republished and still I get obsolete versions of the files on my site. Is there a cache somewhere in RW that isn’t being cleared? This has been happening for about a week, and I haven’t changed any settings in RW as far as I can see. It can’t be the server, because I’ve completely cleared the contents of the target folder there.
Of course I could manually upload the files instead of letting RW do it, but I shouldn’t have to do that, and indeed until last week everything was working as expected. I’ve consulted with my provider’s support (Hostinger) and they agree that it must be a RW problem.
New info: I exported the site from RW, opened it, and lo and behold it exported the obsolete files as well. I looked briefly at the source code for the site and at a glance it looks right.
The problems that are still showing up are: From the home page, if you go to the page “Cello”, either by clicking the link called “Cello Music” or by clicking the Cello tab in the site menu bar, you are taken to a page on which the 2nd and 3rd stacks (Goltermann and Haydn), for which the titles should have links like the Cervetto stack, have no links, and Goltermann on the dropdown menu takes you nowhere. But if you go to the Haydn stack from the dropdown menu, and then look at the dropdown menu from there, “Goltermann” has changed to “Goltermann Danses Allemandes”, and that menu item functions properly, taking you to Goltermann page. Hope these details will help.
Your mention of “aggressive caching” led me to switch the upload speed in RW from the fastest to the slowest. I re-uploaded the whole site that way, but it didn’t help; the problems detailed above persist.
I don’t see “Goltermann”, I see “Goltermann Danses Allemandes”. I don’t have to click on the Haydn menu item in order to see that, I see “Goltermann Danses Allemandes” from the beginning and it takes me here.
So I think yes, you are dealing with aggressive caching. The upload speed in RapidWeaver’s publishing settings has nothing to do with caching.
I checked the response headers on your site and I see you are using “hcdn”, or Hostinger’s CDN. It looks like you can flush (clear/empty) their CDN cache by following their guide here:
Click on the button that says “Flush Cache”, then go back to your browser and clear your cache and history there too (clear everything). Then try testing the site again.
Also, when you are making updates to your site, it’s recommend that you put your Hostinger CDN in Development mode, to avoid these caching issues when you are trying to view your updates live. There is a section in that above help article on how you switch on development mode while editing your wesbite.
Hope that helps. If you have any other problems let me know.
Yes, indeed, that completely solved the problem, as well as pointing me toward what I can do to avoid it in future. Many thanks! I very much appreciate your prompt, knowledgeable, and helpful response, as well as the fact that you went to Hostinger and knew what to look for there. That seems to me to be above and beyond the usual level of support available at many developers.
