There is, as far as I know, no way to hook into wp-config.php from a Theme. For one, wp-config.php shouldn’t be writeable; for another, wp-config.php is executed well-before a Theme’s functions.php file is parsed. For a great overview of how WordPress boots, have a look at this two-part post by Theme.FM (part 1, part 2) … Read more
I have the same problem before. I put WP_POST_REVISIONS in the end of wp-config.php file and it didn’t work correctly. You should put your codes before defining ABSPATH and before this line: /* That’s all, stop editing! Happy blogging. */ it must be something like in the following: define( ‘WP_POST_REVISIONS’, 6 ); /* That’s all, … Read more
I had the axact same problem. My solution: edited/etc/apache2/sites-enabled/000-default.conf. It needs to look like: <VirtualHost *:80> ServerAdmin webmaster@localhost DocumentRoot /var/www/html <Directory /> Options FollowSymLinks AllowOverride all </Directory> <Directory /var/www/> Options FollowSymLinks AllowOverride all Order allow,deny allow from all </Directory> ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined </VirtualHost> It works!
I came up with this solution. This function checks in each directory level starting from the directory of the current file for the file wp-config.php. <?php function find_wp_config_path() { $dir = dirname(__FILE__); do { if( file_exists($dir.”/wp-config.php”) ) { return $dir; } } while( $dir = realpath(“$dir/..”) ); return null; } ?> To actually include the … Read more
No the passwords won’t break (those are in the database and aren’t changed by changing the salt). However all logged-in users will have to login again. More on Salts here. Note: Updating your keys & salts will force all logged in users to log in again, because changing them automatically invalidates the login of any … Read more
My guess is – yes, you are stuck with exactly that. Checks for EMPTY_TRASH_DAYS seem to be hardcoded as condition for switching interface between trash and delete in several places.
WordPress tells us: the WP_MEMORY_LIMIT option allows you to specify the maximum amount of memory that can be consumed by PHP. This setting may be necessary in the event you receive a message such as “Allowed memory size of xxxxxx bytes exhausted”. Or as the PHP docs put it [A memory limit] helps prevent poorly … Read more
After many hours of debugging and despair, the problem is now solved. It turned out to be a very obscure thing. The redirect is issued by the function ms_load_current_site_and_network() inside /wp-includes/ms-load.php. It was issuing the redirect because /wp-includes/ms-settings.php was not able to set a domain. The reason it was not able to set a domain … Read more
Using the defines the user sets in wp-config: mysql_connect(DB_HOST, DB_USER, DB_PASSWORD); EDIT: Since your script is outside the WordPress environment, what you want to do is initiate it before using the defines in wp-config. require_once(‘./path/to/the/wp-config.php’); mysql_connect(DB_HOST, DB_USER, DB_PASSWORD);
I haven’t tested this, but if you would need to find such a solution, I would probably try to do it in the following way by adding a script into the if ( SOME_CHECK_IF_STEP-1_WAS_PASSED ) condition you’ve described above, that would: check the DB for the {$wpdb->prefix}sitemeta table; if it does not exist -> return … Read more