Open markkap opened 5 years ago
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
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.