You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 25, 2022. It is now read-only.
Since it is placed in the wp-content directory which is exposed to the web it should be easily identified as something for which access is denied. At least in calmPress by the default .htaccess is going to block access to all . (dot) files and directories
The text was updated successfully, but these errors were encountered:
Thinking about it some more, I am not sure that having it under wp-content is a good decision as in this case you need to know where it is located before you read the configuration and therefore you either need to define WP_CONTENT_DIR before the configuration can be read or just ignore its value when looking for the configuration
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since it is placed in the
wp-content
directory which is exposed to the web it should be easily identified as something for which access is denied. At least in calmPress by the default.htaccess
is going to block access to all . (dot) files and directoriesThe text was updated successfully, but these errors were encountered: