A couple of those are still relevant, particularly Yoast and All-In-One SEO and SEOPress. But there is a newcomer that is quickly gaining ground and very popular lately too: Rankmath.
My recommendations (especially if you don't have crazy unique needs) is to use either RankMath or SEOPress. They are my favourites so far. I've used Yoast before and it's pretty decent, but they charge an arm and a leg if you want additional features (they're way more expensive than the rest - to be fair they are the most established though too so they probably are fine sine large companies won't care about the price and want a reputable brand). So if you need to go to a "pro" level too, SEOPress is the cheapest, and then Rankmath, and both are far cheaper than Yoast. Generally speaking though most SEO plugins work just fine if the needs are basic as if most people's needs for most small business websites (unless they have multiple locations).
@d19dotca I would add (if you're also moving domain) that in some cases there are remnants of the old domain, and so after doing pretty much what you describe above I tend to use the Better Search and Replace plugin to search for and replace any reference to old domain.
@ruihildt Updates to packages are rolled out slowly. So if a user tries to check for an update manually (i.e they click for 'check for updates') and they are not part of the rollout, they get shown that message. Generally, it is safe to update anyway but we are just being careful here.
Yes, would be great to have this but have to see if it's possible. The main issue is that most of the migrator plugins bring in the source code of WordPress and this is incompatible with the managed WordPress concept.
I was only thinking Managed to Developer conversions which could be done from outside of WP easily. Just have to change the WP directory at the end of the conversion.
Developer to Managed is more tricky. It would have to be destructive and overwrite all files that are read only but keep everything else. Possible - but more involved.
@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.
@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).
@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 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?
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?
@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!
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.