wp-config.php Generator

Build a correct wp-config.php without copy-pasting from a 2014 blog post

Tumatakbo sa iyong browser. Walang ina-upload.

Database

Database name Database user Database host Table prefixChanging this on a NEW install is fine. Changing it on an existing site requires renaming tables and rewriting two option rows — it is not a config change.

Debugging

Enable WP_DEBUGLogs PHP notices, warnings and errors. Pairs with the two options below — never enable it alone on a live site. Write errors to wp-content/debug.logRecommended. Errors go to a file instead of the page. Hide errors from visitorsSets WP_DEBUG_DISPLAY false. Without this, WP_DEBUG prints PHP errors — including your server's absolute paths — to anyone loading the page. Log database queries (SAVEQUERIES)Useful when hunting a slow page. Costs memory on every request — turn it off again afterwards.

Hardening

Disable the theme & plugin file editorDISALLOW_FILE_EDIT. If an admin account is ever compromised, the built-in editor is how a PHP backdoor gets written. There is no good reason to leave it on. Force SSL for the admin areaFORCE_SSL_ADMIN. Only enable once HTTPS actually works, or you will lock yourself out. Enable automatic core updates

Limits

WP_MEMORY_LIMIT (MB) Post revisions to keep0 disables them. Unlimited revisions are the quiet reason many wp_posts tables get enormous.

wp-config.php

Salts are generated in your browser with crypto.getRandomValues(). They are never sent anywhere — but for the record, WordPress's own api.wordpress.org salt endpoint is equally fine; it returns fresh random values over TLS.

Tungkol sa wp-config.php Generator

Generate a wp-config.php with the constants you actually need — debug logging, memory limits, file-edit lockdown, upload limits, table prefix, and fresh salts. Everything is generated in your browser; nothing is sent anywhere.

Kaugnay

Iba pang tools na baka kailanganin mo

WP_DEBUG Configurator

Turn on the debug log without breaking your live site

Max Upload Size Fixer

Raise the upload limit — and get all three values consistent

WordPress .htaccess Generator

The rules WordPress needs, plus the hardening rules it does not ship with

FAQ

Mga Tanong

Ligtas bang bumuo ng wp-config.php salts sa isang browser?

Oo. Ang salts ay ginagawa gamit ang crypto.getRandomValues(), ang cryptographically secure na random number generator ng browser, at hindi kailanman lumalabas ng iyong makina. Para sa talaan, ang sariling api.wordpress.org salt endpoint ng WordPress ay pantay ding ligtas — nagbabalik ito ng sariwang random values sa TLS. Ito ay convenience, hindi security fix.

Bakit hindi ito humihingi ng aking database password?

Dahil hindi mo dapat i-type ang isang production database password sa isang web page, gaano man ito ka-mapagkakatiwalaan ang sabi nito. Ang nabuong file ay may placeholder — punan mo ito nang local, sa iyong editor.

Puwede ko bang baguhin ang table prefix sa isang existing na site?

Hindi sa pamamagitan lang ng pag-edit ng wp-config.php. Ang pagbabago ng $table_prefix sa isang live na site ay nangangailangan ng pag-rename ng bawat table AT pag-rewrite ng dalawang row sa options at usermeta tables. Baguhin ito sa isang sariwang install, o hayaan na lang.