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 has been archived by the owner on Jan 25, 2022. It is now read-only.
Seems like a good convention is that the only files in the root directory are files that are intended to be accessed from the outside. As better-wp-config.php is not intended to be accessed from the outside, wp-includes might be a better place for it.
The text was updated successfully, but these errors were encountered:
hmmm, I see it might be a problem for WordPress installs, but for calmPress and classicPress that is probably the best way to go. So this brings back the need to be able to "tell" the code where the configuration is located. My suggestion is to move the line wp_config()->load_config();
to wp_config.php and pass the directory in which the configuration is located as a parameter
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Seems like a good convention is that the only files in the root directory are files that are intended to be accessed from the outside. As
better-wp-config.php
is not intended to be accessed from the outside,wp-includes
might be a better place for it.The text was updated successfully, but these errors were encountered: