Yeah, making them read only makes the most sense. It's not like URLs change that often but you certainly wouldn't want to change it in WP or Cloudron would freak.

@girish said in Is it possible to configure the Apache Logs in Wordpress (Developer)?: Currently, you cannot change this, no. You have to use the LAMP app if you want to change the apache configs. In the LAMP app, there is an app.conf which gives you control over logging. You'd expressed interest in more fine-control over logging in another thread. If that's still true, I'll deal with the Apache over-Logging for now looking forward to a time where we figure out a solution for a way to best configure logs for the end-user. Going to LAMP would just feel like I'd be contributing less and less to the Wordpress (Developer) and (Managed) codebase(s) and that's my real goal. To make Wordpress (Developer) the best it can be in Cloudron. So maybe, one day, those access logs will be configurable.

@girish said in Can I send the Wordpress Debug Log to the Cloudron Logs: I agree we should visit this at some point for better logging This fixes the Wordpress "custom log path issue". But I do think we should revisit in the future about other apps and how we might be able to symlink the logs together. Anyway, you got me 75% there on this one, so thank you for that! ️

@girish That makes sense why it wasn’t in mine. I’m planning to reinstall anyway for LDAP support so I’ll let your install script add the custom COOKIEHASH for me. ️

I'm gonna look into this to get a definitive answer on if WP-DEBUG errors get piped to Cloudron's logs (which would be super useful). I'll post back guys (and if it doesn't, I'll see if I can make it do so and share the code).

Can confirm while converting the CRON Job to support multisite, it's still 1 minute and has been since I've been working on it.

@d19dotca great, thanks

Wait the permalink thing fixed the error I believe.

My error. I had the site stuck in recovery mode. It is back up now. I am back to normal. Thanks

@d19dotca Thanks for your input. I happen to feel the same way about this as I do about the LAMP app. In the store, just let me choose my PHP version and only have one LAMP app. I think this method has a better conveyance for new users of Cloudron. But, admittedly, this is harder work than having them separate - but it's food for thought for the developers.

@girish first update of many was successful! Thanks @girish !

Pushed an update now to PHP 7.4. It will roll out slowly.

@celeb If you open the web terminal, run the command env | grep CLOUDRON_MYSQL. You will see the credentials. I think in wordpress since you have multiple installs, be sure to use a table prefix.

@isubbu Do you see anything in the logs? It's in the console section of the app - https://cloudron.io/documentation/apps/#log-viewer

@Vladimir Indeed. This solution is documented in the Managed WP docs and not in the unmanaged one - https://cloudron.io/documentation/apps/wordpress/#cron-tasks . I will fix it up.

I had similar problem, not with DISABLE_WP_CRON but with define( ‘WP_POST_REVISIONS’, false ); It seems putting that command inside wp-confing.php it does not make any change on behavior...

@imc67 thanks, it wasn't a production app and so I just completely deleted the whole thing. At present I don't have any app installed there so that might explain certificate thing

@girish damn! I almost feel stupid, I just listen to the Gatsby dude which was saying you have nothing to set in your wordpress thank for your research and your time

@girish I should've added that site health was still reported as good even with this REST API issue. But yes, now that issue has gone away too [image: 1590833175610-great_job.png] BTW, to get perfect good health it also recommended I uninstall Twenty Seventeen and Twenty Nineteen themes too, and to just keep the themes I was using, it's parent, and Twenty Twenty. So perhaps only ship the package with Twenty Twenty? (Also, an aside really, but perhaps don't ship with Hello Dolly plugin too? Uninstalling it is always one of the first things I do! I can't imagine anyone actually really wanting it)

OK, I pushed an unmanaged WP update that updates the plugins but this won't affect existing installs though. You have to update the plugins yourself.