[Resolved] Autoloaded data wpcf_checkbox_migration
This support ticket is created 4 years, 5 months ago. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
While doing some maintenance with WPEngine it came to our attention that an option name that might be related to toolset is added a lot of autoloaded data to DB queries.
The option name in question is wpcf_checkbox_migration
Initially I thought this was related to Contact Form 7 and deleted everything in the option before disabling autoload.
However, after coming accross wpcf-fields and reading some data inside that is related to our CPTs, I started to wonder if I didn't delete something that was required by Toolset.
I have a DB backup but could you provide more info about wpcf_checkbox_migration, what it does and why there's so much autoloaded data inside it?
Hello. Thank you for contacting the Toolset support.
"wpcf_checkbox_migration" option is tracking the conversion of checkbox and checkboxes fields when switching settings about storing zero in the database when unchecked.
And our Devs are agree that this option should not be autoloaded. Thank you for reporting this and I will report this issue in front of our Devs and they will make sure this option should not be autoloaded and fix the issue.
I got the news that there should be no problem but the only possibility that the problem could occur is if you go and edit the such checkbox/cheekbones field settings and change it settings to save 0 to database.
Also, I suggest, you can keep the "wpcf_checkbox_migration" option value unmodified and just make sure it should not be autoloaded as that issue I already reported to our Devs and it will be fixed soon and fix will be released with near future release of the Types plugin.
