It seems manually restarting mysql allowed it to get unstuck and finish uninstalling. Perhaps if I'd have tried that before I'd have gotten it up update too.

It was resolved by activating the OpenID plugin. I am not sure how it was deactivated in the first place.

The managed WordPress never had redis. The developer WordPress has redis .

Works now Update showed up and worked as expected. Thank you @girish

@ImatBagjaGumilar Good news! I'm very glad for this. Keep us posted in case of any need.

Closed due to inactivity

@joseph thanks! @james local comp time is fine. how do I know it is not correct though? Btw this issue still persist somehow, but when I tried to open it from incognito mode it's fine, so probably it's the browser cache. Thanks for the help.

Hi Joseph, thank you for your reply - autoupdates where enabled for plugins. Let me check if that solves the issue :).

Did this get sorted out?

I don't think there is a plugin per se, but you should be able to use the Cloudron API to do this. In the past I had played around with WordPress Multi site and the Cloudron SSO plugin to allow site creation, but didn't get much further.

@necrevistonnezr This was resolved after clearing numerous caches on client and server side. Didn't look further into it.

Pretty much all my sites have MainWP Child, All-in-One WP Migration, Instant Images, Media Cloud, and Fonts Plugin. And sometimes Blogo. EDIT: Bogo, a translation plugin. Blogo was one of my fav blogging apps on the Mac way back when.

Don't have exact dates, but we will start working on it from next week.

@joseph said in Issue with WPvivid Backup File Size and Download Process: Or is this somehow related to Cloudron ? My guess would be the locked down nature of the WordPress (Managed) Cloudron package is stopping WPvivid from working properly and the solution is likely to be using WordPress (Developer) instead, which IMHO ought to be the default Cloudron WordPress app given so many issues people have with WordPress on Cloudron seem to be related to using the (Managed) app.

So, this happens because the package wants to re-configure WP with the correct domain , database etc on start up. Making the config file read only makes it not work. Not sure if this is fixable.

This is out now.

I got it working. Turns out I had made a mistake.

Ah perfect, solved again then