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

@jdaviescoates With Cloudron no need of any backup wp plugin anymore

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

Thanks for the reply. I do have automatic updates enable, and in the app it says "Automatic Updates is currently enabled." But for some reason the automatic updates haven't been applied since packaged version 3.3.0 on 08/09/2023 for multiple of my sites. I am able to manually click update in the Updates section of the app, so I am good for now, thanks.

I'm sorry for awakening an old thread, but as this subject came up first in my Google search, I thought it would be wise to share a proper solution regarding the unfiltered_html setting in Cloudron's WordPress managed app. In the WordPress managed app, the unfiltered_html capability is configured in the wp-config.php file : define('DISALLOW_UNFILTERED_HTML', true); to revert this you can just change this line to the following one: define('DISALLOW_UNFILTERED_HTML', false); The reason WordPress managed on Cloudron could be a better choice for some use cases, particularly from a security standpoint, is noteworthy. In the managed version, most of the WordPress files are on an immutable partition, meaning they cannot be altered. This greatly lowers the risk of security issues caused by unauthorized changes to the files. Also, as the WordPress core files are part of the WordPress cloudron app's, they are not included in the Cloudron's backups, making the backups lighter and quicker since only plugins data and customizations are backed up, not the entire WordPress core.

@opensourced thanks for confirming! We are rolling out that package slowly.

@dsp76 I think this was a bug in the package not setting WP_CONTENT_DIR maybe. I have pushed a new package which sets this, can you check if that helps? I could not test WPML personally since it seems this is some paid plugin (unless there is a test version somewhere for me to test)

@dsp76 the migration is no different from any other app. For WP, I didn't find any plugins that specifically migrate only the database and the plugins alone. The managed WP app does not allow changing the WP code itself. This is the reason the guides focus on WordPress Developer - most of the migration plugins just tarball the entire WP source. Generally, https://docs.cloudron.io/guides/migrate-wordpress/#migration-without-a-plugin should work though (as long as you have no changes to WP code).

Thank you! The Site Logo block did the trick. Thanks, @girish! Wordpress has gotten so complex!

nothing but depreciated errors. weird thing is, I've rebuilt the site using a backup from all-in-one wp migration tool to www.website.com and redirected website.com to it. site is still standing. Attacks happening to root domain?

I will remove that line altogether. This closed issue list was maintained 5-6 years ago but it's not anymore.

Plugin version 2.5.7 fixes it

@Jeyakumarrathnaselvi So, WP itself is running OK but you face this issues when uploading a plugin/theme ? It would help a lot if you can give us complete information in a single shot and explain the problem in detail with reproduction steps. Otherwise, we all have to guess.