{"id":17133685,"date":"2023-10-18T16:29:24","date_gmt":"2023-10-18T16:29:24","guid":{"rendered":"https:\/\/wordpress.org\/support\/topic\/perfect-solution-260\/"},"modified":"2023-10-18T16:29:24","modified_gmt":"2023-10-18T16:29:24","slug":"perfect-solution-260","status":"publish","type":"topic","link":"https:\/\/wordpress.org\/support\/topic\/perfect-solution-260\/","title":{"rendered":"Perfect solution"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Especially after the update to allow a custom version string, either through a GUI setting or programmatic hook, this plugin fixes a persistent problem when doing site updates. Too often we have browsers holding onto cached CSS\/etc after doing an update. We want them cached, but wanted a way to invalidate those when changes are made. This now allows us to use the version as a &#8220;point in time&#8221; refresh point. Caching will happen until we tell it a new version is installed. It works perfect for us. Thanks so much to Mwale for sharing this freely!<\/p>\n","protected":false},"template":"","class_list":["post-17133685","topic","type-topic","status-publish","hentry"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/17133685","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic"}],"about":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/types\/topic"}],"version-history":[{"count":0,"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/17133685\/revisions"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/media?parent=17133685"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}