Skip to main content

Pantheon release notes

Your destination for staying informed about our latest innovations and product updates.
Subscribe to RSS feed
August 21, 2024

Writing more than 100,000 files in the same directory can push the Pantheon filesystem beyond its intended design. Starting September 21, 2024, our platform will automatically reject file writes if the directory is at capacity. This precaution helps avoid catastrophic failures to ensure the site remains online and operational.

When excessive files are written into a directory due to an owner or developer error, the site may lose access to the filesystem, resulting in a critical failure. Recovery from this issue is complex and often requires manual intervention from the Pantheon Support team. The recovery process can be time-consuming, sometimes taking hours or even days, and full restoration is not always guaranteed.

However, this situation is entirely preventable. By automatically rejecting file writes that exceed the 100,000 limit, the system prevents catastrophic failures and keeps the site stable.

Currently, Pantheon provides multiple alerts to customers when the directory size reaches various tolerance levels. Learn more about these alerts and how to optimize in our documentation for highly populated directories.

Upcoming changes

Before: Users could continue writing files to a directory indefinitely, though exceeding 100,000 files limit in a single directory would reduce performance and put the site at risk of complete and irreparable volume corruption.

After: If the file count in a directory exceeds 100,000 files substantially, additional writes will be blocked to maintain system stability.

Unchanged: When a directory reaches 50,000 files due to export or backup activities, a warning will be displayed on the dashboard, and an email notification will be sent to the site owner (limited to one per seven days). The warning system functionality remains unchanged.

August 16, 2024

The 1.32.1 update is now available for the WordPress (composer managed) upstream. This release fixes a bug that was causing some WordPress core resources (CSS and JS files, as well as the default favicon image) to return a 404 error due to improper URL construction on single sites.

For more details, refer to the WordPress (Composer Managed) changelog.

Action required

To benefit from these updates and ensure your site is using the most current version, apply the update to your WordPress (composer managed) site or upstream.

Applying updates

This update should not affect files that would have been edited in site codebases. The only file changed by this update is the Pantheon-maintained filters.php file in the app/mu-plugins directory. However, if any conflicts occur, it is recommended to manually resolve them by running the following command:

For assistance with managing merge conflicts, refer to our documentation on auto-resolving via the dashboard or manually resolving via the command line.

August 15, 2024

In response to your feedback, Pantheon has temporarily paused the automated overage program. We're currently evaluating the program and the potential enhancements that will address your feedback and deliver the best possible experience to you.

To ensure there is no disruption in your site’s performance, we recommend you to:

  • Continue monitoring your site plan's traffic;
  • Ensure you're on the right site plan to maintain a secure, performant, and lightning-fast website.

The Pantheon Team will continue to:

  • Work on tooling to help you better monitor your site traffic;
  • Work with you at renewal to review historical traffic and determine the best fit plan.

We appreciate your continued partnership and patience as we enhance our policy to better serve you.

August 8, 2024

The WordPress Pantheon Advanced Page Cache v2.1.0 update is now available. This latest update resolves a bug that caused some sites to set the cache max age to 23 hours regardless of the value set in the WordPress admin as well as a minor update to identify if a filter is being used to override the cache.

What's new?

  • Enhanced debugging information: If the pantheon_cache_default_max_age filter is being used anywhere in your code, the message that displays in the dashboard that the filter is in use will now attempt to display the callable function that is hooked to the filter, providing an easier way to get insights into what is happening.

Pantheon Advanced Page Cache Max Age filtered message

Upgrade the plugin now to take advantage of these improvements and make the most of Pantheon's edge caching layer.

August 7, 2024

Pantheon has revamped the user flow for managing site plans, enhancing the overall checkout experience with streamlined processes and improved usability.

Highlights

  • Streamlined user flow: The new design simplifies the checkout process and improves plan comparisons, resulting in a smoother and more intuitive experience.
  • Adhere to accessibility standards: We've improved inclusivity and usability by meeting accessibility guidelines and enhancing navigation for all users.
  • Align with the Pantheon Design System: This ensures consistent visual design, layout, and user interface elements across our platform.

New site plan experience

For instructions on selecting your site plan, please visit our documentation.

August 6, 2024

The 1.32.0 update is now available for the WordPress (composer managed) upstream. This release is a maintenance update to resolve some inconsistencies with the upstream distribution of WordPress (composer managed). Most notably, this update includes a removal of decoupled packages that were erroneously being added to the non-decoupled upstream as well as other minor updates.

For more details, refer to the WordPress (Composer Managed) changelog.

Action required

To benefit from these updates and ensure your site is using the most current version, you need to apply the update to your WordPress (composer managed) site or upstream.

Applying updates

This update aims to resolve known issues that could lead to merge conflicts. However, conflicts may still occur, especially as we are continuing to make changes in the Early Access (EA) phase. If you run into merge conflicts with this update, you can manually resolve them by running the following command:

For assistance with managing merge conflicts, refer to our documentation on auto-resolving via the dashboard or manually resolving via the command line.

July 29, 2024

The update is now available for the WordPress (composer managed) upstream. Previously, the 1.31.0 update was released and then quickly rolled back. This release fixes issues with subdirectory multisite that were discovered following that earlier release, as well as implements the filter added to the Pantheon MU Plugin in version 1.4.5.

Highlights

  • Removes code that for handling wp-admin URLs. This code was not working as intended and testing revealed it to be unnecessary.
  • Adds a filter to disable the subdirectory multisite custom wp-content directory warning.

For more details, refer to the WordPress (Composer Managed) changelog.

Applying updates

If you run into merge conflicts with this update, you can manually resolve by running the following command:

For assistance with managing merge conflicts, refer to our documentation on auto-resolving via the dashboard or manually resolving via the command line.

Additional notes

This release should show up on your dashboard as an available update. It is advised to apply updates manually using the documentation above if there are conflicts, whether you previously applied the 1.31.0 update or not.

July 29, 2024

The Pantheon MU Plugin v1.5.0 update is now available. This latest update is included with next version of WordPress and can be installed on WordPress (composer managed) installs using composer update or by checking for updates in the dashboard.

What's new?

This update introduces a new "comptibility layer" feature designed to enhance the compatibility of your site’s plugins. Here are the key highlights:

  • Automatic compatibility fixes: The compatibility layer automatically detects many plugins listed in our WordPress Plugins and Themes with Known Issues guide. If a plugin is detected, relevant fixes are applied automatically.

  • Compatibility reports: If a plugin is detected but no fix is available, the compatibility layer generates a report for you.

  • Site health integration: Compatibility reports are added to a new section of the Site Health page, accessible under the Tools menu in your WordPress administration dashboard.

Upgrade now to take advantage of these enhancements and ensure your plugins work seamlessly with your WordPress site.