Making WordPress.org

{5} Accepted, Active Tickets by Owner (Full Description) (23 matches)

List tickets accepted, group by ticket owner. This report demonstrates the use of full-row display.

DrewAPicture (2 matches)

Ticket Summary Component Milestone Type Created
#620 developer.wordpress.org activity should appear on profiles Profiles enhancement 09/23/2014

Now that developer.wordpress.org is truly taking shape, it would be great if we could start thinking about how we can get contributor activity appearing on a person's profile.

So far we have the following activity:

  1. Contributions to the theme and plugin developer handbooks:

https://developer.wordpress.org/plugin/credits-2/ https://developer.wordpress.org/theme/credits/

  1. Submitting a user contributed note

For example: https://developer.wordpress.org/reference/hooks/wp_get_attachment_image_attributes/#comment-61

And possibly (when the workflow is sorted)

  1. Having a suggestion approved for changes to curated code reference content

It would be cool if contributors could get a badge under the following circumstances:

  • anyone who is listed as contributing to the handbooks
  • anyone who has 10 or more user contributed notes approved in the code reference

#1866 Add a basic "suggest an edit" workflow to the handbooks plugin Handbooks enhancement 07/29/2016

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 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.

Otto42 (2 matches)

Ticket Summary Component Milestone Type Created
#2699 Add a new role to the forums: plugin/theme support Support Forums enhancement 04/07/2017

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.

#3973 Search enhancement request so that HelpHub contents will be included in the result Support Hub enhancement 12/03/2018

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

SergeyBiryukov (2 matches)

Ticket Summary Component Milestone Type Created
#20 Possible for user's to break layout when adding forum posts Support Forums defect 07/17/2013

When a user wraps text in their forum posts with "<li>" 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

#2204 Forum RSS Feed Issues Support Forums defect 11/03/2016

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 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.
  1. 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.
  1. 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.
  1. The subject line no longer includes the post author, which would be fine if the actual author value was set correctly.
  1. 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.

coffee2code (2 matches)

Ticket Summary Component Milestone Type Created
#1085 Duplicate results in developer.wordpress.org search Developer Hub defect 06/16/2015

Go to developer.wordpress.org and search for add_attachment hook:


You'll get 5 duplicate results for a single hook:

#1424 Automate meta contributor badge assignment when receiving props Profiles defect 12/01/2015

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]).

coreymckrill (6 matches)

Ticket Summary Component Milestone Type Created
#3003 Tagregator - Twitter resets settings randomly WordCamp Site & Plugins defect 07/26/2017


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.

#2893 Admin Flags: Add Attendee filtering by Flag WordCamp Site & Plugins enhancement 06/22/2017

Currently the Camptix Attendee Flags doesn't allow filtering by flag, it'd be great if it did.

If you've got a flag Speaker set, you can't display all attendee's who are flagged as a Speaker unless you export it.

The attached patch adds the Flags as filter views on the Attendee post type listing.

#2894 Admin Flags: Internationalise the post-status-change label WordCamp Site & Plugins defect 06/22/2017

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.

#2923 Layout / Responsive issue on Opera for Android (Central Wordcamp) WordCamp Site & Plugins defect 07/04/2017

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 :


I posted this info on slack yesterday and @coreymckrill recommended me filling a ticket here.

Regards, Jason

#2849 Add sessions list and other details to speaker pages WordCamp Site & Plugins enhancement 06/05/2017

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.

#3122 Documentation for prefilling coupon field in CampTix via query string WordCamp Site & Plugins enhancement 09/11/2017

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.

dd32 (2 matches)

Ticket Summary Component Milestone Type Created
#2931 Plugin Directory: Incorrect parsing of code blocks Plugin Directory defect 07/05/2017

The description for 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:

`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]]
* 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.' );`

#3985 Out of bounds pagination requests to the plugin directory return a 'raw' 404 Plugin Directory defect 12/09/2018

E.g., https://wordpress.org/plugins/browse/popular/page/999/ returns a raw NGINX 404 page.

These should return standard WP 404 behaviour.

iandunn (1 match)

Ticket Summary Component Milestone Type Created
#2823 Improve IP Geolocation Results API defect 05/11/2017

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.

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?

netweb (1 match)

