Found the solution… the problem was due to placement of the conditional statement in the wp-config.php file. It needed to be inserted before the require_once(ABSPATH . ‘wp-settings.php’); line near the bottom of the default config file, otherwise the constants are already defined and cannot be redefined. So final section of the wp-config.php file now looks … Read more
You can move the wp-config file one level up. You can also create a .htaccess file and upload it to your uploads folder with this code: <Files ~ “.*..*”> Order Allow,Deny Deny from all </Files> <FilesMatch “.(jpg|jpeg|jpe|gif|png)$”> Order Deny,Allow Allow from all </FilesMatch> Or install a plugin for security which also scans your installation so … Read more
update the fields in general settings in wp-admin. I think it will solve your issue. please make sure that you will not give any static path for any image
Try memory_limit = 128M in php.ini. Your syntax may be wrong. You can run a function called phpinfo to see what kind of memory allocation you really have. Make a plain text file and call it phpinfo.php and put just this line in it: <?php phpinfo(); ?> then put the file in the root of … Read more
(s)FTP into your site, or use a file manager provided by your host, and undo what you did. Then, if you were editing PHP with the built in editor as I suspect, don’t ever do that again– ever. It is like working on an airplane while it is in the air. Create a local copy … Read more
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.