The ‘problem’ (if you want to call it that) is not only isolated to RapidWeaver - I’ve seen the same thing happening in concrete5 which also uses a similar system of cache-busting links. Then right-click the refresh button and select Hard Reload from the menu. If you do want to do a ‘hard refresh’ of your website cache in Chrome (without effecting other websites you browse to) open the web inspector in Chrome. If you are using CloudFlare, login to your CloudFlare account and clear the cache there. Then do a full republish of the website and see if that makes any difference. So you could try disabling ‘cache busting links’ in your site settings. Therefore, try installing the Beta version if Chrome won’t install on Windows 10 or 11. In case you’re unfamiliar, these are experimental versions of Chrome that usually include upcoming features and bug fixes. Then, check if Chrome can install the pending update successfully. If you cannot install Google Chrome on Windows 10, you might be able to fix this issue simply by switching to a Beta or Canary version. Reopen Google Chrome, click the three-dot menu icon in the top right corner, and select Help > About Google Chrome. And yes, it could effect what website visitors see, when they arrive at your website. In the Processes tab, right-click on Google Chrome and select the End task option. That can give the impression of newly published pages sometimes looking broken - the content will be correct but other styling or functionality might misbehave. If you have ‘cache busting links’ enabled in RW7, then Chrome will respect this and will not purge its cache of CSS or JS files when it comes back to view one or more of your webpages.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |