Category: Code Examples

Introduction to WordPress Security Keys
WordPress introduced security keys in the WordPress 2.6 Release to better encrypt information stored in the user’s cookies.

Security Keys will look like these examples, but don’t use the duplicate keys given below:

define( 'AUTH_KEY',         't`DK%X:>xy|e-Z(BXb/f(Ur`8#~UzUQG-^_Cs_GHs5U-&Wb?pgn^p8(2@}IcnCa|' );
define( 'SECURE_AUTH_KEY',  'D&ovlU#|CvJ##uNq}bel+^MFtT&.b9{UvR]g%ixsXhGlRJ7q!h}XWdEC[BOKXssj' );
define( 'LOGGED_IN_KEY',    'MGKi8Br(&{H*~&0s;{k0<S(O:+f#WM+q|npJ-+P;RDKT:~jrmgj#/-,[hOBk!ry^' );
define( 'NONCE_KEY',        'FIsAsXJKL5ZlQo)iD-pt??eUbdc{_Cn<4!d~yqz))&B D?AwK%)+)F2aNwI|siOe' );
define( 'AUTH_SALT',        '7T-!^i!0,w)L#JK@pc2{8XE[DenYI^BVf{L:jvF,hf}zBf883td6D;Vcy8,S)-&G' );
define( 'SECURE_AUTH_SALT', 'I6`V|mDZq21-J|ihb u^q0F }F_NUcy`l,=obGtq*p#Ybe4a31R,r=|n#=]@]c #' );
define( 'LOGGED_IN_SALT',   'w<$4c$Hmd%/*]`Oom>(hdXW|0M=X={we6;Mpvtg+V.o<$|#_}qG(GaVDEsn,~*4i' );
define( 'NONCE_SALT',       'a|#h{c5|P &xWs4IZ20c2&%4!c(/uG}W:mAvy<I44`jAbup]t=]V<`}.py(wTP%%' );

Benefits of WordPress ‘Salt’

Description:
The WordPress revisions system records each saved draft or published update. You can see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what changed in each revision—what was added, what remained unchanged, and what was removed. Lines added or removed are highlighted, and individual character changes are highlighted. Click the ‘Restore This Revision’ button to restore a revision.

Introduction to feature called revisions:
As stated above, ‘Revisions’ are posts stored drafts for future proofreading of blog posts. It creates multiple copies of the blog posts you are working on in your MySQL Database in plain English. So it naturally affects & increases the size of your WordPress’s MySQL Database size in megabytes.

Suggestion:
So I would suggest using the following code to successfully control the WordPress Post Revision Count to ultimate ‘3’ to stop it from growing above & creating clutter in your WordPress Database.

Specification:
Put the following code in your WordPress Installation’s wp-config.php file to limit the number of post-revision WordPress stores in the database. Old revisions are automatically deleted.

Introduction to WordPress’s New Functionality Automatic Background Updates:
WordPress 3.7 introduced automatic background updates to promote greater security and streamline the update process. By default, only minor releases are enabled for maintenance and security purposes, as well as translation file updates. The default behaviour in WordPress 3.7 is the automatic core update for minor versions, i.e., from 3.7.0 to 3.7.1. WordPress’s Graphical User Interface (GUI) does not offer configuration options. To change the behaviour, modify the wp-config.php file in your WordPress root installation or add filters to your theme’s functions.php file.

In WordPress, there are four types of automatic background updates:

1. Core updates
2. Plugin updates
3. Theme updates
4. Translation file updates

Core Updates
Core updates are subdivided into three types:

1. Core development updates, known as the “bleeding edge.”
2. Minor core updates, such as maintenance and security releases, e.g. 3.7.1
3. Major core release updates, e.g. 3.7

But If you want to turn them on or off selectively, here is how you will do it,

Turn them on or off via wp-config.php

Enable Automatic Updates for core – development, major, and minor versions