Plugin Author
Paul
(@paultgoodchild)
Very strange indeed… never seen that before. The only thing I can suggest is that the options values haven’t been set as an array correctly. No idea how.
I’ve made a quick edit and uploaded it to the github account. Could you download this file and replace the one on your site?
https://raw.githubusercontent.com/FernleafSystems/Shield/develop/src/features/options-vo.php
Let me know how you get on with this sure.
I can’t explain why but the debug-site works now. Here’s my test steps:
1. Replaced my ‘options-vo.php’ with your edited file, the problem was gone!
2. Updated plugins (including your new v5.0.2), the problem did not return!
3. I also tried to uninstall and reinstall the plugin without any problem!
Not sure what your modified file do. Shouldn’t your file be overwritten when updating to v5.0.2? Why did the problem not come back then?
I’m still a bit worries for reinstalling and activating Shield v5.0.2 on the live site. Should I use your file first like on debug site?
Update:
I took the big step and updated the live site as well (after I carefully backed up the site). I installed v5.0.2 without your file and everything works fine.
I will leave it for some days now and watching if anything happens. Will come back and mark topic as solved afterwards.
Feel free to write some comments of what ground cause could be… db junk?
Plugin Author
Paul
(@paultgoodchild)
I’m not sure what would cause your options values to be populated with anything else other than the array, but the fix I put in place would ensure that the value is always going to be any array and wouldn’t throw up the previous error.
Glad it’s working for you.
