FILE SCAN exclusions failing

Hi Exo,

This type of error is probably due to some sort of failure during updating of the plugin. And yes it does prevent newly added exclusions from being saved.

If not already add the line below to the wp-config.php file:

define('ITSEC_DEBUG', true);

This should add an extra Debug menu item under the Security menu option.

Then navigate to Security > Debug.

Under the Settings section select file-change and then click on the Load button.

There should be 5 entries displayed which more or less look like below (Data types: 2 arrays, 1 object, 1 integer and a boolean):

{
"file_list": [],
"types": [],
"expected_hashes": {},
"last_scan": 0,
"compare_file_hashes": true
}

For visual aid I’ve intentionally left out (full) values for the first 3 entries.

If, by any chance there is a “notify_admin” entry (or any other unmatching) entries, try and remove those “entry”: value, combinations. Once removed click on the Save button.

Do the above at your own risk (preferably after making sure there is a recent database backup available).

+++++ To prevent any confusion, I’m not iThemes +++++

Ok, thank you for your feedback.

Was the “notify_admin” entry the only one that needed to be removed ?

I’ll have a quick look at the File Change update/upgrade code. With some luck I hope to be able to identify the bug that is causing this issue.

Oh I may need the following data:

In the Debug page Settings section select global and click on the Load button.

Please share the integer values displayed for “build” and “initial_build”.

• This reply was modified 3 years, 5 months ago by nlpro.

Curiously, in those settings I can see log_location & nginx_file are totally wrong (possibly from a site hosting change a year or so ago), not sure why they should remain wrong.

If you are currently using the Apache web server instead of Nginx an incorrect value for the global[‘nginx_file’] setting is no problem. Only when you switch back to using Nginx, the value for the global[‘nginx_file’] setting needs to be corrected.

Likewise an invalid path value for the global[‘log_location’] setting only needs to be corrected if the “How should event logs be kept” UI setting is set to either “File Only” or “Both”. You are probably currently using “Database Only” which is the recommended value due to a bug recently discovered in file logging.

Anyway both of these settings are categorized as “conditional-settings” in the module.json file of the global module.

I’m getting the same “A validation function for file-change received data that has an entry for email when no such entry exists.” whenever I tried to save the exclusions file. Was there any solution beyond the above?

I had to deactivate the plugin and delete it and then reinstall. Then it worked (no version change).