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?
Planet:
In r18253-dotorg I altered a feed url from httpHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. to httpsHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information., which requires the planet cache to be cleared in order for feed updates to continue. I have not deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. this change yet to planet.
r18257-dotorg alters where planet gets it’s headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes./footer from, using some new APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. endpoints, to fetch a new header/footer.
Tested & confirmed working on sandbox.
Please deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. & clear Planet cache.
Codex:
In r14081-deploy I altered the Codex header/footer curl script to pull from the same set of new API endpoints.
Tested & confirmed working on my sandbox.
Please deploy & clear the Codex cache.
Could I please get a deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. on the #codex?
RevisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. [10700:10705] have added canonical and noindex tags, better 404 titles, and most importantly removed the permissions to create new Codex pages by regular users as it’s no longer being used for that (other than by spam bots). These changes were tested.
If the cache could also be cleared to remove the global survey r16681-dotorg and the above additions from the caches that would also be great.
Can I please have the following SQL commands run against the Codex Mediawiki database?
INSERT INTO interwiki (iw_prefix, iw_url, iw_local, iw_trans) VALUES ('wporgmake', 'https://make.wordpress.org/$1', 1, 0);
INSERT INTO interwiki (iw_prefix, iw_url, iw_local, iw_trans) VALUES ('wporglearn', 'https://learn.wordpress.org/$1', 1, 0);
This is designed to allow us to create external links and redirects to handbooks, which (will) live in WordPress on make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ and learn.wordpress.org.
Seeing mixed reports over the past few days of 500 responses when visiting codex.buddypress.org.
Most informative report so far:
Others report it maybe specific to Firefox on Windows; I have not been able to reproduce.
Thoughts?
Can we get the Codex cache flushed?
This is assuming that commit r3672 to the deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. repo was done to the “live” SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. tag (0006). If not, it will need to be ported to the current branch in use and then the cache flushed.
To reduce CPU usage, I have enabled file-based caching on https://codex.wordpress.org/ In theory, when pages are edited, the cache should automatically be invalidation and logged in users should not be shown cached content. If it causes problems, please let me know. Initial reports show CPU usage has been reduced by about 75%
