-
Important PHP Updates: 8.5 Now Available, 8.4 Becoming Default, 8.1 Removal Reminder
Continue reading: Important PHP Updates: 8.5 Now Available, 8.4 Becoming Default, 8.1 Removal ReminderWP Cloud follows the PHP project’s supported-versions life cycle. Each release branch is supported for two years from its initial stable release, plus an additional two years for critical security fixes only. Note that for PHP versions >8.1, WP Cloud has adopted a modified schedule. Each year, hosts should work with their customers to upgrade…
-
End-of-Year 2025 Deploy Freezes
Continue reading: End-of-Year 2025 Deploy FreezesThe WP Cloud platform will hold deploys on the following schedule to facilitate smooth operations for our eCommerce and news sites. We do this to provide increased platform stability for our clients’ publishers and stores on specific high-traffic event days. This schedule may be altered and/or amended for security and breaking events as needed. U.S.…
-
phpMyAdmin 5.2.3
Continue reading: phpMyAdmin 5.2.3phpMyAdmin, accessible via the site-phpmyadmin endpoint, has been updated to 5.2.3.
-

Supercharge Your WordPress Sites: WP Cloud Unveils PHP Memory Limit Pricing
Continue reading: Supercharge Your WordPress Sites: WP Cloud Unveils PHP Memory Limit PricingWe’re excited to announce a significant enhancement to the WP Cloud platform: configurable RAM per PHP Worker with our new PHP memory limit-based pricing model. This feature empowers our partners to fine-tune performance for memory-intensive WordPress sites without compromising reliability. Understanding PHP Memory Limits The PHP memory limit setting controls how much memory a single…
-
WP Cloud Platform Update Schedule
Continue reading: WP Cloud Platform Update ScheduleIn addition to our platform documentation and announcement posts, we’ve launched a new resource to help you plan for upcoming changes on WP Cloud: the Platform Update Schedule. This page gives hosting partners a single place to see planned changes to PHP and WordPress versions on the platform, with dates you can use for planning.…
-
Images Now Support Site Accelerator Parameters
Continue reading: Images Now Support Site Accelerator ParametersWP Cloud’s Content Delivery Network (CDN) was built to deliver images and static files fast. As of August 12th, we now support Site Accelerator API parameters as part of image URLs, allowing sites hosted on WP Cloud to make use of WordPress.com’s Site Accelerator service to crop, resize, filter and modify image assets without creating…
-
WordPress 6.8.2
Continue reading: WordPress 6.8.2WordPress 6.8.2, a short-cycle maintenance release, was deployed to the WP Cloud platform shortly after the core release today. For a full list of bug fixes, please refer to the release candidate announcement.
-
Restore a Site From Backups
Continue reading: Restore a Site From BackupsWhen creating a new site on the WP Cloud platform, clients can now set the new restore_from parameter to a pair of backup IDs (filesystem and database). This will provision a new empty site and then restore the provided backups to it. For example: curl -H “Auth: API_AUTH_TOKEN” -X POST \ –data “domain_name=restored-site.example.org” \ –data…
-
Egress Firewall Rules
Continue reading: Egress Firewall RulesA new set of API endpoints is now available for customizing the outbound firewall rules for sites on the WP Cloud platform. Clients can now allow individual sites to access external databases, SSH/SFTP, and other services that were previously blocked. To add a firewall rule: curl -H ‘Auth: API_AUTH_TOKEN’ -X POST \ –data “direction=egress” \…
-
Control HSTS IncludeSubDomains and Preload with the WP Cloud API
Continue reading: Control HSTS IncludeSubDomains and Preload with the WP Cloud APIWhy HSTS matters Enabled by default on WP Cloud, HTTP Strict Transport Security (HSTS) can instruct browsers to load a domain over HTTPS. Adding the includeSubDomains and preload directives: What’s new While strict-transport-security is enabled on all domains using WP Cloud by default, the WP Cloud Atomic API recently added two endpoints to independently control the includeSubDomains and preload…