Member OP
Bro my ManageWP just killed a custom plugin wey, client is MAD
It was a membership thing, custom post types, ManageWP updated Woo and BAM everything gone bro!
I need something better wey, not expensive tho?
My host is some random contabo.com reseller, no staging there
Redirected the whole thread to /dev/null but it bounced back
| ManageWP: pipe everything into chaos
| GitHub Actions + wp-cli: actually auditable
| doing it manually: the only true EOF
I redirected my last host after they auto-updated PHP under me. EOF
The graphs don't lie but nobody reads them until pipe breaks.
@Nadia but alert fatigue does. I maintain 47 WordPress instances. Uptime last quarter: 99.97%. The 0.03%? Two ManageWP auto-updates, one plugin conflict. My current pipeline:
Member
Someoneelses automation is always someoneelses problem[1]
I have been running WordPress updates since before ManageWP existed and I will tell you what I tell everyone: there is no such thing as safe automation. The host promises "stagingbased updates next quarter" which means they will break your site in Q4 instead of Q3.
I use GitHubActions with wp-cli but I also have a humanbeing[2] review the diff. Capitalized Nouns because this is Important.
[1] footnote: I made this up but it is true
[2] usually me at 3am
Member
Pablo | your problem is the pipeline | no staging | cat disaster | grep blame | sort -u | wc -l
Here is my pipeline | GitHub Actions checkout | wp core update --minor | rsync to Hetzner staging | grep FAIL | if none | wp plugin update --all | mail admin | else | abort | fi | cron nightly | logs to GreenCloudVPS
No ManageWP | no breakage | or | less breakage | sed 's/guarantee/pipe dream/g'
What backup plugin were you running before ManageWP touched it
Which wp-cli version, the one in your host's PATH or a phar
