Making WordPress.org

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

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

Clorith (1 match)

Ticket Summary Component Milestone Type Created
#3587 Default image when sharing forum topics on social networks Support Forums enhancement 04/20/2018

While sharing this forum topic on Facebook, I've noticed that differently from what happens when we share a /news blog post, there is not a default image with it. As a fallback, Facebook tries to get the first image, so the topic is displayed with the user avatar (in this case a random image).

Can we use some default image for these cases too?

DrewAPicture (1 match)

Ticket Summary Component Milestone Type Created
#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 (6 matches)

Ticket Summary Component Milestone Type Created
#4825 Add Enterprise content to wordpress.org General Q1 enhancement 11/05/2019

The Enterprise Growth council has been working on content geared toward enterprise decision-makers as a companion to the content the Growth Council created in 2018.

This is essentially a microsite that will live at wordpress.org/enterprise. All the content and designs required for this is here: https://drive.google.com/open?id=1lRpTt88b5bcdbiClPNZwmVP6w1q1QGFJ

and here: https://docs.google.com/spreadsheets/d/1uPa6m2hVb4Oz-qOvTEDn2FUC1-uBRVoDvohc7YNmYRY/edit#gid=0

Any additional coordination with the council can take place in #council-ops https://wordpress.slack.com/archives/C9GG77GRJ

#4123 Proposal to improve the main navigation menu accessibility General defect 01/29/2019

Several HTML5 sectioning elements automatically create 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 <nav> elements are mapped to an ARIA role=navigation. Therefore, <nav> 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 <nav> elements at all. For example, the home page (screenshot from Safari and VoiceOver):


Other sections do use navigation landmarks but not for the main menu. For example, the Themes section has two of them:


Same in the Plugin section sub-pages:


For clarity, these are respectively:

  • a <nav> element with a role="navigation": it was common practice to repeat the role even if redundant, to support old browsers assistive technologies
  • a <div> element with a role="navigation", which is equivalent to a <nav>

Besides technical details, the most important navigation (the main one) doesn't use a navigation landmark. Wrapping the main menu in a <nav> 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.


  • wrap the existing main menu markup in a <nav aria-label="Main menu">
  • 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


  • modernize the markup: remove role="navigation" and just use a <nav> element

Note about the wording: When screen readers encounter a <nav> 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.

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

#5277 Plugin Directory Admin: Add 'button' or method to trigger plugin syncs via wp-admin Plugin Directory enhancement 06/18/2020

In light of the June 18 outage where plugin updates aren't being properly synced, @otto42 pointed out it would be useful if the wp-admin page for a plugin had a button or such to 'force' an update. This would obviate the need for grabbing someone with systems access every time a plugin got stuck for whatever reason, and in cases like this would let us ensure security fixes were properly handled in a timely manner.

#5343 SVN: Update precommit hooks to block 'compressed' files. Plugin Directory enhancement 07/29/2020

Pre-commit hooks should block the following prohibited filetypes:

  • .phar
  • .zip
  • .7z
  • .tar.[whatever]
  • .rar
  • .dmg

Those are basically the common ones people make mistakes with. It should apply to themes and plugins SVN.

#4184 Add a robots.txt disallow all rule to ps.w.org Version Control defect 02/18/2019

Replace the contents of https://ps.w.org/robots.txt with:

User-agent: * Disallow: /

SergeyBiryukov (3 matches)

Ticket Summary Component Milestone Type Created
#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.

#4695 Add FAQPage schema markup to plugin pages Plugin Directory defect 08/20/2019

Plugin pages, like https://wordpress.org/plugins/autoptimize/, often contain FAQ content.

When this is the case, we should output FAQ schema markup, with an aim to encourage Google to show FAQ questions+answers in the search results (therefore achieving extra visibility and clickthrough-rates).


  • Add an additional node to the existing schema markup on plugin pages, for "@type": "FAQPage".
  • Add a mainEntity property to house the questions.
    • Loop through each question/answer, and construct a Question node with an acceptedAnswer property.

