You better use a .htaccess file, where you force https with: RewriteEngine On RewriteCond %{HTTPS} off RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] The file goes in the root folder of your WP installation. If there is any, put this code on the beginning of the existing file. And you can then change the settings in the WP … Read more
I define some variables used in my theme at the top of functions.php….one of them being $press_here=”yes”; Then at the top of my template files I use <?php global $press_here; if( !isset( $press_here ) ) die(‘You don\’t have permission to view this page.’); Which then gives the error message I define there when being accessed … Read more
The official reply is that ABSPATH is more for backward compatibility with code which was written when plugins were including wp-config.php and overriding WP_CONTENT_DIR should be enough. https://core.trac.wordpress.org/ticket/29626#comment:3 https://core.trac.wordpress.org/ticket/26592#comment:8
You can place a .htaccess file in the folder wp-admin with the following content: <Files “setup-config.php”> Order Deny,Allow Deny from all </Files> Optionally you can add the line Allow from {your ip address} after Deny from all, so you can access the file.
There’s no “parser” that needs to be “smart”. It’s just a PHP file that runs as part of WordPress loading. The reason you need to put edits before that line is because the line that comes after it is this: require_once( ABSPATH . ‘wp-settings.php’ ); And this line basically loads all of WordPress. So any … Read more
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;
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
Yes, you can safely delete that file. It’s a template of what a minimal wp-config.php looks like, so as soon as you have a working wp-config, you don’t need it. It will never be restored unless you reinstall WordPress from scratch, e.g. by downloading and unpacking a clean WordPress installation. If for some reason you … Read more
The constant to output errors to screen is actually define( ‘WP_DEBUG_DISPLAY’, true ); WP_DEBUG_LOG would generate a debug.log in your wp-content directory, not in your site root.
The first part (add_filter()) tells WordPress to use the direct-write method. The second part (define()) tells WordPress to apply 0751 permissions to any directory it creates. More information here. I would not consider using the Direct Write method to be safe to use in a live, public, shared-hosting environment. Also, it might not – and … Read more