Yeah, this can happen as well like a plugin be pulled even if made for cp.
However a tag on WP, that says more than “it works”
An entry in our directory is a clear commitment as well.
If the devs intent is as genuine as it is when saying (maybe in a chat or support thread) “will be working for as long I can make it” or similar, which’s less reassuring than an actual “commitment” thru tags or pushing to our directory, they won’t mind adding the tag or even pushing to the dir.
This did happen already.
I do agree, though, we should ask and encourage plugin developers to list their plugin in the CP directory. This is the main indicator of their seriousness in supporting CP compatability.
I’ve had this discussion before with others, but will post here as a general comment. I view plugins as falling into two broad categories. Those where it doesn’t matter too much if they fail, and those that are absolutely critical. So, if an image slider on your site stops working it’s no big deal. If the payment gateway on your e-commerce site fails it’s serious… you are losing sales and losing money.
To me, one obvious place for developing paid plugins is in extensions for Classic Commerce. We really need fail-safe solutions for CC, and e-commerce site owners are more than happy to pay for reliable plugins in this area. They earn money from their sites and any outlay for a plugin is small change for them.
Yes, I agree. We are getting there slowly with Woo plugins becoming compatible with CP and developers using CC to power e-commerce stores.
Whatever helps people make money, that’s what you can make money on.
I totally agree with this.
It takes time and a lot of hard work to set up an income-generating website, but while that’s not happening yet, a budget-limited website owner (like me) has no choice but to depend on free plugins.
Of course, when enough money is coming in, I’ll be more than happy to support the developers by donating or by buying their premium products.
How about going even more basic? Just a simple contact form plugin to do the job? No frills, except maybe for anti-SPAM, like CAPTCHA. Many people don’t have a need beyond that.
I’ve checked out the Canuck theme, where the author has included a simple contact form, and i agree with his reasoning, that many folks don’t need the many features of a form builder.
I myself have installed Fluent Forms, but I only need it for a basic contact form. Too bad Contact Form 7 no longer supports WP 4.9…
@anon98749105 I have just pushed a stable version of plugin as you describe above to Git. I plan to submit for review on Monday.
If I understood you right, you would be using something like that (contact form), right? Do you mind if I inbox you so I can send to you the plug for a quick round of “user” testing?
Only if you want, no obligation.
The plugin has no reCaptcha as I consider that unnecessary and also problematic, it however includes a honeypot where bots get captured and stopped from submission.
(reCaptcha can be tricked by bots, so can honeypots, and human spammers can break any barrier as well, so mostly I do not really care a lot about reCaptcha and the likes. Never had issues with it, so far)
The plugin allows you to put a contact form on a page with name, subject, email and message - labels are customisable as well success and error messages + receiver email.
I think this could be a start for something simple, targeted, and easy to maintain. Thus could stay free, and perhaps some AddOns could be done as “pro” supplements (or I could add some filters for developers to add their own logic here and there).
Anyway, let me know if you up for some tests. I am stepping out an hour or two but will be back after.
Sounds like one I’d be interested in, so happy to do some testing.
Yes, I’ll be very happy to test it.
thanks!
EDIT: I don’t mind honeypot. One of the WP plugins I planned to use in CP was WP Armour, which is anti-SPAM using honeypot. But Shield Security already has anti-SPAM for comments, and Fluent Forms has its own honeypot, and so I didn’t install it.
Hi @anon98749105 - cool. @azurecurve already took it for a spin and found a BUG + added a feature request too, which I now will first tackle
I will then contact you inbox for another round of tests once I solved this/added feature.
Might be next week 
no problem… looking forward to it…
OK so with 7 voters we can’t motivate a developer to produce plugins 
I would have thought there would be more need behind this, but probably everyone is happy using (meanwhile maybe outdated without notification) WP Plugins.
I am closing the poll and will use this, plus Plugin dev help needed for possible dedicated CP plugin - #10 by Pross, "Must Have" Plugins List and What are your top 5 plugin needs? - #24 by Daniel to compiles a list, that shows:
Based on that I hope dev’s could then (proceed) picking what they want to develop, and users what they want to support, or snippets, or tutorials, whatever adequate.
The contact form plugin bespoken above has been submitted today to the repo (that one that provides remote updates).
As soon it went thru that, it will also be submitted to CP repo.