Hi,
I’m planning the future of my wordpress site, that’s been running since WP2, and has never gone beyond 4.8, and AFAIK I’ll have to upgrade it to WP5 (or is it 6) to enable the crossgrade to CP…
Just wanted to check, does / can CP do automatic updates for semantic-patch minor versions?
Thanks,
Minor ones, not major ones. But your host can have its own update mechanism in place. See the CP doc.
Note that current CP is based on WP 6.2 (minus block editor related code). This means your plugins and theme should also support WP 6.2).
Thanks, I read the doc, and the gist I got from it was the auto-updating depended on the hosting account having Softaculous or similar…
I’ve never used a hosting panel installer for my Wordpress installs, always manual uploads and running the appropriate php file, and then updating from within Wordpress, so I’ve always assumed the auto update in Wordpress was an internal to Wordpress thing.
So that’s what I was wondering - does CP update itself using its own self-contained functionality (so it’s portable to the most bare-bones hosting account), or is it dependent on whether the hosting package has an installer?
To be honest, after looking into the code and talking with a CP dev I 'm doubtful about auto-updates between minor versions. There’s a recent patch-update (2.7.4) and my local test install only prompts me. Does not auto-update. WP has a “Switch to automatic updates for maintenance and security releases only.” feature on the Updates page, CP does not. We need to investigate.
Yeah, it would be a good feature to introduce. It’s a bit of a must-have in cases where a security issue happens while you’re travelling, for example, and don’t have access to do it manually, etc.
We discussed this a while ago and agreed that we would not auto-update sites at all. We don’t know what each site has installed and we don’t know what implications an update might have for custom code.
Is there a mailing list / RSS feed for announcements for security patches, etc?
The Announcements category on here and on Zulip, and the news category and overarching header on classicpress.net, all announce an update within minutes of its being released.
OK, so the RSS feed at the home page provides update notifications, cool.
The important thing being the news comes to me, rather than me having to go out looking for the news.
Hi,
Now I’m even more confused.
The documentation states that minor version updates (for example, 2.7.x → 2.7.y) are enabled by default:
Because of that statement, I spent quite a bit of time trying to figure out why none of my sites had ever updated automatically.
My sites are hosted on Xserver in Japan. I have both:
None of them have ever performed an automatic minor update.
However, I found a forum post stating that the project decided not to auto-update sites at all because updates could affect plugins, themes, or custom code.
If that is indeed the current policy, then the documentation appears to be incorrect or out of date.
Thanks for all your work on ClassicPress.
@Guido07111975 I think the OP is pointing out something significant. I am afk today but available on mobile if you need me to review docs eventually.
Yes, I initially thought it does update between minor versions, but it seems it does not. When looking in old versions of the doc, my conclusion is it does not update (it only prompts you to update). You can change this to auto-updates (patch/minor) by using a filter. Did not change the wording yet, because I’m not 100% certain how everything works.
I found the reason why I thought it does update between minor versions. In an older version of the doc this is included:
If your ClassicPress version number is 1.0.0-rc1 or higher, then your site will automatically upgrade to later versions in the 1.x release series by default.
So does this apply to CP version 2 as well or not?