@d19dotca Yup, they cover all sorts of obscure things for all countries, including cash on delivery and other random country-specific popular services. Ebay uses them now. Rates seem pretty fair. Certainly easier than setting them all up individually.

@Lonk Both versions.

@ruihildt said in Are there any issues with the Divy builder theme?:

@d19dotca I can confirm Elementor (and Pro) works perfectly well with both managed and unmanaged versions. Same with Divi.

Thank you!

It looks like both of those improved over the last two years and have contributed and extended WP so things are much more compatible, and doesn't affect the read-only Cloudron app install.

@theTECHIEflyer which themes are these?

@girish said in Change PHP Max Input Vars:

[PHP]
max_input_vars = 5000

It worked, thanks!

@rmdes I think you might have misunderstood my earlier post.

Managed WP - there is no way to use redis on this. Even if you install the redis plugin, redis itself is not available to the app. But as also mentioned in the other post, redis provides an object level caching. It's kind of unlikely that it will make your site amazingly fast. Think of it as a cache for database objects. Given that in Cloudron's case, the database itself is local, redis access won't be magnitude faster than mysql.

Unmanaged WP - these apps have redis enabled by default. In fact, there is no way to disable redis in these. There is a feature request to be able to dynamically turn on/off redis.

With that explanation... do your current WP installations not reflect the above?

@rmdes Yes, I have been doing some load tests with Cloudron app vs Vanilla WP vs OpenLite Speed. Generally, having redis is not much of a difference. What makes the big difference is static page caches like W3 Total Cache. It's also the reason OLS on first run appears so fast (it has a cache plugin enabled by default). Redis cache is for objects and dynamic pages, it's not going to make things much fast.

Note that one pain of these static cache plugins is that you have to clear the cache manually (or set some timer to re-generate the cache).

This is fixed in the latest packages. Thanks for reporting.

@johnbolt Sure, just revert it from your backups. Under the backups view of the app, look for package versioned 2.11.1 (this has the older WP). After reverting, disable automatic updates (in the Updates section of the app).

@girish said in what runs cloudrun wp and what does it manage?:

want to edit WP core files. In such a case, Cloudron cannot do automatic updates since the user edit files and it's not possible to know what the update has to do. This one also uses apache.

Thanks for the reply.

@girish I was actually going to post this before too... that trailing slash is important. However, this behaviour only seems to impact the managed app. The unmanaged app doesn't require that trailing slash. Any ideas why these are different?

@ice said in Wordpress has stopped working:

Jul 27 17:20:01 [Mon Jul 27 16:20:01.042734 2020] [php7:error] [pid 41] [client 172.18.0.1:48468] PHP Fatal error: Cannot redeclare authLdap_send_change_email() (previously declared in /app/data/wp-content/plugins/authLdap-2.4.2/authLdap.php:849) in /app/data/wp-content/plugins/authldap/authLdap.php on line 849, referer: https://my.removed/

This is the problem. I think the issue was because the LDAP plugin was updated by you (?). The fix is to remove wp-content/plugins/authldap directory using the File Browser (do not remove the authLdap-2.4.2 directory). Does that work?

@ice Let's discuss in https://forum.cloudron.io/topic/2947/wordpress-has-stopped-working

@imc67 I wish there was a way to track WP Mail SMTP package updates. I have fixed up the package by hand now but it's something I need to keep in mind everytime I update WordPress. I have also fixed up the package to install the latest plugins/themes (on first run only). Thanks for reporting!

Yeah, we made changes specifically to preserve the mail from. If you find that it doesn't work, please report back.

Update: It is thankfully as easy as removing the data from the users table in the user_pass column. 🙂

Removing the value from the user_pass column on each user who you want to only authenticate using LDAP/Cloudron, will force that expected behaviour. If there is a password in the database, authentication will succeed with the local password OR the LDAP/Cloudron password, so removing that password will force it to rely only on LDAP/Cloudron authentication.

Dear @Captain-Kirk @girish @jdaviescoates @scooke appreciate very much your suggestions!

I'll check which one fits for my needs.

What about security. Did you have any security related issues? I mean something like privilege escalation, or login attempts from external users.

Many thank's

Thanks!
The migration went super smooth and fast with the "All In One" plugin.

@yusf I wish you luck!