Example output

  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "What does the plugin do to help speed up my site?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "It concatenates all scripts and styles, minifies and compresses them, adds expires headers, caches them, and moves styles to the page head, and scripts (optionally) to the footer. It also minifies the HTML code itself, making your page really lightweight."
  }, {
    "@type": "Question",
    "name": "But I’m on HTTP/2, so I don’t need Autoptimize?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "HTTP/2 is a great step forward for sure, reducing the impact of multiple requests from the same server significantly by using the same connection to perform several concurrent requests. That being said, <a href="http://engineering.khanacademy.org/posts/js-packaging-http2.htm">concatenation of CSS/ JS can still make a lot of sense</a>, as described in <a href="https://css-tricks.com/http2-real-world-performance-test-analysis/">this css-tricks.com article</a> and this <a href="http://calendar.perfplanet.com/2015/packaging-for-performance/">blogpost from one of the Ebay engineers</a>. The conclusion; configure, test, reconfigure, retest, tweak and look what works best in your context. Maybe it’s just HTTP/2, maybe it’s HTTP/2 + aggregation and minification, maybe it’s HTTP/2 + minification (which AO can do as well, simply untick the “aggregate JS-files” and/ or “aggregate CSS-files” options). And Autoptimize can do a lot more then “just” optimizing your JS &amp; CSS off course 😉"
  }, {
    "@type": "Question",
    "name": "Will this work with my blog?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Although Autoptimize comes without any warranties, it will in general work flawlessly if you configure it correctly. See “Troubleshooting” below for info on how to configure in case of problems."

Sanitization concerns

All HTML tags should be stripped from fields, with the exception of the text property of an acceptedAnswer, which should:

  • Accept <a>, <strong> and <em> tags.
  • Disallow/remove any values/properties/attributes of these tags (other than the href attribute on <a> tags).
  • Remove invalid markup (e.g., an <a> without a closing </a>).

#3954 Support Forums: Add counters to moderation links Support Forums enhancement 11/24/2018

@sevlad suggested adding counters to moderation links that require an action, see an example screenshot.

For a quick access from any page, it might also be a good idea to add these links under "My Account" in admin bar, as a follow-up to [6303].

coffee2code (4 matches)

Ticket Summary Component Milestone Type Created
#4277 Profile template meta tweaks Profiles enhancement 03/15/2019
  • Change the <title> 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:
<meta property="og:type" content="profile" />
<meta property="og:title" content="{{Full Name}} - WordPress user profile" />
<meta property="og:description" content="{{Meta description}}" />
<meta property="og:url" content="{{URL}}" />
<meta property="og:site_name" content="WordPress" />
<meta property="og:image" content="{{Gravatar Large Image}}" />
<meta property="profile:username" content="{{Username}}" />

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

#4280 Add schema markup to profile templates Profiles defect 03/15/2019

The following code should be adapted and added to profile templates (values from https://profiles.wordpress.org/jonoaldersonwp/ used for reference).

<script type="application/ld+json">
            "name":"{{Page title}}",
            "description":"{{Meta description}}",
            "name":"Jono Alderson",
            "jobTitle":"Special Ops",
            "worksFor": {
            "sameAs": [
            "mainEntityOfPage": { "@id" : "https://profiles.wordpress.org/jonoaldersonwp/#webpage" }

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.

#5247 Import Hosting Handbook Markdown from Github Handbooks enhancement 06/03/2020

In #5240, a hosting handbook repo was created: https://github.com/wordpress/hosting-handbook

Now, I'm looking to figure out the best way to set up automated import of the Markdown there.

I noticed that both WP-CLI and Gutenberg are set up to auto-import, with slightly different ways of using the library plugin.

I've tested importing on a VVV meta repo, but am having trouble testing the styles.

Attached is a first draft of the WP-CLI handbook plugin ported to the hosting handbook. Not sure if it's better to go this route, or duplicate less code somehow.

dd32 (8 matches)

Ticket Summary Component Milestone Type Created
#1639 Themes Trac browser does not display UTF-8 text correctly Trac Q1 defect 03/19/2016

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

#2192 Change the name of "invalid" ticket resolution Trac defect 10/31/2016

Particularly for Trac newbies, "invalid" can feel like a bit of a put-down, even with an explanation of why the ticket is being closed.

Maybe not-a-bug, not-a-core-bug, or something of that nature would be better?

Bikeshedding welcome on this ticket.

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

#4245 HTTP requests to pingomatic.com should 301 to the HTTPS equivalent SSL defect 03/07/2019


http://pingomatic.com/ should redirect to https://pingomatic.com/ http://pingomatic.com/stats/?cat=dog should redirect to https://pingomatic.com/stats/?cat=dog

#5570 Plugins API - inconsistent results for short_description if being trimmed. Plugin Directory defect 01/10/2021

My plugin has a short description longer than 150 characters in the readme.txt (due to the ampersand being turned into it's HTML entity taking it over the limit).

However, the API request for 'plugin_information' returns different results for the short_description at different times of the day.

curl --location -g --request GET 'https://api.wordpress.org/plugins/info/1.2/?action=plugin_information&request[slug]=wp-user-manager&request[fields]=short_description'

It can return:

The most customizable profiles &amp; community builder WordPress plugin with front-end login, registration, profile customization and content restrict &hellip; Which is 150 chars if you don't count ' &hellip;'

But then a later call to the API returns:

The most customizable profiles &amp; community builder WordPress plugin with front-end login, registration, profile customization&hellip;

It feels like some double trimming is happening somewhere along the line.

#1078 Enable community-translator Translate Site & Plugins Q1 enhancement 06/10/2015

The community translator is a tool that enables front-end translations of strings for projects that use GlotPress to store their translations. It consists of a few parts:

  1. A front end script that highlights translatable strings, provides the UI to translate them, and submits the translations
  2. A backend plugin that prepares translation data for the script (based on gettext filters, for example)
  3. A GlotPress plugin to extend the api (gihub link coming soon)

Enabling it on WordPress.org would allow front end translations of rosetta, the plugin directory, the theme directory, etc. Demo: https://cloudup.com/iU6acgS9-x1



  • Do we want this to load for all users? Only previously active translators? something else?
  • Fix URLs in the translator plugin for wporg cdn
  • Design adjustments

props akirk hew julesaus

#4555 Plugin Directory Administration: Mass Email Tool Plugin Directory enhancement 06/26/2019

We need an admin-only tool that will allow us to mass-email plugins.

One exists but currently can only be run by a server admin, which limits usability.

1) Provide a list of plugins

2) Provide an email subject and body with basic substitutions

3) The tool would then email everyone with commit access and listed owner the message

Substitutions needed:


With Helpscout you can pre-fill everything BUT the body: https://docs.helpscout.com/article/119-pre-fill

So it doesn't look like we can use that for our bulk-mail tool.

If it's secure and has the capability to be given a usable UX, whatever tool is used on the back-end should be fine.

Limiting the number of plugins mailed at a time is also fine. Handling more than 50 of those at a stretch is usually pretty annoying anyway :)

#4487 Set the codex to readonly HelpHub task 05/31/2019

The codex has, for the most part, been migrated to HelpHub and DevHub now, and it's primarily a matter of setting up redirects, and clearing out spam that requires edits on the codex.

In light of this, I'm proposing we look at making the Codex readonly to avoid further edits that may fragment the imports already made, and to prevent spam edits. This doesn't need to be done in a week (although that would be nice ;) ), but setting a clear cutoff date seems reasonable and sets expectations.

