plugin compatability
|
View:
New views
19 Messages
—
Rating Filter:
Alert me
|
 |
plugin compatability
by Rich Pedley
::
Rate this Message:
Sorry for sending this to the list, not sure where it should go.
The new plugin compatibility section on a plugin page. As suspected I have recently had someone mark mine as 'broken' with the latest version of WP. Luckily others have marked it as 'Works'. I knew that at some point this would happen, and feel that it isn't good for plugins authors. There appears to be no way for a plugin author to see why someone marked it as broken, it could be for any reason - possibly not even connected with the plugin itself! A lot of queries I get are from people that don't understand WP let alone the use of plugins... I therefore feel the usefulness to be reduced and may even be harmful for some developers. So I suggest it is either removed, or people are required to enter in a reason why it is broken and that the plugin author is given a chance to respond. As it stands a plugin could be marked as broken simply because someone doesn't like it! _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: plugin compatability
by scribu
::
Rate this Message:
Something that might help would be to allow only logged-in users to vote on
compatibility. -- http://scribu.net _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
|
|
|
Re: Fwd: Re: plugin compatability
by esmi at quirm dot net
::
Rate this Message:
on 05/11/2009 10:08 scribu said the following:
> Either that, or there should be only one button: "Works". +1 for this idea if it could be integrated with a display of the number of downloads for the current plugin version. esmi _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: Fwd: Re: plugin compatability
by Rich Pedley
::
Rate this Message:
> Sorry, I checked now and you do have to login to vote.
oh good ;) > Integrating the compatibility check with the support threads would be > useful: > When a user votes that a plugin is broken, he could post a message with > the > error he is experiencing. I would like that, and then link a list of 'broken' reports to the relevant post allowing plugin authors to respond, and for people to see the responces. > Either that, or there should be only one button: "Works". :) nice, I've started clicking that when I release a new version... which shouldn't really be allowed. (same as rating) _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: plugin compatability
by Lynne Pope
::
Rate this Message:
2009/11/5 <elflop@...>
> > So I suggest it is either removed, or people are required to enter in a > reason why it is broken and that the plugin author is given a chance to > respond. As it stands a plugin could be marked as broken simply because > someone doesn't like it! > Even with it requiring login before voting the system can be gamed. I don't understand why anyone would vote actually. They go to the repository, download the plugin, install, test, then... go back to the repository to vote??? That seems to be a stretch to me. I've downloaded two plugins since that new feature went up. Couldn't be bothered going back just to vote. If others are like me then the voting will only ever be done for ulterior reasons and honest reporting will be up the spout and washed away completely. For compatibility feedback to be really useful it should be provided as a rating from the WordPress plugin admin screen, not from a download page that genuine users may not go back to. IMO anyway ;) Lynne -- http://twitter.com/elpie/ _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: plugin compatability
by chrisbliss18
::
Rate this Message:
Good, I thought I was the only one that thought this.
This whole compatibility deal should be automated and all the information should come from a reputable source. If it can't be automated and verified, then it will never be truly useful. Chris Jean http://gaarai.com/ http://wp-roadmap.com/ Lynne Pope wrote: > Even with it requiring login before voting the system can be gamed. I don't > understand why anyone would vote actually. > They go to the repository, download the plugin, install, test, then... go > back to the repository to vote??? > That seems to be a stretch to me. > > I've downloaded two plugins since that new feature went up. Couldn't be > bothered going back just to vote. If others are like me then the voting will > only ever be done for ulterior reasons and honest reporting will be up the > spout and washed away completely. > > For compatibility feedback to be really useful it should be provided as a > rating from the WordPress plugin admin screen, not from a download page that > genuine users may not go back to. IMO anyway ;) > > Lynne > > wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: plugin compatability
by Lynne Pope
::
Rate this Message:
2009/11/6 Lynne Pope <lynne.pope@...>
> > > For compatibility feedback to be really useful it should be provided as a > rating from the WordPress plugin admin screen, not from a download page that > genuine users may not go back to. IMO anyway ;) > It's really late and that part was badly written. The "WordPress plugin admin screen" may confuse someone. I mean the plugin page of the WP admin user interface. Sorry if I caused any head-scratching there! This could be something as simple as a question when a user deactivates or uninstalls a plugin. Lynne -- http://twitter.com/elpie/ _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: plugin compatability
by Mohammad Jangda
::
Rate this Message:
>
> So I suggest ... people are required to enter in a reason why it is broken > and that the plugin author is given a chance to respond. As it stands a > plugin could be marked as broken simply because someone doesn't like it! +1. Ideally, we should give users the option to specify the versions of PHP, MySQL, browser, etc. that they're using. That would be an amazing help for plugin developers. But, at the very least, I think a free-form text field to provide some details about what's broken would also be a good alternative. For compatibility feedback to be really useful it should be provided as > a rating from the WordPress plugin admin screen According to the blog post announcing the plugin compatibility beta ( http://wordpress.org/development/2009/10/plugin-compatibility-beta/), seems like this is something that's planned: "Eventually, we’d like to gather this compatibility feedback from within WordPress, allowing you to vote directly from your plugins admin screen." -- Mohammad Jangda www.digitalize.ca | @mjangda _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: plugin compatability
by John Myrstad
::
Rate this Message:
Maybe broken report should ask for more info on configuration and not count
if not two users with the same configuration reports it as broken ? _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: plugin compatability
by Ken Newman-3
::
Rate this Message:
On 11/5/2009 4:31 AM, elflop@... wrote:
> Sorry for sending this to the list, not sure where it should go. > > The new plugin compatibility section on a plugin page. As suspected I > have recently had someone mark mine as 'broken' with the latest > version of WP. Luckily others have marked it as 'Works'. I knew that > at some point this would happen, and feel that it isn't good for > plugins authors. > > There appears to be no way for a plugin author to see why someone > marked it as broken, it could be for any reason - possibly not even > connected with the plugin itself! A lot of queries I get are from > people that don't understand WP let alone the use of plugins... I > therefore feel the usefulness to be reduced and may even be harmful > for some developers. > > So I suggest it is either removed, or people are required to enter in > a reason why it is broken and that the plugin author is given a chance > to respond. As it stands a plugin could be marked as broken simply > because someone doesn't like it! users see this as a valuable resource and participate. If we all go and mark plugins that work for us as working, then it will mitigate (outnumber) those with ulterior motives. No, you won't have a perfect score, but that's not the point. If most people choose not to participate, then it doesn't matter that someone tries to game the system: only people with issues vote and everything appears broken anyway. I feel that "cheating" is mute. We have to convince people that this resource is worth the effort of maintaining it. An optional comment box for developer messages is about the only useful thing suggested so far. Either crowd sourcing works here or it doesn't. _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: plugin compatability
by scribu
::
Rate this Message:
On Thu, Nov 5, 2009 at 5:58 PM, Mohammad Jangda <batmoo@...> wrote:
> +1. Ideally, we should give users the option to specify the versions of > PHP, > MySQL, browser, etc. that they're using. That would be an amazing help for > plugin developers. But, at the very least, I think a free-form text field > to > provide some details about what's broken would also be a good alternative. > All the additional (non-sensitive) info could be collected automatically when the voting is done from the user's install. That would be really neat. -- http://scribu.net _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: plugin compatability
by Doug Stewart
::
Rate this Message:
This is the same set of problems developers with apps in the Apple App
Store encounter, as well as Amazon. There's no real accountability for reviews in a direct sense. Amazon, at least, allows for 3rd parties to mark reviews "helpful" or "unhelpful" which seems to factor into which reviews the Amazon site presents as [semi-]authoritative. One thing to take a cue from the App Store on is suggested reviews at time of plugin deactivation. If you delete an app from your iPhone, a dialog pops up and says "Would you like to review this app before deleting?" or somesuch, giving users an opportunity to register their complaints in a 1-5 star fashion. I've actually seen a couple of WP plugins that seem to do something similar -- Woopra comes readily to mind as one, as does Intense Debate. So I guess I'm saying that the problems are not insurmountable but do bear some special consideration prior to implementation time, particularly in accounting for potential griefers. -- -Doug http://literalbarrage.org/blog/ _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: plugin compatability
by Eric Marden-2
::
Rate this Message:
On Nov 5, 2009, at 11:46 AM, Ken Newman wrote:
> We have to convince people that this resource is worth the effort of > maintaining it. An optional comment box for developer messages is > about the only useful thing suggested so far. Either crowd sourcing > works here or it doesn't. I agree with Ken here. I've been voting on both my own plugins and those I use all the time. Put the effort in, and it will be useful. Adding a comment box would be helpful at this point, but the real fun will come when you can do this in wp-admin/plugins.php - Eric Marden __________________________________ http://xentek.net/code/wordpress/ _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: plugin compatability
by Peter Westwood
::
Rate this Message:
First of all.
It is possible that in-the-admin plugin compatibility voting will come in a future version but it's not something for the current version of WordPress. We need to see how the voting goes and wait for us to get some data to look at. On 5 Nov 2009, at 19:21, Doug Stewart wrote: > One thing to take a cue from the App Store on is suggested reviews at > time of plugin deactivation. If you delete an app from your iPhone, a > dialog pops up and says "Would you like to review this app before > deleting?" or somesuch, giving users an opportunity to register their > complaints in a 1-5 star fashion. I think this is a really bad idea personally. This is like only asking your unsatisfied customers for a review. You will likely only get negative low scoring feedback - yes some of it will be constructive and helpful. The opportunity cost of installing a free app is so low that you are much more likely to do it even if it in no way fits your needs and therefore also much more likely to delete it as it cost you nothing. westi -- Peter Westwood http://blog.ftwr.co.uk | http://westi.wordpress.com C53C F8FC 8796 8508 88D6 C950 54F4 5DCD A834 01C5 _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: plugin compatability
by Lew Ayotte - Full Throttle Development
::
Rate this Message:
I was thinking the same thing...
One thing to take a cue from the App Store on is suggested reviews at > time of plugin deactivation. If you delete an app from your iPhone, a > dialog pops up and says "Would you like to review this app before > deleting?" or somesuch, giving users an opportunity to register their > complaints in a 1-5 star fashion. > Lew Ayotte Full Throttle Development, LLC 706.363.0688 478.246.4627 lew@... http://fullthrottledevelopment.com http://twitter.com/full_throttle http://twitter.com/lewayotte On Thu, Nov 5, 2009 at 2:21 PM, Doug Stewart <zamoose@...> wrote: > This is the same set of problems developers with apps in the Apple App > Store encounter, as well as Amazon. There's no real accountability > for reviews in a direct sense. Amazon, at least, allows for 3rd > parties to mark reviews "helpful" or "unhelpful" which seems to factor > into which reviews the Amazon site presents as [semi-]authoritative. > > One thing to take a cue from the App Store on is suggested reviews at > time of plugin deactivation. If you delete an app from your iPhone, a > dialog pops up and says "Would you like to review this app before > deleting?" or somesuch, giving users an opportunity to register their > complaints in a 1-5 star fashion. > > I've actually seen a couple of WP plugins that seem to do something > similar -- Woopra comes readily to mind as one, as does Intense > Debate. > > So I guess I'm saying that the problems are not insurmountable but do > bear some special consideration prior to implementation time, > particularly in accounting for potential griefers. > > -- > -Doug > http://literalbarrage.org/blog/ > _______________________________________________ > wp-hackers mailing list > wp-hackers@... > http://lists.automattic.com/mailman/listinfo/wp-hackers > wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: plugin compatability
by Ade Walker
::
Rate this Message:
I have two problems with the new compatibility vote system:
1. What does a less than 100% "Works" compatibility rating actually mean to the average plugin "searcher"? For example, go to http://wordpress.org/extend/plugins/google-sitemap-generator/ and you will see (at the time of writing this) that 4% of votes say "Broken". How am I, the "average plugin searcher" to interpret this? That the plugin is no good? That the plugin may not work? That it only works 96% of the time? It doesn't mean any of these, of course, but I'm not sure that such a rating helps me (the less tech-savvy user) to decide whether to use the plugin or not. 2. As mentioned by elflop, there is no way of knowing a voter's reason for marking a plugin as Broken. Is it really broken, ie throws an error, or is it just incompatible with another plugin? Or is the voter disatisfied with the functionality? Or did he/she just get out of the wrong side of bed that day? In other words, is the "customer" always right and, when he isn't, how does the developer undo the damage which has been done? On balance, I think it's a nice idea, with potential benefits of encouraging authors of neglected plugins to resume development or, at least, to update the readme.txt file. However, I think in reality there will be a large number of plugins - including popular and generally well though-of plugins (like the example I mentioned above) - having less than 100% compatibility ratings. And I don't think anyone, whether end-user or developer, benefits from this. :-/ 2009/11/5 <elflop@...> > Sorry for sending this to the list, not sure where it should go. > > The new plugin compatibility section on a plugin page. As suspected I have > recently had someone mark mine as 'broken' with the latest version of WP. > Luckily others have marked it as 'Works'. I knew that at some point this > would happen, and feel that it isn't good for plugins authors. > _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: plugin compatability
by Ken Newman-3
::
Rate this Message:
On 11/5/2009 5:34 PM, Ade Walker wrote:
> I have two problems with the new compatibility vote system: > > 1. What does a less than 100% "Works" compatibility rating actually mean to > the average plugin "searcher"? For example, go to > http://wordpress.org/extend/plugins/google-sitemap-generator/ and you will > see (at the time of writing this) that 4% of votes say "Broken". How am I, > the "average plugin searcher" to interpret this? That the plugin is no good? > That the plugin may not work? That it only works 96% of the time? It doesn't > mean any of these, of course, but I'm not sure that such a rating helps me > (the less tech-savvy user) to decide whether to use the plugin or not. > site. You'd rather them make the consensus more obvious. OK, so switch the display to read "Preliminary feedback: 96%" in small, then a big ol' fat "Consensus: GOOD TO GO!" That should solve that problem. Seriously, WordPress users are a pretty competent and fairly intelligent group. I'm sure that the 4% isn't turning many people off this plugin. 2. Undoing damage done. Yeah, this might be a concern, but as I understand it, Each version of wordpress, you get another fresh start! :) how great is that? _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: plugin compatability
by Eric Marden-2
::
Rate this Message:
On Nov 5, 2009, at 5:34 PM, Ade Walker wrote:
> you will see (at the time of writing this) that 4% of votes say > "Broken". How am I, > the "average plugin searcher" to interpret this? That the plugin is > no good? On Nov 5, 2009, at 5:50 PM, Ken Newman wrote: > but as I understand it, Each version of wordpress, you get another > fresh start! :) how great is that? It seems to me that this was the exact reason it rolls to 0% on a new version, is a good enough solution to the (valid) concerns raised by Ade. Besides, I'm not that attached to folks using my plugins... I release them so that I can take advantage of the auto-update feature, else I'd just leave them on my site and use my own source control server to package them for download. So if less than 100% turns them off from trying it, I won't be upset. - Eric Marden __________________________________ http://xentek.net/code/wordpress/ _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
| Free embeddable forum powered by Nabble | Forum Help |
