pronl

@rogejr

Please note what is stated in the FAQ section of the readme.txt file:

= Where can I get help if something goes wrong? =
* Official support for this plugin is available for iThemes Security Pro customers. Our team of experts is ready to help.

Free support may be available with the help of the community in the www.ads-software.com support forums (Note: this is community-provided support. iThemes does not monitor the www.ads-software.com support forums).

• This reply was modified 8 years, 4 months ago by pronl.

@rayuela1

Every plugin has issues …
Luckily most of them can be resolved.

• This reply was modified 8 years, 5 months ago by pronl.

@williamrperry

Absolutely correct.

It is also worth noting that the Database Backup module will only display the Backup Location setting (which includes the “Restore Default Location” button) when the Backup Method setting is NOT set to “Email Only”.
And since “Email Only” is the default value you might wonder where is that Backup Location setting ?

Showing/hiding the Backup Location setting depending on the Backup Method value selected makes no sense.
When selecting the Backup Method “Email Only” it still uses the Backup Location setting value to temporarily create the backup file so it can then be emailed.

The current show/hide behaviour is only causing confusion …

@jecho & @neco_69

What web server are you using (Apache, nginx, MS IIS) ?

@rayuela1

Ah right. That explains. The database backup(s) seem to be failing. Those .zip files with 0 bytes is an indication there is a problem with zipping the .sql backup file.

And due to a known bug the iTSec plugin sends an email even though the database backup creation process is failing to complete the zipping step. And because it fails it will retry over and over again …
Ultimately resulting in using up all diskspace on your hosting.

@mirgcire

Perhaps the WP_DEBUG constant is set to true in the wp-config.php file.
PHP does not perform echo commands by itself.
The scandir command is unable to find the folder and PHP simply signals a warning.
Weird it does not appear in the error_log. It should.

@rayuela1

Ok, I see. Do note that in order for the backup file to be emailed it needs to be created first.
So it looks like the backup file is not removed\deleted after sending the email.
Is it a .zip or a .sql file ? And what is the size of the file ?

The duplicate emails issue can easily be fixed by tweaking the iTSec plugin configuration.

• This reply was modified 8 years, 5 months ago by pronl.

@rayuela1

Are you actually receiving a backup email with a backup file attached to it ?

@beachlizard

Looks like your issue is not related to the Daily Security Digest bug introduced in the 5.6.3 release.

• This reply was modified 8 years, 5 months ago by pronl.

According to the 5.5.0 Changelog:

Enhancement: The Database Backups, Local Brute Force Protection, Network Brute Force Protection, Strong Password Enforcement, and WordPress Tweaks features are now active by default on new installations.

and

Enhancement: The WordPress Tweaks feature now uses the “Disable File Editor” setting by default on new installations.

So it’s up to you to disable the WordPress Tweaks “Disable File Editor” setting.
Not a bug.

@eehmke

Ok, so we have 2 issues here.

• An incorrectly translated string in German.
• The red WARNING should be a NOTICE with a different color.

Simply go to the better-wp-security plugin translation site and suggest a new German translation for this string. Yep, you can contribute to the translation yourself ??

Never mind the other issue. Minor cosmetic thing …

@beachlizard

Are you still receiving duplicate “Daily Security Digest” emails after updating to the 5.6.4 release ?

@hhgk & @byronyasgur

Updating to the 5.6.4 release should resolve your issue.

According to the 5.6.4 Changelog:

Bug Fix: Fixed issue that caused the daily digest email to be sent every day, even if no lockouts occurred and no file changes were found.

• This reply was modified 8 years, 5 months ago by pronl.

Updating to the 5.6.4 release should resolve the issue as initially reported in this topic (as well as some other related issues).

According to the 5.6.4 Changelog:

Bug Fix: Fixed issue that caused the daily digest email to be sent every day, even if no lockouts occurred and no file changes were found.

… or update to 5.6.4 (released today).
According to the 5.6.4 Changelog:

Bug Fix: Fixed issue that could prevent saving of File Change settings, resulting in an error messages of “A validation function for file-change received data that did not have the required entry for latest_changes.”

Oops, looks like something slipped through that should not have.
Try and remove any code lines related to the ‘latest_changes’ setting in the following 2 files:
(Create backup copies first !)

• core\modules\file-change\scanner.php:

$this->settings['latest_changes'] = array(
	'added' => count( $files_added ),
	'removed' => count( $files_removed ),
	'changed' => count( $files_changed ),
);

• core\modules\file-change\settings.php:

'latest_changes' => array(),

Works for me ??

• This reply was modified 8 years, 5 months ago by pronl.