6.4.1 is a maintenance release that fixes a few bugs, outlined here.
UPDATE: October 12th 17:30pm (UTC)
The Intercom platform issue has been resolved and support chat is back up.
October 12th 16:10pm (UTC)
The platform that we use for providing support (Intercom) is currently experiencing issues (status here). During this time you may not be able to contact our support team via live chat.
You can still email us at firstname.lastname@example.org and we will reply as quickly as we can.
We apologize for the trouble caused by this.
March 22nd, 2023
A network provider for the MyPressable Control Panel began experiencing issues around 18:35 UTC on March 22nd, 2023. This affected access to my.pressable.com.
Network connectivity was restored at 18:46 UTC and my.pressable.com is accessible again.
Our hosting servers, and end-user sites, were not affected by this issue.
15:00 UTC – March 8th, 2023
The maintenance is complete.
21:40 UTC – March 7th, 2023
The MyPressable Control Panel is undergoing maintenance.
This may lead to temporary 502 error messages when accessing certain pages across https://my.pressable.com. These errors should resolve themselves upon refreshing or reloading the affected page.
End user sites, the Pressable API, and other Pressable services are unaffected.
If you encounter issues with your site(s) or account, please reach out to our support team.
UPDATE – 15:56 UTC: SFTP & SSH connection issues have been resolved.
Our systems team is currently investigating and working with the Jetpack team regarding issues with creating and assigning Jetpack licenses to newly created sites.
This appears to have affected all sites created since 2022-11-03 at 15:16 UTC time.
We will update this post once the issue has been resolved.
Thank you for your patience.
UPDATE 2022-11-04 at 19:07 UTC – The issue has been resolved and all sites affected have been successfully assigned Jetpack licenses.
UPDATE: The situation below should be resolved on Pressable’s end.
We have been made aware of an issue that may affect sites updating to WooCommerce 6.8.1.
If this occurs, you may see display issues on your site’s home, shop or cart pages or they may display the standard WordPress “Critical Error” page.
You may also see errors such as the following in the PHP Error logs for your site which reference the previous 6.8.0 version of the plugin:
PHP Fatal error: require(): Failed opening required '/wordpress/plugins/woocommerce/6.8.0/templates/content-product.php' (include_path='/:.') in /wordpress/core/6.0.1/wp-includes/template.php on line 772
We have found that clearing the Object Cache for the affected site will resolve the issue.
The WooCommerce team have been made aware of this issue.
If you have any questions about this, or if the error persists after clearing your Object Cache, please reach out to our support team via chat or e-mail (email@example.com).
0300 UTC – UPDATE: Network services have been restored to the data center and WordPress.org services are back online.
0043 UTC – All WordPress.org services are currently offline. They are working to determine the scope of the problem and how to resolve it.
Please follow the link here for more information and up to date status: https://status.wordpress.org/
UPDATE 17:33 UTC – The Mailgun team have resolved the issue they were having and collaborator creation functionality is now working. If you encounter any further problems, please let us know.
14:30 UTC – We are aware of an issue preventing the addition of Collaborators to sites through the My Pressable Control Panel.
This is being caused by an outage that Mailgun is currently experiencing.
Mailgun are implementing a fix for this at the moment and we will update this post once the issue is resolved or if there are any further developments.
In the meantime, if you require any assistance relating to this issue, please get in touch through chat or e-mail – firstname.lastname@example.org.
We apologise for any inconvenience caused by this and thank you for your understanding.