Multisite site column output bug

Hello,

Could you try to deactivate the plugin with the “Complete deactivation” option enabled and then activate it again?

1. Enter the Antispam by Cleantalk plugin settings on your main website. (WordPress Dashboard -> Settings -> Antispam by Cleantalk -> Advanced settings)

2. Check the last settings “Complete deactivation” and save changes.

3. Deactivate the plugin on the Network “Plugins” page in WordPess Dashboard.

4. Then activate it.

5. Proceed to the plugin’s settings. (See item 1.)

Did it help?

Complete deactivation and reactivation did not resolve the issue. It did clear out the status message for all sites except the primary site, however the message is still duplicated across multiple columns. The message also returns for subsites as soon as I logged into them.

I also reverted the plugin back to 5.186 and the issue is not present in that version, but as soon as the plugin is updated to 5.187 the issue returns.

Looking into this locally, the apbct__manage_sites_custom_column_action() function on cleantalk-spam-protect/inc/cleantalk-admin.php:1244 is not passing any sort of validation or check on $_column_name which means the output is occurring on all custom columns.

The cleantalk status column does not have a specific name, but it can be validated against the int(0) with this replacing line 1261:

if ($_column_name == 0){
        echo $key_status_caption;
    }

• This reply was modified 2 years, 4 months ago by Kylen Downs.

Thankyou for your tip.

I passed the information to our developers.

We will contact you within 3 business days.

Your solution is correct. Thank you.

We added it to the code of our plugin. The fix version can be downloaded here: https://github.com/CleanTalk/wordpress-antispam/releases/download/fix-version/cleantalk-spam-protect.zip.

The changes made will also be included in the next release of the plugin.

Cheers! I appreciate the plugin and support, you guys are awesome!

As better solution than the one I provided, I might suggest actually naming the custom cleantalk column as I can foresee potential conflicts if the logic is left as targeting the int(0) value. By naming the column, it can ensure the if() statement targets the specific cleantalk column to avoid the echo outputting on a different custom column if that other column also happens to be unnamed.

Thank you for your kind words!

I’ve passed your details to our programmer staff.

It was these edits that our developer made to the plugin code.