Use WP ClI for setting wp-config.php constants
We experienced issues with replacing constants in wp-config.php using regular expressions. E.g. it may stop working when new WP release changes default contents of the wp-config.php Using WP CLI seems to be more reliable way of doing it. [MAILPOET-4511]
This commit is contained in:
committed by
Veljko V
parent
1e1ef12d42
commit
3b5d737143
@@ -129,15 +129,12 @@ wp plugin activate woocommerce-memberships
|
||||
wp plugin activate woo-gutenberg-products-block
|
||||
fi # end of check for enabling extra plugins
|
||||
|
||||
# add configuration
|
||||
CONFIG=''
|
||||
CONFIG+="define('WP_DEBUG', true);\n"
|
||||
CONFIG+="define('WP_DEBUG_DISPLAY', true);\n"
|
||||
CONFIG+="define('WP_DEBUG_LOG', true);\n"
|
||||
CONFIG+="define('COOKIE_DOMAIN', \$_SERVER['HTTP_HOST']);\n"
|
||||
CONFIG+="define('DISABLE_WP_CRON', true);\n"
|
||||
|
||||
sed -i "s/define( *'WP_DEBUG', !!getenv_docker('WORDPRESS_DEBUG', '')* );/$CONFIG/" /wp-core/wp-config.php
|
||||
# Set constants in wp-config.php
|
||||
wp config set WP_DEBUG true --raw
|
||||
wp config set WP_DEBUG_DISPLAY true --raw
|
||||
wp config set WP_DEBUG_LOG true --raw
|
||||
wp config set COOKIE_DOMAIN \$_SERVER[\'HTTP_HOST\'] --raw
|
||||
wp config set DISABLE_WP_CRON true --raw
|
||||
|
||||
# activate theme
|
||||
wp theme activate twentytwentyone
|
||||
|
Reference in New Issue
Block a user