Use one main wp-config.php and name the others according to the name of the host: example.com.config.php example.net.config.php and so on. In your main wp-config.php write: $current_config = __DIR__ . “https://wordpress.stackexchange.com/” . $_SERVER[‘HTTP_HOST’] . ‘.config.php’; if ( file_exists( $current_config ) ) require_once $current_config;
There isn’t an RSS of the names of the categories specifically otherwise I would have used the XML from the RSS feed with XSLT to display the category list that way. There is a handy function named add_feed(). You can create any feed or other output with it. Should be useful in your case. And … Read more
I’ve found that I need to change the siteurl and home entries in wp_options when I move from local to a live server. Not sure that should affect a connection to the database though.
Looks like you have 2 WordPress installations. One for the main site, other for the Blog. http://parlourdc.com/wp-content/plugins/akismet/readme.txt http://parlourdc.com/blog/wp-content/plugins/akismet/readme.txt If that’s not on purpose, you have a blog folder in your site root that should be renamed/deleted as it contains a blank WordPress. If you made a page on your main site titled Blog (and with … Read more
Consider everything that comes with a vanilla WordPress installation a core file. Core files will be overwritten on updates, so it’s not safe to edit them. E.g. wp-config.php isn’t a core file, because the vanilla installation comes only with the sample version of that file.
Create a new file names wp-config.php and paste all the code than enter your db credentials it will solve your wp-config issue. <?php /** * The base configurations of the WordPress. * * This file has the following configurations: MySQL settings, Table Prefix, * Secret Keys, WordPress Language, and ABSPATH. You can find more information … Read more
FS_CHMOD_FILE and FS_CHMOD_DIR are applicable only if both of the following criteria are satisfied … the host allows the change in permissions (for an explanation on this, please see https://superuser.com/a/767261 ) the files are created by WordPress (such as WordPress core updates / upgrades, plugin installations / updates, theme installations / updates, or user uploaded … Read more
This depends on what is it that you are developing. If it is a plugin, you have to store such settings in options as the last thing site owner should be asked to do is to modify their config file. If it is your own site, just make it a constant that is declared in … Read more
When defining any WordPress constants in wp-config.php you need to do it before this line: require_once( ABSPATH . ‘wp-settings.php’ ); That line loads many of WordPress’s default constants, and if you haven’t already defined them yourself then they’ll be defined in that line, meaning that any of them that you try to define after this … Read more
The URLs are greyed out in the Settings page because of the entries in the wp-config.php file. If there are entries for these values, those values override the values in the wp-options table, and the override makes the Settings values uneditable. See this in the Codex: https://wordpress.org/support/article/changing-the-site-url/ It is possible to set the site URL … Read more