With Elementor requiring WP 5 for the new 2.8 version, I started thinking about how this affects me and how many other plugin developers may make this a requirement.
For plugins that previously worked just fine on ClassicPress, the requirement is really just a formality.
So I started thinking about ways around this. What I ended up doing was downloading the last version that supported WP 4 and modifying it.
I did two things. Firstly, I bumped the version number to a much higher value to prevent update notices, eg: Elementor 5.0.0 and some minor readme.txt changes.
Secondly, I added a check to see if the user is on ClassicPress or WordPress. If they are on WP, the plugin will not activate and they get a warning message in the admin panel.
This ensures people don’t try to install it on a WP site.
I have also installed the pro version of the File Manager plugin so developers can collaborate on a modification from within the ClassicPress admin panel itself.
For someone who wants a plugin that no longer works with CP for no valid reason, apart from the WP 5 requirement, it offers them a free way to get or request a modified plugin.
Of course it will never get new features or security updates. But the foundation is there for a developer to do that if a customer wishes.
It certainly beats fighting with GitHub to do a simple fork, without it wanting to document every single change you make. A Changelog file could always be added if necessary.
So it’s both a directory and a repository without all the red tape.