WordPress 5.5 auto-updates not working in Managed version, likely due to core updates blocked.
-
@rmdes said in WordPress 5.5 auto-updates not working in Managed version, likely due to core updates blocked.:
it all goes fine but when I want to upgrade WP to latest version, I'm being asked for FTP credentials ?
You cannot update WordPress with the managed version. It's asking for FTP creds because the filesystem is read only. We will push an update to WP 5.5.3 in the coming day or two.
Some technical info: In previous managed cloudron packages, it won't show the update UI. This was because we had a custom plugin that blocked updates. Unfortunately, that plugin also blocked plugin auto updates. I had removed it so that automatic updates of plugins work in Managed WP. That removal has the side effect that you see update WP UI...
-
-
@Lonk said in WordPress 5.5 auto-updates not working in Managed version, likely due to core updates blocked.:
I believe thatโs what he did.
Unfortunately, no. Since, I am not a WP dev, I couldn't figure out how to just disable core updates and keep plugin updates enabled. So, I disabled the plugin altogether. https://git.cloudron.io/cloudron/wordpress-managed-app/-/commit/08e6cf17a24e047806f4846bf1083b33c40642d6 is the plugin we previously had. If you know how to disable just core updates but not plugin updates, let me know and I can put that plugin back in.
-
I'm having this issue again, but not on all my WP's, I'm so confused right now, I don't even know what's happening, but it's asking for credentials again instead of updating from cloudron packages, I'm on managed, I even tried to install a clean new WP and restore my backup from my old WP (also managed) and guess what : exact same problem, can't upgrade, asking for credentials..even though the WP managed app just got installed and is supposed to be last version ?
What's going on here ?
-
@rmdes on the managed app, you cannot update WP. It will behave similar to what you faced i.e it will ask for credentials. This is because WP figures that it cannot write to the code directory and falls back to uploading code via FTP (a behavior I really dislike but I don't think this can be disabled).