The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.?Create a ticket in the bug tracker.
In case you were looking for an blogblog(versus network, site) post about the XML Sitemaps feature project last week, worry no more. Work on the pluginPluginA 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 is progressing smoothly and steadily, we just didn’t publish an agenda post last week. That means it is time for a double update today!
Meeting Recap: March 10th & 17th
For reference, check my previous blog post from March 10th:
A lot has happened since then. Here’s the summary, not necessarily in the right order:
SimpleXML dependency We received great feedback from a variety of big hosting providers, all saying that this PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher extension is widely available and we can rely on it safely. Current status: no action needed.
Rewrite rule conflictconflictA conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved. with plugins As we realized that the new /wp-sitemap.xmlURLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org format clashes with big existing plugins, we decided to look into alternate names for both the rewrite rules as well as the query params. See GitHub issue for details. Current status: needs contributors.
Rewrite rule issues with custom providers It was reported that adding custom sitemap providers might require flushing rewrite rules. Ideally, that shouldn’t be needed. Current status: needs decision.
Last modified date (lastmod) We decided to continue with the proposed PR to remove lastmod from sitemaps (at least for now), but need to make sure there is appropriate documentation. It’s something that can always be added back if needed. Current status: has PR, needs documentation.
Query Filters Valuable feedback emerged from testing, which led to the decision to close the existing PR to make query instances filterable in favor of a simpler approach. In its place, we should make the query arguments filterable, and also add filters to short-circuit queries. Current status: needs contributors.
Please let me know in the comments if I got something wrong in this summary!