Debug Carefully
Only enable WP_DEBUG and SAVEQUERIES on development or staging environments where verbose logs are safe.
Generate a secure wp-config.php file with fresh salts, debug toggles, memory settings, and WordPress hardening options.
<?php
/**
* WordPress wp-config.php
* Generated by GAP3 Tools
*/
// Database Settings
define( 'DB_NAME', 'wordpress' );
define( 'DB_USER', 'root' );
define( 'DB_PASSWORD', '' );
define( 'DB_HOST', 'localhost' );
define( 'DB_CHARSET', 'utf8mb4' );
define( 'DB_COLLATE', '' );
// Security Keys & Salts
define( 'AUTH_KEY', '' );
define( 'SECURE_AUTH_KEY', '' );
define( 'LOGGED_IN_KEY', '' );
define( 'NONCE_KEY', '' );
define( 'AUTH_SALT', '' );
define( 'SECURE_AUTH_SALT', '' );
define( 'LOGGED_IN_SALT', '' );
define( 'NONCE_SALT', '' );
// Table Prefix
$table_prefix = 'wp_';
// Debug Settings
define( 'WP_DEBUG', false );
// Memory Limits
define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );
// Security Hardening
define( 'DISALLOW_FILE_EDIT', true );
define( 'FORCE_SSL_ADMIN', true );
define( 'FORCE_SSL_LOGIN', true );
/* That's all, stop editing! Happy publishing. */
if ( ! defined( 'ABSPATH' ) ) {
define( 'ABSPATH', __DIR__ . '/' );
}
require_once ABSPATH . 'wp-settings.php';Only enable WP_DEBUG and SAVEQUERIES on development or staging environments where verbose logs are safe.
Regenerate security salts when you need to invalidate all logged-in sessions across the site immediately.
Keep production edits in version control and store secrets securely instead of sharing wp-config values in plain text.