Looks link you’re missing the forward slash / which is probably causing it to not locate the right files /.index.php <?php define(‘WP_USE_THEMES’, true); require( dirname( __FILE__ ) . ‘/web/wp-blog-header.php’ ); /web/index.php <?php define(‘WP_USE_THEMES’, true); require( dirname( __FILE__ ) . ‘/wp-blog-header.php’ ); /.htaccess (the same as /web/.htaccess) # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase /web/ … Read more
In WordPress error reporting is primarily controlled by WP_DEBUG and other related constants in wp-config.php file. Typically they are completely independent of theme and plugins, although some (well coded) extensions adjust their behavior accordingly with debug settings.
So in the old days when WordPress updated you got the whole shebang and deleting Akismet after every time was deadly boring. Things had slightly improved since then (partially driven by minimizing traffic it takes to serve update to everyone), but process also got more complicated. Now there are multiple versions of update archive that … Read more
Silly me, I posted this before doing a proper investigation. The issue isn’t with WordPress, it was instead with how Polylang (translation plugin) handled the site url. The solution was to put define(‘PLL_CACHE_HOME_URL’, false); in the wp-config.php before I changed the URL using the WP constants.
Actually you can read all the constants defined in wp-config.php from any place you want. If you have something like this in your wp-config.php define(‘DB_NAME’, ‘some_value’); You can do this for example in your functions.php file echo DB_NAME; Constants are globally accessible from everywhere. So please think about this approach.
admin_url() should be used. However for some websites this request gives error 404 in front-end admin_url(‘admin-ajax.php’) should point to an actual file (admin-ajax.php), as such WordPress won’t pass it through index.php, and so it shouldn’t lead to the theme’s 404 page. (Unless the file has been deleted). … unless you have a .htaccess file which … Read more
Yes. If you use the generator to create the salts then add them to your wp-config.php file you can start reaping the benefits of much greater security. Any current sessions will be invalidated so you’ll have to log back in but otherwise there shouldn’t be any noticeable change. Automatic generation of random salts was added … Read more
Do not rename or modify the sample files unless such modifications are intended for contribution – they are there for reference. The files wp-config.php and wp-tests-config.php are explicitly ignored by .gitignore. Simply create them as new files yourself (or, if you’d like to use the sample files verbatim create symlinks to the sample files) to … Read more
Here a – quick and dirty way – to get ‘live to local’ with wamp. Assuming that you access your live site as in http://yoursite.com Steps to take: Copy your live site as you did, public_html to www Edit wp-config.php and add folowing 2 lines code: define( ‘WP_SITEURL’, ‘http://local.yoursite.com’ ); define( ‘WP_HOME’, ‘http://local.yoursite.com’ ); IF … Read more
Just change define( ‘SUBDOMAIN_INSTALL’, true ); to define( ‘SUBDOMAIN_INSTALL’, false ); More here: https://codex.wordpress.org/Multisite_Network_Administration