Your comments

Hi Ryan, thank you for letting us know about this bug.

Where did you find the credit card input that isn't working as expected? Is it the one found through the Premium Addons section associated with your Connect key?

What browser where you using when you noticed the malfunctioning input? Would it be possible for you to try using a different to access that feature and see if you encounter the same behavior?

I tested that input field using both Chrome and Firefox and so far have been unable to replicate the issue you described, but hopefully we will be able to figure out how to replicate this issue and make any necessary corrections.

Thank you again for reporting this issue and please let us know if you have any additional questions for us while we get this sorted out.

Hi Nocturnaliss, I am happy to hear that you were able to find the controls to manage your Saved Blocks!

I created a feature request ticket with our development team to review this feature idea and hopefully we will be  able to get it added to our roadmap for new Post and Page Builder features.

Thank you for helping us improve our products and please let us know if you have any other ideas for us!

Thank you for contacting us! Our team is currently tracking this particular issue in the GitHub repository for W3 Total Cache and I hope that we will be able to make the change in an upcoming update. Thank you for helping us improve our products and please let us know if you have any other feature ideas or bugs to report!

Thank you for sending us your feature idea Gustavo!

We did not previously have any plans to add Azure Blob Storage as a remote storage option for Total Upkeep Premium, but I have created a feature request with our development team on your behalf to consider implementing this feature in a future update for Total Upkeep. If you are interested, you can subscribe directly to that GitHub issue thread to get updates on the progress of this feature as soon as they occur.

Thank you for helping us improve our products and please let us know if you ever have any other ideas for us!

Hi Marco!

It doesn't appear that you are missing anything, the filter included in your message looks like it should work and I am uncertain why it is not rendering properly on your website.


One thing I suggest trying is changing how the script is added to your website configuration. Instead of adding the code directly to the functions.php file, try installing the Code Snippets plugin and create a snippet with that plugin to add the filter to your website. A major advantage of using the plugin instead of modifying the theme files directly is that it will allow your customization to persist through any future theme updates, otherwise you will need to add your code again each time the theme updates.

Could you also send us a link to a page on your website where we can see the rendering issues with the double hyphens? It is possible that looking at the page source code might give us some insight on why the wptexturize filter is not working as expected.

Thank you for your understanding Marco and please let us know if you have any additional questions for us along the way!

Thank you for contacting us. I completely understand the frustrations with using the current iteration of Total Upkeep and I am sorry that our team has not  yet been able to find a more reasonable fix for getting backups to work as expected within DreamHost's FastCGI configuration. I hope that you are able to find a backup solution that provides you with the usability that you need and if you ever have any questions for us please do not hesitate to ask!

Thank you for letting us know about this bug! Our team will begin investigating this issue and hopefully we will be able to get a fix released in an upcoming update for our plugins. Please let us know if you have any other suggestions about how we can improve our plugins!

Thank you for sending us your feature request! We currently have a GitHub issue in with our development team to consider adding this functionality in a future release, and if you would like, you can subscribe to that thread directly to get updates on the progress of this feature as soon as they occur. Thank you again for your suggestion and helping us improve Total Upkeep!

You're welcome, I am glad to hear that upgrading to PHP 7.4 fixed the issue! Hopefully this issue is limited to those 2 versions, but please let us know if you ever encounter any other problems in the future!

Hi everyone!

So far it seems that the error is created on sites that are using PHP versions 7.2.32 and 7.3.20.  If you have the option, try upgrading to PHP 7.4 to see if that gets rid of the fatal error.  Strangely enough we were able to locate some reports of Drupal sites with a nearly identical error message and upgrading to a newer PHP version fixed the issue for them.

Flushing the cache can also fix the error and you can run the following WP CLI command to flush the cache after you SSH into your server:

wp w3-total-cache flush all

Please let us know if those troubleshooting steps help you restore access to your websites!