Deploy & Clear caches for: Planet & Codex

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.

#prio2 #codex #planet #deploy

Disable Themes Trac browser for root index

As we do for Plugins Trac, can we redirect `https://themes.trac.wordpress.org/browser/?$` to wordpress.org/themes/ ?

Due to the number of themes, TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/./nginxNGINX NGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers. https://www.nginx.com/. 502’s (Apparently it previous crashed trac, unsure what it’s doing now other than timing out) and the upstream trac issue hasn’t been touched in years.

Diff, as per plugins.trac.wordpress.org.

--- trac.wordpress.org.conf  (revision xxxxxxx)
+++ trac.wordpress.org.conf (working copy)
@@ -341,0 +342,5 @@ server_name themes.trac.wordpress.org;
+   # Too many themes, page doesn't load.  Instead just crashes trac
+   location ~ ^/browser/?$ {
+       return 302 https://wordpress.org/themes/;
+   }
+

ref: https://meta.trac.wordpress.org/ticket/4861

#prio3

Remove user agent blocking for Firefox/100 & Chrome/100.0

Currently there’s some User-agent based anti-spam blocks (Primarily on tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. I think) that is blocking requests from Firefox version 100. I can’t see anything blocking Chrome 100, but that will also need to be checked at the same time.

% curl -Is https://core.trac.wordpress.org/ --user-agent 'Mozilla/5.0 (X11; Linux x86_64; rv:100.0) Gecko/20100101 Firefox/100.0' | grep ^HTTP
HTTP/2 403

I assume we have something looking for Firefox/1 as a UA blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. for ancient-versions of Firefox.

Originally reported by @mte90 – https://wordpress.slack.com/archives/C0C89GD35/p1635254249000700

#prio1

Redirects for JSON Schemas

We are working on providing schemas to developers for block.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. and theme.json files. Adding the schema to the top of a JSON file can integrate with code editors to provide tooltips, autocomplete, and validation; making development easier.

Here’s a GIF showing how it works:

block-json-schema2

Right now we are using the SchemaStore as common place to gather schemas, but we want to move to our repository that will allow better versioning and control. We created a directory on GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ to contain the schemas and they can be accessed at:
https://github.com/WordPress/gutenberg/tree/trunk/schemas/json

This allows for adding schemas using the awkward URLs:

https://raw.githubusercontent.com/WordPress/gutenberg/trunk/schemas/json/block.json
https://raw.githubusercontent.com/WordPress/gutenberg/trunk/schemas/json/theme.json

But we can make them less awkward by taking a page out of Microsoft’s book and use redirects. For Windows Terminal schema, Microsoft uses: https://aka.ms/terminal-profiles-schema that redirects to a GitHub url.

So, the ask is to get a similar redirect setup, using either wp.org or w.org domains.

Something like:

https://wp.org/schemas/block.json  => https://raw.githubusercontent.com/WordPress/gutenberg/trunk/schemas/json/block.json

https://wp.org/schemas/theme.json  => https://raw.githubusercontent.com/WordPress/gutenberg/trunk/schemas/json/theme.json

And then in the future when we want to version the schema we could add the version to the redirect and point to the tag/branch in the source code related to that release

https://wp.org/schemas/wp5.9/block.json
https://wp.org/schemas/wp5.9/theme.json

Questions? Thoughts?

Google Search Console domain access + Postmaster tools

A few of us have access to Google Webmaster/Search tools for https://wordpress.org/ and https://wordpress.org/, but we do not have access for the entire wordpress.org domain which would grant us access to https?://*.wordpress.org/ (ie. what we have + subdomains).

Additionally, The marketing team would like access to Postmaster tools for the email deliverability data, which also requires domain verification.

I can see that there’s two existing Google domain authorisations (dig +short TXT wordpress.org) but I’ve been unable to locate whose Google accounts have access to that when asking around.

Can I please have access granted to the domain-level Search Tools / Postmaster tools so that I can provide access to those who need it?

In the event that systems do not have domain-level access, here’s some instructions to get it:
1. Grant my a8c account verification access and I’ll deal giving those who need it; add wordpress.org TXT google-site-verification=RLa_vaBBembqlBHv2iGePxw7Cw2nQhbYjKLX7HWpSks (I’ll add systems a8c account for future uses. If option 2 is taken, I’ll remove this auth attempt from my account)
or
2. Visit Postmaster tools, Add a domain, get the TXT record and add it. Grant my a8c google account access + plus that of @eidolonnight to Postmaster + Search Console (Full access please). Verifying the domain for postmaster tools will also grant search console verification.

