Per https://meta.trac.wordpress.org/ticket/6168 some codex pages have a cached header HTML + CSS which are incompatible with one another, causing a display mismatch.
While we’re migrating away from the Codex, it appears likely to remain for some time.
Can we please
1. Flush the codex cache
2. Lower the cache TTL, perhaps to a week or two, to avoid the need for future system requests?
#codex #cache #prio2
Seeing some problems with the theme previews on /extend. Seems that there’s some kind of server-side caching of files going on and updates aren’t showing in the previewer properly. Not sure when it started.
Example: Minimal Georgia is at version 1.3.
http://wp-themes.com/wp-content/themes/minimal-georgia/style.css shows version 1.2.
http://wp-themes.com/wp-content/themes/minimal-georgia/style.css?foo shows version 1.3.
Is there some good way to invalidate the cache, given that we can’t really modify the themes themselves to add versioning information to the URL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org? I suppose you could put in some kind of plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party to use output caching to look for *.css and such, but that seems haphazard and weird.
I’m really not sure that the wp-themes.com domain should be doing that kind of server-side caching anyway.