@karner42oliver what I meant was that we can trust the CP version to be OK - it was prepared by one of our own community member and developed to cater to the people wanting to continue to use Subscribe2 that they were using in the WP flavour. I also reviewed its code to be sure and found no issue with our version of it.
That sparked my curiosity because plugins do leave traces in the database, and other places. If the WP version uses functions we do not have, or has other tables or something like that - and those are not wiped at uninstall - that is a possible point of friction with CP version. Today I am at capacity, but I will try to test because I really am curious to see if my idea is correct. In that case we might need a compatibility layer for our version.
However meantime the suggestion to use another different plugin for now that the issue persists still stands because a live site can’t just sit still like that with that kind of list to get posts to. It’s not feasible.
It is important for me too - because as you noticed some plugins we do have are forks from WP.
Moreover since we will start to solve the e-commerce issue in the future (I think after Customizer is done) I feel I need to understand more of that. If we end up reforking Woo I want to know what happens when a plugin leaves renmants behind (like I suspect it’s happening here since Matt’s code is sound for CP). Imagine having a user that has Woo, installs our fork and should be able to have their shop working just by deactivating Woo and activating our fork, only to discover their shop crashes down. It’s delicate work and it has to be done with understanding.
Also since WP is diverging very fast, and people need plugins, the most efficient way to go forward is forking because it allows someone with plugin/theme xxx to install the fork for CP and simply go from there IMHO. It is less time consuming, and cost effective to fork at this stage.
And I do think that these new developments (plugins supposedly leaving stuff behind that causes conflicts) is something that started not long ago and results from WP going its own separate way even more.
Developing for both is not an issue, it is totally possible. And it’s not one or the other IMHO. But as CP developers we have to be aware of the issues that might pop up when a user transitions from a WP plugin to its CP counterpart.