I don't know how old our MediaWiki setup is so I don't know if we have these features, but my thought was:

  • Set it to readonly
  • Use the moderation feature to add users doing migration so they can keep adding redirects and removing the spam that's already there spread within the pages as it's discovered.

garrett-eclipse (1 match)

Ticket Summary Component Milestone Type Created
#5493 English Writing Error in Main Privacy Policy Page WordPress.org Site defect 10/31/2020

The privacy policy listed on your main privacy policy page (https://wordpress.org/about/privacy/) appears to be missing the words "will not" in the first paragraph under the section titled "Use of Personal Information".

I believe the sentence should be "We will not use the information you provide to register for an account, attend our events, receive newsletters, use certain other services, or participate in the WordPress open source project in any other way."

iandunn (1 match)

Ticket Summary Component Milestone Type Created
#5445 Planet feed does not have variety General enhancement 09/22/2020

planet.w.org feeds the news in Core's Events & News dashboard widget.

Right now it subscribes to a lot of early contributors who don't publish often, and some who are no longer active in the project.

Most of the remaining sites don't publish often either. The only ones that do are the Tavern and HeroPress, with the Tavern dominating the majority of the items in the feed.

What are some ways to solve that?

IIRC, changes to the feed need Matt's sign-off.

netweb (2 matches)

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

#4894 Add a BP GraphQL API Handbook to developer.buddypress.org buddypress.org enhancement 12/08/2019

As requested by @espellcaste you'll find attached to this ticket the needed edits to the bporg-developer theme to do so that he can start documenting the BP GraphQL API.

ocean90 (3 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?

#4535 Delete "Hello World" posts (and tidy up empty blogs) International Sites (Rosetta) defect 06/26/2019

Various Rosetta sites have a blog with a "Hello World" post. These should be deleted. Because of the incorrect hreflang setup on these sites, these posts cause an absolute SEO nightmare as Google seeks out their (non-existent) siblings across the whole network.

E.g., https://tg.wordpress.org/2012/08/23/hello-world/ https://tt.wordpress.org/2014/07/08/hello-world/ https://fao.wordpress.org/2016/07/20/hello-world/ https://dzo.wordpress.org/2015/02/24/hello-world/ https://kab.wordpress.org/2015/02/24/hello-world/ https://sa.wordpress.org/2011/07/26/hello-world/ https://hau.wordpress.org/2016/07/15/hello-world/ https://bre.wordpress.org/2015/07/17/hello-world/ https://ak.wordpress.org/2016/03/05/hello-world/ https://es-pr.wordpress.org/2016/03/05/hello-world/ https://rup.wordpress.org/2016/03/05/hello-world/

I don't have an easy way of finding them all from the outside-in - I'm hoping that these should be easy to round up?

It's also worth considering that in many cases, these are the only blog posts on these blogs. E.g., https://dzo.wordpress.org/news/, https://bre.wordpress.org/news/

When that's the case and we're removing them, can we also please:

#4289 Delete placeholder pages International Sites (Rosetta) defect 03/15/2019

The following legacy pages should be deleted, and 301'd to a sensible location. May also need removing from nav, if this isn't automatic. Likely going to need to do a few passes of these for ones I miss in the initial sweep... Might also be some duplicates.

'Welcome' flavours (should 301 to site root): https://fuc.wordpress.org/txt-welcome/ https://frp.wordpress.org/txt-welcome/ https://kab.wordpress.org/txt-welcome/ https://tg.wordpress.org/txt-welcome/ https://li.wordpress.org/txt-welcome/ https://nl.wordpress.org/txt-welcome/ https://tt.wordpress.org/txt-welcome/ https://la.wordpress.org/txt-welcome/ https://la.wordpress.org/txt-welcome/ https://si.wordpress.org/txt-welcome/ https://am.wordpress.org/txt-welcome/ https://es-cr.wordpress.org/txt-welcome/ https://lin.wordpress.org/txt-welcome/ https://sq.wordpress.org/txt-welcome/ https://es-ar.wordpress.org/txt-welcome/ https://oci.wordpress.org/txt-welcome/ https://br.wordpress.org/txt-welcome/ https://de-ch.wordpress.org/txt-welcome/ https://cn.wordpress.org/txt-welcome/ https://nb.wordpress.org/txt-welcome/ https://bre.wordpress.org/txt-welcome/ https://gd.wordpress.org/txt-welcome/ https://el.wordpress.org/txt-welcome/ https://hr.wordpress.org/txt-welcome/ https://cs.wordpress.org/txt-welcome/ https://es-mx.wordpress.org/txt-welcome/ https://is.wordpress.org/txt-welcome/ https://bg.wordpress.org/txt-welcome/ https://it.wordpress.org/txt-welcome/ https://it.wordpress.org/txt-welcome/logowordcamp/ https://lv.wordpress.org/txt-welcome/ https://bn.wordpress.org/txt-welcome/ https://ms.wordpress.org/txt-welcome/ https://fy.wordpress.org/txt-welcome/ https://uz.wordpress.org/txt-welcome/ https://ug.wordpress.org/txt-welcome/ https://as.wordpress.org/txt-welcome/ https://mr.wordpress.org/txt-welcome/ https://ky.wordpress.org/txt-welcome/ https://dv.wordpress.org/txt-welcome/

'Install' flavours (should 301 to the local 'download' page if it exists, and the root if not): https://rhg.wordpress.org/txt-install/ https://en-gb.wordpress.org/txt-install/ https://ku.wordpress.org/txt-install-2/ https://fr.wordpress.org/txt-install/ https://da.wordpress.org/txt-install/ https://li.wordpress.org/txt-install/ https://el.wordpress.org/txt-install/ https://eu.wordpress.org/txt-install/ https://srd.wordpress.org/txt-install/ https://so.wordpress.org/txt-install/ https://so.wordpress.org/txt-install/ https://kab.wordpress.org/txt-install/ https://tw.wordpress.org/txt-install/ https://fi.wordpress.org/txt-install/ https://haz.wordpress.org/txt-install/ https://de-ch.wordpress.org/txt-install/ https://os.wordpress.org/txt-install/ https://es-ar.wordpress.org/txt-install/ https://mr.wordpress.org/txt-install/ https://es-mx.wordpress.org/txt-install/ https://es-co.wordpress.org/txt-install/ https://gl.wordpress.org/txt-install/ https://nn.wordpress.org/txt-install/ https://jv.wordpress.org/txt-install/ https://mk.wordpress.org/txt-install/ https://fy.wordpress.org/txt-install/ https://id.wordpress.org/txt-install/ https://ido.wordpress.org/txt-install/ https://ms.wordpress.org/txt-install/ https://sw.wordpress.org/txt-install/ https://ca.wordpress.org/txt-install/ https://kn.wordpress.org/txt-install/ https://azb.wordpress.org/txt-install/ https://sq.wordpress.org/txt-install/ https://tl.wordpress.org/txt-install/ https://zh-hk.wordpress.org/txt-install/ https://es-cr.wordpress.org/txt-install/ https://pl.wordpress.org/txt-install/ https://ko.wordpress.org/txt-install/ https://oci.wordpress.org/txt-install/ https://ky.wordpress.org/txt-install/ https://fa-af.wordpress.org/txt-install/ https://th.wordpress.org/txt-install/ https://bn.wordpress.org/txt-install/ https://as.wordpress.org/txt-install/ https://pan.wordpress.org/txt-install/ https://az-tr.wordpress.org/txt-install/ https://lin.wordpress.org/txt-install/ https://vi.wordpress.org/txt-install/ https://fr-be.wordpress.org/txt-install/ https://ka.wordpress.org/txt-install/ https://xho.wordpress.org/txt-install/ https://hu.wordpress.org/txt-install/ https://fr-ca.wordpress.org/txt-install/ https://is.wordpress.org/txt-install/ https://dzo.wordpress.org/txt-install/ https://sv.wordpress.org/txt-install/ https://ko.wordpress.org/txt-install/ https://sr.wordpress.org/txt-install/ https://co.wordpress.org/txt-install/ https://bre.wordpress.org/txt-install/ https://hr.wordpress.org/txt-install/ https://hr.wordpress.org/txt-install/clean-install/ https://hr.wordpress.org/txt-install/upgrade/ https://gu.wordpress.org/txt-install/ https://km.wordpress.org/txt-install/ https://ar.wordpress.org/txt-install/ https://fa.wordpress.org/txt-install/ https://it.wordpress.org/txt-install/ https://su.wordpress.org/txt-install/ https://tuk.wordpress.org/txt-install/ https://sa.wordpress.org/txt-install/ https://bs.wordpress.org/txt-install/ https://kir.wordpress.org/txt-install/ https://yor.wordpress.org/txt-install/ https://br.wordpress.org/txt-install/ https://nb.wordpress.org/txt-install/ https://tt.wordpress.org/txt-install/ https://ta.wordpress.org/txt-install/ https://uk.wordpress.org/txt-install/ https://snd.wordpress.org/txt-install/ https://arq.wordpress.org/txt-install/ https://tg.wordpress.org/txt-install/ https://twd.wordpress.org/txt-install/ https://eo.wordpress.org/txt-install/ https://ur.wordpress.org/txt-install/ https://hr.wordpress.org/txt-install/clean-install/ https://ug.wordpress.org/txt-install/ https://bcc.wordpress.org/txt-install/ https://khk.wordpress.org/txt-install/ https://ory.wordpress.org/txt-install/

'Themes' themes https://ml.wordpress.org/Themes/

'Sample page' variants https://snd.wordpress.org/sample-page/ https://tzm.wordpress.org/sample-page/ https://rup.wordpress.org/sample-page/ https://az-tr.wordpress.org/sample-page/ https://os.wordpress.org/sample-page/ https://lin.wordpress.org/sample-page/ https://twd.wordpress.org/sample-page/ https://fur.wordpress.org/sample-page/ https://sa.wordpress.org/sample-page/ https://pan.wordpress.org/sample-page/ https://la.wordpress.org/sample-page/ https://as.wordpress.org/sample-page/ https://bre.wordpress.org/sample-page/ https://fuc.wordpress.org/sample-page/ https://tt.wordpress.org/sample-page/ https://azb.wordpress.org/sample-page/

'Releases' variants https://cs.wordpress.org/releases/

'Contact' variants https://es-pr.wordpress.org/contact/ https://ur.wordpress.org/contact/ https://kal.wordpress.org/contact/ https://eu.wordpress.org/argitaraketak/ https://dzo.wordpress.org/contact/ https://scn.wordpress.org/contact/ https://ps.wordpress.org/contact/ https://es-mx.wordpress.org/contact/ https://km.wordpress.org/contact/ https://tah.wordpress.org/contact/ https://ta.wordpress.org/contact/ https://snd.wordpress.org/contact/ https://kir.wordpress.org/contact/ https://sna.wordpress.org/contact/ https://dv.wordpress.org/contact/ https://rhg.wordpress.org/contact/ https://mlt.wordpress.org/kuntatt/ https://frp.wordpress.org/contact/ https://yor.wordpress.org/contact/ https://arq.wordpress.org/contact/ https://sa.wordpress.org/contact/ https://oci.wordpress.org/contact/ https://ido.wordpress.org/contact/ https://lo.wordpress.org/contact/ https://rup.wordpress.org/contact/ https://la.wordpress.org/contact/ https://fao.wordpress.org/contact/ https://kn.wordpress.org/contact/ https://me.wordpress.org/contact/ https://os.wordpress.org/contact/ https://li.wordpress.org/contact/ https://twd.wordpress.org/contact/ https://es-ar.wordpress.org/contact/ https://as.wordpress.org/contact/ https://ltz.wordpress.org/contact/ https://pan.wordpress.org/contact/ https://mya.wordpress.org/contact/ https://en-gb.wordpress.org/contact/ https://ory.wordpress.org/contact/ https://az.wordpress.org/contact/ https://tg.wordpress.org/contact/ https://te.wordpress.org/contact/ https://mri.wordpress.org/contact/ https://khk.wordpress.org/contact/ https://kin.wordpress.org/contact/ https://tuk.wordpress.org/contact/ https://az-tr.wordpress.org/contact/ https://mk.wordpress.org/contact/ https://ast.wordpress.org/contact/ https://gu.wordpress.org/contact/ https://bre.wordpress.org/contact/ https://am.wordpress.org/contact/ https://mg.wordpress.org/contact/ https://mr.wordpress.org/contact/ https://lin.wordpress.org/contact/ https://hat.wordpress.org/contact/ https://ary.wordpress.org/contact/ https://co.wordpress.org/contact/

tellyworth (9 matches)

Ticket Summary Component Milestone Type Created
#4126 "Special contributions" template leaks PII Codex defect 01/30/2019

E.g., https://codex.wordpress.org/Special:Contributions/Jany2786@gmail.com

This template should have a meta robots value of 'noindex, follow'.

#4253 Plugins API `query_plugins` produces wrong number of results Plugin Directory defect 03/09/2019

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.

#4306 Plugin Admin: Update Plugin Stats Report to use HelpScout Plugin Directory defect 03/20/2019

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


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

#2320 Global stats for GlotPress to identify possible future GTE Translate Site & Plugins enhancement 12/08/2016

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.

#4478 Add an `.editorconfig` file to the root of the meta repo General enhancement 05/27/2019

Adding the https://core.trac.wordpress.org/browser/trunk/.editorconfig file to the root of the meta repo should help avoid basic coding standards issues when contributing to the meta team.

Using the same .editorconfig from core should not cause any issues with the current meta projects.


#5140 Can the current day on Meetings show upcoming a little better WordPress.org Site enhancement 04/08/2020


Not sure if the meetings calendar could support it but I find most of the time the first couple early meetings in the day hide the others out there. It would be nice if the current time would change the view so the next few meetings are displayed with all others hidden in the popup link. This might help expose meetings that are about to occur instead of just displaying stale (past) meetings. *This would only apply to the current day.

Thoughts? Thanks

#815 Forums to Support Syntax Highlighting Support Forums Q1 enhancement 01/15/2015

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

#2107 Prevent posting 10k lines of logs in replies, recommend Pastebin or GitHub gists Support Forums Q1 enhancement 10/04/2016

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.


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.

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