开发者 | ezraverheijen |
---|---|
更新时间 | 2014年10月31日 20:17 |
PHP版本: | 3.5 及以上 |
WordPress版本: | 3.9.1 |
版权: | GPLv3 or later |
版权网址: | 版权信息 |
/**#@+
and /**#@-*/
or between # BEGIN WP Auto Salts
and # END WP Auto Salts
(on new lines) or WP Auto Salts won't work.
Please keep in mind that WP Auto Salts is still beta software.
If you have any issues using WP Auto Salts, find a bug or have an idea to make the plugin even better then please help to improve WP Auto Salts.
If you don’t report it, I can’t fix it!
wp-auto-salts
folder to the /wp-content/plugins/
directoryThats's normal behaviour and actually a good thing. WP Auto Salts will try to renew the security keys and salts on activation of the plugin. This will immediately invalidate all existing cookies and force all users to have to log in again.
WP Auto Salts looks for the beginning /**#@+
and ending /**#@-*/
in your wp-config.php and replaces everything between it.
`/**#@+
# BEGIN WP Auto Salts
and # END WP Auto Salts
:
`# BEGIN WP Auto Salts
define('SECURE_AUTH_KEY', 'your unique phrase here');
define('LOGGED_IN_KEY', 'your unique phrase here');
define('NONCE_KEY', 'your unique phrase here');
define('AUTH_SALT', 'your unique phrase here');
define('SECURE_AUTH_SALT', 'your unique phrase here');
define('LOGGED_IN_SALT', 'your unique phrase here');
define('NONCE_SALT', 'your unique phrase here');
END WP Auto Salts`
It is not possible for WP Auto Salts to write to wp-config.php. This can be caused by having a wrong 'file owner' on the server. Typically, all files should be owned by your user (ftp) account on your web server, and should be writable by that account. On shared hosts, files should never be owned by the webserver process itself (sometimes this is www, or apache, or nobody user). Please (contact your hosting company and have them) reset the file owner.