All sites on the Pressable platform have been automatically updated to WordPress 6.6, unless set to Previous (more info here).

To see a full list of features and changes, please head over to the release announcement.

17:18 UTC – Intercom functionality has been restored to normal (incident notes here), and we should now receive chats without issues.

15:04 UTC – The Intercom support platform that we use is experiencing outages affecting our chat functionality. Their team is working on resolving the issue, but there may be some delays in our responses.

If you need help, please email us at help@pressable.com for technical support and sales@pressable.com for Accounts/Billing help.

We will update this post once the issue has been resolved. Apologies for any inconvenience.

Important Dates for PHP 7.4 removal:

• June 3, 2024: PHP version 7.4 will be removed as an option for new sites on June 3, 2024. The default for all new sites will become PHP 8.1 (or another PHP 8+ version if your account default is set to 8.2 or 8.3).
• August 8, 2024: All sites on the Pressable platform that are currently running PHP version 7.4 will be automatically updated to PHP version 8.1.

We’ve put together the following resource to help with the process of updating your sites to PHP 8+: https://pressable.com/knowledgebase/php-update-faq/

If you have any questions or concerns, please contact us at help@pressable.com or start a new chat.

As of 15:00 UTC today we have removed WordPress version 6.4 from the Pressable platform and all sites still using that version have been automatically updated to WordPress 6.5.2.

Less than 0.5% of Pressable sites remained on 6.4 at the deadline.

If you encounter any issues with your site(s), please reach out to our support team.

0:00UTC: WordPress 6.5.2 has been released on the platform. This security and maintenance release features 2 bug fixes on Core, 12 bug fixes for the Block Editor, and 1 security fix. All sites currently set to 6.5 are now on 6.5.2.

All sites on the Pressable platform have been automatically updated to WordPress 6.5, unless set to Previous (more info here).

To see a full list of features and changes, please head over to the release announcement.

13:30 UTC – Pressable was made aware of phishing attempts to access users’ MyPressable.com Dashboard information.

We’ve contacted Cloudflare and Google and have sent out an email (titled: Warning: MyPressable Phishing Attempts) to all customers about this.

We have also published an MPCP News Center Alert (titled Warning: MyPressable Phishing Attempts) and Knowledgebase article for guidance.

Please contact support if you have questions.

13:05 UTC – The issue is now resolved. Related to new protections we added at the platform level that were overprotecting in a few situations.

11:00 UTC – Some Pressable sites may be experiencing intermittent 429 Too Many Requests errors. We are aware of the issue and our platform team is investigating.

20:26 UTC – Intercom functionality has been restored to normal (incident notes here), and we should now receive chats without issues.

19:50 UTC – The Intercom support platform that we use is experiencing outages affecting our chat functionality. Their team is working on resolving the issue, but there may be some delays in our responses.

If you need help, please email us at help@pressable.com for technical support and sales@pressable.com for Accounts/Billing help.

We will update this post once the issue has been resolved. Apologies for any inconvenience.

21:30 UTC – Thursday, February 22nd
The MyPresseable Control Panel job queue and general site administration are back to normal. Issues resolved.

19:55 UTC – Thursday, February 22nd
We’re observing significant improvements in task queues and request responses. Some delays may still be present but services are largely back to normal operation.

18:19 UTC – Thursday, February 22nd
We are currently experiencing issues with the MyPressable Control Panel tasks runner. This may cause delays for certain site-related jobs including the provisioning of new domain names, backup download generation, and other tasks.

Our team is aware and actively working on this. Additionally, we are taking actions to ensure that this issue does not occur again in the future.

We will update this post once the issue has been resolved.