Plugin Directory: Tags for Version Compatibility, Official vs Unofficial

Plugins
1

Hello, I’m new to ClassicPress and testing it on localhost alongside BeaverBuilder.

I installed the ClassicPress Directory Integration but one thing that’s is making me hesitate is that I have no idea which plugins in the directory are compatible with the current version. As I understand version 2.x is a re-fork based on WordPress 6.2 so I would assume that plugins without updates since that was released in April may have compatibility problems.

Another thing is it would be helpful to know which plugins are “official” ClassicPress plugins as opposed to third party plugins,e.g. that a plugin was developed by the ClassicPress team or a member of the core ClassicPress team.

Thanks for the great work, enjoying testing the software out so far!

2

I don’t think you can presume there will be compatibility problems if a plugin has not been updated since we released version 2.0 of ClassicPress. While some core code obviously changed, most of it didn’t; if the plugin continued to work, then there’s nothing for the developer to fix.

As for which plugin developers have contributed to core code, I think the answer is almost all of them.

Here’s one of the things that makes ClassicPress so great; if there’s something you want to achieve but aren’t sure how, there’s plenty of people here willing and able to do so. Someone might even create a plugin just to help you out. It’s certainly been done several times before.