Autload issues for the wsal_local_file options

Hello @lukefiretoss

Thank you for posting this message. Can you please be more specific / elaborate on what the issue exactly is?

Thanks.

mysql> SELECT option_name, length(option_value) AS option_value_length FROM wp_options WHERE autoload='yes' ORDER BY option_value_length DESC LIMIT 10;
+--------------------+---------------------+
| option_name        | option_value_length |
+--------------------+---------------------+
| wsal_local_files_0 |             5931705 |
| wsal_local_files_5 |              809955 |
| wsal_local_files_2 |              128470 |
| wsal_local_files_4 |               57256 |
| wsal_local_files_1 |               57098 |
| wsal_local_files_3 |               32360 |
| rewrite_rules      |               30546 |
| itsec-storage      |               29135 |
| sep_exclude        |               13482 |
| cron               |               12117 |
+--------------------+---------------------+

• This reply was modified 4 years, 2 months ago by Luke Cavanagh. Reason: clarify wording

Hello @lukefiretoss

Those are settings from quite an old version of our plugin, when we still had file scanning integrated in the plugin. We have now taken out file scanning and it can be done via our other plugin, Website File Changes Monitor (which integrates with WP Activity Log).

You can safely delete those settings. Can I ask you what issues did you encounter because of these settings?

Looking forward to hearing from you.

@robert681
Should the local file options be deleted during a plugin update?

Hello @lukefiretoss

Yes, there were some update scripts in previous versions, however, it seems they did not work on yours.

I’ll see if we can include them again in other updates. May I ask what issues you had with these settings or you just noticed them and you want to know more about them?

@robert681

The issue came up when checking for which options had autoload set on them had the most values in them was all.

Thanks for the update @lukefiretoss