After closer inspection what is happening is the Subscribe2 plugin is somehow replacing the serialized data for the BPS Pro plugin with its own plugin data. I spent quite a while looking at the Subscribe2 plugin code and cannot isolate exactly which code is the root cause of the problem. There are around 50 possible things in the code that could be causing the problem, but they are all intewoven throughout this plugin’s code so it is difficult to isolate the exact root source of the problem. I am not sure what the best way to handle this problem is. Will have to revisit this another day.
- This reply was modified 1 day, 10 hours ago by AITpro Admin.