Apologies, I am sure most or all of these have been suggested and I am suggesting a few at once here.

• File manager

• Ability to rename accounts. I am a developer and have 5 accounts and more soon that I am working on for different clients. In the drop down it shows their name, I should be able to rename it so I see the name of the client, not the name they signed up with which sometimes is not someone I know and am not sure which websites it is and need to click around to find the correct account.

• Login timeout. If I don't use the Cloudways admin page for as little as an hour or two I get logged out and need to log back in. I think the timeout should be at least 12 if not 24 hours. I waste a lot of time each day waiting to log back in (click on a link, the single application page loads, then it realizes I am timeout, redirects me to the login screen, need to log in, land back on the main page with the servers, need to click into where I wanted to be...)

• Link should be openable in another tab. Nothing in the CW admin that is a link is an actual link. It is all controlled with JS, so I can't right click and open in another tab.

There is an issue on servers configured by Cloudways, in which the PHP-FPM log buffer (error msg length) is set to 1028 bytes. This is too short for many errors messages generated by Wordpress.

It results in many entries of:
"Message":"AH01071: Got error 'the log buffer is full (1024). The access log request has been truncated.'"

In the PHP error logs views in Application Manager. So rather than seeing the actual error, you end up just seeing this message. Which is, obviously, very unhelpful.

Apparently it's due to the setting of log_limit setting in PHP-FPM, complied with Nginx.
You can read about this here: https://serverfault.com/questions/256459/nginx-php-fpm-long-log-lines-get-truncated

PHP-FPM will need to re recompiled with a patch. See here https://forums.freebsd.org/threads/howto-stop-nginx-php-fpm-from-truncating-your-stack-trace-error-message.56543/

Anyway... I found a workaround solution is to add the following to the PHP Advanced Settings on the Application:

phpadminvalue[logerrorsmax_len] = 2048

Once that is added, property (and useful) error messages are now accessible in the error logs.

I suggest Cloudways either compile PHP-FPM with a higher log_limit, or implement the PHP change I've mentioned, by default on all applications. This would save the customer from having to deal with this issue.

Regards,

Jonathan

From Wordfence:
We tested this issue using the Breeze plugin and found two problems.

This affects Wordfence’s two-factor authentication, if one or more users has set up two-factor authentication, and the reCAPTCHA feature, so using either or both of those features would be broken by Breeze modifying our script tags.

In Breeze’s “Advanced Options”, under “Delay JS inline scripts”, you can remove the line that says “nonce” to avoid having our script deferred.

You will also need to turn off the “JS” option under “Minifcation” in Breeze’s settings. We don’t know why they are modifying our script tag when minification is off but not on, but they have removed parameters that are necessary when loading Google’s api.js file.

Enabling JS minification may work on your site, but that has the potential to break other scripts. You can try it if you like, but be sure to test your site’s functionality if you do. Otherwise, we recommend disabling Breeze temporarily, until their next release that may fix these new issues.

Me: I tried the above suggestion which did not work. Cloudways have downgraded Breeze to an earlier version for me.

Can you please fix the compatibility issue.

Thank you

Currently the created date only shows on the "Applications" page, which paginates apps in groups of 10. We've go over 150 apps, so when we need to find the created date we have to trawl through pages to find the correct app.

So it would be super helpful to have the "Created Date" for an application within the details of a single app. As for where, maybe above/below the "Applications Management" title on the left hand side. Or below that menu? Or within one of the pages - e.g. Access Details.

Should be super simple to add in wherever! Just somewhere within the single app :)

Thanks!!!

I have auto updates enabled, and each time the site is broken until breeze cache is cleared. I notice breeze can be auto-cleared on posts and page updates, but is there no script I could add that would allow it to clear on plugin updates?

There have been several security issues recently that have required sites to be updated immediately. Several plugins have had zero day vulnerabilities that require immediate attention. I have too many sites to update manually as quickly as the plugin authors would like.

Enabling auto-updates on plugins is a great solution, but Breeze cache is the only thing stopping it from working, because each plugin update requires me to clear the cache or my users see a broken layout.

Even if updating plugins manually, why should we have to manually clear the cache also?