WP-Config Generator

Just to reassure any user – this form is not set to gather any information you enter and no information is sent through the ether.

WP Config Generator

A form to create the WP Config file for clients
  • *The underscore already exists
  • When editing a post, WordPress uses Ajax to auto-save revisions to the post as you edit. You may want to increase this setting for longer delays in between auto-saves, or decrease the setting to make sure you never lose changes. The default is 60 seconds.
  • WordPress, by default, will save copies of each edit made to a post or page, allowing the possibility of reverting to a previous version of that post or page.
  • If you want to specify a maximum number of revisions, change false to an integer/number ( e.g. , 3 or 5).
  • The domain set in the cookies for WordPress can be specified for those with unusual domain setups. One reason is if subdomains are used to serve static content . To prevent WordPress cookies from being sent with each request to static content on your subdomain you can set the cookie domain to your non-static domain only.
  • Released with Version 2.5 , the WP_MEMORY_LIMIT option allows you to specify the maximum amount of memory that can be consumed by PHP. This setting may be necessary in the event you receive a message such as "Allowed memory size of xxxxxx bytes exhausted". This setting increases PHP Memory only for WordPress, not other applications. By default, WordPress will attempt to increase memory allocated to PHP to 40MB (code is at beginning of wp-settings.php ), so the setting in wp-config.php should reflect something higher than 40MB. WordPress will automatically check if PHP has been allocated less memory than the entered value before utilizing this function. For example, if PHP has been allocated 64MB, there is no need to set this value to 64M as WordPress will automatically use all 64MB if need be. Please note, this setting may not work if your host does not allow for increasing the PHP memory limit--in that event, contact your host to increase the PHP memory limit. Also, note that many hosts set the PHP limit at 8MB.
  • The WP_CACHE setting, if true, includes the wp-content/advanced-cache.php script, when executing wp-settings.php. By default, the current versions of WordPress have modified this WP_CACHE setting to simple enable caching concepts to be initiated by “other” code (plugins/custom functions) to hook into the Caching API that WordPress provides.
  • Use this, for example, if scheduled posts are not getting published. According to Otto's forum explanation , "this alternate method uses a redirection approach, which makes the users browser get a redirect when the cron needs to run, so that they come back to the site immediately while cron continues to run in the connection they just dropped. This method is a bit iffy sometimes, which is why it's not the default."
  • Added with Version 2.9 , this constant controls the number of days before WordPress permanently deletes posts, pages, attachments, and comments, from the trash bin. The default is 30 days:
  • Occasionally you may wish to disable the plugin or theme editor to prevent overzealous users from being able to edit sensitive files and potentially crash the site. Disabling these also provides an additional layer of security if a hacker gains access to a well-privileged user account.
  • This will block users being able to use the plugin and theme installation/update functionality from the WordPress admin area. Setting this constant also disables the Plugin and Theme editor
  • FORCE_SSL_LOGIN is for when you want to secure logins so that passwords are not sent in the clear, but you still want to allow non-SSL admin sessions (since SSL can be slow). define
  • This field is for validation purposes and should be left unchanged.