Rhapsody348

I can confirm the fix works. Thanks for the quick response!

@carazo,

I can confirm your update fixed the problem. I have been running this update for a couple of weeks with no new entries in the error log. I ran a query to delete all the old failed entries so the tables are a reasonable size. Thanks for this fix!

Javier,

Thanks for your quick response. I will check out the link you reference. I was wondering if I was able to detect when your plugin hooks into the action scheduler so I may divert any requests that would contribute to the failed actions.

@hjogiupdraftplus – I tried the test file you posted in a previously deleted thread. This was on a multisite installation. It appears to operate properly.

@hjogiupdraftplus – I can confirm the behavior on multisite installations too. In a missing post it was pointed out to try deleting line 23 of the file listed below.

wp-content\plugins\all-in-one-wp-security-and-firewall\classes\wp-security-wp-loaded-tasks.php

//add_action('login_init', array($this, 'aiowps_login_init'));

I can confirm that commenting out that line corrects the problem on both stand alone and multisite installations. You may pass this information to your development team to incorporate a permanent fix.

I can confirm this fixes the problem. No errors generated anymore.

• This reply was modified 1 year ago by Rhapsody348.

I installed the zip and will report back later this weekend the results.

The cron runs once per hour. It checks if updates are needed to some custom fields that are added to custom posts created by the All In One Event Plugin, and if needed, makes the updates.

I am able to stop the error log additions by inserting if (isset($_SERVER[‘SCRIPT_FILENAME’])) per the annotated rule-proxy-comment-posting.php file below:

		//Preconditions for the rule
		if (isset($_SERVER['SCRIPT_FILENAME'])) $is_comment_form = (1 === preg_match('/\/wp-comments-post\.php$/i', $_SERVER['SCRIPT_FILENAME']));

@hjogiupdraftplus – I checked using phpmyadmin and the released column is missing in the wp_xx_aiowps_login_lockdown tables from a number of sites. I accessed the WP Security dashboard for sites that are showing in the error log and can confirm that this created the missing fields.

The multisite application I run has over 100 sites so doing this manually is tedious. My suggested fix is that for multisite that the plugin be updated so when the master site dashboard is opened, all sites are scanned for the proper database table structure and if needed any fields detected as missing or not modified per the latest plugin update be flagged. Should the scan find a table flagged, it would call a routine to properly change the database structure.

The first error is being generated during a cron job so the $_SERVER variables do not exist. I made the following patch to correct the problem until it is fixed in the next update. This is done by testing for isset($_SERVER[‘SCRIPT_FILENAME’]) on rule-proxy-comment-posting.php line 42

//Preconditions for the rule
$is_comment_form = (isset($_SERVER['SCRIPT_FILENAME']) && 1 === preg_match('/\/wp-comments-post\.php$/i', $_SERVER['SCRIPT_FILENAME']));

@hjogiupdraftplus – Thanks for the tip. The file was 644 and I tried to change to 654 in cPanel but was unable. I deleted the file and saved the rules again no problem. A new settings.php file was created with 644 rights. The original file must have gotten corrupted. This issue is resolved.

David,

I had an older app that was using mcrypt but have replaced it.

A suggestion – if you are going to check for a deprecated function in your code, prefix the check with an @ to prevent the error warning.

Just looked at the site. Are you generating the calendar events on the page using an ai1ec shortcode? The reason I ask is I note the address bar does not get updated as it does on some of my sites in the agenda view. Are you both the owner and web developer for this? Looks like a cool place ??

It may be a php version issue with the iCal exporter. What version php are you running? There are known problems if newer than 8.0 that I needed to apply some work around patches.

Can you post a link to the page that outputs the existing query? I may be able to determine the approach from that.