#2183 closed task (blessed) (fixed)
Add back meta information to plugin cards for homepage and search results
Reported by: | mapk | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Plugin Directory | Keywords: | |
Cc: |
Description
Let's add back the plugin meta information like: Author, Active Installs, Compatible with, and Last Updated to the Plugin Cards for the homepage and search results. Adding this information back is highly requested by community and important when searching for specific plugins.
Example of new UI: http://codepen.io/mapk/pen/jqxqbo
props @webdevmattcrom for helping with design.
Change History (15)
#2
@
8 years ago
How do you propose we handle the Author section where it has multiple authors?
For an example of that, check out this search.
The existing directory limits it to the first six listed contributors on this view.
The other option, is that we use the Plugin Author
field from the plugin, but we won't be able to use that to link to an archive/search of their plugins.
#3
@
8 years ago
@dd32 If I recall correctly, we did plan to use the Plugin Author. I assumed that the link on that Plugin Author would go to their Profile page, just like it does currently. Like from your search link, clicking the Author "WordPress.org" goes here:
https://profiles.wordpress.org/wordpressdotorg/
Isn't that possible with the Plugin Author field?
#4
@
8 years ago
Isn't that possible with the Plugin Author field?
Nope, the Plugin Author
field are these two lines from the readme.txt: https://plugins.trac.wordpress.org/browser/debug-bar/tags/0.8.4/debug-bar.php?marks=6,8 - There's no ability to link that to a user profile (in this case the name matches a WordPress.org username, but that's in the minority).
Where as the By: WordPress.org, Ryan Boren, Peter Westwood, koopersmith, Jon Cave, and others.
line on the existing directory is from this line: https://plugins.trac.wordpress.org/browser/debug-bar/tags/0.8.4/readme.txt?marks=2 (Each of which is a WordPress.org username, which has a profile, and is listed as the 'Authors' in the directory).
Personally, I think it should be the Plugin Author
field and we live with the fact it doesn't have an archive ability attached to it. Probably best to strip out the off-site link there though too.
This ticket was mentioned in Slack in #meta by tellyworth. View the logs.
8 years ago
This ticket was mentioned in Slack in #meta by edanzer. View the logs.
8 years ago
#7
follow-up:
↓ 9
@
8 years ago
The suggested text here of 4.5+ Compatible
doesn't feel right - That says to me "This plugin requires 4.5 or greater" rather than (the existing) "Compatible up to 4.5".
Should we rename this to Tested With 4.6.1
or Compatible up to 4.6.2
? We should also drop the +
either way.
#9
in reply to:
↑ 7
;
follow-up:
↓ 12
@
8 years ago
Replying to dd32:
The suggested text here of
4.5+ Compatible
doesn't feel right - That says to me "This plugin requires 4.5 or greater" rather than (the existing) "Compatible up to 4.5".
Should we rename this to
Tested With 4.6.1
orCompatible up to 4.6.2
? We should also drop the+
either way.
I think "Compatible up to 4.6.2" is the better route. "Tested with" doesn't quite provide the result that it's good or bad... just that it was tested.
#10
@
8 years ago
- Resolution set to fixed
- Status changed from new to closed
Closing this general ticket. Further enhancements and bug reports belong in new tickets.
#12
in reply to:
↑ 9
;
follow-up:
↓ 14
@
8 years ago
Replying to mapk:
Replying to dd32:
The suggested text here of
4.5+ Compatible
doesn't feel right - That says to me "This plugin requires 4.5 or greater" rather than (the existing) "Compatible up to 4.5".
Should we rename this to
Tested With 4.6.1
orCompatible up to 4.6.2
? We should also drop the+
either way.
I think "Compatible up to 4.6.2" is the better route. "Tested with" doesn't quite provide the result that it's good or bad... just that it was tested.
I guess that's the problem here, It's a Tested-With field, not a Compatible field, it can't really say whether it's good or bad..
"Compatible up to 4.6.2" says to me that "This isn't compatible with 4.7".
"Compatible up to 4.6.2+" just seems weird to me though, although would suggest that it's compatible with future versions too.
#14
in reply to:
↑ 12
@
8 years ago
Replying to dd32:
I guess that's the problem here, It's a Tested-With field, not a Compatible field, it can't really say whether it's good or bad..
"Compatible up to 4.6.2" says to me that "This isn't compatible with 4.7".
"Compatible up to 4.6.2+" just seems weird to me though, although would suggest that it's compatible with future versions too (though the developer in me says with minor x.y.z versions only, not major x.y versions)
If it's a tested field, then let's keep it saying 'tested' as you have it.
Love it! Let's make it happen.