What the hell is going on ? FIX PLUGIN
-
When activated this is remove: IMAGE LINK
And whats happened to CLEARING the logs. I NEED TO CLEAR LOGS 25MB’s unnecessarily wasting my space !
You people better pull yr finger out and make this plugin friendly to us or most of us will leave go else where.
No point having this if you wont do the right thing by US who are the ones using it.
Get real, fix all the issues everyone is complaining about, get it right
-
@nlpro Thank you, that was soooo helpful, you are onto it, cheers buddy
I will try the ( 0 ) for 24hrs and see what happens. Theres 3 months of logs need to remove
Ok, that’s great. However …
Remember I mentioned something about a quirck in the plugin hooking into WP Cron ?
I was able to identify the cause and find a simple (non code) solution as well.
Before posting an explanation I think it is usefull to read 2 relevant quotes from the 6.8.0 changelog:- New Feature: Introduces a scheduling framework for handling events. Cron is now used by default, and will switch to using an alternate scheduling system if it detects an error. To disable this detection set ITSEC_DISABLE_CRON_TEST in your wp-config.php file.
- Important: The ITSEC_FILE_CHECK_CRON and ITSEC_BACKUP_CRON constants have been deprecated. Use ITSEC_USE_CRON instead.
The important parts from these 2 Changelog entries are ‘Cron is now used by default‘ (which means it is the preferred method of the iTSec plugin for scheduling tasks/events) and ‘Use ITSEC_USE_CRON instead‘.
So when the ITSEC_USE_CRON constant is not defined (at all) or defined and set to true (in the wp-config.php file) the iTSec plugin will use the WP Cron system for scheduling tasks/events. It’s important to note that NOT defining the constant seems to be equal to defining it and setting it to true (do note this is my personal opinion based on the available documentation so keep in mind I could be wrong).
Ok, so initially the iTSec plugin hooking into WP Cron seems to work fine without setting any related constant. But I noticed that after a short while the plugin stops hooking into WP Cron. The tasks scheduled by the iTSec plugin in WP Cron mysteriously disappear. Below is a list of the iTsec cron tasks I noticed initially:
Name Schedule Arguments itsec_cron_test False 1524611447 itsec_cron Daily file-change itsec_cron Daily clear-locks itsec_cron itsec-backup backup itsec_cron Daily purge-lockouts itsec_cron Daily purge-log-entries itsec_purge_logs* Daily*This is a leftover from an earlier iTSec plugin release which iThemes forgot to cleanup … Add the following line to your active theme functions.php file to get rid of it:
wp_clear_scheduled_hook( 'itsec_purge_logs' );As you can see iThemes switched to a more abstract scheduling system where all the tasks are named identically (itsec_cron) but the arguments passed to the cron task determines which task is to be executed.
Notice there is 1 task that has a different name: itsec_cron_test.
It seems iThemes includes this task to check whether the WP Cron system is functioning properly.Stay tuned, this post is to be continued …
The topic ‘What the hell is going on ? FIX PLUGIN’ is closed to new replies.
