Change wp-content foldername not possible?!

[sitedock]

Hi there!

I'm trying to rename the wp-content folder name to app.
I do this on every wp-site for some years now.
wp is able to handle that so i renamed the folder and set up the respective constants in wp-config.php

define( 'WP_CONTENT_FOLDERNAME', 'app');
define( 'WP_CONTENT_DIR', ABSPATH . WP_CONTENT_FOLDERNAME);
define( 'WP_CONTENT_URL', WP_SITEURL .'/'. WP_CONTENT_FOLDERNAME);

But that seam not to work cause the server-setup seams to mount the exact "wp-content" folder to the docker container... can i change this somewhere?

Thanks for any hint about this!

[girish]

@sitedock said in Change wp-content foldername not possible?!:

define( 'WP_CONTENT_DIR', ABSPATH . WP_CONTENT_FOLDERNAME);

Is this missing a slash in the middle?

[sitedock]

@girish Thanks for the idea but the ABSPATH is /app/code/ in cloudrons architecture. that seams to be ok. checked this also.

i think it has something to do with the folder mounts. in the appdata folder the rest of wordpress core folders are also missing. only the ones that are available to edit (wp-config.php, php.ini, wp-content).

I assume it is not possible to change to dockerfile for the app?!

[girish]

@sitedock Ah, maybe you are using the WordPress Managed version of the app. There are two WordPress in the app store - Managed and Developer . The Managed one is setup with a readonly file system and it's meant for "blogs". Developer edition is targeting people who want to customize heavily and build websites (like your use case probably). In the developer edition, you the code is in /app/data/public/, so it's all writable.

You can check this in the App -> Update section in the Cloudron dashboard.

[jdaviescoates]

@girish you could save a lot of people a lot of time (not least yourself) by making WordPress (Developer) the default WordPress app that is shown first when searching the app store for WordPress and putting some big warnings in WordPress (Managed) saying something like " you probably do NOT want to use this" with links to docs explaining the difference.

I think renaming "WordPress (Developer)" to just "WordPress" would help too.

Should probably supress WordPress (Managed) from being displayed in Popular App etc too, IMHO.

Nearly every issue people have with WordPress is caused by them using Managed when they should be using Developer.

[girish]

@jdaviescoates I think making WP code writable is too dangerous as the default. There are way too many plugins doing all sorts of things. In fact, the support is quite low only because we prevent people from doing all sorts of things. We don't actually mind redirecting people to WP Developer with sound warnings.

For example, even changing the code directory of this wp-content (like this request), is not needed. But, there are million wp articles on how to re-configure wp in the same of security... we won't win this battle. Maybe there are real reason to re-configure since it's really insecure , which makes the case for managed WP even more ironically.

But I agree that we should maybe let people know of the choices upfront. I think WP managed still has a very large number of install, so it's up front.

[sitedock]

@girish Oh yes you're right. I'll switch to Developer-Edition and tell you if it works with that... I like the idea of having a save Managed Version where everything is secured while having the option to use a Developer-Editon which is more open for customizations...

[sitedock]

As expected it worked as expected with the above code in Developer Edition. Didn't noticed that before, so thanks for your help and sorry for the noise..