#prio1 #email #google

Theme Directory changes

The WordPress.org theme directory will now be accepting direct SVN access for theme updates. This means there’s two changes we need made on the systems side.

Everything else will remain the same for now, we’ll continue to accept ZIP uploads and apply the same theme checks on import. Initial theme submissions will continue to be ZIP-upload only, only updates will be available through 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/..

Dynamic SVN Auth file

The SVN auth file will need updated, similar to plugins:

  • Create a copy of update-wp-pluginPlugin 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-auth.sh & setup the cron task for it.
  • SVN Auth file is available at https://wordpress.org/themes/wp-json/themes/v1/svn-auth
  • Use Authorization: BEARER $THEME_SVN_AUTH_BEARER_TOKEN as defined in secrets.php

The file is currently minimal and only outputting a few lines, but will be ~25k lines when it’s opened to theme authors.
This can be tested by editing wp-content/plugins/theme-directory/rest-api/class-internal.php to either bypass auth temporarily or to output all authorship rules.

pre-commit ruleset for SVN commits

In order to prevent having to rebuild a bunch of things that are reliant upon themes.svn, we’d like to add some pre-commit rules to force commits to be in a specified format, rather than mostly free-form as plugins.svn is.

Rules:

  • Are always in a /Theme-Slug/1.2.3/ folder
  • Is a newer version than currently live
  • Does not alter existing versions (treat them as tags)
  • The /1.2.3/ folder matches the style.css Version:1.2.3 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. value

I’ve put together some rules that work in my testing, but I’m unsure if there’s a different way you’d like to implement it. These were tested against my own SVN server mimicking svn.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/ configuration.

#prio1, #svn, #themes

Create Openverse email address for Helpscout

The Openverse team wants an address openverse@wordpress.org to use with Helpscout.

I’ve created a mailbox within Helpscout for it. It seems that their connection setup has changed, and now in order to connect an email address on an external domain they send a verification code to that external email address.

I guess we can make this work by setting up a forward from openverse@wordpress.org to openverse@wordpress.helpscoutapp.com. Presumably that will let me see the verification code and complete the setup (though I can’t see what the next steps require until I get past the confirmation code). I’m open to suggestions for better ways to do it.

#prio1 #email

Delete 2.9.5 tag at buddypress.svn.wordpress.org

A BuddyPress committer made a mistake in the 2.9.5 tag while back-porting a fix & performing a bunch of minor releases. I do not have the power to bypass the pre-commit hook:

Committing transaction...
svn: E165001: Commit failed (details follow):
svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:
Cannot commit to a tag.

If possible, may I please have this tag deleted: https://buddypress.svn.wordpress.org/tags/2.9.5

Bonus ask, may I please have the power to commit to tags on the BuddyPress & bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org. repositories (or have the restriction removed completely?) It happens rarely, but it’s an easy clean-up for me when it does.

IIRC, the original reason we’d added that hook many years ago was because we were using those tags for deployment to dotorg, but we switched to deployingDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. from plugins.svn when we introduced build processes.

#prio2

Email deliverability time problems

There’s reports that 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/ emails are taking hours to arrive. It appears to affect account creation confirmation emails, tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. emails, and even the WordPress.org mailing list archives (wp-trac for example).

Looking at the time between Account registration & email confirmation for signups, about 24hrs ago (2021-08-01 15:00:00 UTC) the average time between signup and confirmation increased from 6hrs.

I sent myself some test emails from my sandbox 2 hours ago (to gmail) and still haven’t received either of them.

SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. references:
https://wordpress.slack.com/archives/C02QB8GMM/p1627919021012400
https://wordpress.slack.com/archives/C02QB8GMM/p1627927041015000

#email #prio1

Codex DB Password update

After the recent DB password rotate, as mentioned in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. the codex still hasn’t been updated.

See https://codex.wordpress.org/index.php?title=Special:UserLogin&returnto=Main+Page and for a non-cached error message: https://codex.wordpress.org/api.php?action=query&meta=siteinfo&siprop=general

#prio1