Have a page on the website where plugins that support ClassicPress can be added and rated

[discobot]

Plugin compatibility is one of the biggest concerns for people considering the switch. If there was an easily findable place where plugin support for CP could be documented and rated (eg, 1-works great; 2-minor issues; 3-breaks), it would make it easier to select plugins for CP sites.

---

Read-only archive: GitHub · Where software is built

Author: Ray Gulick

Vote count: 60

Status: open

---

Comments

All plugins that worked with WP 4.9.8 should be working

~ posted by Laurence Bahiirwa

Understood, but that will change over time. Having a place CP users can go to find vetted plugins will be helpful to them.

~ posted by Ray Gulick

Good idea - I think this should be part of whatever the ClassicPress plugin directory ends up looking like.

~ posted by James Nylen

Like the idea.

~ posted by Voltaire

Yup!

~ posted by Ron

I would definitely support a plugins directory of sorts, however, I think this is directly related to how much support for GitHub (etc) that ClassicPress will have.

Ref: GitHub · Where software is built

Specifically, to differentiate this project from WordPress, to reduce work load, and to empower developers and agencies rather than creating another fiefdom of favoritism and corruption, I think a sort of “meta engine” or index of plugins would be more appropriate than a full blown WP.org style directory.

We were planning to do something similar for SlickStack, using the below website and their open source code as inspiration:

https://www.staticgen.com

See also:

https://githubreviews.com

This could be up and running in a matter of days, instead of years. Instead of e.g. whitelisting or blacklisting plugins or agencies that ClassicPress doesn’t like, which is the drama that has gone on for a decade at WP.org, it would entail something more along the lines of indexing every single compatible plugin on GitHub that currently supports ClassicPress (whether or not still maintained). I don’t think over moderating or filtering such an index is a good idea because it will only narrow the potential ecosystem of developers, cause drama, etc. Instead, the meta engine could integrate a reviews system, but not host the plugin code. To login and leave a review (or to login to ClassicPress.net) it could require GitHub Oath to ensure that real identities are being used, to avoid trolling and spam, and to eliminate fake reviews and extortion of plugin authors… the reviews could also have a merit-based requirement meaning that only reviews that directly address the plugin’s functionality, code, etc will be retained. Complaining about the agency’s customer service or other unrelated topics (“I’ll change my review if you do XYZ…”) could be disallowed…

~ posted by Jesse

[viktor]

This is an old petition. We have a working directory now and working on improving it. So this is no longer needed.

[joyously]

The idea in the petition is not in the directory we have, though.

[viktor]

If I’m not mistaken, there were numerous discussions about not having rating/review system for plugins. There was one a few days ago on Slack based on something you shared about WP reviews, I think.

[joyously]

Yes, I’m not talking about reviews. But the idea of having a place that lists a lot of plugins and whether they support CP or not is clearly not in the CP plugin directory. The directory is more of a list of plugins from people who already know about CP.
The proposed list would be a lot of work, but it is a lookup table for compatibility. I don’t see a good way to do it.
But I don’t think you should close the petition with a remark about an unrelated thing. Give a real reason.

[viktor]

@joyously

The proposed list would be a lot of work, but it is a lookup table for compatibility. I don’t see a good way to do it.

This actually was attempted:

Plugins Confirmed Working on ClassicPress v1

This list is out of date and no longer maintained. List of plugins

A few real reasons:

• This was attempted before and didn’t last.
• Our focus is on the directory and plugins built for CP.
• We don’t have resources to track compatibility with WP plugins, we shouldn’t do it either. That’s not our focus.