Enable Byte-Range Requests

Request from Chloé Bringmann:

I ran into an error when trying to upload the RSS feedRSS Feed RSS is an acronym for Real Simple Syndication which is a type of web feed which allows users to access updates to online content in a standardized, computer-readable format. This is the feed. on Apple for the new WP Briefing podcast. Would you be able to assist with this?I submitted the WP Briefing podcast to Apple and got the following error:

Can’t submit your feed. Your episodes are hosted on a server which does not support byte-range requests. Enable byte-range requests.

Is this something we can do on w.org, or would this be something where we want to utilize a CDN to serve the files instead?

#prio2

Increase upload size maximum to 100MB on w.org

The current server configuration seems to have a max upload file size of 50MB. I assume this is in the PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. configuration, although it may be limited by the webserver settings as well.

This is currently limited to 10MB on the main w.org network, and 50MB on the make network. These settings are through WordPress itself, in the Network Settings pages.

We would like that to be bumped to 100MB globally. The sites would still be limited to 10 and 50, respectively, with one exception. The https://wordpress.org/news/ site will need larger upload capabilities for the podcast files. Code has been added to allow up to 100MB uploads for the /news site only, but it is currently limited to 50MB by the server.

So, the request is to bump the max upload size on w.org to 100MB.

#prio2

Can I get a deploy…

Can I get a deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. of the codex files?

I made a change to the DotorgRedirect plugin for the codex, to whitelist “wordpress.org” as a valid place for it to redirect to, per request of the docs team: https://wordpress.slack.com/archives/C02RP4WU5/p1543972984189700

So, just need to get that one line change onto the codex.

cc @drewapicture

#prio3

The SSL certificate for “wp.org”…

The SSLSSL Secure Socket Layer - Encryption from the server to the browser and back. Prevents prying eyes from seeing what you are sending between your browser and the server. certificate for “wp.org” is set to be the same one as the cert for “w.org”. Presumably this is because they’re both pointing to the same place which is doing the redirection, but the incorrect domain on the certificate causes an error.

So, wp.org needs a new SSL certificate set up on it.

#prio3

Me (@otto42) and Scott (@coffee2code)…

Me (@otto42) and Scott (@coffee2code) need ssh access to wordpressfoundation.org, if we don’t have such access already. This is so that we can change around the payment systems for donations, as requested by Matt.

Theme previewer missing a theme.

web1 appears to be missing the “tempo” theme for the theme previewer. I tried the normal commands to get it to update as well as reapproving the theme manually, to no effect. Need somebody to take a look at it, see if something is wrong with that directory.

It’ll be in /extend/theme-preview/wp-content/themes/tempo. Should have version 0.0.33 in there like the other webs do.

#prio2

One of the servers seems…

One of the servers seems to not be updating for planet.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/. Every once in a while you can refresh the site and will get a page from December. Like one of the webservers isn’t updating properly or otherwise not running the process.

I have no visibility into the production servers, so can somebody take a look and see if one of them is “stuck” somehow?

Reference https meta trac wordpress org ticket 684…

Reference: https://meta.trac.wordpress.org/ticket/684

SSL certificate for https://plugins-svn.bbpress.org/ is incorrect, it is using a cert from *.automattic.com. Being that a cert exists for *.bbpress.org, I think this needs to be swapped around a bit.

The SSL certificate is broken on the wp…

The SSLSSL Secure Socket Layer - Encryption from the server to the browser and back. Prevents prying eyes from seeing what you are sending between your browser and the server. certificate is broken on the wp-themes.com domain, or rather, it is using the certificate for *.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/. This causes issues with the theme previewer for assorted reasons.

Any chance of getting that certificate corrected?

Related: https://meta.trac.wordpress.org/ticket/483

Something appears to be wrong with the plugin…

Something appears to be wrong with the 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 update process, at least for one plugin:

https://wordpress.org/plugins/post-customizer/

Page was not building at first, a manual update on my sandbox built the page, but now the download links are 404’ing. This suggests the update process isn’t running or isn’t running for this plugin.

Can this be run on all prod webs to see if there are any issues?

php /home/wporg/public_html/plugins/bb-load.php update post-customizer