__group__ ticket summary component milestone type created _changetime _description _reporter
Otto42 4123 Proposal to improve the main navigation menu accessibility General defect 2019-01-29T18:14:14Z 2019-01-31T17:14:41Z "Several [https://www.w3.org/TR/wai-aria-practices-1.1/#html5-sectioning-elements HTML5 sectioning elements] automatically create [https://www.w3.org/TR/wai-aria-1.1/#landmark_roles ARIA landmark regions].
Landmark regions are exposed to assistive technologies and allow users to quickly find information in a page. Ideally, all content in a web page should be wrapped within landmark regions. For now, I'd like to propose to focus on the navigation menu.
In this specific case it's important to know that `` elements are mapped to an ARIA `role=navigation`. Therefore, `` elements are perceived by screen readers and users can jump to them using dedicated keyboard shortcuts.
In the wp.org network, some sections don't use `` elements at all. For example, the home page (screenshot from Safari and VoiceOver):
[[Image(http://cldup.com/t4blUGv__m.jpg)]]
Other sections do use navigation landmarks but not for the main menu. For example, the Themes section has two of them:
[[Image(http://cldup.com/IVXr0-FKBL.jpg)]]
Same in the Plugin section sub-pages:
[[Image(http://cldup.com/h7w1Zs2jNd.jpg)]]
For clarity, these are respectively:
- a `` element with a `role=""navigation""`: it was common practice to repeat the role even if redundant, to support old browsers assistive technologies
- a `

` element with a `role=""navigation""`, which is equivalent to a ``
Besides technical details, the most important navigation (the main one) doesn't use a navigation landmark. Wrapping the main menu in a `` element would be a good, simple, improvement.
Note: when in a page there are multiple landmarks of the same type, it's important to use an `aria-label` to help users to distinguish them. This is also what WordPress core and the bundled themes do.
Suggested:
- wrap the existing main menu markup in a ``
- where present, add to the secondary navigation an `aria-label=""Secondary menu""` (or any better wording)
- the toolbar already uses an `aria-label=""Toolbar""`, no need for any change
Optionally:
- modernize the markup: remove `role=""navigation""` and just use a `` element
Note about the wording:
When screen readers encounter a `` element or a `role=""navigation""`, they already announce ""navigation"": it's recommended to not use this word in the aria-label because it would be announced twice.
" afercia
Otto42 4184 Add a robots.txt disallow all rule to ps.w.org Version Control defect 2019-02-18T13:35:42Z 2019-02-19T08:42:24Z "Replace the contents of https://ps.w.org/robots.txt with:
`User-agent: *`
`Disallow: /`
" jonoaldersonwp
SergeyBiryukov 20 Possible for user's to break layout when adding forum posts Support Forums defect 2013-07-17T21:29:56Z 2019-02-11T01:43:15Z "When a user wraps text in their forum posts with ""

"" tags - The layout of the page breaks.
For an example of this see - http://wordpress.org/support/topic/please-ignore-just-testing-something?replies=1#post-4430248" siobhyb
SergeyBiryukov 4458 Intentionally/permanently archived forum threads should return a 410 status Support Forums defect 2019-05-16T10:53:24Z 2019-05-16T12:37:27Z When a forum thread is intentionally, permanently archived as a result of editorial/quality/spam decisions (e.g., see https://wordpress.org/support/topic/great-theme-alx/), the page should return a 410 HTTP status rather than a 404 status. jonoaldersonwp
SergeyBiryukov 2204 Forum RSS Feed Issues Support Forums defect 2016-11-03T19:01:18Z 2018-03-09T23:28:18Z "The RSS feeds generated by the new Plugin Directory platform have a number of drawbacks/defects compared to the feeds that were generated by the old platform.
1. When a new reply is posted to a topic:
* The ""forum-level"" feed (e.g. https://wordpress.org/support/plugin/media-library-assistant/feed) generates a copy of the initial post for the topic, with the initial date/time and author. This is almost useless; you have to go back to the forum to access the text of the update and see who posted it.
* The ""topic-level"" feed (e.g. https://wordpress.org/support/topic/importing-photoshop-iptc-data-into-wordpress/feed ) generates an update with the correct text, date/time and author.
* The email message generated for ""subscribers"" to the topic also has the correct information, but the message comes as plain-text so markup for code blocks, lists, etc. is lost.
2. When the original post in a topic was modified, the feed generates and ongoing stream of ""updates"" identical to the original except for the ""This topic was modified 2 weeks, 6 days ago by ..."" text. This makes it hard to identify topics with genuine updates.
3. When updates are posted to old topics (e.g. started 8 months ago), no RSS feed update is generated. It is hard to know when new activity occurs in an old topic.
Minor notes:
1. The subject line no longer includes the plugin name, which makes it harder to organize an archive by plugin.
2. The subject line no longer includes the post author, which would be fine if the actual author value was set correctly.
3. The subject line now identifies ""[Resolved]"" topics, but not any other status value.
In short, RSS updates should contain:
* The actual text of the update, with HTML markup
* The actual date/time of the update
* The actual author of the update
* A subject line that includes the plugin name and perhaps the current status in addition to the topic title.
" dglingren
SergeyBiryukov 4311 Forums: Add notice not to report vulnerabilities Support Forums defect 2019-03-21T20:43:08Z 2019-04-02T23:44:58Z "Sometimes people report 0-days in the forums. Perhaps we should add a notice not to report those and direct people to the right places.
Core: https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/
Plugins: https://developer.wordpress.org/plugins/wordpress-org/plugin-security/reporting-plugin-security-issues/
Props to @benlk for the idea!" Ipstenu
SergeyBiryukov 4403 Make -- posts missing the ID called comments Make (Get Involved) / P2 defect 2019-04-25T14:40:08Z 2019-05-08T23:46:21Z "When subscribed to a Make blog, the email sent when a post is published has a link called ""See all comments"", and it has a fragment ID of `#comments`. But there is no ID in the post named comments, so the link just takes you to the top of the post.
The other link, for commenting, is to `#respond`, which does exist and works fine.
Here is an example from the email
https://make.wordpress.org/core/2019/04/25/site-health-check-in-5-2/#comments" joyously
coffee2code 1424 Automate meta contributor badge assignment when receiving props Profiles defect 2015-12-01T19:41:01Z 2017-09-01T16:52:48Z Profile badges don't seem to automatically appear for all areas. My core and plugins badges appeared on my profile on their own (as far as I can tell), but my Speaker badge had to be added manually with some difficulty, and my Meta badge hasn't appeared at all after getting first props a few weeks ago (see [2016]). morganestes
coffee2code 4157 Add Tide Team Badge Profiles defect 2019-02-06T20:51:22Z 2019-03-22T17:17:04Z "Per discussion in Slack
Badges are made with CSS, here is the color needed
color
{{{
#1526ff
}}}
the Tide dashicon - thank you
This can be used as the Team badge & the Contributor badge please.
We will ask Marketing how to request the WordCamp stickers and pins
" cathibosco1
coffee2code 4280 Add schema markup to profile templates Profiles defect 2019-03-15T10:22:26Z 2019-05-03T09:13:07Z "The following code should be adapted and added to profile templates (values from https://profiles.wordpress.org/jonoaldersonwp/ used for reference).
{{{
}}}
NOTE: Optional nodes (like `worksFor`) should only be included when the relevant profile fields are populated.
NOTE: https://meta.trac.wordpress.org/ticket/4277 changes the title and description contents; values here should also change and use the new values specified in #4277.
NOTE: https://meta.trac.wordpress.org/ticket/4278 is required to retrieve/set social profiles in the `sameAs` array.
NOTE: If `name` is not set, fall back to `username`." jonoaldersonwp
coreymckrill 3003 Tagregator - Twitter resets settings randomly WordCamp Site & Plugins defect 2017-07-26T08:05:21Z 2017-11-29T21:42:19Z "Hello,
While I was working on these tickets: #2100 and #2907
I've noticed that my error log was getting grumpy and I saw this error:
`[22-Jul-2017 11:26:20 UTC] PHP Notice: Undefined index: consumer_key in tggr-source-twitter.php on line 152`
For some reason when you view the results page on the front end the twitter module bugs out randomly ( not all times ) and after that php error all the settings are getting reset so you are losing all login information etc.
I haven't been able to find out why.
@dipeshkakadiya is on it for a solution so we can implement it on gwtd3 new website as well.
Pointers for devs:
Grab the /trunk of Tagregator through svn, apply the extra patches to have the latest as they have not been implemented yet and then work on this ticket." xkon
coreymckrill 2894 Admin Flags: Internationalise the post-status-change label WordCamp Site & Plugins defect 2017-06-22T01:29:53Z 2017-10-24T17:48:50Z "When toggling a status in the Flag section, the toggle afterwards is missing the capitalisation, this is because it just sets the label afterwards to the command, rather than the textual label for it.
The attached patch adds internationalised Enable/Disable text which it switches in/out instead of using the command. It's hard-coded inline with the JS, as that's the format of the current JS and changing it up further probably deserves a rethink of the entire flagging UI and storage." dd32
coreymckrill 2923 Layout / Responsive issue on Opera for Android (Central Wordcamp) WordCamp Site & Plugins defect 2017-07-04T13:27:40Z 2017-10-24T17:48:50Z "Hi guy's,
This is the first time I write a ticket here. Do not hesitate to give me advice if it is not the usual way to fill a ticket.
I would like to bring to your attention that there are problems about the layout on the website https://central.wordcamp.org/ for Opera users on Android.
Here is an example on this screenshot, but there are probably others :
[[Image( http://i.imgur.com/Nz9xrbfm.png )]]
I posted this info on slack yesterday and @coreymckrill recommended me filling a ticket here.
Regards,
Jason
" jaz_on
dd32 4331 News archive templates should use canonical URL tags General defect 2019-03-26T12:41:28Z 2019-05-17T01:35:58Z "Individual news articles (like https://wordpress.org/news/2019/01/wordpress-5-0-3-maintenance-release/) correctly use canonical URL tags.
However, archives / the homepage / categories do not.
E.g., https://wordpress.org/news/, https://wordpress.org/news/page/2/, https://wordpress.org/news/category/testing/ should all have/use canonical URL tags." jonoaldersonwp
dd32 4364 Mixed case URLs in the theme directory break the display Theme Directory defect 2019-04-05T08:54:57Z 2019-05-17T02:12:45Z "See, e.g., https://wordpress.org/themes/twentyninetEEn/ vs https://wordpress.org/themes/twentynineteen/.
Looks like the JS process (see https://meta.trac.wordpress.org/ticket/4276) isn't handling that well. Hopefully, fixing #4276 resolves this.
Regardless, I'd like us to 301 redirect the mixed/uppercase version to the lowercase version. To contain the complexity of that, I'd be happy for it to just run on `^/themes/{{path}}/$`." jonoaldersonwp
dd32 1639 Themes Trac browser does not display UTF-8 text correctly Trac Q1 defect 2016-03-19T12:22:13Z 2019-01-23T04:41:17Z "On Core and Plugins Trac, UTF-8 text is displayed correctly:
https://core.trac.wordpress.org/browser/tags/4.4.2/tests/phpunit/tests/pomo/po.php#L115
https://plugins.trac.wordpress.org/browser/edit-parent-comment-id/tags/0.3/edit-parent-comment-id-ru_RU.po#L24
On Themes Trac that's not the case, looks like ISO-8859-1 is the default encoding there:
https://themes.trac.wordpress.org/browser/zalive/1.3.4/languages/ru_RU.po#L20" SergeyBiryukov
dd32 2508 bbPress and Meta Trac should be able to change closed tickets resolution reason Trac defect 2017-02-16T11:48:28Z 2019-01-23T05:17:55Z "If a ticket on bbPress or Meta Trac is closed with a particular resolution the resolution cannot be changed without reopening the ticket:
eg: bbPress Trac (Meta is identical):
* [[Image(https://cldup.com/zOd8gj9Bro.png)]]
BuddyPress and Core Tracs can change resolution withot reopening the ticket:
* [[Image(https://cldup.com/OVt4-n_X-A.png)]]
Taking a punt that the following code needs to be added to bbPress and Meta Trac ""workflow-*.ini"" files. I know bbPress and BuddyPress ""workflow-*.ini"" files are yet to be open sourced, presuming the same for meta:
Via: https://meta.trac.wordpress.org/browser/sites/trunk/trac.wordpress.org/conf/workflow-core.ini#L64
{{{
# Once the ticket is closed
# - reopen
# - change the resolution to something else
...
...
change_resolution = closed -> closed
change_resolution.name = change the resolution, set
change_resolution.operations = set_resolution
change_resolution.permissions = TICKET_EDIT_DESCRIPTION
change_resolution.default = -31
}}}
Aside: It wouldn't hurt to add the ""mark as duplicate"" section also ;)" netweb
dd32 2931 Plugin Directory: Incorrect parsing of code blocks Plugin Directory defect 2017-07-05T23:16:53Z 2018-06-11T03:00:12Z "The description for [https://wordpress.org/plugins/theme-check/ Theme Check] plugin appears to be parsed incorrectly (see the screenshot).
The first code sample lacks the code formatting. In the `readme.txt` both samples are formatted the same way:
{{{
Examples:
`define( 'TC_PRE', 'Theme Review:[[br]]
- Themes should be reviewed using ""define(\'WP_DEBUG\', true);"" in wp-config.php[[br]]
- Themes should be reviewed using the test data from the Theme Checklists (TC)
-----
' );`
`define( 'TC_POST', 'Feel free to make use of the contact details below if you have any questions,
comments, or feedback:[[br]]
[[br]]
* Leave a comment on this ticket[[br]]
* Send an email to the Theme Review email list[[br]]
* Use the #wordpress-themes IRC channel on Freenode.' );`
}}}" SergeyBiryukov
dd32 4245 HTTP requests to pingomatic.com should 301 to the HTTPS equivalent SSL defect 2019-03-07T09:59:15Z 2019-05-03T01:30:19Z "E.g.,
http://pingomatic.com/ should redirect to https://pingomatic.com/
http://pingomatic.com/stats/?cat=dog should redirect to https://pingomatic.com/stats/?cat=dog" jonoaldersonwp
dd32 4360 Trac throwing errors about missing or invalid form token/secure cookies on ticket updates Trac defect 2019-04-03T19:03:27Z 2019-04-04T07:19:45Z "Trac has been directing people to an error page when they try to submit comments or updates to tickets. I first seen this problem mentioned on March 30th.
The message reads `Missing or invalid form token. Secure cookies are enabled, you must use https to submit forms.`.
The submissions are coming from pages that are https in the browser though and cookies are enabled." williampatton
dd32 4468 Plugin Update Check API returns tested field without patch version Plugin Directory defect 2019-05-22T10:31:05Z 2019-05-22T22:16:43Z "When plugins specify `Tested up to:` in their `readme.txt`, the Plugin Directory will append the current patch version number as there should be no breaking changes. This seems not to be reflected in the Plugin Update Check API, causing WordPress Core to show incorrect compatibility info.
For example the plugin ''Contact Form 7'':
The [https://plugins.svn.wordpress.org/contact-form-7/tags/5.1.3/readme.txt readme.txt of the stable tag] has set `Tested up to: 5.2`
[https://wordpress.org/plugins/contact-form-7/ Plugin Directory page] shows `Tested up to: 5.2.1`
[https://api.wordpress.org/plugins/info/1.0/contact-form-7.json Plugins Info API 1.0] returns `tested: 5.2.1`
[https://api.wordpress.org/plugins/info/1.2/?action=plugin_information&request%5Bslug%5D=contact-form-7 Plugins Info API 1.2] returns `tested: 5.2.1`
Result from the Update Check API (`https://api.wordpress.org/plugins/update-check/1.1/`) (trimmed):
{{{
{
""plugins"": {
""contact-form-7/wp-contact-form-7.php"": {
""id"": ""w.org/plugins/contact-form-7"",
""slug"": ""contact-form-7"",
""plugin"": ""contact-form-7/wp-contact-form-7.php"",
""new_version"": ""5.1.3"",
""url"": ""https://wordpress.org/plugins/contact-form-7/"",
""package"": ""https://downloads.wordpress.org/plugin/contact-form-7.5.1.3.zip"",
""icons"": {
""2x"": ""https://ps.w.org/contact-form-7/assets/icon-256x256.png?rev=984007"",
""1x"": ""https://ps.w.org/contact-form-7/assets/icon-128x128.png?rev=984007""
},
""banners"": {
""2x"": ""https://ps.w.org/contact-form-7/assets/banner-1544x500.png?rev=860901"",
""1x"": ""https://ps.w.org/contact-form-7/assets/banner-772x250.png?rev=880427""
},
""banners_rtl"": [],
""tested"": ""5.2"",
""requires_php"": false,
""compatibility"": []
}
},
""translations"": [],
""no_update"": {}
}
}}}
Here, only `5.2` is returned for `tested`. This causes the WordPress Core update screen to show `Compatibility with WordPress 5.2.1: Unknown`.
Given that the [https://core.trac.wordpress.org/browser/trunk/src/wp-admin/update-core.php#L292 respective check in Core] hasn't been touched in 9 months, it seems that the Plugin Check API changed its behaviour." abrain
dd32 4326 Support forum URLs should enforce a trailing slash via a 301 redirect Support Forums defect 2019-03-26T12:04:42Z 2019-05-17T01:45:26Z "E.g., https://wordpress.org/support/view/plugin-committer/corylamleorg should 301 to https://wordpress.org/support/view/plugin-committer/corylamleorg/
https://wordpress.org/support/view/plugin-committer/corylamleorg/page/2 should 301 to https://wordpress.org/support/view/plugin-committer/corylamleorg/page/2/.
https://wordpress.org/support/view/no-replies should 301 to https://wordpress.org/support/view/no-replies/
" jonoaldersonwp
dd32 4325 Pagination and rel next/prev links should build from the canonical, not the request General defect 2019-03-26T11:57:37Z 2019-05-17T01:34:10Z "Pagination links on templates like https://wordpress.org/support/plugin/eshop/page/20/?sausage=dog carry the query parameter through.
These links should instead be constructed from the canonical URL tag, rather than from the query/request.
E.g., the link to page 19 on https://wordpress.org/support/plugin/eshop/page/20/?sausage=dog should be https://wordpress.org/support/plugin/eshop/page/19/.
Additionally, rel next/prev tags in the head also carry the query; these should be built from the canonical.
E.g., the rel prev/next links on https://wordpress.org/plugins/tags/facebook/page/3/?qEGgVZWOMY6QuASuwpvADg&ved=0CD0QFjAHOGQ&usg=AFQjCNE96Vqc6usb8znBhhw9tvxNe3pKUw should be https://wordpress.org/plugins/tags/facebook/page/4/ and https://wordpress.org/plugins/tags/facebook/page/2/ respectievely. " jonoaldersonwp
iandunn 2823 Improve IP Geolocation Results API defect 2017-05-11T20:00:07Z 2017-06-06T17:51:36Z "There are a couple problems with our current data set. They're not strictly related to each other, but I'm creating a single ticket for this because I'm guessing that the solution to both will be the same: switch from our current data source to a better one.
* Problem !#1: Incorrect IPv4 results. No data source will be perfect, but [several online database had correct results for instances where ours weren't https://make.wordpress.org/core/2017/04/14/nearby-wordpress-events/#comment-32448].
* Problem !#2: No IPv6 support. Without this, the results will quickly lose effectiveness. As of May 2017, [https://www.google.com/intl/en/ipv6/statistics.html#tab=ipv6-adoption IPv6 adoption is at 18% globally] and rising relatively fast. Some countries are as high as 32%.
It looks like our database was updated recently (March 2017), but I can't find any info on where the original data comes from. @dd32, @tellyworth, do either of you know? Do you have any thoughts on other potential sources?" iandunn
tellyworth 2467 Plugins not showing on plugin-install screen Plugin Directory Plugin Directory v3.0 defect 2017-02-02T15:23:22Z 2019-02-19T14:44:52Z Not sure if this is a Meta issue, nevertheless, it could be related to the plugins directory. I was doing a plugin search on plugin-install screen of a 4.7.2 site and got a strange behaviour: the search didn't return all the items available. The number is right – 5 items –, but I can only see 4 items on te screen: http://g.recordit.co/yMeHcCzUSY.gif alvarogois
tellyworth 4109 Skip to content link missing in many pages or not working properly General defect 2019-01-28T22:02:42Z 2019-02-15T08:14:14Z """Skip links"" are one of the most simple and better known ways to improve accessibility for keyboard users and assistive technologies users. They allow to bypass blocks of content that are repeated on multiple pages, typically: navigation menus.
They're implemented since years in WordPress core and the bundled themes. They're also part of the WCAG recommendation:
Success Criterion 2.4.1 Bypass Blocks
https://www.w3.org/TR/WCAG21/#bypass-blocks
In order to be effective, a skip link used to bypass the top navigation needs to:
- be the first focusable element in a page
- be revealed on focus
- point to the main content in the page
Far from pretending to be a complete analysis of all the .org network pages, I've gone through the main pages linked in the main navigation menus. To recap:
- Home: no skip link
- Showcase: no skip link
- Themes: no skip link
- Plugins: skip link is not the first focusable element
- Mobile: no skip link
- Support: skip link is not the first focusable element
- Get involved (Make): no skip link
- About: skip link is not the first focusable element and it doesn't appear on focus (conflicts with `clip-path: inset(50%);` inherited by social-icons.css)
- Blog: no skip link
- Hosting: no skip link
I realize the .org network is made of different templates coming from different sources and I guess it's a complicated setup. However, it would be great to make sure the skip to content link is actually present in all pages and works properly." afercia
tellyworth 4253 Plugins API `query_plugins` produces wrong number of results Plugin Directory defect 2019-03-09T14:02:29Z 2019-05-03T01:30:54Z "The `per_page` argument for the Plugins API `query_plugins` action seems to return the wrong number of results in some cases.
So, if you limit the `per_page` to 20, you only get 19 items back event though that there are more than 20 results available.
We are hitting this issue with the WP-CLI `plugin search` command, which shows the exact count of elements returned. See https://github.com/wp-cli/extension-command/issues/156 for the related issue." schlessera
tellyworth 4259 No Twitter Card Found Developer Hub defect 2019-03-11T17:50:55Z 2019-05-03T01:48:39Z "Hello,
There's no Twitter Card found for https://developer.wordpress.org/ on sub-pages.
{{{
INFO: Page fetched successfully
INFO: 6 metatags were found
ERROR: No card found (Card error)
}}}
https://cards-dev.twitter.com/validator
" sebastienserre
tellyworth 4306 Plugin Admin: Update Plugin Stats Report to use HelpScout Plugin Directory defect 2019-03-20T22:19:06Z 2019-05-17T01:19:18Z "Currently Stats_Report (plugins/plugin-directory/tools/class-stats-report.php) checks SupportPress
We've moved so we'll need to update those checks to use (I think) the API for HelpScout
https://developer.helpscout.com/mailbox-api/endpoints/conversations/list/" Ipstenu
DrewAPicture 1866 "Add a basic ""suggest an edit"" workflow to the handbooks plugin" Handbooks enhancement 2016-07-29T15:22:51Z 2019-02-22T17:20:57Z "We've talked about this quite a bit in the context of DevHub where User Contributed Notes are occasionally used as a feedback mechanism. Basically, we need a way for docs consumers to report problems or suggest edits of published documentation on .org.
The initial proposal would be to build or use something akin to [https://wordpress.org/plugins/post-forking/ Post Forking] on the front-end of handbooks and eventually other places like DevHub or HelpHub.
Personally I don't think an MVP has to be a ''complete'' solution, it mostly needs to cover the rift drawn between moving away from the Codex where any user could edit anything to the now largely closed systems on .org.
I think starting with the handbooks would be the way to go." DrewAPicture
Otto42 2699 Add a new role to the forums: plugin/theme support Support Forums enhancement 2017-04-07T14:55:18Z 2018-10-17T22:39:37Z "
Plugin and theme authors currently have the power to mark threads as resolved within their own support forum, which is great.
'''Problem description'''
However, some of the larger plugin/theme shops have a support team to help out on their own support forums. I think it would be useful to be able to recognize those people in the support forums, like we’re able to recognize authors.
'''Proposal'''
So what I would like to propose is adding a new role: Plugin/Theme Support. Everyone with this role should have rights to mark topics within their own support forum as resolved, and should not be affected by posting speed limitations for their own support forum. This role should also show in the forums as ‘Support’, similar to author.
The reason why I propose a new role, instead of adding the capability to the contributor role is because, in my opinion, they serve a different purpose. Let me explain.
A contributor is someone who helped your open source project forward. This can be by providing feedback, writing code, creating images, doing marketing or being a friend of the project, for example.
Someone working on support does contribute his/her (paid) time to your project and is in that way a contributor. However, I think there are more than enough valid use cases where you don’t want someone who contributed code (for example) once to be able to close support request on behalf of the author.
That’s why I think having a separate support role would be viable. It would show the community that this person is vetted and answering on behalf of the plugin/theme author.
'''Related ticket'''
This proposal is related to ticket #2598.
'''Managing support role'''
Of course, it should be possible for plugin authors to manage the list of support people. I see two reasonable ways to do so, which should be mutually exclusive.
One way is by adding the usernames to the `readme.txt` file, the same way contributors are currently added. The other way would be to add users the same way committers are currently added, on the Advanced View of the plugin.
'''Showing support staff'''
To be transparent about this, we’d probably also need a place to list people in the support role. This could be the Advanced View page, or even the plugin page itself.
" TacoVerdo
Otto42 3973 Search enhancement request so that HelpHub contents will be included in the result HelpHub enhancement 2018-12-03T16:19:16Z 2019-01-16T22:39:56Z "If you use the search bar on https://wordpress.org/support, you will see that it neither includes HelpHub articles nor excludes Codex ones.
I feel that we should well be
1. including HelpHub in it and
2. adding a tab for specific search
3. removing Codex indexing
Also, search bar should say ""Search documentation and forums"" or something along those lines and not just forums?
Releated discussion in Slack
https://wordpress.slack.com/archives/C02RP4WU5/p1543850975111100
" atachibana
coffee2code 4277 Profile template meta tweaks Profiles enhancement 2019-03-15T09:27:38Z 2019-05-03T02:28:07Z "- Change the `` content to: `{{Full Name}} ({{Username}}) - WordPress user profile | WordPress.org`. E.g., `Joost de Valk (joostdevalk) - WordPress user profile | WordPress.org`.
- Add and populate a `meta description` tag with the (sanitized) content of the `Bio` field, up to 160 characters (cutting off gracefully with an ellipses character).
- Add and populate open graph tags as follows:
{{{
}}}" jonoaldersonwp
coreymckrill 4243 Clarify Payment Gateway Account Settings for CampTix WordCamp Site & Plugins enhancement 2019-03-06T17:30:17Z 2019-03-21T17:44:28Z "The option ""None"" for Tickets >> Setup >> Predefined Account is unclear - this seems like there would be no payment gateway if that setting is chosen, which makes it unclear how you can access the custom gateway settings.
Changing this label to ""Custom Account"" or ""Local Payment Account"" would be clearer." nickkeenan
coreymckrill 2849 Add sessions list and other details to speaker pages WordCamp Site & Plugins enhancement 2017-06-05T15:08:50Z 2017-12-03T22:12:37Z For the new CampSite theme we had the idea to include a speakers bio page with an improved sessions list not only showing the session title, but also an excerpt as well as links to the slides and WordPress.tv video. We decided against a page template and rather add this additional markup to the post types plugin. Kau-Boy
coreymckrill 3122 Documentation for prefilling coupon field in CampTix via query string WordCamp Site & Plugins enhancement 2017-09-11T14:35:42Z 2017-09-22T18:45:00Z "To save time and avoid typos, it would be great to support a means of that prefilling the coupon field.
For example: city.wordcamp.org/tickets?coupon=2017volunteer
Volunteers, sponsors, speakers, organizers, scholarship recipients, and others rely on coupon codes, and this would enable organizers to ensure they get the coupon code right on the first try." mrwweb
netweb 2537 Support Forums: Audit Log for Mod Actions Support Forums enhancement 2017-02-27T19:46:42Z 2018-03-10T01:21:08Z "It would be helpful if the forums logged who marked a post resolved (or unresovled) as well as closed etc.
From a moderator perspective, this would help track down plugin developers (for example) who automate resolving tickets. It would also mean we'd know who to ping if someone closed a post without a comment.
Example:
* Marked Resolved by Mika 11 Jan 2017, 22:00
* Marked unresolved by Otto 11 Jan 2017, 22:30
or
* Closed by Jan 13 Feb 2017, 11:30
* Opened by Marius 14 Feb 2017, 00:13" Ipstenu
ocean90 668 Open-source News Theme General enhancement 2014-10-23T13:40:11Z 2018-06-15T07:38:36Z "While we were building the new bbPress theme we discovered that the WordPress theme live on https://wordpress.org/news/ would've been the best starting point. We now had to hack together stuff from various places.
Wouldn't it make sense to open-source that theme used at /news/ as well?" DeFries
tellyworth 1278 Plugins Install API: Add ability to order results API enhancement 2015-10-01T00:27:16Z 2018-02-01T05:34:47Z "Copied over from #wp12696:
Replying to [ticket:12696 apeatling]:
> It would be awesome if you could pass an ordering parameter to plugins_api() that would allow you to return a list of filtered plugins in a specific order.
>
> I'd love to be able to use the API to return a list of the most popular / newest / recently updated plugins on the repo that contain the tag ""buddypress"".
>
> Something like this would be awesome:
>
> {{{
> $plugins = plugins_api( 'query_plugins', array( 'tag' => 'buddypress', 'page' => 1, 'order' => 'popular' );
> }}}
>
> Even better, also allow search filtering:
>
> {{{
> $plugins = plugins_api( 'query_plugins', array( 'tag' => 'buddypress', 'search' => 'album', 'page' => 1, 'order' => 'popular' );
> }}}
>
> I'd be happy to implement this if I can get access to the API source on WordPress.org.
Reply from Otto:
> This wouldn't be terribly difficult to add to the API, but it's pointless until core supports doing it there and is able to request the ordering. So, moving to the plugins component.
Now that the arguments for `plugins_api()` have been [#wp34035 documented], paired with the fact that there are existing filters in `plugins_api()` for modifying arguments, I think there's now a more compelling case for implementing an 'orderby' (or similar) argument in the dotorg API." apeatling
tellyworth 2320 Global stats for GlotPress to identify possible future GTE Translate Site & Plugins enhancement 2016-12-08T18:31:29Z 2019-05-13T06:09:49Z "On some locales (like Catalan), most of the translations are done by 3-4 people (with 2 of them being GTE), even if according to https://translate.wordpress.org/locale/ca there are 10 GTE, and almost a 100 contributors.
This is a problem not only because it simply doesn't scale (with the amount of strings that themes & plugins have, 3-4 people are not enough), but also because is extremely hard for GTEs to identify ""active"" contributors to help and guide them so they become one day GTE, and for contributors to find active GTE so their strings get approved and don't stay forever as pending.
Ideally, there should be a way of ""filtering"" the teams page (https://make.wordpress.org/polyglots/teams/?locale=ca) with some kind of ""active"" filter, with active being a rule such as ""has translated/reviewed more than X strings (could be 0) in the last 3-4 months"".
That could help to really asses the health of a team, as you could quickly identify how many people is actively contributing to the project.
Also, if that filter included some kind of aggregated cross-project stats (similar to the ones you get ""per-project"" in translate.wp.org), pointing to the projects they contributed, it would be easier to ""measure"" the amount of contributions people is doing: I, as a GTE, am more in validating strings translated by someone who contributes regularly than strings from someone who only translated 1 string two months ago. Computing such a huge amount of stats won't be light in terms of resources, but in order to be useful, these stats don't need to be ""live"": a weekly update would be more than enough to get a sense of the current state.
This would also give extra visibility to the health of the team, on top of the ""activeness"" filter: knowing there are 100 people active when 99 of them only have translated one string isn't a sign of healthy at all.
" xavivars
tellyworth 815 Forums to Support Syntax Highlighting Support Forums Q1 enhancement 2015-01-15T15:05:02Z 2019-01-23T00:44:13Z "Quite often we're sharing code snippets to help our users when providing support. I would love to see the support forums support syntax highlighting. In it's current implementation it's not incredibly helpful to the end user.
Here's an example:
https://wordpress.org/support/topic/reorder-posts-in-collection?replies=4" nphaskins
tellyworth 2107 Prevent posting 10k lines of logs in replies, recommend Pastebin or GitHub gists Support Forums Q1 enhancement 2016-10-04T08:26:25Z 2019-01-23T00:44:18Z "To provide debugging information some users post their full logs in a reply. These can be up to 10k lines which makes reading the page really annoying because you have to scroll like 5 minutes.
Examples:
* https://wordpress.org/support/topic/qtranslate-x-compatibility-2/#post-8250157
* https://wordpress.org/support/topic/no-confirmation-email-received-2/#post-8235539
I suggest to prevent posting replies which have more than X chars/words/lines and to recommend using a service like Pastebin or GitHub gists." ocean90
tellyworth 2260 Support Forums - Support three backticks Support Forums Q1 enhancement 2016-11-21T17:37:28Z 2019-01-23T00:44:24Z Since people are getting more and more used to slack and markdown and the three backticks for code blocks, we should consider supporting that in bbPress Ipstenu
dd32 3718 Theme Directory: Allow minimum WP and PHP version requirement Theme Directory task 2018-07-17T09:31:18Z 2019-05-17T01:49:55Z "As a follow up to https://core.trac.wordpress.org/ticket/40934 and #2952, this ticket aims to add headers for version requirements to WordPress themes.
Themes do not always support all WordPress versions (for example Twenty Seventeen requires WP 4.7), and, while that is not a common practice seen so far, there are also themes that require a higher PHP version than 5.2. Core should highlight such incompatibilities, but as a prerequisite we need to allow theme authors to indicate required versions." flixos90