John Green
Forum Replies Created
-
@jetxpert
Thanks for your ongoing help and sharing your solution. I’ve made a completely different change. I moved the wp-admin and wp-login pages elsewhere so the hacking stopped and I no longer have any events at all. Instead of relying on the e-mails I will now be checking for events on a regular basis by logging into the admin back end. Although this is not a long-term solution, I don’t really have a need for the notification e-mails right now so I am instead going to wait for the plugin to update again and/or events to start again before pursuing this further.@jetxpert That’s interesting for several reasons.
Firstly, I saw the article at https://ww.wp.xz.cn/support/topic/database-logs-not-clearing/ which mentions ITSEC_USE_CRON but it didn’t make sense to me so I didn’t implement it. If that setting is essential, why is the email working intermittently?
Secondly, iThemes Security has already edited wp-config.php by adding the following based on my configuration, so why not that property as well if it’s so critical?
// BEGIN iThemes Security - Do not modify or remove this line // iThemes Security Config Details: 2 define( 'DISALLOW_FILE_EDIT', true ); // Disable File Editor - Security > Settings > WordPress Tweaks > File Editor define( 'FORCE_SSL_ADMIN', true ); // Redirect All HTTP Page Requests to HTTPS - Security > Settings > Secure Socket Layers (SSL) > SSL for Dashboard // END iThemes Security - Do not modify or remove this lineIf it is essential, perhaps it can be added by the plugin itself in the next upgrade?
@jetxpert debug.log is in the wp-content directory – it is only created after you activate debug logging and the first log entry is written. I redacted it because it can be different on each host. wp-content is just below the root directory of WordPress itself. Your webhost control panel should be able to take you straight to it.
To activate logging, you have to add (or edit) two lines in wp-config.php (which is in the WordPress root directory):
/** * This will log all errors notices and warnings to a file called debug.log in * wp-content (If Apache does not have write permission, you may need to create * the file first and set the appropriate permissions (i.e. use 660) ) */ define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true );See the Codex for details: https://codex.ww.wp.xz.cn/Editing_wp-config.php#Debug
and https://codex.ww.wp.xz.cn/Editing_wp-config.php#Configure_Error_LoggingYou shouldn’t leave this on your live server too long because it affects performance.
- This reply was modified 7 years ago by John Green.
I’ve had one log entry in debug.log so far (I’ve deleted part of the path):
[07-Jun-2019 10:35:55 UTC] PHP Notice: Undefined offset: 1 in /usr/www/..[deleted]../wp-content/plugins/better-wp-security/core/admin-pages/logs-list-table.php on line 192@jetxpert I didn’t enable the debug log so there is no debug.log file to review.
It actually stopped again soon after midnight today, so I’m going to enable the logs and keep an eye on it.
@jetxpert The e-mails started again at 21:51 GMT on May 5th. I’m not sure why. One thing I did was to go back into each of the settings pages and click ‘save’ again but this seems unlikely to be the fix as I did it several hours before they restarted. I’m still on version 7.3.3 (the latest free version).
@jetxpert Thanks for confirming it’s not just me.
I’ve been on 7.3.1 since March. I only upgraded to 7.3.3 yesterday, several days after the problem started. There definitely wasn’t an auto-update to 7.3.2 in between.
Like you, I see the logs in the admin showing that the plugin actually worked from May 31 up to today, but the e-mails haven’t gone out. I have other e-mails working from the site so it’s not the e-mail system.
As I’m using the free version, I don’t have access to Customer Support.
I’ll post here if I spot an improvement.
Also, LightShot (prntscr.com) isn’t working to show your screenshots – I just see a small white square. What were you trying to show?