Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WP_ALLOW_REPAIR #27

Closed
PDowney opened this issue Nov 24, 2019 · 2 comments
Closed

WP_ALLOW_REPAIR #27

PDowney opened this issue Nov 24, 2019 · 2 comments

Comments

@PDowney
Copy link

PDowney commented Nov 24, 2019

WP_ALLOW_REPAIR found within the wp-config.php file should be set to false unless it's specifically being used. Any visitor can run database repairs and optimizations on a site with it enabled, regardless of whether or not they are logged in.

Try it by visiting yoursite/wp-admin/maint/repair.php

define('WP_ALLOW_REPAIR', false);

@jessuppi
Copy link
Member

@PDowney Thanks for your suggestion, it is now commented out by default. I've added a new section in the default wp-config.php boilerplate called:

Inactive Defined Constants (Modify Using Custom Functions Or Otherwise)

Ref: 9b85691

@jessuppi
Copy link
Member

A few others added (to be expanded in future), for future reference:

/** the following defined constants should not be hardcoded to allow for modification */
/** modify these constants using the Custom Functions MU plugin or otherwise */

// define('WP_ALLOW_REPAIR', false); // default = false
// define('SAVEQUERIES', false); // default = false
// define('CONCATENATE_SCRIPTS', false); // default = false
// define('SCRIPT_DEBUG', false); // default = false

Ref: https://github.com/littlebizzy/slickstack/blob/master/wordpress/wp-config.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants