We’re working through the final remaining aspects of this transition, and will close this out shortly. Thank you for your patience throughout. Clients are very happy with the performance and white-labelling, and some clients have chosen the Evolution skin config which makes the end-user interface look remarkably similar to cP’s GUI.

Our key focuses at the moment are:

1. Backups exposing via GUI to clients and end clients
2. rspamd configuring optimally to improve filtering
3. SPF records fixing IPv6 and include parts within
4. ACME/LEGO (Let’s Encrypt) SSL re-automation

Separately, there has been a marked global increase in malicious attacks against WordPress websites - this has been phenomenally vast, and we’re seeing it across the industry taking many shapes and forms, unlike any sort of attacks we’ve seen before, this seems to mark a paradigm shift in terms of programmatic attack waves 24/7.

We’re actively working on that front as well, which has delayed these final works on DA, as the change has been so pronounced. Please ensure you are keeping software up-to-date, are not relaxed with permissions, do not leave DB find-replace tools present after usage etc, and ask our crew for help if you’d like detailed checks.

G’day,

Please note that WordPress have recently released v6.9.2, v6.9.3 and v6.9.4 in the space of 2 days.

Note that some fixes were only successfully applied in v6.9.4 so it’s the only v6.9 release considered safe.

The 13 security fixes included are being back-ported from WordPress v6.9.x through WordPress v4.7.x.

• We will be gradually upgrading all sites not already upgraded by this weekend
• This is to the latest release on the existing sub-major branch only
• For example: WordPress v6.1.9 would update to v6.1.10

If you wish to be excluded, please advise us ASAP and confirm you’ll perform the updates.

Cheers,
Merlot Digital