Ticket Summary Component Milestone Type Created
#2537 Support Forums: Audit Log for Mod Actions Support Forums enhancement 02/27/2017

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.


  • Marked Resolved by Mika 11 Jan 2017, 22:00
  • Marked unresolved by Otto 11 Jan 2017, 22:30


  • Closed by Jan 13 Feb 2017, 11:30
  • Opened by Marius 14 Feb 2017, 00:13

obenland (1 match)

Ticket Summary Component Milestone Type Created
#3539 Implement programmatic or settings changes that can be made to /plugins/ and /themes/ General task 03/30/2018

Implement programmatic or settings changes that can be made to /plugins/ and /themes/ to allow for individual theme or plugin pages to conform to the SEO Standards. Examples of this format will be:

(1) /themes/

  • Title - ? (For example, $Theme_Name, Free $Main_Theme_Category Theme - WordPress)
  • H1 - ?
  • Meta Description
  • ? (of note, we can not do all of the standards, we must start with the most important)

(2) /plugins/

  • Title - ? - $Plugin_Name, $Main_Plugin_Category Plugin - WordPress
  • H1 - ?
  • Meta Description
  • ?

More information on this can be found here: https://docs.google.com/document/d/13YxtyPNIz8798EpZT-AXh1SW2QNLGm9PBhtDJo7O16o/edit?usp=sharing

ocean90 (2 matches)

Ticket Summary Component Milestone Type Created
#668 Open-source News Theme General enhancement 10/23/2014

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?

#3748 Consider using WP-CLI for string extraction Translate Site & Plugins enhancement 08/07/2018

The last 8 months or so I have been working on a new WP-CLI 18n-command that makes it easier for WordPress projects to generate POT files.

Before that, I have been using makepot.php for years, but the tool is not intuitive and really flexible. Also, with JavaScript internationalization (#wp20491) and Gutenberg being a thing, it was clear that makepot.php wasn't the right tool for the job anymore.

Then there's also issues like #3601 and #wp42747 that make it harder for WordPress projects to really use makepot.php. Even for WordPress core I discovered two cases where strings were not extracted at all:

  • <strong>ERROR</strong>: "Table Prefix" can only contain numbers, letters, and underscores. (source: wp-admin/setup-config.php:262)
  • <strong>ERROR</strong>: "Table Prefix" must not be empty. (source: wp-admin/setup-config.php:258)

The WP-CLI command on the other hand does not have these issues.

That's why I propose switching to this new WP-CLI command for string extraction on WordPress.org infrastructure.

Some of the features:

  • Automatically detects plugins and themes and extracts file headers.
  • Allows extraction of only a specific text domain.
  • Supports JavaScript string extraction, even for JSX and ESNext.
  • Allows merging the resulting POT file with an existing one, e.g. one created by Babel.
  • Powerful rules to include/exclude specific directories (minified JS files, vendor, .git folder, etc.)
  • Supports extracting strings from WordPress core the same way it's done today with 4 different projects. See https://github.com/wp-cli/i18n-command/pull/69 for examples.
  • Can warn about strings with wrong placeholders, as well as misleading or missing translator comments. This could be very useful for core but also plugin/developers to improve polyglots UX.

Also, the command is extensively tested with Behat (with PHPUnit tests for some parts planned) and is already used in third-party projects.

With WP-CLI being an official WordPress project and this new command being superior to makepot.php in many ways, I think we have an opportunity to consolidate lots of things here, reduce the maintenance burden, and to make it easier for people to use WordPress I18N tools and to contribute to them.

It goes without saying that I'd love to help making this a reality, even if it means adding some new features to the command or fixing nasty bugs.

I'd suggest giving this command a go locally with some plugin, theme, or core to get a feeling for it.

Since we built it with WP-CLI 2.0 in mind, which should be released tomorrow, you might need to run the following commands to install it locally:

wp cli update --nightly
wp package install wp-cli/i18n-command

Alternatively, you can check out the GitHub repository and run it from within its directory (still requiring WP-CLI 2.0 though).

tellyworth (2 matches)

Ticket Summary Component Milestone Type Created
#2467 Plugins not showing on plugin-install screen Plugin Directory Plugin Directory v3.0 defect 02/02/2017

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

#1278 Plugins Install API: Add ability to order results API enhancement 10/01/2015

Copied over from #wp12696:

Replying to 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 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.

Note: See TracReports for help on using and creating reports.