-
Notifications
You must be signed in to change notification settings - Fork 64
Description
Platform
AWS
bndiagnostic ID know more about bndiagnostic ID
16ed5086-ea59-1bd6-36d4-b3596923777e
bndiagnostic output
? Apache: Found possible issues
? Wordpress: Found possible issues
? Resources: Found possible issues
https://docs.bitnami.com/general/apps/wordpress/troubleshooting/debug-errors-apache/
https://docs.bitnami.com/bch/apps/moodle/troubleshooting/deny-connections-bots-apache/
bndiagnostic was not useful. Could you please tell us why?
The suggested guides are not related with my issue
Describe your issue as much as you can
(migrated from community.bitnami.com)
The recent changes regarding moving to native system packages seems to have move some of the folders around a bit for WordPress. Indeed there are now 2 WordPress folders:
- /opt/bitnami/wordpress
- /bitnami/wordpress/
There is a shortcut/symlink between /opt/bitnami/wordpress/wp-content and /bitnami/wordpress/wp-content. This works great normally, but a fair few plugins are getting messed up poaths when looking for files. For example when looking for their own plugin assets they are getting the following URLs:
example.com/wp-content/bitnami/wordpress/wp-content/plugins/{plugin-name}/path/to/file.jss
File could obviously be anything: .css, .png, etc.
The obvious fix is to just remove one of the folders, e.g. remove the symlink and move the entire “/bitnami/wordpress/wp-content” directory into the “/opt/bitnami/wordpress/wp-content” location. However I thionk that bitnami has separated these for a reason? what would be the implications of doing this?