Testing version correctly checks for TLD.

By the way, the plugin front page at https://www.ads-software.com/plugins/stop-spammer-registrations-plugin/ shows “1 of 13 support threads in the last two months have been resolved.”, which is on the scary side. Marking this as resolved (or having it originally set as “not a support question”) would paint a more correct picture of the great support you’re offering for the plugin ??

I will review the questions and see if I can mark a few as resolved.

I have been here answering questions and trying to help, but I always assumed it wasn’t up to me to mark an issue as resolved.

thanks,

Keith

Ideally it isn’t, but these www.ads-software.com forums aren’t fine-tuned to provide the most effective support system. I’ve left some feedback on Core Trac, eg. #23072, #23704, #24145, #24065 and today #24532.

This thread gave me the idea for a new status “awaiting user’s verification for resolution”. The plugin author (or possibly anyone else) could set it when they have offered a possible resolution for the ticket. The user who opened the thread would get an email notification that, unlike the usual one, would contain a request for action to accept / reject the resolution, setting the ticket either as resolved or not resolved.

Plugin authors should have a checkbox for setting this status below their reply forms.

What do you think of this idea? Could it suit your workflow?

Regarding www.ads-software.com development, I noticed today that Core Trac now has headers and footers that match the rest of the site. That’s a good step forward towards a consistent service experience.

The next step would be to use the same login cookie as these support forums. At the moment if I’m logged into these forums, I still have to login to Trac to be able to view the report of my tickets at https://core.trac.www.ads-software.com/report/24.

Daedalon,

I like your thoughts on this. The support forums are very important to me, and I get lots of good user feedback when I keep up on them. It enhances my plugins and certainly contributes to their download rate.

Adding new tools will help. New fields and status codes will help. Even if some ideas are duds and rarely used, the others may prove to be very useful and popular.

Another thought: Plugin author’s should be notified by mail if someone leaves a comment, even if they have not checked the notify by mail box. Some of my older plugins have had comments and that I was not aware of. There could be an option on email notifications on the author’s account page, perhaps, which defaults to checked. This would allow a global notify option.

I would also like the ability to store a beta version in SVN. This would let users download my testing code directly from the plugins page. Perhaps there is a way to do this already in SVN, but it would have to be supported by the plugin repository pages. I frequently update the code in my plugins, but I resist updating the repository until the plugin has enough changes to justify it. Hundreds of users often download the test code from my website.

Keith

Events Manager includes a feature for updating directly to development versions from within the plugin. You might want to take a look at that feature, it might make your life easier and the plugin development cycles shorter.

You also have a development version available for anyone to download, hosted by WordPress at https://www.ads-software.com/plugins/stop-spammer-registrations-plugin/developers/. I’m not sure exactly how the versioning system works, and I don’t think there’s a possibility to tag a version as beta and have users test it while you’re adding new comments to the development version, but it’s a start and I’ve found this useful with testing Events Manager.

Regarding creating Core Trac feedback for these support forums:

1. I’ll create a ticket for adding the “awaiting user’s verification for resolution” status and functionality. Edit: #24536.

2. I like your ideas for those other ways of helping plugin development work. However, as I’ve kept myself clear of any plugin responsibilities so far, I’m not the best person for creating tickets for those. You could file a ticket almost by copy-pasting what you wrote (if those tickets don’t already exist), and then you’d be able to answer any additional questions based on your experience.

I’d be happy to hear when that’s done and to be cc’d in those tickets.