{"id":98,"date":"2021-05-11T00:32:17","date_gmt":"2021-05-11T00:32:17","guid":{"rendered":"http:\/\/iplocationblock.test\/changelog\/validation-timing\/"},"modified":"2021-05-11T11:55:32","modified_gmt":"2021-05-11T11:55:32","slug":"validation-timing","status":"publish","type":"codex","link":"https:\/\/iplocationblock.com\/codex\/validation-timing\/","title":{"rendered":"Validation timing"},"content":{"rendered":"

Normally, a plugin will be loaded at a certain phase during WordPress boot process and will typically do its jobs after init<\/code> action hook. It means that a plugin will be kept waiting until almost all plugins have finished to be loaded.<\/p>\n

But it\u2019s wasteful to give spams and attackers those resources of your server.<\/p>\n

The \u201cValidation timing<\/strong>\u201d at \u201cValidation rule settings<\/strong>\u201d can help to drastically reduce load on server especially against brute-force attacks.<\/p>\n

<\/p>\n

\u201cmu-plugins\u201d (ip-location-block-mu.php)<\/h3>\n

\"Validation<\/p>\n

When you select this mode as \u201cValidation timing<\/strong>\u201d, this plugin will install ip-location-block-mu.php<\/code> into your \/wp-content\/mu-plugins\/<\/code> which is for must-use plugins<\/a>. It means that this plugin will be loaded and execute validation prior to other typical plugins.<\/p>\n

Note that in case of multisite, ip-location-block-mu.php<\/code> will be called on every site but doesn\u2019t affect a site where IP Location Block is not activated.<\/p>\n

Restrictions<\/h4>\n

As you can find the order of execution in action reference<\/a>, mu-plugins are processed prior to theme setup. Consequently, the following two restrictions would be raised.<\/p>\n

    \n
  1. \n

    Custom filter hooks<\/a> in functions.php<\/code> does not work<\/strong>
    It is bacause the functions.php<\/code> in the theme folder would not have been parsed when this plugin do its jobs. In this case, you must<\/strong> put your own code into drop-in.php<\/code> which should be placed in the geolocation database folder. You can find drop-in-sample.php<\/code> as a sample in this plugin\u2019s folder, i.e. \/wp-content\/plugins\/ip-location-block\/wp-content\/ip-geo-api\/<\/code>. Please rename it to drop-in.php<\/code> and put it into your     Geolocation API folder<\/a> when you use it.<\/p>\n<\/li>\n

  2. \n

    Human friendly error page<\/a> is unavailable<\/strong>
    It is because the theme setup would not have finished when this plugin do its jobs. It means that when you select 404 Not Found<\/code> as Response code<\/strong>, 404.php<\/code> in your theme folder might not work. In this case, you must<\/strong> save your human friendly error page as a static file. If you want to show a human friendly page for blocked visitors, you must<\/strong> configure as follows:<\/p>\n