I'm not accepting clients, so this is not a plug, I'm just saying this to frame where I am coming from. I do audits and WordPress code reviews for folks like junior college districts and largish content marketing sites; these range from load-testing and auditing the servers to examining the code quality of custom plugins and themes. I also do a lot of one-off and custom WP work for similar levels of clients.
Here's one element that you might find useful that I wasn't seeing in your reviews and that I don't see in a lot of reviews (because it's a pain in the butt to do the work to uncover):
looking at the hooks/ expandability of the plugin.
Like, you might audit the actual code quality and see how easy you think it might be to accomplish various customizations without, say, forking the plug.
I'm always surprised at the variability on this point among various plugins. Some plugins are filtering all kinds of things, some don't filter much at all. Some have really flexible and easy to modify CPTs, some have a ton of functionality hard coded. Some things have really baroque systems that would be easy to expand, but they are written using some crazy complicated architecture and you have to do hours of reading code to understand what you'd want to do.
A second thing that you might look at is the nature of "paid-ness" of the plugins. There is one business listing plugin (which I hate writing extensions for) that basically breaks the site if you don't re-up the subscription every year. There are other plugins that play nice-- you buy them once, and they work everywhere just fine and if they release a new major version you can buy it again. I don't like paid-for commercial stuff in GPL, but that's at least reasonable. What isn't reasonable are licensing schemes that do things like break local/staging/test/prod environments because the license is tied to some crazy thing like the URL.
Anyhow, it's a pretty site, so I wish you well.
Also to add on the code quality. It would be nice to know if the plugin properly registers styles and js. A ton of plugins arbitrarily inject to header or footer or inline or all three. One of the first things I do when we test a plugin is to see if it functions as needed and then I go see what wreckage it has caused to the html/perf. I then decide if I can live with myself.
To all Wordpress plugin developers. I’d easily pay 2-10x for higher quality considerations. Most plugins I find so cheap $ they take away my ability to complain or have a high expectation.
A free plugin isn't free if you have to slave through the code trying to sort somwthing out.
Code review/table structure, etc are highly requested featured right now. I'm working on it but I don't want to rush and put something wrong out there.
I don't understand your second point. Can you point me to the plugin which keeps breaking after the license expires.
Well, that, once again, is a pain in the ass to find.
For instance, there is this business listings plugin:
Personally, I found it a massive pain in the ass to use, but on top of that the add-on plugins are setup to work only with the specific version of the main plugin. So you can't update just one, you have to update them all, and you have to pay for them all each update== regardless of if there is an actual change to the software.
IMO, that's BS. The WordPress community, in general, disagrees with me, but whatever :D
Another example is that ACF used to (and maybe still does, I have an unlimited license and this doesn't seem to be a problem) set its license based on the URL of the site, so if I clone the site to another URL (like for staging on WPEngine) then the key is no longer functional and the plugin breaks.
Perhaps this used to happen in the past but not anymore.
I would call them plugin descriptions at best, but not reviews. Each of the bigger plugins like Gravity Forms or Advanced Custom Fields has so much functionality under the hood that I feel you're not even touching the surface.
Again, good and possibly useful description of each plugin, but they are not in-depth reviews.
I keep this in mind while reviewing plugins:
- Functionality of the plugin
- Any security issue the plugin has
- Support offered by the devs as well as the pricing
- Any weird gotchas or unexpected behavior with other plugins
Recently I posted an in-depth review of Carbon Fields and ACF.
Let me know what you think about it!
I only read through the ACF review, but I saw it a number of times there.
The reason I ask is I've always learned to put a space in front of the parentheses and a quick Google search also only yields sources that say to do so. That being said, I'm American and my Google sources seem to be mostly American sources. Are you British, perhaps?
Probably not, but it sounds like good spin.
Apparently there are others who have asked the same https://www.quora.com/Why-do-many-Indians-not-use-spaces-pro...
For the link, I don't use WP myself but if I ever do I'll find this post again.
After having spent hundreds of hours customizing that plugin, this was a devastating experience. I'm still leery of plugins and rarely install anything that could leave me stranded if it went unsupported one day.
At wpplugincheck we verify the plugin is clean by checking for any issues at wpvulndb. I'm also looking at automating plugin code testing.
In my plugin therefore tried to do things properly and avoid changing too much core functionality. It would be great if your site could review plugins on that sort of criteria.
My plugin (basically finished but not fully tested)) for anyone that's interested: https://github.com/SeanDS/alp
It could also help to know the spread. Why % are 4 stars? 5?
But that's just my opinion here.
Reviewing the quality of code is not exactly straightforward. Right now, I'm looking at how to address code review/table structure/api access of plugins while keeping the review concise enough so that non-techy Wordpress users can understand.
If that fails, a (hidden by default) box with the content could work. Have it open when they click some button or what not.