What the hell is going on ? FIX PLUGIN

nlpro!!! dear it’s very good that you are looking for solutions
but this plug-in has a premium branch and is asked for money and all the corrections should be made by the developers
so that not one self-respecting developer will not fix it as for today as I wrote already above
the cleaning function does not work normally, and also the branch 6.9.2. has more than 47 errors!
With all this, the 6.8.1 branch works correctly and has so many errors!
I think with the message 6.9.2. all the clearest topic can be closed!

kot41

If you prefer not to be notified by email of any follow-up replies please unsubscribe from this topic.

The itsec_cron_test task is also a single event task which receives the scheduled execution time as an argument.
If the result of the most recent itsec cron test event is negative the plugin changes the internal settings ‘use_cron’ to false and ‘cron_status’ to 0.

		Default		Cron	No Cron
		--------	-----	--------
use_cron	true		true	false
cron_status	-1		1	0

(Where cron_status -1 is undetermined, 1 is available and 0 is unavailable).

And this is exactly what I see happening. So why ?

It turns out that in the itsec_cron_test callback the following code is executed:

// Disable cron if the user hasn't set the use cron constant to true.
if ( ( ! defined( 'ITSEC_USE_CRON' ) || ! ITSEC_USE_CRON ) && ITSEC_Lib::use_cron() ) {
	ITSEC_Modules::set_setting( 'global', 'use_cron', false );
}

ITSEC_Modules::set_setting( 'global', 'cron_status', 0 );

Notice the comment which says that cron should be disabled when the user has NOT set the ITSEC_USE_CRON constant to true.
The condition that follows says: disable cron when the ITSEC_USE_CRON constant is not defined OR when it is set to false.

Earlier we saw in the changelog that cron is now the default scheduling mechanism.
(Which to me implicates that not defining the ITSEC_USE_CRON constant is equal to ITSEC_USE_CRON = true).
Also the default value of the internal ‘use_cron’ setting is true …
But the condition in the itsec_cron_test callback says disable cron when the ITSEC_USE_CRON constant is not defined. Clearly there is a contradiction here.

So to fix this issue (or prevent it from happening) simply add the line below to your wp-config.php file:

define('ITSEC_USE_CRON', true);

Even though it is the default (preferred) scheduling system, if you want the iTSec
plugin to KEEP using cron you HAVE to add the line above to your wp-config.php file.
Also keep in mind, after adding the above line to the wp-config.php file, it may take a day for the next itsec_cron_test task to kickoff and correct the situation.

Please note the above recommendation is for the 6.9.2 release only.
If anything changes in a new release I’ll try and update this topic.

Below a bit of history about the scheduling constants used by the iTSec plugin in the wp-config.php file. It will probably help understand my reasoning:

Old scheduling framework (pre 6.8.0 release):
—————————————————–
Default: page-load

Alternative: cron
Configured separately per module by defining the following constants in the wp-config.php file (and setting them to a true value):

File Change Detection: ITSEC_FILE_CHECK_CRON
Database Backup : ITSEC_BACKUP_CRON

Not defining these constants was equal to setting them to false.

New scheduling framework (6.8.0 release and newer):
———————————————————–
Default: cron
The former ITSEC_FILE_CHECK_CRON and ITSEC_BACKUP_CRON constants are deprecated.

A single constant is used (ITSEC_USE_CRON) which IMHO should only be used to prohibit the iTSec plugin to use the default cron system for scheduling module tasks.
Since cron is the default scheduling system it makes sense to assume that NOT defining the ITSEC_USE_CRON constant is equal to ITSEC_USE_CRON=true.
But as I explained in my previous post that does not seem to be the case in the iTSec plugin 6.9.2 release. IMHO this is a bug in the itsec_cron_test callback.

Alternative: page-load

I think it’s also important to mention that you should always try to use cron for any scheduling activities. There are several obvious benefits to using cron to handle scheduled tasks as opposed to on page-load. iThemes rightfully switched to using cron by default in the iTSec plugin.

• This reply was modified 6 years, 11 months ago by nlpro.
• This reply was modified 6 years, 11 months ago by nlpro.