ticket,summary,component,priority,type,owner,status,created,_changetime,_description,_reporter
6395,"""Fill"" Button style color & dimention changed",International Sites (Rosetta),normal,defect (bug),,new,2022-07-08T05:36:00Z,2022-07-08T06:16:23Z,"On P2 and Rosetta site, I used to customize the background color only (to WordPress blue #0074AA) and used the default text color, white. It used to look fine, but recently the button's default colors & dimensions seem to have changed.
You can see the issues here:
https://ja.wordpress.org/get-involved/
https://make.wordpress.org/polyglots/2022/05/31/polyglots-monthly-newsletter-may-2022/
It'd be nice if the default color for P2/WordPress.org sites are #0074AA (background) and white (text), so I don't have to manually customize them each time. Right now, the default background color is set to white.",Nao
3922,"""How to create a WordPress business website"" landing page on WordPress.org",General,normal,defect (bug),,new,2018-11-14T16:28:33Z,2023-04-11T21:41:39Z,"Hi,
We at the WordPress marketing team have created a new extensive guide on [https://make.wordpress.org/marketing/2018/11/07/how-to-create-a-business-website-with-wordpress/ ""How to create a business website with WordPress.""].
Can we create a landing page on WordPress.org on the same topic?
The idea is that it would attract a lot of people who are not currently WordPress users but are thinking of creating a business website.
Thanks.
",joelobo
5246,"""Make"" meetings need to filter for start_date and end_date",Make (Get Involved) / P2,normal,defect (bug),,new,2020-06-02T20:40:08Z,2020-06-02T20:40:08Z,"Currently, recurring meetings will show in the current month even if the start_date is set in the future.
So it looks as if the routine that generates lists of meetings doesn't filter correctly on at least start_date (and possibly also on end_date).",tobifjellner
5245,"""Make"" meetings: Make it easier to plan a one-time meeting",Make (Get Involved) / P2,normal,enhancement,,new,2020-06-02T20:15:55Z,2020-06-03T22:12:06Z,"The interface for CPT ""meetings"" under make.wordpress.org contains several radio buttons and settings for recurring meetings. We should add an alternative (one more radio button) for a non-recurring meeting.",tobifjellner
4347,"""Order & Orderby Parameters"" section in manually curated part of the code reference for WP_Query doesn't mention ordering by meta_query clauses",Developer Hub,normal,enhancement,,new,2019-03-29T14:05:39Z,2019-05-17T01:55:04Z,"[[https://make.wordpress.org/core/2015/03/30/query-improvements-in-wp-4-2-orderby-and-meta_query/|WP 4.2 introduced]] the ability to ""name"" clauses in `meta_query` and to use those ""names"" in `orderby`.
It would be nice if the ""Order & Orderby Parameters"" mentioned that ability and gave an example of its use.
The last example in that section (as of 2019-03-29) does include a `meta_query` but the `orderby` in that example is `meta_value_num` and not a ""named"" clause in the `meta_query`.",pbiron
5768,"""Rosetta for inactive translations"" feature for the current theme",International Sites (Rosetta),normal,defect (bug),,new,2021-06-08T08:39:31Z,2021-06-08T08:39:31Z,"The change made in #487 to is no longer working with the current theme.
Example: https://szl.wordpress.org/ (the last release was 4.7.2) doesn't have a download button in the top banner, but it's also not showing a banner to indicate that the locale is inactive.
Reference:
https://make.wordpress.org/community/handbook/translating/teams/inactive-translations/#inactive-locales",Nao
6371,'0' (zero) array key not displayed in Code Reference,Developer Hub,normal,defect (bug),,new,2022-06-20T23:29:57Z,2022-06-29T21:20:57Z,"In the [https://core.trac.wordpress.org/browser/tags/6.0/src/wp-includes/l10n.php?marks=590#L587 _n_noop() function DocBlock], the returned array includes the `'0'` (zero) array key.
On the [https://developer.wordpress.org/reference/functions/_n_noop/ _n_noop() function page], while the key description is displayed, the key itself is not, see the screenshot.",SergeyBiryukov
6457,(design/css) o2 dropdown (...) item isn't aligned middle & looks slightly broken when only one menu item,Make (Get Involved) / P2,normal,defect (bug),,new,2022-08-27T03:21:08Z,2022-08-27T03:22:45Z,"For Example:
in `Make WordPress Core` page (https://make.wordpress.org/core/) click the three dots icon (...) at the top right corner of any post and a dropdown the menu item 'shortlink' will appear. you'll see it doesn't look vertically centre aligned.
I also found, using 'vertical-align:middle' to the 'li' tag ('nav.o2-dropdown-actions ul li') or the 'a' tag inside the 'li' fixs it.
using 'line-height:1' to the 'li' tag also makes it center aligned.",hztyfoon
6443,/page/2/ being adding to reply links incorrectly,Support Forums,high,defect (bug),,new,2022-08-14T13:42:24Z,2023-02-01T16:26:10Z,"Replies on the first page of a topic and getting ""/page/2/"" added with the links, breaking them. For example, see https://wordpress.org/support/topic/smileys-not-working-on-mobile/?view=all
This reply is still on the first page:
{{{
https://wordpress.org/support/topic/smileys-not-working-on-mobile/page/2/?view=all#post-15900871
}}}
but doesn't work unless /page/2/ is removed.
It may be significant that this is the 10th reply in the chain. Subsequent replies also have /page/2/",sterndata
5519,301 redirects for new titles in HelpHub,HelpHub (wordpress.org/documentation),normal,enhancement,,new,2020-12-01T09:59:57Z,2022-01-25T14:30:04Z,"As part of the redesign for Helphub, we will change titles for some articles and we would like to know how to proceed. Jono suggested adding 301 redirect links. Are there any steps to that? This is to be done with the make/docs team",estelaris
6948,404 — File not found.,HelpHub (wordpress.org/documentation),normal,defect (bug),,new,2023-04-25T05:24:34Z,2023-07-25T13:39:19Z,"I have found two issues in the documentation.
The first issue is that the video URL to a ""404 - File not found"" error. This means that the video cannot be accessed as the file does not exist or has been moved or deleted.
The second issue is that there is an error being displayed on console for both pages stating that ""JQuery is not defined"".
Attached screenshot for your reference.",utsav72640
7466," in breaks layout",Support Forums,normal,defect (bug),,new,2024-02-14T03:42:11Z,2024-02-14T05:06:39Z,"See this forum topic: https://ja.wordpress.org/support/topic/%e3%83%8f%e3%83%b3%e3%82%ac%e3%83%bc%e3%83%a1%e3%83%8b%e3%83%a5%e3%83%bc%e3%81%ae%e7%b7%a8%e9%9b%86%e6%96%b9%e6%b3%95%e3%81%8c%e5%88%86%e3%81%8b%e3%82%89%e3%81%9a%e5%9b%b0%e3%81%a3%e3%81%a6%e3%81%84/
It seems the user input ""→"", the system wrapped it with
{{{
}}}
, then it was included into
{{{
}}}
and
{{{
}}}
contents without being escaped.
{{{
→ウィジェットに…"" />
→ウィジェットに…"" />
}}}
",takayukister
5144,[all websites] Declare HTML5 scripts and styles support for better compliance with W3C validator,General,normal,defect (bug),,new,2020-04-12T23:09:27Z,2021-05-21T12:48:08Z,"Hi,
Given almost all WordPress themes are written in HTML5, they should declare HTML5 support for styles and scripts to avoid using `type` attributes in styles and scripts. Otherwise, W3C validator will throw a warning because of the `type` element.
This option was introduced in WordPress 5.3. For reference, see:
- https://make.wordpress.org/core/2019/10/15/miscellaneous-developer-focused-changes-in-5-3/
- https://core.trac.wordpress.org/ticket/42804#comment:32",audrasjb
6984,[WordPress.tv] Widgetize sidebar and add terms for the different taxonomies,WordPress.tv,normal,enhancement,,new,2023-05-12T08:59:48Z,2023-05-12T11:26:38Z,"WordPress.tv has a tonne of content and it can be **hard for new users to discover** that this **content** is organized (among other things) by topic, language and speaker.
I created a demo ""overview"" page using tag cloud blocks to illustrate the wide range of content we have: https://wordpress.tv/overview/
I would like to be able to add tag/term clouds (or dropdowns?) to the sidebar to the **homepage and to archives** (singles are ok as they are, because the terms are already listed there).
It looks like the **sidebars are currently hard-coded** into the theme. My suggestion would be to **widgetize** the sidebar to allow editors to tweak its content. If this is not viable or practical for some reason, let's at least add these tag clouds on archives and the homepage (even if they are hard.coded).
Thank you! ",mrfoxtalbot
5548,A more inclusive commenting policy for P2,Make (Get Involved) / P2,normal,enhancement,,new,2020-12-15T10:17:16Z,2020-12-16T00:16:27Z,"Comments on some P2s and on some posts are more actively monitored than others.
While I understand requiring a previously approved comment in order to help combat spam, this can really get in the way of people contributing and having a diversity of opinions within an appropriate timeframe. This policy can contribute to echo chambers and those are uncool.
I would strongly advise that someone who has a previously approved comment on any P2 should be allowed to comment on another P2.
I would recommend at least not requiring comment moderation if the user has author+ caps on any other .org site, to facilitate inter-team collaboration.",carike
6972,A suggestion for the convenience of translation editors,Translate Site & Plugins,normal,defect (bug),,new,2023-05-06T16:46:53Z,2023-05-06T16:54:16Z,"When clicking on the Waiting button, not only the Waiting lines (yellow) but also the Translated lines (green) which already have a translation should be displayed.
This is very convenient for the editor when choosing the best translation.",irinashl
6597,Ability to ignore the most used translation in the consistency tool,Translate Site & Plugins,normal,enhancement,,new,2022-11-26T10:26:22Z,2022-11-26T10:26:22Z,"Example: https://translate.wordpress.org/consistency/?search=Page&set=nl%2Fdefault&project=
In nl_NL & nl_BE, sometimes we clean up old translations. Some translators are trying to find all wrong translations with the consistency tool to get rid of all the bad translations.
Now, the tool only searches until it has 500 results. But, what if there are more than 500 entries and the entries it finds are all the correct translation?
I think it would be cool if we had an option where we could ignore only the most popular result. In the example given earlier, you'd be able to click a button where it says: ""Ignore first result and search again"". That way the cool could search through the database without the first result to find the remaining wrong translations.",NekoJonez
6372,Ability to remove Geolocation EXIF data,Photo Directory,normal,feature request,,new,2022-06-22T14:44:26Z,2024-01-11T07:50:29Z,"Photos can have geolocation included in the metadata. The submission process should allow contributors to tick a box to have this data removed from a photo. An option should also be exposed to photos that have already been accepted and are included in the directory for contributors to remove location coordinate metadata from the file.
Some photos are nice to include this data while other times it is not. For example, a photo of the grand canyon or other public space is interesting to include, but a photo at someone's private residence (even when there are no people in it) may expose some private data to the internet.
Looking through some photos in the directory, I'm able to find plenty of images that do include the data. Note this is in the original image only, and not in the resized versions.",circlecube
6217,Ability to report a photo,Photo Directory,normal,feature request,,new,2022-03-25T04:39:13Z,2024-02-29T19:41:50Z,"Though the photos are moderated, there is always a chance that something will be missed that should disqualify a photo from the directory.
Unless it exists and I'm missing it, there should be a way for individual photos to be flagged or reported so they can be re-reviewed.",mdburnette
4171,Ability to temporarily block translation editors & show a warning,Translate Site & Plugins,normal,enhancement,,new,2019-02-11T13:41:03Z,2021-12-08T13:31:05Z,"I’m not sure if this is the case only for my locale, but lately there’s been more & more submissions that are obviously just imported *.po files, which were translated using Google Translate and with no further inspection.
The plugin / theme authors think that someone did a great job and ask for PTE rights for such a person.
As most strings are short, about 50% of such translations are correct, while the rest is garbage – totally wrong even for really easy & obvious strings (example: “Dashboard” was translated to “Dashboard of a car” in my language). That aside, no PHP context is considered for such translations.
This means that reviewing such submissions requires literally making the translation from the start, reviewing the context, fixing the lost letter capitalization, correcting inconsistencies. A GTE would therefore do the translation as if there was none. This does not help, it actually takes up the GTE’s and project author’s time. This is the opposite of what helping in translation is.
If such garbage is submitted and it’s obvious that it’s an automatic translation (not just a case of not sticking to the conventions), I myself reject all Waiting strings submitted by such a user for that project.
**Here are my requests:**
1. Easy: somewhere near the *.po import buttons, place a warning saying “If you submit a translation which was done automatically (like using Google Translate) and isn’t manually corrected, ALL the strings will be rejected, even if a lot of them came out correctly. If you did the whole translation manually, you don’t need to worry.”. Maybe even warn: “You will be blocked from further submission to all projects for 2 weeks.”.
2. Enable the GTEs to actually block translation submission from such accounts, for 2 weeks seems fine.
3. Enable GTEs to bulk-remove all non-accepted translations made by a user for all projects at once.
Discussion: [https://make.wordpress.org/polyglots/2019/02/09/ability-to-temporary-block-translators-who-submit-garbage/]",eclare
7131,Access to individual theme project translation pages from translation ranking,Translate Site & Plugins,normal,enhancement,,new,2023-07-11T06:52:21Z,2023-07-11T06:52:21Z,"I don't know if it's an error or what is the reason but if you access to the themes ranking, in the translations area (https://translate.wordpress.org/locale/ca/default/stats/themes/), do not have access to the individual page of the translation project of a theme, you have no way to access the individual page of the translation project of a theme. Example: https://translate.wordpress.org/locale/es/default/wp-themes/astra/
This is possible from the plugin ranking, by clicking on the ""Translated Percent"" for this project. While in themes it takes you here: https://translate.wordpress.org/projects/wp-themes/astra/ca/default/ same as if you click on the right column ""Translated"".
== What is the problem?
To see the translation status of a theme, from the translation ranking, you have to click on the project name. Example: ""Astra"". Then you have to look for the language in the language list and click on the language to see the status of that project. This should be repeated as many times as themes you want to check.
In plugins, you can click on ""Translated Percent"" of each plugin and open a new page.
== How to solve it?
By making clicking on the ""Translated Percent"" of a theme in the themes ranking, go to the individual translation page of that theme. Example: https://translate.wordpress.org/locale/ca/default/wp-themes/astra/ as it is already working in plugins.
Thanks",Marc4
3026,Access to WP-CLI profile badge management,Profiles,normal,enhancement,,new,2017-08-06T08:46:05Z,2020-06-16T03:39:24Z,"As one of the WP-CLI team reps, I'd like to be able to manage the WP-CLI profile badges for our contributors.
So far, there's no automated mechanism to add the relevant profile badges to WP-CLI contributors, as development happens on GitHub.
I'm also not quite sure yet whether we can completely automate this, as account names don't always match up between wordpress.org and GitHub.
For these reasons, I'd like to have the above access, so that I can manage this manually until we've been able to discuss/implement a better solution.",schlessera
6881,Accessibility issues in Make blog comment fields,Make (Get Involved) / P2,normal,defect (bug),,new,2023-03-23T07:56:11Z,2023-03-23T08:32:40Z,"[https://profiles.wordpress.org/nalininonstopnewsuk/ Nalini Thakor] brought up how accessibility tools such as Dragon app, Google dictation, and Microsoft dictation cannot write successfully in the comment section of make blogs. In one instance, content kept getting duplicated without a way to delete it. (See original [https://wordpress.slack.com/archives/C02RW657Q/p1677598756120129?thread_ts=1675185074.464699&cid=C02RW657Q Slack conversation here].)
When a redesign happens on Make blogs, could we make sure accessibility tools write correctly in the comment fields, too, please? (I am submitting this on behalf of Nalini. Please reach out to them in Slack for more information.)",bsanevans
7314,accessibility of svg image in wordpress.org footer,WordPress.org Site,low,enhancement,,new,2023-10-19T13:31:07Z,2023-11-01T19:24:01Z,"In the footer on https://wordpress.org/ there is a svg image with the words ""code is poetry"". In terms of accessibility it has too low color contrast to be readable for colorblind people.
secondly why isn't it plain text? it would be much quicker for screen readers.",jkjkjk
6449,accessibility problems with new download page,WordPress.org Site,normal,enhancement,,new,2022-08-19T16:15:29Z,2022-09-26T02:37:49Z,"I saw #6445 and went to look at the new [https://wordpress.org/download/ download] page. My first impression was stark and unfriendly.
* The copy has imperative statements with no ending period, followed by sentence fragments that do end with a period.
* There are four different styles for links on the page, not counting the menu. Only a few of them have a little arrow to show it goes somewhere else. The Get WordPress link in the header is the most prominent thing as the page loads, so it's tempting to click it. The Download link looks like a ""button"" and yet it is not using a download block, but a button block. The Installation guide link looks like a ""button"", giving the impression that the guide would be downloaded like the link above it.
* The required versions are below the fold. They are written in an incomplete sentence. They are low contrast and small.
* The list of blue on blue words are partially hidden. This is bad for dyslexics. These underlines are not adding value, but detract. The words are large, so they catch your eye, but are in a thin font that does not quite overcome the blue on blue, and since there is no explanation or link for them, it is useless to have them there.
* When I used Ctrl+ to make the font larger so I could read the required versions, part of the blue words disappeared. It is ironic that it is the word ""extendable"".
",joyously
7155,Accessibility Statement is not in footer,WordPress.org Site,lowest,feature request,,new,2023-07-22T11:04:16Z,2023-07-26T19:51:31Z,"I expected to find the WordPress accessibility statement (https://wordpress.org/about/accessibility/) in the wordpress.org footer but didn't. Many organizations that take accessibility seriously choose to display their accessibility statement in a place that is easy to find, usually the footer. Moreover, I've noticed in user tests those who use assistive technologies, such as screen readers, often look for an accessibility statement in a footer to understand a site's accessibility program before they start browsing content.
Beyond meeting users' expectations and establishing Accessibility as a WordPress priority, linking to the WP accessibility statement in the footer keeps WP.org in line with best practices and rules established by the W3C's Web Accessibility Initiative (WAI). Check out the ""Where to put an accessibility statement"" section of Developing an Accessibility Statement: https://www.w3.org/WAI/planning/statements/.
In researching tickets, an accessibility statement was mentioned as part of #3975. That ticket generally referred to footer/header links, while this ticket is only concerned with adding an accessibility statement link.
As for placement, I would suggest adding ""Accessibility Statement"" between ""Matt"" and ""Privacy"". Putting ""Accessibility Statement"" before ""Privacy"" follows the link order that is in the About page navigation.",elblakeo31
5216,"Accessibility: Text Changes, change ERROR to Error",General,normal,enhancement,,new,2020-05-16T14:45:10Z,2020-05-29T08:31:21Z,"Based on core ticket, I convert all {{{ERROR}}} to {{{Error}}}.",navidos
5486,"Activate setting ""user must be logged-in"" to comment on rosetta and /team sites",International Sites (Rosetta),normal,task (blessed),,new,2020-10-26T16:48:22Z,2020-10-26T16:48:22Z,"Please
Activate the setting ""Users must be registered and logged in to comment""
- on all Rosetta sites
- on all Rosetta /team sites.",tobifjellner
7457,Active Menu issue in mobile view,General,normal,defect (bug),,new,2024-02-09T08:51:02Z,2024-02-09T08:51:02Z,"In mobile view when the user visits any subpage of the About page, then it confuses the user which page is activated.
https://www.awesomescreenshot.com/video/24798690?key=8dcedfbb8249edf654a2708508b728bc
css
{{{
.wp-block-navigation:not([class*=has-text-decoration]) a:focus {
text-decoration-line: none;
}
.wp-block-navigation .current-menu-item > a{
font-weight: 700;
text-decoration-line: underline;
}
}}}
",harsh175
5756,Activity log is not populated when a topic title consists of only emoji,Profiles,normal,defect (bug),,new,2021-05-28T13:50:39Z,2021-12-17T04:49:41Z,"Probably an edge case, but still.
Topics/Review consisting of only emoji in title does not show in the activity log.
This topic [https://wordpress.org/support/topic/%f0%9f%8c%8a%ef%b8%8f%f0%9f%8c%8a%ef%b8%8f%f0%9f%8f%84%ef%b8%8f%f0%9f%8c%8a%ef%b8%8f/] does not show in [https://profiles.wordpress.org/surfboards/]
Replies consisting of only emoji do correctly show in the activity log, though.",bradparbs
5567,Adapt the page title on filtered plugin review archives,Support Forums,lowest,defect (bug),,new,2021-01-08T15:56:38Z,2021-02-23T17:39:08Z,"URLs like https://wordpress.org/support/plugin/gutenberg/reviews/?filter=4 should take the 'score' filter into account in the page title.
Alter the template as follows:
From: `
[%plugin_name%] Reviews - page %page% | WordPress.org`
To: `[%plugin_name%] Reviews (%star% stars only) - page %page% | WordPress.org`",jonoaldersonwp
6708,Add keyword on Trac 'needs-copy',Trac,normal,enhancement,,new,2023-01-24T23:39:33Z,2023-01-31T02:20:07Z,"Could Meta please add to Trac under:
Modify tickets/ Change Properties / Workflow keywords
The keywords 'needs-copy'. We need this on quite a few tickets and we have 'needs-copy-review', just not the initial step. It will be much easier having this as a drop down rather than adding it manually.
Thanks.
",webcommsat
6507,"Add ""Changes Requested"" sections to Trac reports",Trac,normal,enhancement,,new,2022-09-28T19:52:03Z,2022-09-28T19:57:52Z,"Recently, a `changes-requested` keyword was introduced in Core Trac.
We should update the reports that are workflow oriented to include a section for this new workflow state:
- [https://core.trac.wordpress.org/report/6 Report 2] (All tickets, workflow oriented)
- [https://core.trac.wordpress.org/report/6 Report 6] (next major release, workflow oriented)
- [https://core.trac.wordpress.org/tickets/minor/workflow Report 4] (next minor release, workflow oriented)
- [https://core.trac.wordpress.org/report/8 Report 8] (Future releases, Workflow Oriented)
There's likely a few more.
Discussion related to adding the keyword: https://wordpress.slack.com/archives/C18723MQ8/p1650951302813149. Added in [r11798].",desrosj
7345,"Add ""Compatible up to"" plugin header",Plugin Directory,normal,enhancement,,new,2023-11-09T09:52:50Z,2023-12-05T07:24:42Z,"This idea has been floating around for a while. It would be really helpful for plugins to be able to set a maximum supported WP version in addition to the minimum/required version. That would allow the plugins to ensure they are being updated on time and will not cause errors in future versions of WordPress.
Thinking that an optional `Compatible up to` header in the plugin's file (same as `Requires at least` and `Requires PHP`) would serve that purpose well. Then in core that header can be checked and the plugin not loaded if WordPress is newer, similarly to how the `Requires PHP` check works.
On the plugins directory side the `Compatible up to` header may eventually be used to sent a warning message when installing plugins through wp-admin. Perhaps like ""This plugin is too old and is not compatible with your version of WordPress"" instead of the ""This plugin has not been tested with your version of WordPress"" when the header is present. ",azaozz
7513,"Add ""My favorites"" functionality to the WordPress Photo Directory",Photo Directory,low,feature request,,new,2024-03-11T13:45:45Z,2024-03-11T15:34:30Z,"As the WordPress Photo directory grows bigger, it would be interesting to have the option to mark a photo as favorite and have a list of your favorite photos.
Some samples from other directories:
Patterns:
https://wordpress.org/patterns/favorites/
Plugins:
https://wordpress.org/plugins/browse/favorites/
Themes:
https://wordpress.org/themes/browse/favorites/
",nilovelez
5235,Add 'HelpHub Contributor' role for on-boarding users.,HelpHub (wordpress.org/documentation),normal,enhancement,,new,2020-05-27T14:56:47Z,2020-07-13T15:14:14Z,"In HelpHub, we have two roles: HelpHub Manager and HelpHub Editor, but we need weaker persona who requires approval process to publish their contents.
When on-boarding new contributors, there are no way to restrict their publishing to pubic.
",atachibana
7508,Add 'sustainability' to the Ticket->focuses dropdown shortcode,Trac,normal,defect (bug),,new,2024-03-07T08:20:09Z,2024-03-07T08:20:09Z,"We added a sustainability focus to trac in https://meta.trac.wordpress.org/ticket/7039. This ticket is to add this focus to the dropdown on the Tickets page so users can quickly navigate to see tickets in the focus.
I created a patch for this in https://github.com/WordPress/wordpress.org/pull/207",adamsilverstein
6407,Add 301 redirect information to Block Editor Handbook,Developer Hub,normal,feature request,,new,2022-07-15T12:07:08Z,2022-11-09T21:52:35Z,"When updating a page for the block editor handbook, once in a while, the page's slug or URL
Examples:
* Single page's slug changes:
''block-filters'' to ''block-hooks''
* Single page's parent folder changes
''**old:** reference-guides/filters/block-filters''
''**new:** reference-guides/hooks/block-hooks''
* Two pages are combined into a third.
''**old:** reference-guides/filters/block-filters
** old:** reference-guides/filters/block-actions
**new:** reference-guides/hooks/block-hooks''
In all this cases, the import process would need to accommodate also 301 redirects from the old pages to the new pages, so links to the old pages won't go dead.
Currently, the manifest page object reads:
{{{
{
""title"": ""Block Filters"",
""title"": ""Block Hooks"",
""slug"": ""block-filters"",
""markdown_source"": ""../docs/reference-guides/filters/block-filters.md"",
""parent"": ""filters"",
},
}}}
For the updated pages the manifest would look like this, with a possible new field ""redirect_from""
{{{
{
""title"": ""Block Filters"",
""title"": ""Block Hooks"",
""slug"": ""block-hooks"",
""markdown_source"": ""../docs/reference-guides/hooks/block-hooks.md"",
""parent"": ""hooks"",
""redirect_from"":[""reference-guides/filters/block-filters""]
},
}}}
Note: {{{redirect_from}}} is an array, in case it needs more than one value, to cover the third examples, when there needs a redirect from two old pages to a single new page.
Then it would look something like this:
{{{""redirect_from"":[""reference-guides/filters/block-filters"", ""reference-guides/filters/block-actions""]}}}
With this information, the import script could create the 301 redirect strings on when importing the new docs.
Maybe new location string should have a ""../docs/"" for accuracy?
I am not familiar where and how the magic works on server level for for the block editor handbook. So, there are still a few blind spots that need to be filled.
",bph
6929,"Add a ""Last modified"" date on glossary page and not only per row",Translate Site & Plugins,low,feature request,,new,2023-04-10T14:12:22Z,2023-04-10T15:12:13Z,"I think it would be handy to see if there is an update if you have above or underneath a locale glossary a date when it's last editted.
Otherwise, you will have to scroll through the whole list.",NekoJonez
7259,"Add a ""Report a vulnerability"" button/link to plugin repo pages",Plugin Directory,normal,enhancement,,new,2023-09-07T16:33:30Z,2023-10-04T21:57:38Z,"Contributors who have been involved with the project long enough know that they should email plugins@wordpress.org to report vulnerabilities. On the other hand, newer contributors are often not aware of this and will discuss or disclose vulnerabilities in the plugin's forum and in other places.
The plugins team has been discussing the idea of adding a visible ""Report a vulnerability"" button or link somewhere in the plugin page itself.
Clicking on this button could show a form that would be sent to the plugins team email. If we want to make it even simpler, the link would take the user to the [https://developer.wordpress.org/plugins/wordpress-org/plugin-security/reporting-plugin-security-issues/ relevant handbook page]
The idea is to provide a very simple path for new users to report vulnerabilities in the correct way.
This ticket is a simplified version of the idea proposed in #6939",mrfoxtalbot
7139,"Add a ""Security Supported"" statistic to stats page",WordPress.org Site,normal,enhancement,,new,2023-07-13T14:45:03Z,2023-07-14T06:43:37Z,"WordPress has great security/bugfixes support for old versions, the version 4.1 which was first released December 2014 has just recently gotten a security and bug fix release: https://wordpress.org/documentation/wordpress-version/version-4-1-38/
Adding a graph that shows how many of the active WordPress installations still have security support would really show how good WordPress is for website creators in the long run.
Inspiration: https://www.t3versions.com/statistics-detail/20
The site in question: https://wordpress.org/about/stats/",benniledl
5484,"Add a ""Tag and release"" button",Plugin Directory,normal,feature request,,new,2020-10-26T07:08:03Z,2022-03-30T05:27:59Z,"As a follow up to #5352, it'd be ideal if plugin authors had a button on https://wordpress.org/plugins/developers/releases/ which allowed a single-click ""Tag a release from `/trunk` to `/tags/x.y`""
For many people (myself included) the tagging process gets old quickly and can often be done incorrectly when the version isn't bumped in the right places, ie. a release is made with the old version still in the plugin headers, or the `Stable tag`
With Release Confirmations requiring tagging, and not just releases from trunk, having an easy way to go from trunk to a tagged release would be helpful.
Logic:
If the plugin version in the /trunk/$plugin.php headers is > $latest_release display the button as ""Tag and release $version""
The tag would be based on the version header as-is, and ensure that it's greater than (as according to `version_compare()`) than all their other versions.
The process would create a commit to the plugin, copying trunk to the tag, and updating the `Stable Tag` line in the readme at the same time.",dd32
7179,"Add a ""Uploading image"" message or similar in the Submit photo page",Photo Directory,normal,enhancement,,new,2023-08-05T10:34:58Z,2023-08-05T10:34:58Z,"Add a ""Uploading image"" message or similar in the center and front of the screen to indicate that the file is been loading, because right now for large images may take some seconds to refresh the page and none message or animation are shown, so, this may be a bit confusing for some users.
",necobm
5949,Add a 'needs-e2e-tests' keyword to trac,Trac,normal,enhancement,,new,2021-11-10T05:09:52Z,2021-12-01T21:37:34Z,"Trac currently has a very specific 'needs-unit-tests' keyword, and it could be useful to have the same to encourage end to end tests.
The simplest solution might be to add a 'needs-e2e-tests' keyword, but also open to other ideas.
Trac does seem to have a lot of keywords, and I also noticed there are requests for more (#5634), so an alternative would be to rename 'needs-unit-tests' a more generic 'needs-tests'.",talldanwp
1866,"Add a basic ""suggest an edit"" workflow to the handbooks plugin",Handbooks,normal,enhancement,DrewAPicture,accepted,2016-07-29T15:22:51Z,2020-05-04T16:53:17Z,"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
4894,Add a BP GraphQL API Handbook to developer.buddypress.org,buddypress.org,normal,enhancement,netweb,accepted,2019-12-08T11:12:50Z,2020-03-03T19:49:33Z,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.,imath
6598,Add a button to the consistency tool to ignore archived projects,Translate Site & Plugins,normal,enhancement,,new,2022-11-26T10:28:38Z,2022-11-26T15:52:41Z,Just as the title of this ticket says. I think it would be helpful if you had a button to ignore archived projects in the consistency tool since they are extremely low priority to translate.,NekoJonez
7012,Add a checkmark or something to say when it's the final patch,Trac,normal,enhancement,,new,2023-05-25T14:40:21Z,2023-05-26T01:04:22Z,"In today's early bug scrub, we discussed this ticket: https://core.trac.wordpress.org/ticket/50523
Yet, the patch wasn't 100% done yet and still being worked on.
So, I think it would be handy if we had a sort of checkbox when uploading a patch that said: ""Final patch"" or something for that trac ticket. So, it's clear when testing instructions can be written or when a patch can be tested and when it's feature complete.
This is a rough idea and we should think about it and discuss how it's going to work in this ticket.",NekoJonez
6282,Add a column date added to the glossary,Translate Site & Plugins,normal,enhancement,,new,2022-04-18T20:33:15Z,2022-04-18T20:33:15Z,"Currently if you are not a GTE, you cannot see when a glossary entry was added.
To keep track of new glossary verbs it would be very helpful if the column of date added is shown in the table. In that way you will get a quick view of newly added glossary verbs.
Even better would be a notification in the polyglots channel of the locale, after a new glossary verb is added.",psmits1567
6756,Add a copy to clipboard button to code blocks,Make (Get Involved) / P2,normal,feature request,tellyworth,reviewing,2023-02-14T16:43:32Z,2023-02-17T05:07:48Z,"Many web services display a ""Copy to clipboard"" button on the right hand side of a code block. It would be great to have the same on code blocks that appear on the Make sites, and maybe even the developer reference.",johnbillion
5449,Add a favicon to https://plugins.trac.wordpress.org/,Trac,lowest,defect (bug),,new,2020-09-24T07:40:54Z,2020-09-24T07:40:54Z,"Requests to https://plugins.trac.wordpress.org/ by most browsers request a favicon. The lack of one causes an (expensive) 404.
Adding a generic WP favicon to https://plugins.trac.wordpress.org/favicon.ico would benefit performance.",jonoaldersonwp
7417,Add a filter for plugins that have Live Preview enabled,Plugin Directory,normal,enhancement,,new,2024-01-19T15:34:03Z,2024-01-24T20:07:39Z,It would be nice to be able to search/filter plugins that have Live Preview enabled.,codente
5557,Add a hovering button to join slack community in Make Blog Network,Make (Get Involved) / P2,low,enhancement,,new,2020-12-23T00:38:46Z,2021-02-03T20:34:54Z,"While looking through Netlify, I noticed they had a neat nudge via a ""Join us on slack"" hovering button that follows you as you navigate the documentation: https://www.netlifycms.org/docs/contributor-guide/
It would be lovely to have the same for the Make Blog Network mainly for the handbook pages. There are various mentions of joining the slack community but it's very easy to miss right now as they are hyperlinks that blend into the background.
For good measure, here's a quick link to a screenshot showing what I'm talking about: https://cloudup.com/ceURVhBbFnX",annezazu
4759,Add a link icon to FAQ questions for plugins,Plugin Directory,normal,enhancement,,new,2019-10-08T21:55:34Z,2022-04-06T04:04:24Z,"The current FAQ has no way to retrieve the link to a particular question. Per #4519 it needs to be a button for accessibility reasons, but that means you can't right-click to copy the link. So instead you have to go into your browsers dev tools, copy the anchor link and combine that with the current URL.
https://cl.ly/651906af9a71
It could be helpful to add a link icon next to the question title that holds the full anchor link. ",helgatheviking
6415,Add a link to the overview page to the menu bar of meta trac,Trac,low,enhancement,,new,2022-07-20T16:38:07Z,2022-07-20T16:38:07Z,"I find the homepage of the meta trac extremely easy when I want to search for a certain ticket.
https://meta.trac.wordpress.org
But, once you clicked through, there is no real way to go back to that page apart from going back to the previous pages or going to the url directly.
A sort of ""home"" button or ""overview"" or adding the overviews you have on the homepage as views on the ""view tickets"" page would be lovely.",NekoJonez
2699,Add a new role to the forums: plugin/theme support,Support Forums,high,enhancement,Otto42,accepted,2017-04-07T14:55:18Z,2023-05-25T14:48:55Z,"
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
7255,"Add a one-off ""I have read the guidelines"" checkbox before posting for the first time",Support Forums,low,enhancement,,new,2023-09-07T09:38:30Z,2024-02-26T20:15:01Z,"We could add a checkbox requesting new users to acknowledge they have read and agree with the guidelines and with the community Code of Conduct. This checkbox would only show the very first time a user posts a new support topic, review or reply.
This was not very practical or realistic in the past because the guidelines were just too long but with it would be doable with [https://make.wordpress.org/support/2023/08/proposal-for-updated-support-guidelines/ the new ones].
The goal of this checkbox would be not only increase the chances of users actually reading the guidelines but **it would also ""cover"" moderators** in those cases when we ban/block someone and they claim they were unaware of a given rule or guideline. ",mrfoxtalbot
7251,Add a Preview in Playground button to the plugin directory,Plugin Directory,normal,defect (bug),tellyworth,accepted,2023-09-05T11:41:21Z,2024-02-08T03:17:29Z,"Now that the WordPress Playground has made it possible to safely test any plugin, we should add a button or link to the Plugin Directory so that users can preview a plugin with a single click.
Clicking the button/link would open a new window with a target URL similar to https://playground.wordpress.net/?plugin=hello-dolly (with the plugin's slug of course).
The button/link could go near the existing Download button, or it could even replace it. I'll defer to design feedback on the appearance and UX considerations.
Other decisions and considerations:
* Should it simply open a new tab with the playground preview, or something else (popup?)
* Does it need any logic for selecting the WP/PHP version or can we go with the default?
* Should it be available on all plugins, or selectively (eg only those actively maintained, or supporting a recent WP version?)
* What should the landing page of the preview be? (Perhaps `/wp-admin/plugins.php`?)
Note that this proposal is for a very simple Playground preview, a MVP. There are many additional ideas that we can discuss and add later.",tellyworth
4184,Add a robots.txt disallow all rule to ps.w.org,Version Control,lowest,defect (bug),Otto42,accepted,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
4770,Add a robots.txt disallow rule for /raw-attachment/,Trac,normal,defect (bug),,new,2019-10-22T14:52:16Z,2019-10-22T14:52:41Z,"'Raw attachment' URLs associated with a ticket should not be crawled (or indexed).
E.g., https://core.trac.wordpress.org/raw-attachment/ticket/43037/43037-2.diff, https://core.trac.wordpress.org/raw-attachment/ticket/43037/user.php
We should add a rule to the trac `robots.txt` file, which adds a `disallow: /raw-attachment/` rule.",jonoaldersonwp
5347,Add a robots.txt file to lists.wordpress.org,Mailing Lists,lowest,defect (bug),,new,2020-08-03T10:22:44Z,2024-02-21T23:31:02Z,"The site at lists.wordpress.org should have a robots.txt file, with the following content:
{{{
User-agent: *
Disallow:
}}}
",jonoaldersonwp
5928,Add a row background color-coding legend to the top of the various core Trac reports,Trac,normal,enhancement,,new,2021-10-13T19:48:49Z,2023-01-25T20:00:31Z,"The various Core Trac reports set specific background colors on some rows, but not others. And different reports use different background colors.
It would be great if there were a legend that explained the color-coding at the top of the report.
See this thread during [https://wordpress.slack.com/archives/C02RQBWTW/p1634153668228000 today's New Contributor Meeting] in slack for background (pun intended)",pbiron
5760,Add a Search Highlighter to Make Sites,Make (Get Involved) / P2,normal,enhancement,,new,2021-05-30T19:50:51Z,2021-05-31T08:42:17Z,"Search results on Make sites can be quite intense, that's both good and bad.
There's a lot of great information to go through, especially when most posts are several-paragraph complications with short titles and even more important discussion in the comments.
However, sometimes there's enough information that one's eyes might glaze over and they may miss what they're looking for.
Adding a search highlighter will allow the searcher to focus attention as they navigate the results returned, leading to a far more efficient and productive search experience.",macmanx
5681,Add a test template to Trac tickets,Trac,normal,enhancement,,new,2021-03-29T11:04:36Z,2021-09-21T13:57:04Z,"During the WordPress 5.6 release cycle, the squad had a test lead and amongst the different tasks, we started actively looking into improving the quality of everything released in WordPress.
To make sure all tickets can get properly tested, developers need to help the testing team to test their submissions.
This means that developers:
- Need to add test cases/steps in all tickets so testers know exactly what to test;
- If a ticket has priority, notify #core-test in Slack
There is a #core-test channel in Slack where we’re happy to help out any developer or tester with testing or the scenarios that need to be covered.
**Possible fix**
We cannot expect every developer to exactly know what to write to explain to the test team what needs to be tested and how. This means the Trac template needs to be updated with testing information.
The issue is in this: inserting comments as on GitHub can be done, but are not very user friendly, as a Trac comment will look like this:
{{{
#! Comment
Note to: ....
}}}
This kind of comment in Trac might scare off (new) developers and this is something we absolutely do not wish.
We’d like to propose the following:
When creating a Trac ticket, you can submit various details, such as Keywords, Priority, and Description. Extra steps with details on how to test will be added here. Perhaps it’s wise to automatically add an URL after it with a short ‘how-to’ on how to write testing descriptions. If one is unsure of how to write testing descriptions, the developer will then also learn where to reach out for help.
We should make the fix as clear as possible, but not without forgetting the goal. While we want to make sure that developers will continue to develop and provide the best testing scenarios possible, the ultimate goal is to test more and deliver more quality products.
**Template:**
- List the exact steps necessary to reproduce the problem.
- Specify the environment details where you reproduced the issue, e.g. WordPress version, PHP version, browser & version, operating system & version, plugins installed, and their versions.
- Paste any relevant error messages.
- Are there any workarounds for this issue?
- How can this issue be tested to ensure it’s fixed?
- Are there any testing dependencies, such as a plugin or script?
- What is the expected behavior after applying the patch?
Thank @monikarao, @carolinegeven, @hellofromtonya, and @ma0sm for brainstorming and review",francina
5542,Add a way to convert theme reports to support forum posts,Theme Directory,normal,enhancement,,new,2020-12-11T07:27:12Z,2020-12-24T10:46:01Z,"
Each theme in the directory has a support forum and a report button.
Sometimes the report button is used incorrectly for support questions.
These reports are replied to manually but it relies on the person who submitted the report
to create a new support issue or contact the theme author.
It would be good to have a way to convert the report to a support forum issue
alternatively forward the report directly to the theme author.
",poena
479,Add ability to browse activity history to profiles,Profiles,normal,enhancement,,new,2014-05-17T17:06:06Z,2022-05-16T03:38:29Z,"Currently profiles only show recent activities and there is no way to browse through the history.
Example: https://profiles.wordpress.org/aaroncampbell
It's possible to browse through activity history on the old WordPress support profiles: http://wordpress.org/support/profile/aaroncampbell
This is useful because it makes the following possible:
1) browse through a contributor's history
2) see a contributor's activity for a specific time period
3) see how a contributor's activity developed and changed over time
4) contributor can demonstrate what s/he was doing during a specific time period
5) find a contributor's first contribution (overall, and for a specific contribution area)",siobhan
7269,Add Accessibility Checker plugin to .org sites,WordPress.org Site,normal,enhancement,,new,2023-09-11T16:20:49Z,2024-02-23T21:22:28Z,"Currently, there is a need to improve the content accessibility across .org sites. This is content that comes from posts, pages, and other post types. Essentially, anything that is not written in code in a plugin, mu-plugin, or theme. In order to help content publishers meet basic accessibility guidelines, this request is to add Accessibility Checker to .org sites and make it available for sub-site admins to activate.
Plugin: https://wordpress.org/plugins/accessibility-checker/
There is also an option to use the pro version at no cost to WordPress.org. Free and pro code is GPL license compatible.",alexstine
7065,Add additional notice to the Plugin Submission form,Plugin Directory,normal,enhancement,,new,2023-06-14T20:11:47Z,2023-06-19T21:29:09Z,"Currently the [https://wordpress.org/plugins/developers/add/ plugin submission form] includes a notice that shows how many plugins are awaiting review, and the current wait time.
Given that our wait times are currently very long, I propose adding a secondary notice to this page, with text along these lines:
> We are currently experiencing long delays in plugin review times. To help us approve your plugin sooner, please ensure that you have read the [https://developer.wordpress.org/apis/security/ Security chapter] of the Plugin Handbook.
>
> Our three most common reasons for not approving a plugin are:
> - The plugin contains unescaped output: [https://developer.wordpress.org/apis/security/escaping/ Learn about Escaping Data]
> - The plugin accepts unsanitized data: [https://developer.wordpress.org/apis/security/sanitizing/ Learn about Sanitising Data]
> - The plugin processes form data without a nonce: [https://developer.wordpress.org/apis/security/nonces/ Learn about Nonces]
>
> If the code in your plugin falls into one of the above categories, **your plugin will not be approved**. The plugin review team will refer you back to these Handbook pages, adding further delay to the review process.
It's my hope that this type of notice will reduce the amount of submissions that require multiple reviews.",lukecarbis
6680,Add alt-s for id wp-admin-bar-user-info,WordPress.org Site,normal,defect (bug),,new,2023-01-14T21:28:10Z,2023-01-16T04:11:49Z,"Could you please add into alt's description name of current user nickename ?
class=""avatar avatar-26 photo"" and ‘class=”avatar avatar-64 photo”‘
[[Image(https://i.ibb.co/fHC7BXJ/Fixing-Word-Press-Word-Press-org-Google-Chrome.jpg)]]",blackstar1991
6101,"Add an ""exactly this word"" option in the filters",Translate Site & Plugins,normal,enhancement,,new,2022-02-15T07:57:34Z,2022-02-15T07:57:34Z,"In the locales I work on, sometimes translators copy nl_NL translations over to nl_BE. We have a couple of differences, like nl_NL uses ""site"" and we use ""website"".
Now, when I'm searching in projects if everything is translated correctly... it's quite annoying to go through it all and see the places where ""website"" AND ""site"" are used. In those cases, I would find it handy if I could check an option where it searches only for the search term and other spellings don't appear. ",NekoJonez
5668,Add an 'empty' robots.txt file to s.w.org,General,lowest,defect (bug),dd32,accepted,2021-03-19T11:02:23Z,2023-02-17T08:35:48Z,"https://s.w.org/robots.txt currently redirects to wordpress.org.
For SEO and performance reasons, we should implement a robots.txt file at this location.
The contents should be:
{{{
User-agent: *
Disallow:
}}}",jonoaldersonwp
4478,Add an `.editorconfig` file to the root of the meta repo,General,normal,enhancement,tellyworth,accepted,2019-05-27T18:44:42Z,2019-05-31T01:20:04Z,"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.
https://editorconfig.org/
",netweb
6797,Add an ability to translate strings for exact post/page/article,Translate Site & Plugins,normal,feature request,,new,2023-02-23T09:10:15Z,2023-04-19T21:28:11Z,"1. When strings are processing for translation, add information about where these strings are used on WordPress.org / Learn e.t.c. and their order on the page.
2. Add filter to search strings by page/post/article, where they are used to translating specific post/page and ability to sort them by 'native' order on the page.
3. Add link to translate current post/page/article to user's native language.
The implementation of this can be tricky, but I believe that these enhancements will be very useful, and the outcome is worth the effort. Right now to translate a specific page you need to search for each string from the original page that slowing the process. Otherwise, if you will be translating stings without context and order, the result can be patchy and vague for understanding.
This proposal can be split on several tickets to isolate different parts and achieve the end result by steps.",oglekler
5233,Add an easy way to hide forums sections from localized helphub sites that don’t use forum feature,HelpHub (wordpress.org/documentation),normal,defect (bug),,new,2020-05-27T12:34:24Z,2020-05-27T13:20:11Z,"Some Locales don't have any forum but use `locale.wordpress.org/support` to provide a localized helphub (documentation) instance.
However, the homepage of their helphub website displays a forum search widget in the header and some forum-related informations in the footer.
It would be nice to provide a simple way to hide forums sections from localized helphub sites that don’t use forum feature. I think a customizer option would probably be the easiest way to hide these sections.
Workaround patch coming. ",audrasjb
6985,Add an extra parameter 'show_in_rest' in custom taxonomy code snippet of developer doc.,Developer Hub,normal,enhancement,akhterarif,assigned,2023-05-13T04:49:26Z,2023-05-13T04:49:26Z,"An extra parameter ''show_in_rest'' has to be added in the following section.
https://developer.wordpress.org/plugins/taxonomies/working-with-custom-taxonomies/#step-2-creating-a-new-plugin
It is not working with the current settings while creating post with **Gutenburg** editor the taxonomy section is not showing. If we add the ''show_in_rest'' to ''true'' in ''$args'' array of the code snippet it shows the taxonomy in post creation window.",akhterarif
7420,Add announce to new meta-learn dev-squad host,"Communication (Matrix, Slack, IRC)",normal,enhancement,psykro,assigned,2024-01-23T15:12:28Z,2024-02-07T01:39:07Z,Please add announcement permissions to @digitalchild for the #meta-learn channel.,psykro
6108,Add automated guideline checks and constant feedback to plugin authors about it,Plugin Directory,low,defect (bug),,new,2022-02-16T02:24:31Z,2024-02-22T06:47:03Z,"Currently a lot of plugin guidelines are enforced purely through manual processes by reviewers, often in response to complaints/contact from others.
It would be ideal if we had a system similar to [https://wordpress.org/plugins/theme-check/ ""Theme Check""] where automated checks are run over each plugin commit/release.
This could be used to flag serious issues:
- ERROR: Your plugin name should not include the terms 'WordPress' or 'Plugin'.
- ERROR: Your plugin name should not need to be 50 words
Feedback on user errors:
- WARNING: You included 'John Smith' within your 'Contributors:' line in your readme, this should only include WordPress.org usernames of developers, not real names.
- WARNING: Your plugin slug is 'my-cool-plugin', your textdomain should be the same to be compatible with translations from translate.wordpress.org. Detected 'dd-text'.
and less-serious, but annoying things:
- NOTICE: screenshot-1.png is 4MB in size, consider optimizing it.
- INFO: Your plugin includes screenshots in the plugin folder, rather than using assets, this results in 5MB extra files within your plugin ZIP.
Due to the different flow for Plugins verse Theme updates, the results of this would need to be handled differently.
My thoughts are a combination of the following:
- Email to the plugin committers post-version-update
- Displayed at the top of the Plugins page for plugin committers only
- and/or Displayed on the Development tab for plugin committers, and everyone else.
- Logged to a Slack channel, similar to #themereview-firehose and #meta-language-packs",dd32
4195,Add block editor template for the helphub_version post type,HelpHub (wordpress.org/documentation),normal,enhancement,SergeyBiryukov,reviewing,2019-02-21T21:18:13Z,2023-04-17T19:36:14Z,"While working on the 5.1 version page on the HelpHub, I found that there was no equivelant to https://codex.wordpress.org/Template:Release in the HelpHub.
I think that block editor templates would be a great way to ensure consistent formatting is used and no information is forgotten when creating pages for new versions.",desrosj
7316,Add Blue Checkmark | Plugin Support Topics,Support Forums,normal,enhancement,,new,2023-10-19T17:39:55Z,2023-11-01T19:35:00Z,"**Issue:**
Currently, plugin support topics are labeled as ""Resolved"" with a Green checkmark. Unfortunately, plugin developers are also using the Green checkmark as an indicator that they viewed and answered the topic, but did not necessarily resolve it. As a result, when not resolved, topic owners have to reopen the topic or further discuss it with the developer.
Here's one good example: https://prnt.sc/jvlYgHxPuhQS
The above situation causes confusion and frustration amongst plugin users who are searching for a real fix or solution to their issue(s).
**Solution:**
Based on the above, I would like to recommend the creation and placement of a Blue checkmark next to the support topic when it has been viewed and answered by the plugin developer. If and when the topic is truly resolved, the topic owner or the developer can then change the topic to ""Resolved"" (Green checkmark).
**Implementation:**
1. Add ""answered"" to the topic Status dropdown box. Details: https://prnt.sc/Zqc0ir35Wr5L
2. When ""answered"" is selected, a Blue checkbox is placed next to the support topic.
**Benefits:**
1. Eliminate ""tug of wars"" between the topic owner and plugin developer concerning the final resolution to a plugin issue.
2. Plugin users can identify and view ""real"" plugin solutions a lot faster.
3. Plugin developers will have an option to label topics that have been viewed and answered, but are not resolved or address properly the topic owner's request.
Cheers!",generosus
5478,Add brotli compression to emoji image files,General,normal,enhancement,,new,2020-10-18T19:16:00Z,2021-08-05T18:57:38Z,"Wordpress sites load emoji from https://s.w.org
Currently the files are gzip encoded. Can be improved to have brotli compression too. ",superpoincare
4875,Add bulk suspension and reinstating admin tool for themes,Theme Directory,high,enhancement,,new,2019-11-25T17:53:56Z,2020-01-28T18:07:47Z,"I've been working on this on and off in my spare time for some week or two.
Theme review reps need better tools when working on suspending themes and reinstating them. Currently, we have a big issue if we find an author violating the rules and not fixing them in a timely manner so we need to suspend all of their themes. At the moment this is a lengthy process where you need to find all the themes, go and suspend one by one, then go to trac and send a message that the theme has been suspended for violating rules.
The proposed patch adds a way to suspend themes in bulk and also reinstate them.
The workflow goes like this:
All the themes that need to be suspended are found, selected and with a bulk action can be suspended. The theme rep will then be brought to a new suspension message screen where they can add the suspension reason and the duration of the suspension.
This information is stored in a theme meta and can be visible in the theme edit screen. This also helps with keeping track of who suspended a theme and when in the past.
In addition to that, a cron job is added which will be ran twice a day that will check all the suspended themes, and those that have the necessary metadata will be checked if they need to be reinstated (unsuspended). A permanent ban can be set with a super high suspension date (+1000 years).
There is also Suspended Packages screen which holds all the suspended themes, and assorted data with them. Those can also be reinstated in bulk if necessary.
Now I've added a call that would update the ticket on trac for the theme that is suspended. But this is where I need help from meta team with trac experience.
Ideally, we'd have 2 new statuses for the themes: `suspended` and `suspended-under-review`. When a theme is suspended, the last trac ticket should be changed to `suspended` and the author shouldn't be able to upload themes.
Once suspension passes and we reinstate the themes, on reinstating the theme the new status should be `suspended-under-review` so that the changes can be updated, but the theme won't be set live. I think for this we might need a new post status in the admin so that we can differentiate those.
Once the themes have been reviewed and fixed we'd approve them and set them live.
The things that 've changed are:
{{{
modified: wp-content/plugins/theme-directory/admin-edit.php
new file: wp-content/plugins/theme-directory/assets/suspend-form.css
modified: wp-content/plugins/theme-directory/class-wporg-themes-repo-package.php
new file: wp-content/plugins/theme-directory/class-wporg-themes-suspended-repo-packages.php
new file: wp-content/plugins/theme-directory/inc/class-wporg-themes-list-table.php
new file: wp-content/plugins/theme-directory/inc/class-wporg-themes-suspended-list-table.php
modified: wp-content/plugins/theme-directory/jobs/class-trac-sync.php
modified: wp-content/plugins/theme-directory/theme-directory.php
}}}
The details are in the patch I'll attach.
There is still some work to be done, but I need meta's help with this one, as it's quite a big change, but would help theme review reps considerably.
",dingo_d
5047,"Add check to forum subscriptions if the account is ""Blocked"" or ""Spectator""",Support Forums,high,defect (bug),,new,2020-02-21T13:58:12Z,2022-02-18T03:43:55Z,"When a user for cause has their forum account set to ""Blocked"" or ""Spectator"" then they lose the ability to edit their existing subscriptions.
Can a check be added to the subscriptions so that those two account types do not get notifications from the forums?
A user that was blocked (for cause, that's important) and is still getting emails from the forums. Because their account is ""Blocked"" they cannot edit or clear their subscriptions.",jdembowski
6526,Add context to support forum search results,Support Forums,normal,enhancement,,reopened,2022-10-08T21:37:45Z,2023-04-26T09:49:06Z,"Do a search for a word like ""security"". The only way to know the context of these items is '''if''' the OP added the name of the plugin or core area to the subject. Since doing so is redundant when someone is posting a note in a support forum dedicated to a specific area, most requests are not labelled such.
See screenshot. What do '''you''' think is the context for any of those items ... aside from ""All In One WP Security"". Are the requests about core, a plugin, a theme, custom development?
[[Image(https://dl.dropboxusercontent.com/s/y7y4pgkowkam49j/221008142158.png)]]
== Suggestion 1
Ref #6525 (Add context to support forum topic URI). The context would show in the green URI and this request for enhancement would be satisfied.
== Suggestion 2
Note all of the requests have ""Labelled ''Support Forums''. Use this meta field to insert context labels.
1) Core, Theme, Plugin, or Development
2) A slug for a theme or plugin. (Preferred since names change)
Therefore:
Labelled: Support Forums, Core, installation
Labelled: Support Forums, Theme, twenty-twentytwo
Labelled: Support Forums, Plugin, akismet
== Suggestion 3
Consider setting the thumbnail to something othr than the generic WordPress logo - perhaps the featured image for the relevant plugin or theme.
== Summary
I'd like to see all of these implemented. Any would be an improvement. TY
== Note
Image subject to removal on final determination of this request.",Starbuck
6525,Add context to support forum topic URI,Support Forums,normal,enhancement,,new,2022-10-08T21:04:44Z,2022-10-11T01:12:11Z,"**Problem:** We cannot identify the context of a support post until we open it.
== Example 1 - Context for Plugin Support
Live random example of problem:
https://wordpress.org/support/topic/many-to-many-relationship-help-please/
Challenge: Guess whether that's related to core, ACF, MetaBox, or some other plugin.
Open the link to see:
""Support » Plugin: WP Data Access » Many To Many Relationship (Help, please)""
==== Suggestion 1: Add the plugin slug to the links of all plugin support topic URIs.
''!https://wordpress.org/support/plugin/name/slug''
Redirect if required to the current ''!https://wordpress.org/support/topic/slug''
If the URI matches `support\/plugin\/(.*)\/(.*)$` rewrite to `support/topic/$2`.
== Example 2 - Context for Core Forums
Live random example of problem:
https://wordpress.org/support/topic/error-establishing-a-database-connection-1035/
Challenge: Of the 1035 examples of that slug, what is the context of this discussion? Is it about a plugin? Core? What aspect of core?
Open the link to see:
""Support » Installing WordPress » Error establishing a database connection""
If it seemed obvious that this was about core, consider:
https://wordpress.org/support/topic/error-establishing-a-database-connection-1034/
That's a request with the exact same topic name that leads to a plugin:
""Support » Plugin: Page Builder by SiteOrigin » Error establishing a database connection""
==== Suggestion 2: Add the label ""forum"" and the section to the URI.
Existing forum link for the above thread:
https://wordpress.org/support/forum/installation/
New thread link:
https://wordpress.org/support/forum/installation/error-establishing-a-database-connection-1035/
Now it's obvious that this discussion applies to core and not a plugin, which can eliminate page loads of data that's not relevant to current research.
To implement:
Rewrite `support\/forum\/(.*)\/(.*)$` to `support/topic/$2`.
== Example 3 - Context for Theme Forums
Live random example of problem:
https://wordpress.org/support/topic/remove-padding-7/
Challenge: Of the 7 examples of that slug, what is the context of this discussion? Is it about a plugin? Core? What aspect of core? A theme?
Open the link to see:
""Support » Theme: Twenty Twenty-Two » Remove Padding""
The other six requests with the exact same topic name lead to other themes and plugins.
==== Suggestion 3: Add the label ""theme"" and the theme name to the URI.
Existing forum link for the above thread:
https://wordpress.org/support/theme/twentytwentytwo/
New thread link:
https://wordpress.org/support/theme/twentytwentytwo/remove-padding-7/
Now it's obvious that this discussion applies to a specific theme.
To implement:
Rewrite `support\/theme\/(.*)\/(.*)$` to `support/topic/$2`.
== Combining the suggestions
Rewrite `support\/(forum|plugin|theme)\/(.*)\/(.*)$` to `support/topic/$2`.
Currently all links matching that pattern lead to a 404.
== Notes
Anchor links in URIs must not be broken - the dollar-sign $ terminator in the regex above might not be valid.
Example: support/plugin/name/slug#anchor
Modify rewrite with something like:
`support\/(forum|plugin|theme)\/(.*)\/(.*)(|#(.*))$` > `support/topic/$2$4`
Implementation requires changes in many places on this site to insert more metadata into links.
Consider adding a user profile toggle to allow opt-in for new functionality. This can also be used to facilitate debugging before full production.
The suggested implementation details are secondary and only intended to be helpful. The primary request is to solve the problem where we have no context with ""support/topic/slug"".
Another implementation, perhaps easier though less elegant, might be to display links with a querystring, based on a user profile opt-in toggle. Example:
''!https://wordpress.org/support/topic/slug?context=forum+installation''
or
''!https://wordpress.org/support/topic/slug?context=theme+twentytwentytwo''
or:
''!https://wordpress.org/support/topic/slug?forum=installation''
''!https://wordpress.org/support/topic/slug?theme=twentytwentytwo''
''!https://wordpress.org/support/topic/slug?plugin=akismet''
Again, the query string isn't intended to influence processing, it's there for human consumption. This querystring solution won't help with wp.org SEO. I'm thinking more context in the URI path would help with searches on wp.org and from outside.",Starbuck
4750,Add Contributors & Developers section to theme single page,Theme Directory,low,enhancement,,new,2019-10-01T14:08:34Z,2024-01-10T02:16:26Z,"I believe that it would be great add a 'Contributors & Developers' section to theme single page (the same way we have on plugin single page).
[[Image(https://i.imgur.com/JWKi3N6.png)]]
This would allow us to see the WordPress community history of the theme developers, and also highlight everyone that helps on the theme development.",felipeloureirosantos
6573,add counter for total amount of translated lines into profile,Translate Site & Plugins,normal,enhancement,Amieiro,assigned,2022-11-09T19:57:17Z,2022-12-21T10:29:14Z,"Currently there is no possebillity to find out how many lines in total you have translated.
Proposal 1. Create a button within your profile to generate the overal count stats
Proposal 2. Currently translation counts per project are added on dayly basis into your profile. Add this count into a general counter within your profile.
Both solutions give the translator confirmation of the efforts he has done.",psmits1567
7411,Add Courses section to Profiles,Profiles,normal,feature request,,new,2024-01-17T20:36:47Z,2024-02-08T02:09:05Z,"WordPress.org profiles currently have Activity, Plugins, Photos, Favorites, and Translations sections. I propose that we add a new Courses section that would show all the learn.wordpress.org courses that some one has taken. Perhaps with a profile option to also show the course result / total grade so that this section effectively becomes a community members ""transcript"" of Learn courses?",JeffPaul
2596,Add Default Text in Support form as a Template for Asking Good Support Questions,Support Forums,normal,enhancement,,new,2017-03-22T21:28:30Z,2023-03-08T16:33:09Z,"In a similar vein to #363, it would be useful to allow plugin/theme authors to provide a support template for users to submit their support requests based on pre-given questions.
Github implemented it this way:
https://github.com/blog/2111-issue-and-pull-request-templates
Potentially, a plugin author could include a file in their repo called .support to pre-populate the New Ticket field. It's unclear to me the complexity of this request but it would certainly make the back and forth of support tickets in the Support Forum in general much more efficient if well-implemented.",webdevmattcrom
3577,Add Dictonary for Captioner on WordPress Events,Handbooks,normal,enhancement,,new,2018-04-16T21:32:03Z,2021-03-19T23:03:53Z,"At some WordPress Events there are transcribers who type what the speaker is saying on the stage. This allows people to also read what the speaker is saying. This makes the whole conference more accessible, especially for the hearing impaired and non native speakers.
Currently speakers are asked to send their slides in advance, so that the captioners can prepare und understand the technical and WordPress terms which will be used in the talk.
I chatted with the captioners to find out what I as a speaker could do to help them. They showed me, that they had created their own WordPress dictionary from the slides they had received from the speakers. They are also reusing this dictionary for future WordPress conferences and expanding on it with new words, that they get from further slides.
The problem with this workflow is, that
1. some speakers don't send the slides beforehand or don't have every technical word in the slides.
2. Questions and last minute changes at the slides could include technical/WordPress specific words, which are not in the captioner´s dictionary.
3. Sometimes they do not know how some technical written terms are pronounced (like i18n)
Some examples for WordPress related words
- Jetpack and other common plugins
- i18n, A11y ... - the captioners don't know how this is spoken out
- Aria, ....
So I thought that we as the WordPress Community could help the transcriptioners by providing them an dictionary with WordPress related words, which their could use and import into their tool.
I asked them if this would be helpful and they loved the idea. The good side would be that we could give this dictionary to the captioners at every WordPress conference which they can import into their tool.
All they need is the terms and how the term is spoken. An excel sheet would be enough.
To create this table I would suggest to make it like a Wiki, which is Open Source and could be extended from the community. But of course this should be discussed, what the best way would be, if we decide to realizing it.
A starting point could be this Dictionary:
https://make.wordpress.org/marketing/2018/02/28/wordpress-jargon-glossary/
Maybe we could start with a small table and than ask for feedback from the captioners to check, if this is a format their could use (the captioners from WordCamp London said, they would like to give us feedback). In this way we can make sure, that the format is correct, before we continue.
The captioners doing an amazing job and having an big impact to make the WordCamps more accessible. I would love, if we could make their job more easier. ",Travel_girl
89,Add email notifications for new jobs on jobs.wordpress.net,Jobs (jobs.wordpress.net),high,enhancement,,new,2013-08-19T11:42:22Z,2023-12-17T17:49:46Z,"I didn't see a way to subscribe via email to jobs on jobs.wordpress.net . There are RSS feeds available, but other resources provide an option for email subscription, so do make blogs and WordPress.com blogs and Jetpack-driven blogs. ",nofearinc
7298,Add emoji reaction to trac comments,Trac,normal,defect (bug),,new,2023-10-06T17:11:58Z,2023-12-05T18:19:42Z,"Sometimes you want to express your feeling towards a ticket/comment and there is no point actually to write anything, so it will be great to have several emoji reactions: great 🔥, good 👍, no good 👎, ""I don't know"" 🤷, looking 👀, 'I am on it' 🏃♂️, agree 💯 or ✅, do not agree 😐 or 😶, 'read docs' 📚, ""let's hope"" 🤞 and 'thank you' 🙏 or ❤️ or 🙌
And just one nice smile 🙂
Thank you!",oglekler
4825,Add Enterprise content to wordpress.org,General,high,enhancement,Otto42,accepted,2019-11-05T18:14:42Z,2020-11-18T19:08:48Z,"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]",chanthaboune
4695,Add FAQPage schema markup to plugin pages,Plugin Directory,normal,defect (bug),SergeyBiryukov,accepted,2019-08-20T09:58:16Z,2023-02-17T07:44:52Z,"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).
== Approach
- 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"",
""@id"": ""{{CANONICAL_URL}}"",
""url"": ""{{CANONICAL_URL}}"",
""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, concatenation of CSS/ JS can still make a lot of sense, as described in this css-tricks.com article and this blogpost from one of the Ebay engineers. 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 & 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 ``, `` and `` tags.
- Disallow/remove any values/properties/attributes of these tags (other than the `href` attribute on `` tags).
- Remove invalid markup (e.g., an `` without a closing ``).",jonoaldersonwp
5738,Add Feedback form to Dev Handbooks,Developer Hub,normal,enhancement,,new,2021-05-18T07:03:02Z,2023-08-24T14:06:00Z,"So we have a bunch of Dev Handbooks at https://developer.wordpress.org/
Right now Code Reference has the feedback box enabled.
I'd love to complete the feedback mechanism coverage by extending that to cover the non GitHub sync'ed handbooks namely - Theme, Plugin and Common API handbooks.
We did the same work for HelpHub here at #4915
Feedback box I'm referring via screenshot attached",Kenshino
4867,Add feeds for plugin support forum topic replies,Support Forums,normal,enhancement,,new,2019-11-21T11:38:13Z,2023-03-29T08:10:23Z,"The ability to receive notifications for new replies in the WP.org forum threads would enable plugin authors and maintainers to review and reply to those threads in a timely manner without having to subscribe to email notifications for each thread.
Currently we implement the following custom feeds on WP.org plugin support forums in addition to the standard bbPress feeds via the [https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html/wp-content/plugins/support-forums?rev=9255&order=name support-forums plugin]:
- Plugin ontributor feed https://wordpress.org/support/view/plugin-contributor/sergeybiryukov/feed/ (defined [https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html/wp-content/plugins/support-forums/inc/class-support-compat.php?rev=9255#L137 here])
- Plugin commiter feed https://wordpress.org/support/view/plugin-committer/sergeybiryukov/feed/ (defined [https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html/wp-content/plugins/support-forums/inc/class-support-compat.php?rev=9255#L125 here])
Those feeds currently list only the forum topics created for the plugins associated with that user. Could we extend those feeds to also include the topic replies?
Or create a support ""firehose"" feed for individual plugins that include both the topic and the replies? This sounds like a better general solution since anyone could access those.
Somewhat related to #2071.",kasparsd
3329,Add filter to translate.wp.org on Plugins/Themes listing to order by last activity date,Translate Site & Plugins,normal,enhancement,,new,2017-12-13T19:06:47Z,2021-03-11T01:32:06Z,"Hello,
I'd like to propose an additional filter be added to the dropdown found on Plugins/Themes on translate.wp.org, screen;
https://i.imgur.com/Dc88w65.png
It might be two so you could have it go both ways but something like;
Recently Updated (Old first)
Recently Updated (New first)
This would sort the Plugins or Themes listing to be chronological by most recent update allowing translators to focus on the more active themes/plugins.
*In my case I would like to cross-out the really old themes as they're less likely to continually change.
Hope that makes sense,
Thanks",garrett-eclipse
5232,Add flagged user view,Support Forums,normal,enhancement,,new,2020-05-27T11:17:02Z,2023-03-29T08:58:10Z,"It would be beneficial to have a view that lists flagged users.
This would of course be a restricted view for moderators, and should show:
- The flagged user
- Who flagged them
- When they were flagged
- When they last interacted on the forum (most recent topic/reply)
There's no way of knowing how many flagged accounts exist, and this would help to not only keep tabs on that, but also to be able to more reliably check in on older flagged accounts and then more reliably remove their flag in a timely manner.",Clorith
1510,Add full transcripts to videos on WordPress.tv,WordPress.tv,normal,enhancement,,new,2016-01-08T23:37:47Z,2024-01-23T06:09:52Z,"The videos on WordPress.tv provide a wealth of information, but this information is pretty much invisible on the web, both for search engines, the internal search system on the site, and for users who don't want to watch / listen to the videos. The lack of transcripts is also a major accessibility concern.
Adding full transcripts of videos would remedy this situation and provide significant benefits:
- Videos become accessible to a far greater audience
- Presented content becomes searchable from within wordpress.tv
- Presented content becomes indexable for search engines resulting in organic traffic and (probably) boosting the exposure of the videos to a larger audience
- Visitors can choose to read the transcript rather than watch the video (reading is often faster than watching)
- Translation (even automatic) of videos is vastly simplified with the side effect of potential multi-lingual captions
- Videos with poor audio quality become easier to digest for visitors
- Transcripts provide an excellent opportunity for future enhancement of the site including transcript-based navigation similar to what's found on Lynda.com
== Implementation ==
I propose a panel directly below the video player that shows the first few paragraphs and provides a ""reveal more"" link or similar to reveal the whole transcript. Ideally the DOM should contain the entire transcript to make the content accessible for search.
== Practical Implementation ==
The obvious question is ""where are these transcripts going to come from""? Three options:
1. Edited text dumps from CART captioning during events
2. Edited dumps from volunteer video captions
3. Volunteer text transcripts",mor10
5935,Add Google Tag Manager to status.wordpress.org,General,lowest,defect (bug),,assigned,2021-10-22T07:29:57Z,2021-10-22T08:12:57Z,The site at status.wordpress.org omits our standard Google Tag Manager integration. This should be added.,jonoaldersonwp
6310,Add gp-translation-helpers for the Reject with Feedback Feature,Translate Site & Plugins,normal,enhancement,,new,2022-05-11T08:45:42Z,2022-05-11T08:47:46Z,"In order to introduce the [https://make.wordpress.org/polyglots/2022/02/08/agenda-weekly-polyglots-chat-feb-9-2022-0700-utc/ Reject with Feedback] to translate.wordpress.org, we'll add the [https://github.com/GlotPress/gp-translation-helpers/ GlotPress/gp-translation-helpers plugin] to the meta repository.
Development mostly happens in the [https://github.com/GlotPress/gp-translation-helpers/ git repository], we'll sync it to svn on a ""nightly"" basis.
The feature and plugin is being regularly discussed in the [https://make.wordpress.org/polyglots/tag/weekly-meetings/ weekly polyglots meetings].
cc @amieiro @spiraltee",akirk
5641,Add history log for themes status adjustments,Theme Directory,normal,enhancement,,new,2021-02-26T14:07:45Z,2021-02-26T14:07:45Z,"Creat a notes/history log in themes admin where status changes for themes are recorded.
Things like initial upload date, go live date, author transfers and status changes between live/suspended/delisted etc.
This should be automated notes added when the state changes - no need for manual ability to add notes.",williampatton
5962,Add indication of the fact that the translation has been imported,Translate Site & Plugins,normal,enhancement,,new,2021-11-24T14:33:50Z,2022-01-26T19:21:51Z,"Currently you cannot see that a translation is imported. You have to check the date/time to figure out that the translations have been imported.
It would be welcome if in GlotPress within the Meta details an indication is present that shows that the translation suggestion has been imported, not added manually.
",psmits1567
4525,Add insights to the plugin language packs page,Translate Site & Plugins,normal,enhancement,tellyworth,reviewing,2019-06-22T18:57:23Z,2020-06-02T08:27:09Z,"This ticket is about the Plugin **language packs** page.
https://wordpress.org/plugins/site-health-manager/ (Main plugin page)
https://translate.wordpress.org/projects/wp-plugins/site-health-manager/
https://translate.wordpress.org/projects/wp-plugins/site-health-manager/contributors/
https://translate.wordpress.org/projects/wp-plugins/site-health-manager/language-packs/ (**This page**)
----
The main plugin page displays the number of languages the plugin has ( on the sidebar - **[https://wordpress.org/plugins/site-health-manager/ Languages: See all 9]** ).
The problem is that the number of languages is not the same as the number of updated languages. It only represents the total language packs created.
I would like to see in the plugin language packs page more data, not only a dumb list. I would like to see insights and maybe a graph like the one we currently have in the contributors page.
Extra data to display:
* Total number of language packs
* Current plugin version
* The number of packs for the current version
* The number of packs for older version.
* Pie Chart displaying languages packs by version.
The chart can show plugin developers if the languages packs are mainly for obsolete versions or for the latest version. This single chart is much more useful than the list of languages.
",ramiy
7021,"Add keywords to the documentation: has-testing-info, needs-testing-info, add-to-field-guide, needs-user-docs",Handbooks,normal,enhancement,,new,2023-05-29T20:12:09Z,2023-06-20T16:30:56Z,"https://make.wordpress.org/core/handbook/contribute/trac/keywords/
- `has-testing-info`
- `needs-testing-info`
- `add-to-field-guide`
- `needs-user-docs`
Even if their meaning seems to be clear, I believe that they should be described. I have seen incorrect usage of at least the `add-to-field-guide` keyword.
",oglekler
5696,Add link to create new topic for closed topics,Support Forums,normal,enhancement,,new,2021-04-08T08:38:37Z,2023-04-05T16:59:23Z,"Many times a user will end up on a closed (old) topic from search results, looking for an answer to their problem. Once inside a specific topic, it's not too obvious how to add a new topic.
Similar to [ticket:3999 #meta3999] that adds a link to create new topic near ''reply form'', there should be a link to create a new topic in that same forum for closed topic.
",vladytimy
5620,Add link to view=all for moderators,Support Forums,normal,enhancement,,new,2021-02-16T15:16:47Z,2023-04-05T16:39:00Z,"Moderators have the possibility to include archived and spammed topics when viewing:
- A specific topic thread
- A user's profile
- Topic lists in a forum
- the view ""all-topics""
However, when operating from a mobile, it's not very user-friendly to edit the URL field in the browser and add this parameter.
Two suggestions:
1. Add a convenient link (visible only to mods and admins) to view the same page with the view=all query parameter added.
2. When watching a user's profile with the query parameter view=all enabled, include this parameter in the on page links for topics, replies and reviews.
Related #2490",tobifjellner
3999,"Add link/button to create new topic near ""reply form""",Support Forums,normal,enhancement,SergeyBiryukov,reviewing,2018-12-13T18:07:13Z,2023-04-05T16:59:23Z,"Quite often, users who want to ask a new question submit their question as a reply to some earlier question (their own question or someone else's).
One reason for this seems to be that they've arrived to the forum either via an emailed link from a topic they've participated in earlier, or via Google.
And, once you're inside a specific topic, it's not too obvious how to add a NEW question/topic. There will be a link to the forum itself in the sidebar (which is further down on narrow screens), but it's still not obvious that that's the way to go.
Instead, they'll fill out the only form they see.
Suggestion: Add a button near the response form ""Create new topic""",tobifjellner
7297,Add locale mapping to DeePL API requests,General,normal,defect (bug),amieiro,assigned,2023-10-06T09:38:42Z,2023-10-18T19:30:31Z,"Currently GlotPress only send requests to ""base"" languages (es, de, fr) but if would be really useful if it also included all the variations.
For example, es_MX, es_AR, es_CR... can be requested as ""es""",nilovelez
5895,Add markdown validation to the readme validator,Plugin Directory,normal,feature request,,new,2021-09-10T13:03:32Z,2022-03-30T05:27:59Z,"There is a Readme validator on wordpress.org:
https://wordpress.org/plugins/developers/readme-validator/
But this is only checking for the readme standard:
https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/
And not for the markdown.
If a plugin is for example omitting the “closing” of the title markdown, writing `= V3.9.2 - 04.07.2021` instead of `= V3.9.2 - 04.07.2021 =` the validator wouldn't mark this with an error or warning or note.
Although it would help to show a preview (see: #2538), maybe we could validate markdown additionally.
There are some PHP markdown parser, but I am not sure if there are validators (or if those parser can be used for validating):
https://php.watch/articles/php-markdown-libraries
If we have a plugin/library for this it could be used in Github actions or other test environments before deployment to wordpress.org. Or we could maybe add this check to the pre-commit hook, so we can reject committing wrong formatted Readmes.
Thanks to @dd32, @clorith an @ocean90 for the help on Slack about this issue.",zodiac1978
7426,Add minimum word count for description,Photo Directory,normal,defect (bug),,new,2024-01-29T12:48:00Z,2024-02-01T04:55:58Z,"Hey, often the photo descriptions are not detailed enough, the moderator team has much work to do with writing a detailed description for photos that they know little about because they are not their own.
In this pr I added a minimum number of words for the description.",benniledl
6582,Add new field in listing of projects,Translate Site & Plugins,normal,enhancement,,new,2022-11-20T12:05:46Z,2022-11-20T12:12:29Z,"Currently if you open the plugin project list or one of the other listings, it does not show a field ""Changes requested"". It would be great if that field could be added in the header of a project or in the the details
Now there is no way to see if within a project ""Changes requested"" are present.",psmits1567
3423,Add new functionality for editor/locale requests,Translate Site & Plugins,normal,task (blessed),,new,2018-02-06T09:07:04Z,2021-01-24T14:30:30Z,"There has been quite a lot of discussion within the Polyglots team about changing how we manage editor requests. Currently, the Make/Polyglots site is used to manage these requests but it's become clear that it simply isn't manageable as requests get lost, people forget etc. It's been proposed that we find a new way to handle these types of requests and reserve the P2 for the Global Team for other things instead.
Current list of proposed ideas (not exhaustive at all):
- Add new functionality into Translate.WordPress for users to click a button to 'request PTE' status.
- Add a new forum to the support forums where people can post a new thread to request things.
- Add a new UI to somewhere, perhaps a Rosetta site where people can request PTE status.
- Add a new Trac instance so people can create a ticket for a request.
Lots of ideas, some better than others but also some are more difficult to implement too.
We need something to integrate into the current PTE workflow that'll let GTEs add new PTEs easily as the current workflow doesn't work very effectively.
Please discuss and share ideas on how best to approach this.",danieltj
5339,Add new sorting filters to Plugins tab in the Translate WordPress dashboard,Translate Site & Plugins,normal,enhancement,,new,2020-07-25T07:30:08Z,2020-08-31T18:50:46Z,"
== Currently available filters for plugins and themes
The two tabs with the most translation projects on the translation platform dashboard (Translate WordPress), which are also the ones most used by translators, are Themes and Plugins tabs.
Each of these tabs has 11 different options for filtering plugins or themes with different criteria:
* Untranslated Favorites, Remaining Strings (Most first)
* My Favorites
* Remaining Strings (Most first)
* Remaining Strings (Least first)
* Waiting + Fuzzy (Most first)
* Waiting + Fuzzy (Least first)
* Waiting + Fuzzy (Newest first)
* Waiting + Fuzzy (Oldest first)
* Percent Completed (Most first)
* Percent Completed (Least first)
* 100% Translations
[[Image(https://i.imgur.com/6ubL8eN.png)]]
''A view of the current filters in the Plugins and Themes tab''
== What filters can and cannot do
These sorting filters are enough to work with themes, as them only have one translation project and work perfectly when you want to sort the results according to the tasks you have planned: translate themes from 0%, complete plugins with few strings, etc.
The same is not happening with plugins. A plugin generally have four translation projects:
* Development (trunk)
* Development Readme (trunk)
* Stable (latest release)
* Stable Readme (latest release)
The platform counts the strings by calculating the sum of the strings from all the projects, including the Readmes. The issue with this is that translators generally give priority to the Development/Stable strings that are applied to the plugin itself, while the Readme strings refer to the information shown on the plugin page at WordPress.org and the changelog, which is usually of lower priority.
At es_VE locale we have many plugins 100% translated, but some of them still have strings pending in the Readme projects (over 1000 in some). So when you use the current filters, there's no way to filter out plugins with pending or 100% finished strings for only the Development/Stable projects. This makes it difficult for you to translate the new strings in the updated plugins because the results you get are not accurate when including the Readme projects.
As an example, if at this moment you use the [https://translate.wordpress.org/locale/es-ve/default/wp-plugins/?s=&filter=percent-completed Percent Completed (Most first)] filter to see the new strings added to the updated plugins in order to complete them, the results will be return plugins that are currently already at 100%, but have pending strings in the Readme projects.
[[Image(https://i.imgur.com/17dsLZ0.png)]]
''Example of results when using the Percent Completed (Most first) filter: The plugins shown are already translated.''
== The proposal: add 4 new filters
An improvement that would significantly enhance the translators' experience is the addition of 4 new filters that allow to skip readme projects from the results. The proposed filters are the following:
* Remaining Strings - Development/Stable (Most first)
* Remaining Strings - Development/Stable (Least first)
* Percent Completed - Development/Stable (Least first)
* Percent Completed - Development/Stable (Most first)
[[Image(https://i.imgur.com/2OafOSO.png)]]
''A sketch of the proposed filters.''
",YordanSoares
6591,Add Note or Feedback comment Add/Editor not working,Developer Hub,high,defect (bug),,new,2022-11-23T13:55:50Z,2023-02-28T09:48:38Z,"Go to Any function of wordpress
For Ex : https://developer.wordpress.org/reference/functions/wp_get_attachment_url/
Try to Add comment which having some php code
for test i'm trying to add
Ex :
ID);
foreach($media as $post_images) { ?>
ID )); ?>"" />
After adding above code switch to preview and it display completely wrong code
i have tried with inbuilt [php] & [code] none works
Check the screenshot attached
",mayur8991
6549,Add notifications for Publish/reject of video submissions,WordPress.tv,normal,feature request,,new,2022-10-24T01:15:38Z,2022-10-24T01:16:38Z,"Hi everyone,
I sent the video ""Creando un Sitio WordPress desde Cero con Gutenberg"" last week and I haven't heard back, I don't know how it is known if the video is approved or already published. I have asked in the wptv channel on slack and they suggested me to put a ticket here.
It would be good to add email notifications when the video is published or rejected",tets
7478,Add option to deactivate glossary on pages,Make (Get Involved) / P2,normal,defect (bug),,new,2024-02-20T14:34:10Z,2024-02-20T14:34:10Z,"Hey, I am using the glossary plugin and I would like to only use the glossaries on posts.
I would love to either have a settings page and allow to turn of the glossaries on pages or even better have a filter in Glossary_Handler::glossary_links that allows to not do glossaries on the content.",benniledl
6534,Add option to delete or request to delete photo,Photo Directory,normal,feature request,,new,2022-10-12T05:42:44Z,2022-10-12T05:42:44Z,"While uploading the photo to the photos directory, mistakenly I uploaded the same photo twice. So, I want to delete the duplicate photo but there is no option to delete it.
If we provide the option to delete the photo, then the author will delete such photos from their own.
Or, we can add an option to request to delete the photo and a notification will be sent to the moderator and they can take the action after checking it. ",kafleg
6911,Add Patterns Tab in profiles page,Profiles,normal,enhancement,,new,2023-04-03T04:28:47Z,2023-11-15T19:52:14Z,"On WordPress.org [https://profiles.wordpress.org/kafleg/ profiles page], we can see the contribution tab for activity, themes, plugins, photos, etc. But Patterns is missing. As we have a separate directory for the patterns, I would love to see patterns on the profiles page.
It's a great way to appreciate the contributors and acknowledge them. ",kafleg
5731,Add performance index to each theme and plugin in the repository,General,normal,enhancement,,new,2021-05-09T14:57:17Z,2021-05-11T19:04:06Z,"To add a performance index to each theme and plugin in the repository is a big thing, but this will make authors think about performance, how many queries to a database they are making and how difficult their code is to execute and users of this theme or plugin can have a better understanding if usage of it worth at all.
I think it's something that the Tide Team can do for the greater good.
When an e-shop with one purchase in a couple of days has a heavy premium theme and a mountain of plugins, many of which can be disabled easily, and using costly hosting just for all this to run, it is a bit ridiculous. Hopefully, by having good examples at hand such site owners will start asking high-performance from authors to whom they are paying and we will raise standards and save more energy for purposes of fighting global warming as a side effect.",oglekler
2902,Add PHPCS to theme upload process,Theme Review,normal,enhancement,,new,2017-06-27T17:36:32Z,2023-08-24T16:12:19Z,"As we are working on a PHPCS ruleset that we can apply to WordPress Themes this should run during the upload process.
https://github.com/WPTRT/WordPress-Coding-Standards",grapplerulrich
4977,Add plugin closed message to plugins_api.,API,normal,enhancement,,new,2020-01-21T21:21:26Z,2022-06-03T11:07:28Z,"Currently, the return is a WP_Error, which is fine. However, the message displays that the plugin could not be found. With our use-case, we're trying to distinguish between third-party plugins and .org plugins. Ideally, the message would be contextual.
I suggest that there are two WP_Error objects we can expect from the API. One if the plugin is missing (and it truly doesn't exist) and one if the plugin has been closed (meaning, it exists, but is closed).
This would benefit our use-case, and I imagine other plugins that need to check programmatically if a plugin has been removed from the repo.",ronalfy
1502,Add redirects for URLs referenced in git-svn-id,Trac,lowest,enhancement,,new,2015-12-30T18:30:50Z,2022-06-05T17:29:50Z,"Looking at older commits in my Git repo shows me a `git-svn-id` with a URL to the SVN changeset, but those URLs go to a generic Apache 404 page. Can we redirect them instead to the commit page of Trac?
For example, https://develop.svn.wordpress.org/trunk@14248 would be redirected to https://core.trac.wordpress.org/changeset/14248.",morganestes
6642,Add rel-me to profile links,Profiles,normal,enhancement,,new,2022-12-22T10:31:00Z,2023-06-05T01:18:01Z,"Add [https://microformats.org/wiki/rel-me] (XFN) to ""Website URL"", ""GitHub URL"" and "" Find me on:"" Links.
With this it is possible to easier use the WordPress Profile page with several IndieWeb ([https://indieweb.org]) services and to verify the Profile on Mastodon: [https://docs.joinmastodon.org/user/profile/#verification]",pfefferle
5471,Add Serbian Latin locale with transliteration of Serbian Cyrillic locale,Translate Site & Plugins,normal,task (blessed),ocean90,reopened,2020-10-11T15:36:45Z,2023-01-26T12:11:58Z,"Background: https://make.wordpress.org/polyglots/2017/12/07/revisiting-serbian-latin/
Todos:
- Create a new locale sr_SR_latin
- Set up translation sets on translate.w.org for sr/latin
- Make translation sets for sr/latin read-only
- Add a task which automatically copies new translations from sr/default with transliteration to sr/latin
- tbd;",ocean90
5462,Add signposting to the end of truncated pagination,General,low,enhancement,,new,2020-10-05T10:20:26Z,2020-10-05T10:21:21Z,"For logged-out users, we cut off all pagination at 49 pages. This aims to reduce the performance impact of requests to deeply paginated URLs.
This has an unfortunate side-effect of making it ''seem'' like there are only 49 pages of any given result type. This may confuse users.
As such, when a logged-out user requests page 49 of a series (which would otherwise have had more than 49 pages), we should show a ""Log in to see more"" component.
This may require some minimal design and copy considerations.",jonoaldersonwp
6610,Add smooth scroll to the page for jumping another section,WordPress.org Site,normal,enhancement,,new,2022-12-03T06:45:55Z,2022-12-05T08:36:59Z,Currently the wordpress.org and it's associated websites has no smooth scroll effect for jumping another section from the navigation panel. I think this could be great enhancement if the smooth scroll feature was done.,saifullahsiddique
6964,"Add some calming comment about spurious IMG tags from emojis leading to ""links in reviews""",Support Forums,normal,defect (bug),dd32,accepted,2023-04-28T15:52:33Z,2023-05-03T01:23:34Z,"If a user adds an emoji in a ""blockified"" forum, then this creates some spurious IMG tags. This problem is tracked in https://github.com/Automattic/blocks-everywhere/issues/135
However, until that gets solved, we have a situation with unclear communication, as a dependency:
It would be good to add a note in the following two strings about this:
https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html/wp-content/plugins/support-forums/inc/class-ratings-compat.php?marks=365#L365
{{{__( 'Error: Please do not add links to your review, keep the review about your experience in text only.', 'wporg-forums' ),}}}
https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html/wp-content/plugins/support-forums/inc/class-ratings-compat.php?marks=499#L499
{{{__( 'Please do not add links to your review, keep the review about your experience in text only.', 'wporg-forums' ),}}}
Something along the lines: ""In some cases, you may get a false report of this problem if you've been using emojis in your text.""
Reported in Slack by abitofmind",tobifjellner
3240,Add speaker's social media handle to WordPress.tv video link,WordPress.tv,normal,enhancement,,new,2017-11-01T11:30:03Z,2021-04-14T06:57:23Z,"Hello,
I run the Twitter account for our local WordPress meetup. Amongst other things, we like to use it to share videos from WordPress.TV that we think our members and followers may be interested in.
The ""Click to Share on Twitter"" button very helpfully gives us the box already filled-in with this format: [Speaker's name]: [Talk title] [url] via @WordPressTV
But we also like to let the speakers know their talk is appreciated. So if they have a Twitter account, we normally swap the Speaker's name for their Twitter handle.
This, however, means a few extra minutes work digging around either the event's website, google or twitter itself.
Since this information is already available to the WordCamp organisers (most of us normally enter it when registering to attend), I thought it may make a small change that would benefit both end users and speakers.
Many thanks.",carmemias
4621,Add support for 'Tested up to' header in the main plugin file,Plugin Directory,normal,enhancement,,new,2019-07-23T22:21:36Z,2022-10-21T09:48:07Z,"Background:
* #2952 added support for `Requires PHP` plugin header in `readme.txt`.
* #4514 added support for `Requires at least` and `Requires PHP` headers in the main plugin file.
Since [9050], the preferred placement for `Requires at least` and `Requires PHP` headers is the plugin's main file, rather than `readme.txt`.
(Per discussion with @Otto42 in #WP46938, WordPress core should read the headers it needs from the plugin's PHP file, while the `readme.txt` is intended for the WordPress.org directory.)
It occurred to me that the `Tested up to` header still can only be defined in `readme.txt`. Even though core doesn't read it from the file at the moment, I think it makes sense to be able to define all three headers (`Requires at least`, `Tested up to`, `Requires PHP`) in the same place, for consistency.
Otherwise, developers who define them in the plugin's main file could be confused as to why two of them work as expected, but the third one does not.",SergeyBiryukov
5665,Add support for comma separated revision numbers on Make blogs,Make (Get Involved) / P2,normal,defect (bug),,new,2021-03-16T18:55:24Z,2021-03-17T00:24:38Z,"On Trac, specifying a commit range with commas and/or hyphens is supported:
- [1234,5678]
- [1234-5678]
- [1234-5678,9012]
The same format is supported on Make blogs, but it seems that commas do not get matched.
I noticed this while [https://make.wordpress.org/core/2020/12/23/continuing-the-transition-to-github-actions-for-automated-testing/?preview_id=86231&preview_nonce=8e50cc6f08&preview=true rereading this post] before drafting a followup (see the last paragraph before the ""Known next steps (updated)"" heading 2/3 the way down).
I also tested with only commas, but that also does not work. So using `,` combined with `-` can be ruled out as the reason.",desrosj
6862,Add support for component Slack channels,Make (Get Involved) / P2,normal,enhancement,,new,2023-03-15T19:01:14Z,2023-03-15T19:16:43Z,"On the components pages, it would be nice to link off to Slack channels when a component has one. This would make it easier for someone to get started contributing to that component help encourage more public conversations instead of contributors DMing others listed as maintainers.",desrosj
2424,Add text of reviews to plugin search to improve search,Plugin Directory,normal,enhancement,,new,2017-01-23T17:03:48Z,2021-07-22T19:26:43Z,"Plugin search has a disconnect between the terminology that the plugin author uses and what an end user of the plugin uses. We should be able to help bridge this gap by indexing the text of reviews of the plugin. For plugins with a small number of reviews we will probably index all of the text. For very large plugins we can do some simple analysis of the reviews to pull out the important words (maybe using significant terms on an ES index of the support forums).
Background:
- reviews are stored in the support forums (bbPress2)
- There are 8.5m posts in the support forums and some (presumably large) number of comments
Steps to make this happen:
- Jetpack needs to be installed on the forums
- Jetpack sync needs to be enabled to sync all posts and comments from the forums (and some amount of post meta probably)
- An Elasticsearch index with all support forum threads needs to be created
- A new field(s) should be added to the plugin ES index containing data from the forums, and the all_content fields should have review data added to them
- The search query needs to be modified to use the new field
By completing steps 1, 2, and 3 the Jetpack search api will also be able to support searching within/across forums.
The hardest and most unknown part of this (to me) is installing JP (and maybe debugging JP Sync if there are problems). The ES indices (including indexing bbPress2) is all stuff we've done before.
",gibrown
3178,Add user-friendly explanations of current workflow keywords on a ticket,Trac,normal,enhancement,,new,2017-10-03T12:42:29Z,2017-10-04T19:59:05Z,"When a ticket is closed on a completed milestone, a helpful message is shown at the bottom of the ticket:
[[Image(https://i.imgur.com/2YnqngO.png)]]
It would be neat if similar messages were displayed on tickets which have the following keywords:
* `needs-testing`
* `needs-refresh`
* `needs-patch`
The intention is for inexperienced users to see a helpful message that clearly states the next action that needs to be taken on a ticket. For example, the message for a ticket with the `needs-refresh` keyword could be:
> This ticket has a patch that is out of date and no longer applies cleanly. The existing patch needs to be updated, or a new patch needs to be written. Click here for information on how to write patches.
Ideally the messages would stand out more clearly, possibly in the same style as the ""Are you in the right place?"" message at the top of the new ticket screen.",johnbillion
6401,"Add verification for the user names in the ""Props"" in commit messages",Version Control,normal,enhancement,,new,2022-07-11T20:49:54Z,2022-07-12T02:07:36Z,"It's pretty bad/quite embarrassing when there are any errors in the props part of a commit message. This idea to reduce that risk came while chatting with @hellofromTonya: would it be possible to verify the WP.org user names that are added as props in commit messages? Can probably be (yet another) precommit script, perhaps.
Then if a prop doesn't match any user name, stop the commit and look into the GH to trac name conversion ""list"". If a match is found, suggest the change in the svn error message (is that possible?).",azaozz
5506,Add version validation to Release tooling,WordPress.org Site,normal,defect (bug),,new,2020-11-13T02:48:46Z,2021-06-02T21:35:30Z,"The WordPress.org release management tooling currently trusts the user filling out the forms, and prefills/includes details about what it's going to release, but it's easy to forget / miss something.
For example, today beta4 was originally packaged as `5.6-beta4-49588` rather than `5.6-beta4`, a mistake that has happened numerous times before (Sometimes due to core.svn builds being delayed, others just mistakenly not bumped the right digits).
In the past we've also had `x.y-Beta1` (should be lowercase, unlike `x.y-RC1`) and also minor versions skipped (ie. releasing `x.y.3 -> x.y.5` instead of `x.y.4`, unintentionally skipping a digit), both of which should easily be prevented with some simple version checking in the UI.
There's also some checks in place to work with/prevent the re-releasing of packages, so more UI around ""This doesn't quite look right, are you sure?"" would benefit others in the future.
cc @helen and @SergeyBiryukov since you've been doing most releases lately, is there anything else that comes to mind that I've missed here? If it's something that human eyes can say ""That doesn't look quite right"" then surely some big red text to that effect wouldn't go astray :)",dd32
7490,Add Wistia shortcodes to be able to add Wistia videos to plugin readme.txt files,Plugin Directory,lowest,feature request,,new,2024-02-25T08:55:15Z,2024-02-26T03:45:07Z,"Currently, the readme.txt only supports embedding of YouTube and Vimeo video files.
I want to request the addition of Wistia video embeds.
Why Wistia?
Wistia is a platform with business goals in mind. It allows for more control over the videos shown on plugin description pages.
The most interesting features to me are:
- Allows AB testing of videos, which helps find the video version with the most positive impact on the viewers.
- More stylistic control, like changing backgrounds or adding rounded corners.
Why is that interesting for the wordpress.org repository?
Suppose plugin developers have better tools to measure the impact of their videos on their audience and improve those videos based on that data. In that case, it will help them create better videos and a better plugin experience overall. ",alekv
5326,Adding a tag Free / Freemium,Plugin Directory,normal,feature request,,new,2020-07-21T09:50:52Z,2022-03-30T05:27:59Z,"Hello,
This ticket follow a discussion hold in the French WP Slack about completely free and freemium plugins.
Several folks think we should know before installing a plugin if it's a free plugin or a freemium plugin.
For some people it's a search criteria to not have paying features in the plugin they will install.
We think about a tag in the header which add an icon in the Plugin directory and in the WP Backend.
What do you think about this idea?",sebastienserre
3878,Adding Badges for WordCamp Volunteers and Attendees,Profiles,normal,enhancement,,new,2018-10-20T17:45:23Z,2023-06-12T14:41:39Z,"Hello,
I just come back from the Nice WordCamp (in Nice France) and realize that 2 badges are missing.
* Volunteer: Without volunteer,there's no WordCamp, their job is wonderfull and a badge should be automaticclay or manually assigne by the lead organizator.
* Attendees: because.... the same (without attendees no WordCamp and they're speaking around them about the events and our community so they allow the comunity to growth.
What are you thinking about this?",sebastienserre
6023,Adding theme upload page link in Trac ticket,Theme Directory,normal,enhancement,,new,2022-01-18T15:51:14Z,2022-03-09T09:56:45Z,"On themes Trac ticket page, it would be great we had a link to the upload page. https://themes.trac.wordpress.org/ticket/111076
It can use the same footer or footer text as https://wordpress.org/themes/
The text that we have on the themes page footer is:
**Add Your Theme**
The WordPress theme directory is used by millions of WordPress users all over the world. [https://wordpress.org/themes/getting-started/ Submit your theme] to the official WordPress.org theme repository.
",kafleg
6271,Admin actions bumps last updated date,Theme Directory,normal,defect (bug),,new,2022-04-12T06:59:35Z,2022-07-29T05:21:50Z,"Marking a theme as delisted, or relisting said delisted theme, changing author, etc, updates the `post_modified` date to now - that field is used for the `Last Updated` date in the themes API.",dd32
3158,Advanced Search Filtering Keywords,Developer Hub,normal,enhancement,,new,2017-09-22T16:32:21Z,2022-09-26T02:24:40Z,"Hello! I'm a fan of the DevHub but I would like a little more advanced search filtering keywords. These don't necessarily need to have easy UX as that could get messy but definitely needs documentation somewhere.
A usecase example would be when searching for hooks, you can click the ""Hooks"" checkmark which will pull up hooks matching your query... but what if you only want to look for action hooks or filter hooks?
Or, if I want to pull up all hooks or functions in a certain file? Available in a certain version?
The first thing that comes to mind is what I'm used to which is the WordPress Stack Exchange [https://wordpress.stackexchange.com/help/searching ""Advanced Search""] which uses a simple structure of `keyword:value` and could maybe be used here too. Possible keywords could include:
- `type:action` | `hook:filter`
- `file:comment.php` | `file:wp-includes/admin-bar.php`
- `version:4.8` | `vers:4.0`
This is something that could be built upon but I think it's a nice step forward without adding clutter to the clean search as it is now.
",Howdy_McGee
7221,"After download, link Get Involved to /Contribute",Make (Get Involved) / P2,normal,enhancement,,new,2023-08-19T20:35:48Z,2023-10-12T22:59:00Z,"
Let's change the link on Get Involved to [https://make.wordpress.org/contribute]
[[Image(https://cldup.com/XrSb0qFFQx.jpg)]]
[[https://cloudup.com/cZrsRmuDk3z(Screenshot)]]",courane01
7304,Alignment issue on all tickets listing pages.,Trac,normal,defect (bug),,new,2023-10-16T07:18:39Z,2023-12-05T18:20:33Z,"
On all ticket listing pages like ""https://meta.trac.wordpress.org/report/1"", in ""Update"" & ""Max items per page"" the vertical alignment is broken for the ""Update"" button and other elements.
Attaching a screenshot for reference.
",sujichandran14
5146,"All Recent Topics RSS Feed returns topics from plugins and themes, not the general forums",Support Forums,normal,defect (bug),,reopened,2020-04-14T16:05:52Z,2023-03-29T08:46:01Z,"I've just subscribed to the Recent Topics RSS feed in Slack https://wordpress.org/support/topics/feed/ but it only seems to be returning topics created on plugin and theme support pages, and none from the general forum topics.",mmediagroup
5911,Allow 'contributors' that can edit published handbook pages to edit them without review,Handbooks,normal,defect (bug),,new,2021-09-22T08:50:20Z,2021-09-22T08:51:49Z,"When a user is added to a make site with any role (including the 'contributor' or 'subscriber' roles), they're granted access to edit handbook pages, including published ones.
However, if they attempt to edit the page, they're forced to 'submit for review' which unpublishes the existing page.
If the user has the 'edit_pages' capability, they're able to edit and publish handbook pages (but not actual pages).
HelpHub has a dedicated Editor role, perhaps that's needed here, or we should just let all users (other than 'subscriber'?) on a site edit all aspects of handbook pages.
See https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html/wp-content/plugins/handbook/inc/handbook.php?marks=43-71,306-327#L300",dd32
2289,Allow cmd/ctrl-enter to submit the comment form in Trac,Trac,normal,enhancement,SergeyBiryukov,reopened,2016-12-03T05:53:47Z,2020-09-14T14:29:28Z,"Trac is very jumpy when composing comments and the preview loads. It's very easy to lose track of the submit button or even misclick. I'd like for cmd/ctrl-enter to submit that form, as it's a very common paradigm and particularly helpful when you're quickly leaving comments on Trac.",helen
2847,allow filtering of @since tax archive by the type of change,Developer Hub,normal,enhancement,,new,2017-06-02T01:33:48Z,2019-05-27T03:10:13Z,"It would be very helpful to allow filtering of the @since tax archive by whether the change in a given version was a ""newly introduced"" vs. a ""modification"" from previous versions.
This would be useful not only for developers but also for those writing dev-notes (or the Field Guide) as a new release is being readied.",pbiron
7055,Allow filtering of the WordPress profile activity stream,Profiles,normal,feature request,,new,2023-06-13T06:44:07Z,2024-01-15T01:06:56Z,"It would be very helpful if you could filter the activity stream on a WordPress profile by the types of activity. Take my own feed for example:
https://profiles.wordpress.org/joostdevalk
It could look simple, will attach a gif.
",joostdevalk
3236,Allow for beta channels for plugins and themes,API,normal,enhancement,,new,2017-10-30T14:31:51Z,2021-07-28T21:29:22Z,"Ref: #WP42376
It would be neat if plugins and themes could tag beta versions which get delivered via the updates API to sites which have opted in to receiving beta updates.
Is this something that's doable?",johnbillion
6122,Allow for retraction before moderation,Photo Directory,low,enhancement,,new,2022-02-18T16:54:11Z,2022-03-17T09:47:17Z,"In the list of unmoderated images, make a link to allow the submitter to retract (delete) it. This would only exist for unmoderated photos.",topher1kenobe
6485,Allow GTE's to manually release language pack for project,Translate Site & Plugins,normal,feature request,,new,2022-09-14T14:09:47Z,2022-09-14T15:53:17Z,"Currently language packs are released dependent on amount of translated strings when they reach threshold (i.e. for plugins and themes its 90%),
once created language pack will be updated everytime despite amount of translated strings (it can fall below threshold).
Here are different scenarios for using it, notably this case:
https://make.wordpress.org/polyglots/2022/09/12/translating-for-the-user-isnt-it/
plugin or theme may have enormous count of promotional, advertising and even strings indendent for PRO version use.
Discussed in Slack meeting:
https://wordpress.slack.com/archives/C02RP50LK/p1663163184676919
Up and somewhat below.
This button shall IMO be available for GTE's only, so PTE's are still encouraged to get their project translated without asking for an exception.
",fierevere
5552,Allow mods to hide moderator badge,Support Forums,low,enhancement,,new,2020-12-18T03:50:15Z,2023-06-13T14:27:12Z,"Recently it was pointed out that super admins on WordPress.org (ie. some of the most active meta developers currently) are classified as Moderators on the support forums - that's in general a good thing, but it's also resulted in any of our support replies being flagged as moderators, even if we're not part of the moderation team.
It was also pointed out, that threads started by moderators (For example, reviews) are also flagged as moderator posts, when it has nothing to do with their moderation capabilities.
I'm putting this out there for discussion:
1. Should an option for moderators be added to exclude their badge from a given reply/thread?
AND/ OR
2. Should the moderator badge be updated to check for specific roles being applied, rather than moderation capabilities, so that those of us who are super admins (but not part of the moderation team) aren't flagged as such?",dd32
5535,Allow moving threads into the Plugin/Theme support forums,Support Forums,normal,enhancement,,new,2020-12-09T05:57:17Z,2023-04-05T16:18:11Z,"Currently to move a thread into the Plugin/Theme support forums, a moderator is required to load wp-admin, add the appropriate taxonomies, and then change the forum to 'Plugins' or 'Themes'.
It'd be much easier if there was a move-to-plugin/theme option available in the thread view.",dd32
6588,Allow multiple changes on one topic edit,Support Forums,normal,defect (bug),,new,2022-11-22T17:55:13Z,2023-05-04T09:01:29Z,"When modifying a post to change the forum (e.g., requests and feedback to fixing wordpress), changing the stats of the NSFW box at the same time gets lost if it's the same transaction.",sterndata
969,Allow multiple screenshots,Theme Directory,high,enhancement,,new,2015-03-22T21:30:42Z,2022-10-19T22:07:44Z,"At the moment only one screenshot can be uploaded
Themes are about designs. Screenshots are great for displaying the different design elements on the theme.
The screenshot is normally of the home page without any plugins activated. Some themes support specific plugins and it would be helpful for the users to see at a glance how the theme looks like with those plugins activated.
The theme demo #30 at the moment is very bare and the screenshots are good alternative.
",grapplerulrich
5708,Allow only moderators to remove modlook tag,Support Forums,high,defect (bug),,new,2021-04-20T06:00:58Z,2022-04-08T14:35:45Z,"Currently, if someone reports a topic, the tag ''modlook'' is added. As far as I understand, the author or anyone replying on that topic can remove ''modlook'' tag from the list, before a moderator has the chance to review that report, so unless the topic is reported again, it stays in the wild as it is.
The ability to remove ''moodlook'' tag should only be available to moderators.
Maybe an extra check {{{user_can( $user_id, 'moderate' )}}} when ''modlook'' is removed from the list of tags would do the trick.",vladytimy
6839,Allow option for anonymous posting by moderators,Support Forums,high,enhancement,,new,2023-03-07T16:18:14Z,2023-08-10T17:46:04Z,"There are some occasions where it would be valuable for a moderator to have the ability to post anonymously in the support forums.
Having this functionality would offer individual moderators some protection from being contacted directly in Slack or ""followed home"" outside the forums.
This would in turn reduce the potential for harassment of moderators, which has occurred before, and which has discouraged some folks from moderating more actively.
It would also provide a unified voice to help better educate and familiarize posters with the forum guidelines, and also encourage more replies to remain public.
Posting anonymously could be **optional** – and other moderators would still be able to see who made the post, in case any follow-up is needed.
Attaching a quick mockup below for one idea of what this could look like on the posting side.
(I accidentally removed the original post, re-adding!)",zoonini
7380,Allow plugin reviewers to test newly submitted plugins in Playground,Plugin Directory,normal,enhancement,,new,2023-12-20T06:41:09Z,2024-02-23T04:21:03Z,"Currently, the Live Preview button in the Plugin Directory is only available for published plugins.
It would be helpful if the plugin moderation team had an easy way to preview and test plugins that have been submitted to the Directory but not yet published.
This requires a few moving parts:
* A mechanism to generate Blueprints specially for plugin reviewers
* CORS headers to allow Playground to fetch uploaded plugin zip files (since unpublished plugins are not available from `downloads.w.org`)
* Preview links in the queue admin pages
",tellyworth
6878,Allow plugin slug changes during approval-stage,Plugin Directory,low,enhancement,,new,2023-03-23T03:07:58Z,2023-03-23T03:07:58Z,"First let me say: NO, we don't want to support plugins changing their slugs. This is super-complicated and out-of-scope of this ticket.
Plugins can currently have their slug changed prior to being approved, but once approved the team has no ability to change the slug. This is because it's at this point where the SVN directory is created, SVN access is granted, etc.
It would be useful if there was a tool that allowed a plugin reviewer to force-change a plugin slug in that approved stage, before the author commits code. This is sometimes needed as authors don't attempt to let the reviewer know their desired slug until too late, or, something happens on our end that causes the slug not to be set properly.
ie, it'd be a tool that works in the below 'approved' post_status:
- pending: New plugin submission, slug can be changed at will by reviewer.
- approved: Plugin submission approved, slug can no longer be changed.
- publish: Plugin author has committed code, slug changes are never permitted.
",dd32
7167,Allow plugin/theme autor to opt-out of translate.wordpress.org,Translate Site & Plugins,normal,feature request,,new,2023-08-01T07:38:27Z,2023-08-02T16:48:48Z,"There are some cases where projects can and shouldn't be translated in translate.wordpress.org
* Projects that are translated in an external GlotPress (i.e. Mailpoet)
* Locale-specific plugins (TypeSquare Webfonts for エックスサーバー)
* Freemium plugins that include hundreds of hidden strings from the paid version
We need a way of getting those kind of projects out of Translate, both for saving server resources and for avoid volunteers to waste time on translations that wont be used.
Proposed solutions:
* A readme.txt/style.css flag to opt-out from translation
* A way for Plugin Review Team moderators to flag projects as opted-out fron translation
* A streamlined way of removing translate.wordpress.org projects",nilovelez
3505,Allow plugin/theme reps to respond to reviews at any time,Support Forums,normal,enhancement,,new,2018-03-11T09:54:15Z,2023-06-14T10:49:41Z,"Currently, we allow reviewers to edit their review indefinitely, but the topic it self is auto-closed like everything else on the forums.
If a review is edited, the reps have no way of reacting to this if that cutoff date is hit.
Opening up reviews to allow replies at any time for those with commit, contributor or support rep roles with a plugin or theme makes sense, and would of course also mean opening it up to the reviewer to respond to those replies.
The drawback here is that by doing so, we are negating the effect of manually closing a review, which is currently done if a review goes off the rails.
Is this trade off acceptable? If they go off the rails then the user(s) are generally flagged as well as is, this would mean flagging is the only reliable reaction in such a case.
See also #3504 which is related, but doesn't cover the aspect of opening things up after the auto-cutoff.",Clorith
3507,Allow pre-defined page slug translations,International Sites (Rosetta),low,task (blessed),,new,2018-03-12T01:23:11Z,2020-04-09T03:22:08Z,"As a spin off of #3046 it'd be great if we can allow rosetta sites to translate page slugs.
For example, currently we've got `/plugins/` and `/themes/` (both are actual sites though, not pages) and we're about to add `/about/*` (Which are pages), these english slugs are not very welcoming when everything else on the site is translated.
The translation should occur through translate.wordpress.org, I'd suggest something like `_x( 'about', 'Page Slug' );` or something along those lines.
Combine that with a cron-job which pulls from GlotPress and pushes changes to rosetta sites, a `site_url` filter to change the english versions to the translated ones, and some code to remember old page slugs.",dd32
3880,"Allow redefining or augmenting information in the ""INTERESTED IN DEVELOPMENT?"" section",Plugin Directory,normal,defect (bug),,new,2018-10-22T19:22:33Z,2018-11-29T00:10:25Z,"Currently:
Browse the code, check out the SVN repository, or subscribe to the development log by email or RSS.
We should really be able to override this text and these links since:
- Development is almost always on Github
- Github's code-browsing features are more intuitive and familiar to most developers
- Github provides it's own methods for subscribing to development progress
- Github provides it's own contribution documentation recommendation through the CONTRIBUTING.md -- we should be able to link to that here.
Unfortunately, I think most people are trained to ignore that section, and instead look in the readme sections for contribution information, but it seems obvious we should make this section more realistic, intuitive, and configurable by plugin authors. And if not configurable, at least providing the ability to add more text below it by way of another readme section.",jtsternberg
7177,Allow Seemingly Anonymous forum post Edits,Support Forums,normal,enhancement,,new,2023-08-04T16:30:15Z,2024-03-14T08:32:58Z,"Related to #6839, #5718, #5717
When a post is edited by anyone, it puts in their name and the time.
By default, if the action is done by a moderator and it's **NOT** their own post, this should show as 'WordPress Moderation Team' instead of the user name, but only to the logged in users.
All other mods and cape wearers should be able to see which Mod did what, for accountability.
Right now, we have a checkbox for 'don't log edit'
I recommend we ''remove'' that, and change it to an auto-checked ""log edit as anon""",Ipstenu
3043,Allow team reps to assign contributor badges,Profiles,normal,enhancement,coffee2code,assigned,2017-08-15T11:11:25Z,2020-08-27T06:23:49Z,"As per the discussion here: https://meta.trac.wordpress.org/ticket/3036#comment:4
Currently it seems that only Network Administrators can assign badges to contributors (i.e. add them to the badge groups). It would be great if we could extend this to allow selected individuals (the team reps most likely) to do this as well.
While some badges are assigned automatically, there are certain contribution paths that are not able to have automated badges due to the nature of the contributions. In those cases, the contributors need to be manually added to the relevant group(s) and it would be a whole lot simpler if team reps could do this themselves at their discretion.
Let me know if you need any further info from me about the requirements here, but it's pretty straight forward as an idea (although I'm not sure how simple it would be to implement).",hlashbrooke
5693,Allow themes to re-use a rejected slug,Theme Directory,low,enhancement,,new,2021-04-06T07:04:07Z,2021-04-07T00:53:07Z,"Currently when a theme is rejected/not-approved the rejected theme blocks the usage of that slug going forward.
For example, in 2010 a theme called 'Green' was uploaded: https://themes.trac.wordpress.org/ticket/2 and added to SVN: https://themes.trac.wordpress.org/browser/green/
That theme was rejected, but 11 years later no other theme can re-use that slug without someone from meta stepping in to make it happen.
That's a ""bad"" example, as uploading a theme called Green would actually be blocked by the active installs check, but it's an example of a theme that we've still got hosted even though it's not of benefit to anyone.
I think we should remove these old uploads which haven't been accepted/etc and allow the name to be re-used by something else - assuming it can meet the other upload requirements.
Perhaps it should stay blocked for the author of the uploaded theme for a given amount of time, 12 months seems plenty of time to me, after that any rejected themes (that were never published) should release their slugs and remove their SVN directories.
Having the post objects shift from being in a 'draft' state to 'rejected' would also help cleanup the wp-admin listing.
Proposal:
For any submitted theme that is marked as rejected, and has never been published on WordPress.org:
- After 12 months, rename the post slug to `rejected-$slug` to free the slug
- After 12 months, `svn rm https://themes.svn.wordpress.org/$slug` to free the SVN location",dd32
2947,Allow uploading and embedding of video files to Trac,Trac,normal,enhancement,,new,2017-07-10T16:54:44Z,2017-07-11T00:02:03Z,"It would be great to be able to upload and embed a video (at least mp4s) to Trac. Often when showing off an existing flow or demonstrating a patch, we'll have to record our screens, and then convert or export the video to a gif. However, gifs are large, compress poorly, and you can't manipulate them at all to pause/rewind/skip ahead. It's a really bad experience.",melchoyce
5453,Allow users to view their props launched in a release,Trac,normal,defect (bug),,new,2020-09-26T12:57:06Z,2020-09-28T17:12:00Z,"When I'm on the Trac Ticket Reports, I have no option to search for the ticket I have contributed in, like for example with a patch, and that has been released in a WordPress version.
As soon as the ticket is closed, it becomes a real struggle to search for it.
It would be nice IMO to have a new option named ""Tickets released with one of my contributions"" or something like this. With the possibility to query by WordPress version, so for example, I would be able to look after all tickets I have worked on for 5.5.",Mista-Flo
5875,Allow XML configuration examples in WP core handbook,Make (Get Involved) / P2,normal,defect (bug),,new,2021-08-24T21:38:51Z,2021-08-26T06:07:39Z,"In a recent [https://www.youtube.com/watch?v=O_sLjiPs494 working session on WP core testing local workflow] with @hellofromTonya, @jrf, and other contributors, the [https://make.wordpress.org/core/handbook/testing/automated-testing/phpunit/ documentation on PHPUnit usage] in WP core handbook was overhauled.
To make one of the test running workflow options clearer, the article includes this code snippet to be added to the `phpunit.xml[.dist]` file:
{{{
}}}
The problem is that this snippet is removed every time the post is edited, presumably by KSES filtering. So anyone editing the page currently has to keep that in mind, and reinstate the snippet over and over again.
It would be very helpful if the code was not removed on page edits. Since it is not meant to be executed, and is only there for documentation purposes, allowing this in the handbook context should be safe without any security concerns.",SergeyBiryukov
6086,Allow ZIP Uploads for plugin updates,Plugin Directory,normal,feature request,,new,2022-02-07T04:53:35Z,2022-03-30T05:29:41Z,"Not all plugin authors are comfortable with SVN, it would be beneficial if we could provide the ability for plugin updates to be uploaded through a form and/or an API.
Any uploads would be committed to SVN as trunk, tagged, and the existing release process would then occur.",dd32
6553,Alphabetically sort the Workflow Keywords dropdown,Trac,normal,enhancement,,new,2022-10-28T19:39:01Z,2022-10-28T19:39:01Z,"Apart from making the keywords list easier to read, sorting the keywords alphabetically will group the ""has"" and ""needs"" keyword types so that they are easier to select.
This would also make the dropdown's appearance consistent with the intentional ordering of other dropdowns, such as the alphabetical sorting on Component.
",ironprogrammer
5529,Alter trac robots.txt,Trac,normal,defect (bug),,new,2020-12-03T14:01:30Z,2020-12-03T14:01:36Z,"*.trac.wordpress.org sites should add the following rule to their robots.txt files:
`Disallow: *format=rss$`",jonoaldersonwp
6417,And prev/next navigation to single pattern view,Theme Directory,normal,defect (bug),,new,2022-07-21T14:53:24Z,2022-07-21T14:53:24Z,"The display of patterns on the theme page is fantastic!
When I click on a pattern, it opens nicely into a full page view with a left side menu on top of which I see arrows for navigation.
They let me go from theme to theme but I am missing similar prev/next buttons for the next pattern on the particular theme.
For that, I need to go back to the previous page and click on the next pattern thumbnail.
Here is a short video to see the process now.
I fear the top of the left navigation on the single theme and single pattern page would need to get a bit of a redesign, as it is now quite confusing. ",bph
6776,API-REST profile users link,Profiles,normal,defect (bug),,new,2023-02-17T08:30:44Z,2023-02-17T08:49:20Z,"Checking a profile URL via REST API, like:
https://profiles.wordpress.org/wp-json/wporg/v1/users/javiercasares/
The link URL is:
link: ""https://profiles.wordpress.org/author/javiercasares/""
But that URL doesn't work. It should be:
link: ""https://profiles.wordpress.org/javiercasares/""",JavierCasares
6977,Archive of taxonomy page should display the excerpt,WordPress.tv,normal,enhancement,,new,2023-05-09T08:58:53Z,2023-05-09T09:27:20Z,"Hello,
Some of the submitted video have a really long description. For example: https://wordpress.tv/2023/05/08/constructeurs-de-page-et-developpement-sur-mesure-les-bienfaits-de-lapproche-hybride/
This description is shown in the different archive page of WordPress.tv: https://wordpress.tv/language/frenchfrancais/
Should it be possible to automatically shorten them ?",sebastienserre
5536,Ask for the Plugin or Theme that a support thread belongs to in the Create Topic form,Support Forums,normal,enhancement,,new,2020-12-09T07:01:51Z,2023-04-05T16:24:17Z,"The create topic form on the Support Forums has this text displayed before it:
> Looking for help with a specific theme or plugin? Don't post here – instead, head to the theme or plugin's page and find the ""View support forum"" link to visit the theme or plugin's individual forum.
It seems that many people disregard that and create topics anyway, and it often ends up with the topic being duplicated into the plugins forum.
Perhaps we should ask ""What plugin or theme does this apply to?"" and give an auto-completed list of plugins/themes, and then allowing the user to select either ""Ask this question in the _XYZ forum_, or the general _Fixing WordPress forum_"" as part of the topic creation flow.
If the topic gets created in the general forum, we can keep the plugin/theme metadata around to ease future categorisation of threads.",dd32
929,Automate badge for training team,Profiles,low,enhancement,coffee2code,assigned,2015-03-04T01:56:04Z,2020-08-27T06:23:49Z,"The training team would like to automate their profile badge. (Note that at this time their badge is not being displayed. See #918.)
They want any edit to a post on make.wordpress.org/training or learn.wordpress.org to automatically give a badge to that user. Given that we already track posts and comments across make.wordpress.org, it shouldn't be hard to set this up, but it's no hurry. We'll also need to track edits on learn.wordpress.org.",samuelsidler
1424,Automate meta contributor badge assignment when receiving props,Profiles,normal,defect (bug),coffee2code,accepted,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
3986,Automate regional WordCamps in the Upcoming Events dashboard widget,Events API,normal,enhancement,,new,2018-12-09T17:39:47Z,2019-10-17T04:02:15Z,"Currently, regional events like WordCamp EU and WordCamp US need to be [https://meta.trac.wordpress.org/browser/sites/trunk/api.wordpress.org/public_html/events/1.0/index.php#L925 hardcoded] in order to display within the Upcoming Events dashboard widget. Would be great to automate this process.
Would likely need another checkbox to indicate a regional event when creating a new WordCamp event. May also require an additional database table to store regional events.",brettshumaker
2312,Automate theme reviewer badges,Profiles,normal,enhancement,,new,2016-12-06T16:13:03Z,2018-03-27T17:28:18Z,"Anyone who is in the ""reviewers"" group on the theme review trac should get a theme reviewer badge.
https://themes.trac.wordpress.org/admin
",grapplerulrich
7132,Automatic translation for exact strings,Translate Site & Plugins,normal,feature request,,new,2023-07-11T09:15:53Z,2023-07-26T08:26:15Z,"When translating, there are certain words that are translated in one way or another depending on, for example, whether they are a noun or a verb, the context, etc. However, there are certain words, or combinations of words, that always, always, translate the same.
My suggestion is that just as there is a glossary for each local community, where the GTE suggest a translation, that there is a way in which they can define some words or phrases that always translate the same, so that they translate automatically. No suggestion.
I don't mean a word within a sentence, or combinations of words within a sentence. That would cause problems. I mean exact string matching. When the entire string to be translated is the same as the entire string that a GTE has marked as ""automatically translatable"", it is automatically translated to the text marked by the GTE.
This should be defined by the GTE of each local community.",Marc4
2335,Automatically assign user set as admin for a new forum as a key master,International Forums,normal,enhancement,,reopened,2016-12-18T08:56:43Z,2021-10-20T21:11:40Z,"I created a new forum for Hindi at hi.wordpress.org/support after the official request (https://make.wordpress.org/polyglots/2016/11/21/want-to-make-a-request/) following the instructions for adding a new global site.
The admin email added was the email of the person requesting the forum, who would be the future key master.
The expected behavior was then for that user to be automatically assigned as key master of the new forum. That didn't happen, I had to manually go and change the user role on the site.
Can I request that the admin for a new international forum is automatically assigned as a key master as the new forum is created?
",petya
6410,"Automatically grant ""Core Performance Contributor"" badge based on GitHub contributions",Profiles,normal,feature request,,new,2022-07-18T13:17:34Z,2022-11-30T21:52:41Z,"The ""Core Performance Contributor"" badge was recently introduced to acknowledge contributions to the WordPress performance team. Assignments for this badge are currently manually controlled, but it would be great to have some automation for it in addition.
Specifically, the proposed flow is the following: Whenever a GitHub user that has their wordpress.org account connected to their GitHub account contributes to the https://github.com/WordPress/performance with code (PR or commit), the wordpress.org user should automatically receive the ""Core Performance Contributor"" badge on their profile.
How exactly to implement this is flexible, it would also be great to credit contributors that file issues, to not only focus on code contributions. If that is more complex though, it could also happen in a follow-up effort.",flixos90
4697,Backfill Credits API data for older releases,API,normal,enhancement,,new,2019-08-20T17:51:25Z,2020-07-10T11:11:47Z,"Background: #577, #3114.
At the moment, the [source:sites/trunk/api.wordpress.org/public_html/core/credits Credits API] only has data for WordPress 3.2+.
In comment:2:ticket:577 and comment:1:ticket:3114, a possibility of backfilling the data for older releases was suggested.
In a brief [https://wordpress.slack.com/archives/C02QB8GMM/p1566312195442900?thread_ts=1566294998.438700&cid=C02QB8GMM Slack discussion], @jonoalderson noted that it would indeed be beneficial for the project.
The list of contributors should be relatively easy to get via Git/SVN history or release posts:
||3.1||https://wordpress.org/news/2011/02/threeone/||
||3.0||https://wordpress.org/news/2010/06/thelonious/||
||2.9||https://wordpress.org/news/2009/12/wordpress-2-9/||
||2.8||https://wordpress.org/news/2009/06/wordpress-28/||
||2.7||https://wordpress.org/news/2008/12/coltrane/||
Earlier release posts didn't include contributors, so Git/SVN history would be the only option for them.
Release leads might be harder to track down, but still seems doable.",SergeyBiryukov
7252,Background content should not be scrollable while the secondary menu is opened.,Make (Get Involved) / P2,normal,defect (bug),,new,2023-09-06T06:07:14Z,2023-09-06T06:07:14Z,"In https://make.wordpress.org/meta/, background(body) should not be scrollable while secondary menu was open. Also, there is some space above the menu while we scroll.
I have attached video for better understanding.
Video URL :- https://share.cleanshot.com/J02psVkKVLWq2cjXR63z",himanshuc
6927,bbpress home page - design issue on small devices,bbpress.org,normal,defect (bug),,new,2023-04-07T09:55:11Z,2023-04-11T01:28:24Z,bbpress home page ( https://bbpress.org/ ) - image content text overflow on small devices,chiragrathod103
6928,bbpress nav menu Toggle not working properly.,bbpress.org,normal,defect (bug),,new,2023-04-07T10:06:48Z,2023-04-11T01:28:08Z,"Currently, the https://bbpress.org/ nav menu toggle is not working properly on the small device.
Reference URL: https://nimb.ws/D5fCdl",dhrumilk
2129,bbPress.org forum profiles should have a link to the WP.org profile,buddypress.org,normal,enhancement,,new,2016-10-11T11:41:13Z,2022-06-02T13:27:31Z,"Follow up to #2068 for bbPress.org
bbPress.org forum profiles should have a link to the users WP.org profile, like `@netweb on WordPress.org` on the WP.org profile itself.
Creating a patch from [4206] for bbPress only in bb-base theme should be relatively straight forward.
Note: Not required for Buddypress.org as Buddypress.org use BuddyPress member profiles",netweb
2008,bbpress.org/forums and buddypress.org/support activity should appear on profiles,Profiles,normal,enhancement,,new,2016-09-09T06:58:41Z,2020-08-27T06:23:49Z,bbPress 2.x topics and reply activity on bbpress.org/forums and buddypress.org/support should appear should appear on profiles e.g. https://profiles.wordpress.org/netweb#content-activity,netweb
2642,Better boosting for phrase matches (or add support for the user to specify a phrase),Plugin Directory,normal,enhancement,,new,2017-03-29T22:51:55Z,2021-07-22T17:28:51Z,"There are a number of examples of users wanting to find a particular plugin. We used to support this with exact matching against slugs, but that has other downsides. In general, exact matches don't work great when the words in the plugin name are very generic and there are not that many of them. But when there are many words we can probably do better.
Some examples:
- ""Easy AdSense Ads & Scripts Manager""
- ""Post Tags and Categories for Pages""
When the user has written a lot of characters, I'm wondering if we should increase the boosting of the phrase search. I experimented with higher boosting on this field at one point already and decided against it, though other things have changed since then.
I think that just adding support for having the user specify the phrase by putting quotes around it would solve this use case and would be less likely to have bad effects for other searches. About 0.2% of all unique searches currently use quotes, so some users are already using them (though not many).
I think the most compelling use case this adds support for is when a user wants to find a specific plugin to be able to get to the support forums.
",gibrown
5748,Block ability to add links in reviews,Support Forums,normal,enhancement,dd32,reopened,2021-05-25T14:23:53Z,2023-04-12T16:12:35Z,"Forum policy prohibits links in reviews, whether a directly typed on or one added via the ""link"" icon on the editor toolbar. Currently, moderators either remove the links or archive the review. This tends to generate discussion that is usually unproductive.
Suggestion: Modify the editor such that it detects that it's being used in a review and detects & rejects links.",sterndata
6703,Block editor prevents emojis in reviews,Support Forums,normal,defect (bug),,new,2023-01-23T13:20:42Z,2023-01-27T22:08:40Z,"in {11383}, links in reviews were blocked by actively looking for HTTP prefixes (see #5748).
With the introduction of the block-editor for writing reviews, we are now observing that emojis are converted to twemoji `img` links on the fly, which is causing attempts at writing reviews that include emojis to be blocked by this same link filter.",Clorith
5374,Block trac ticket submissions with inappropriate language,Trac,normal,enhancement,,new,2020-08-12T22:02:13Z,2020-08-12T23:56:23Z,"Occasionally a trac ticket gets submitted with.. heated language.
Users get frustrated, which is understandable. We should discourage this by requiring they re-write the ticket if it contains a handful of forbidden words. Perhaps by disabling the Create Ticket button until it passes a simple check.
",tellyworth
5934,Blocking User from Signup Does not Fully Document in profile,General,normal,defect (bug),dd32,accepted,2021-10-21T17:32:47Z,2021-10-26T18:51:04Z,"With the new-ish signup tool that allows us to un-spam registrations, it also lets us block users from that interface. However, while it does log who did the action, it doesn't do so in a trackable way. That is, we only get logged ""Changed to blocked by X"" but none of the reason.
Generally the reason is ""Bio and/or registration URLs were spammy"" but none of that is recorded.
What we need is a change to the notice.
1. Where was the account spammed/blocked from? This can be ""Banned by X via ...""
2. A COPY of the bio and URLs (recommend truncation since some bios are 5000 word porn stories, not kidding). That way it's obvious to everyone else ""Oh, yeah, the person with the bio about their casino is probably spam""
Example of a spammy signup:
url: http://10040656...
from: metro hispania
occ: Security guard
interests: sex
or:
url: https://www.facebook.com/Huge-Market-1234566
from: Main Street
Those should be copied into the user notes.",Ipstenu
5623,Blocks list incorrect on plugin directory page,Plugin Directory,normal,defect (bug),,new,2021-02-17T15:38:02Z,2023-10-24T18:37:33Z,"The blocks listed on some plugin directory pages don't appear to line up with what is available when the plugin is installed.
The example I identified is https://wordpress.org/plugins/layout-grid/
There are technically two blocks but one is only accessible as an inner block and they do have different names and labels in the plugin code.
**For reference:**
Block registration: https://github.com/Automattic/block-experiments/blob/master/blocks/layout-grid/index.php#L4
Block definitions: https://github.com/Automattic/block-experiments/blob/master/blocks/layout-grid/src/index.js",daisyo
291,"Bring core trac improvements to other trac instances (meta, bbPress, BuddyPress)",Trac,high,enhancement,,new,2014-01-22T04:09:35Z,2022-03-04T00:06:33Z,"Nacin has introduced some lovely changes to core trac. It would be fantastic to have the same functionality on meta trac. I'm particularly thinking about the ability to star and follow tickets, but also the duplicate ticket suggestions and the nice box that mentions that someone is opening their first ticket.
In relation to this - the CC functionality seems to have disappeared on meta trac, but it hasn't been replaced by the follow functionality so there's currently no way to follow a ticket. ",siobhan
712,Bring the Showcase to Rosetta sites,Showcase,normal,enhancement,,new,2014-11-04T08:41:03Z,2020-03-06T22:42:55Z,"Since it is possible to add showcase elements [https://meta.trac.wordpress.org/changeset/475 as a CPT], it would be fine to have an archive page for the showcase as [https://make.wordpress.org/polyglots/2011/09/12/the-showcase-is-now-a-post-type-its/ announced] in 2011 ;-)
Like https://wordpress.org/showcase/
",CoachBirgit
2531,Broken link to mailing list on bbPress Trac,Mailing Lists,normal,enhancement,,new,2017-02-23T20:47:06Z,2019-01-08T03:29:07Z,"https://bbpress.trac.wordpress.org says:
> There is also an [http://bbpress.trac.wordpress.org/timeline?daysback=90&max=50&format=rss RSS feed] and a [http://lists.bbpress.org/mailman/listinfo/bbdev mailing list] for those interested.
The URL is http://lists.bbpress.org/mailman/listinfo/bbdev, which redirects to a 404 page: https://bbpress.org/mailman/listinfo/bbdev.
Any chance to revive that mailing list? Having an archive like that in Gmail is quite handy as a quick search tool.
There are active ""firehose"" lists for [http://lists.wordpress.org/pipermail/wp-trac WordPress] and [http://lists.wordpress.org/pipermail/buddypress-trac BuddyPress], but not for bbPress. There were [http://lists.wordpress.org/pipermail/bb-trac/ bb-trac] and [http://lists.wordpress.org/pipermail/bbdev/ bbdev] in the past, but the latest activity in both is from 2009.",SergeyBiryukov
5598,Broken links to usability tests in Test Team handbook,Handbooks,normal,defect (bug),ironprogrammer,assigned,2021-02-02T22:09:05Z,2022-09-28T21:18:18Z,"In the WordPress handbook, on the page for Gutenberg testing,
https://make.wordpress.org/test/handbook/gutenberg-testing/#how-you-can-help-every-test-matters
The links for the three usability tests-A, B and C are missing throughout the page.
Thanks
",femkreations
7135,buddypress home page - design issue on small devices,buddypress.org,lowest,defect (bug),,new,2023-07-12T12:49:46Z,2023-07-13T01:46:33Z,Text overlap over image in buddypress home page.,dhaval_parikh
5141,BuddyPress.org: Add link of developer pages to the main navigation,buddypress.org,normal,enhancement,,new,2020-04-09T07:30:43Z,2020-04-22T19:41:41Z,"This is to propose adding the link to developer.buddypress.org to the main navigation of BuddyPress.org as one of the dropdown links under ""Documentation""
Documentation
--Users (codex.buddypress.org)
--Developers (developer.buddypress.org)
Thanks.",mercime
699,Bug Gardeners should have predefs available on ticket pages,Trac,normal,enhancement,,new,2014-10-29T19:35:50Z,2018-02-17T08:14:05Z,"Going to be testing with this ticket. When It's ready, I'll add a patch. Sorry for any noise.
Goal is to be able to have bug gardeners easily close tickets as a support request and also as an idea that belongs in the ideas forum (that will come next).
Came from trac backlog chat at todays summit. ",jorbin
3389,Build Elasticsearch Index: Developer Hub,Developer Hub,normal,task (blessed),gibrown,assigned,2018-01-17T23:32:39Z,2023-05-12T08:31:18Z,"Unclear exactly how important an ES index is here, but opening up for discussion.
Related tickets: #556 #3019 #174
An easy example where results are terrible: https://developer.wordpress.org/plugins/?s=posts (""post"" of course is much better).
Steps to create this:
- Enable Jetpack on developer.wordpress.org so we can sync all posts
- Build a custom index. I think a custom index is needed so we can do custom analysis of the function names, etc. Could then do boosting when matching a function name.
Note to self: Opengrok has a Lucene custom analyzer for php (and others): https://github.com/oracle/opengrok/tree/master/src/org/opensolaris/opengrok/analysis/php
",gibrown
3388,Build Elasticsearch Index: Support Forums,Support Forums,normal,task (blessed),gibrown,assigned,2018-01-17T23:17:58Z,2023-03-08T16:23:49Z,"Many improvements to search and related topics we could make by having an ES index.
Some related tickets: #7 #8 #37 #36
Steps:
- Enable Jetpack to sync all posts and comments (this is a hard step, 6m posts or so)
- Build a custom ES index for the posts. Almost certainly will need to be custom
",gibrown
7492,Button Alignment Issue on Small/Mobile Device,Theme Directory,normal,defect (bug),,new,2024-02-27T15:39:02Z,2024-02-29T05:02:35Z,"In mobile or small device, button alignment is not same. This need to be fixed.[[Image(https://i.imgur.com/Wo5RoZX.jpg)]]",devmuhib
6146,Button overlapping in mobile device,Handbooks,low,defect (bug),,new,2022-02-28T05:39:56Z,2022-03-09T07:55:43Z,"open below link and select mobile device.
https://make.wordpress.org/meta/projects/",umesh84
6631,Button padding produces horizontal scrolling issue and white space at very narrow widths,Five For The Future,low,defect (bug),,new,2022-12-16T05:15:05Z,2023-11-30T16:42:59Z,"The page generates a horizontal scrolling bar and white space in the responsive (max-width:320px and below) on this page [https://wordpress.org/five-for-the-future/].
Solution:
{{{
.wp-block-button__link{
padding: calc(0.667em + 2px) calc(0.333em + 2px);
}
}}}
For better understanding I provide the Video attachment Link:
Video link: [https://share.cleanshot.com/3acw3opubpTOYhU6TPrK]",himshekhar07
7112,ca (ca.wordpress.org) Handbook sync,Handbooks,normal,enhancement,,new,2023-07-01T10:38:40Z,2023-07-01T10:38:40Z,"Same as ticket #6714 (following #4572).
We want to sync the Official Catalan GitHub repo to the Handbook .
Same as the Spanish one, we check and review in a “hard security way” the Organization, so the repository can be synced without problem and with all reviews before changing / updating anything.
GitHub repo:
https://github.com/wpcatalunya/catalan-handbook
Manifest:
https://github.com/wpcatalunya/catalan-handbook/blob/main/bin/handbook-manifest.json
Catalan Handbook:
https://ca.wordpress.org/team/handbook/
Allow @javiercasares to https://ca.wordpress.org/team/
cc// @anagavilan @estelaris @glycymeris @marc4 @nao",JavierCasares
6742,Calculation Error in WordPress 3.8.x Translation in Assamese,Translate Site & Plugins,normal,defect (bug),,new,2023-02-08T08:45:34Z,2023-02-09T04:33:26Z,"Calculation Error of counting translated and untranslated strings as well as translation percentage in WordPress 3.8.x Translation in Assamese Language
Link: https://translate.wordpress.org/projects/wp/3.8.x/as/default/",mehrazmorshed
5140,Can the current day on Meetings show upcoming a little better,WordPress.org Site,normal,enhancement,tellyworth,accepted,2020-04-08T19:18:53Z,2020-04-13T04:31:37Z,"Hello,
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",garrett-eclipse
4224,Can we provide a Data Export Request form/page similar to the Data Erasure Request form/page,Profiles,normal,enhancement,tellyworth,reviewing,2019-02-26T18:14:29Z,2020-09-23T21:28:39Z,"Hello,
Currently, the export process for WP.org is to contact dpo@wordcamp.org (which w/ #3660 will change to a wp.org email hopefully). It would be nice to provide a Data Export Request form/page similar to the existing Data Erasure Request form/page.
Data Erasure Request - https://wordpress.org/about/privacy/data-erasure-request/
And once created would be nice to have it linked directly from the Privacy Policy.
Aside from the above approach or in tandem the export and erase requests could be made via a button in the wp.org user profile. This approach would mitigate spam requests as the user would already be logged in to make the request.
I understand core doesn't provide this functionality as of yet so if core is blocking this type of implementation then the good news is these features are part of the V2 privacy roadmap and once it's made progress will circle back.
Core Ticket - https://core.trac.wordpress.org/ticket/44013
*As well there's an existing plugin that covers alot of the front-end on this which can be looked to for code - https://en-ca.wordpress.org/plugins/gdpr-data-request-form/
Thank you",garrett-eclipse
7162,Can't undo favorite theme on mobile,Theme Directory,normal,defect (bug),,new,2023-07-30T12:40:25Z,2023-07-30T12:40:25Z,"When you want to undo a favorite from a theme on mobile... You can't on Opera or Chrome (tested on Android).
It stays favorited and the blue box showing you pressed the button shows higher then the heart icon.",NekoJonez
7164,Can’t create Updates CPT,HelpHub (wordpress.org/documentation),normal,defect (bug),dufresnesteven,assigned,2023-07-31T13:43:01Z,2023-08-01T05:31:33Z,"Hi,
I can’t create Updates CPT on fr.wordpress.org/support/ and wordpress.org/documentation/.
This is a CPT created via an extension developed by Coren McKrill and available for updating WordPress documentation posts.
It is impossible to create an ""update"" using the save later function offered by the plugin in the editor, because the plugin menu is not displayed when the arrow next to the Update button is clicked.
It's a bit inconvenient at a time when we have a lot of posts to update for the release of version 6.3.
Can you solve the problem?
Thanks for that.",jdy68
5410,Categories not displayed on the page of the video,WordPress.tv,normal,enhancement,,new,2020-09-02T20:47:54Z,2020-09-02T20:47:54Z,"https://wordpress.tv/category/learn-wordpress/ is grouping all the videos of the 'Learn WordPress' category, but opening any video of that list, the category is not shown.
The page with the video should add the categories in the sidebar.",casiepa
5589,Category archives pages : accessibility improvement (HTML),HelpHub (wordpress.org/documentation),normal,enhancement,,new,2021-01-27T11:50:39Z,2021-02-12T16:52:33Z,"This ticket is about **category archives pages** in helphub/support sites, for example : https://wordpress.org/support/category/getting-started/
Accessibility of theses pages can be improved by moving links around `article` inside `h2` tag (title).
Actual markup :
{{{
Users Your Profile Screen
Users → Your Profile The Your Profile Screen is accessible from both the main navigation menu under Users and by clicking on your name link […]
}}}
New markup :
{{{
Users → Your Profile The Your Profile Screen is accessible from both the main navigation menu under Users and by clicking on your name link […]
}}}
",Chaton666
7440,Category to Planet.WordPress.org not working,Planet (planet.wordpress.org),normal,defect (bug),,new,2024-02-05T15:31:33Z,2024-02-06T00:20:01Z,"https://poststatus.com/planet/feed does not seem to be appearing on https://planet.wordpress.org.
Human readable articles https://poststatus.com/category/planet/",courane01
3593,Centralize GitHub Markdown importer,Handbooks,normal,enhancement,,new,2018-04-27T14:07:56Z,2019-02-13T19:15:26Z,"There are currently a few teams that want GitHub Markdown importing to feed their handbook: [https://meta.trac.wordpress.org/changeset/4733 CLI], [https://meta.trac.wordpress.org/ticket/2968 REST API], [https://meta.trac.wordpress.org/changeset/6304 Gutenberg], [https://meta.trac.wordpress.org/ticket/3377 WPCS], and probably more to come in the future, I think it would be worth a small refactoring effort to produce a reusable plugin that handle this across all teams & sites.
@rmccue has already done a lot of preliminary work for making this reusable in https://github.com/WP-API/markdown-sync, but some details are still missing.
Basic functionality could look like the following:
1. Field to enter a markdown source on GitHub. This could be a nice, proper UI, but simply accepting a custom field under a common field key convention would be enough for an MVP. Something like [https://github.com/WP-API/markdown-sync/blob/master/inc/class-importer.php#L17 wporg_markdown_source] would do the trick.
2. Refresh button in the post edit screen to fetch the latest version of the content from GitHub and make updates as needed.
3. Cron job that goes through all posts that have a custom field as registered on 1. and update as needed.
4. Ability to specifiy a manifest file that defines the posts (and their post type) to create and their respective markdown sources.
5. Cron job that goes through the manifest file and adds/removes/updates posts as needed.
1., 2. & 3. are also great for one-off pages/posts that should be updated from an arbitrary GitHub file, without it being tied in an automated structure. As an example, a feature project page like the one from [https://make.wordpress.org/core/features/servehappy/ servehappy] could be set up to be updated from the corresponding GitHub repo's [https://github.com/WordPress/servehappy/blob/master/README.md README.md file], or individual pages in the different team handbooks could be set up for easier collaboration.",schlessera
6517,Change HelpHub header to say Documentation,HelpHub (wordpress.org/documentation),normal,enhancement,,new,2022-10-05T14:05:06Z,2022-10-17T10:26:54Z,"We have as a Docs Team discussed and done some research that the word ""Support"" on a pure documentation page is misleading.
We'd love for this to change to Documentation.",Kenshino
4677,Change how 'Active Installations' is calculated on 'Popular' tab,Theme Directory,normal,defect (bug),,new,2019-08-16T10:46:13Z,2023-10-28T15:32:12Z,"Ref: https://wordpress.org/themes/browse/popular/
It's generally accepted that the algorithm for the 'Popular' tab is based on two variables:
- Time in Directory
- Active Installations
This works well when .org is the primary distribution method, as both values start at 0.
However, some authors/companies have realised you can manipulate the algorithm by accumulating installations before uploading your theme.
So the variables look like this:
Time in Directory = 1 day
Active Installations = 10,000
Because the time in directory is so low compared to the active installations, the theme will be given an artificially high position.
It would be more accurate to include the time it took to accumulate **all** the installs. In which case the variables would be:
- Time Since First Active Install
- Active Installations
There are two possible solutions:
1) Store the number of active installations when a theme enters the directory and deduct that amount from any calculations. This would effectively reset the current variables to 0 (as they should be).
Simplified:
`$value = $time_in_directory * ($active_installations - $active_installations_on_entry)`
2) Replace 'Time in Directory' with 'Time since first active install'. I believe this would require storing the value from the Update API.
Simplified: `$value = $time_since_first_install * $active_installations`",DannyCooper
5773,Change search algorithm in themes page,Theme Directory,normal,defect (bug),,new,2021-06-12T15:42:46Z,2021-07-22T19:44:27Z,"Some of the theme authors are mentioning other popular themes name in their description. Because of that, when user search the name of other popular theme, their theme will appear on the search page.
Example: https://wordpress.org/themes/search/astra/ Here, theme Astra is searched but some theme with text `astra` in the description appear.
Also, you can see how authors are doing tricks and write popular theme name in their description. https://wordpress.org/themes/coin-market/",kafleg
2264,Change the default Twitter account in Rosetta local sites at .org,International Sites (Rosetta),normal,enhancement,,new,2016-11-23T10:58:37Z,2019-07-10T10:29:28Z,"By default, every post shared via JetPack buttons in Rosetta local sites at wordpress.org (i.e: es.wordpress.org) are shared with the @WordPress appended.
It could be necessary to allow local sites to access to Settings -> Sharing in order to change this twitter account and put the local community twitter account, if it exists (i.e. @wp_es)",fernandot
2192,"Change the name of ""invalid"" ticket resolution",Trac,normal,defect (bug),,assigned,2016-10-31T01:41:00Z,2024-01-23T06:11:41Z,"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.",pento
6940,Changes requested add link in email,Translate Site & Plugins,normal,enhancement,,new,2023-04-20T15:07:06Z,2023-04-20T15:07:06Z,Is it possible to add a link to the string where the changes is requested in the email?,crash_47
6672,"Changes/additions for support article ""Must Use Plugins""",HelpHub (wordpress.org/documentation),normal,enhancement,,new,2023-01-11T17:49:56Z,2023-01-11T17:49:56Z,"📄 https://wordpress.org/support/article/must-use-plugins/
- 👍 Overall well written.
- ❌ But some aspects are not yet covered (out of my own experience):
1. Integrate proper keywords into that official support article so that ""Must Use Plugins"" becomes more prominent in search engine results as an intended/supported method to ""disable updates and update notifications for a particular plugin"". Phrases/Keywords to include:
- How do I keep a plugin frozen at a certain version?
- How do I disable auto-updates?
- How do I disable update notifications?
- The ""update available"" badge over the plugins menu entry does not go away for plugins with auto-updates disabled?
- How do I remove that badge counter? (for the single affected plugin)?
2. Improve this: Moving a plugin folder there is not enough. You need a PHP file pointing at it.
The documentation indeed mentions:
> WordPress only looks for PHP files right inside the mu-plugins directory, and (unlike for normal plugins) not for files in subdirectories. You may want to create a proxy PHP loader file inside the mu-plugins directory:
- Even though I'm somehow tech-savvy, the term `proxy PHP loader file` scared me off as too technical.
- Proposed alternative terms: stub file, auxillary file, inclusion file.
- And as the code snippet was quite empty and inconcrete, it did not convey the idea to me either.
- For these both reasons I overread that section.
- Please include a more concrete/vivid code snippet, that better conveys the idea,
- such as the code snippet, that I received in this [#57310#comment:4 support session] that had started as [#57310 my feature proposal] which staff and me rejected for good reasons after having discussed in detail.
- In the code snippet use a real world description field like ""I keep that plugin frozen in v1.2.3 because I need feature X which was removed in v2+. And then was abruptly abandoned. But I really need the plugin to work as it does in v1.2.3."". Then the reader immediately gets the idea!
3. Please also add: How to correctly migrate an **enabled plugin** to a **must use plugin**
- I found out by [#57310#comment:3 trial and error].
- Users may appreciate if the support article could cover that use case as well.",abitofmind
7070,Character entities (>) instead of an actual html tag (>) on Automated Testing handbook,Make (Get Involved) / P2,normal,defect (bug),,new,2023-06-15T14:42:29Z,2023-06-15T14:42:29Z,"Hello, I was referring to this page earlier [https://make.wordpress.org/core/handbook/testing/automated-testing/writing-phpunit-tests/], and it is showing character entities instead of an actual tag in the examples.
https://tinyurl.com/2bmcrbk3
",prashantbhivsane
7233,chat.wordpress.org: make the join link more prominent,"Communication (Matrix, Slack, IRC)",normal,enhancement,,new,2023-08-24T14:28:20Z,2023-08-24T15:54:34Z,"I just helped someone at contributor day join the Making WordPress Slack, and the link to join is pretty buried in the page. Could we update the design so the joining link it more prominent?
Some ideas:
- Make the link to login a button
- Add more space around the join section so it's more prominent
- Update the typography to make the header easier to see
Alternately, redesigning this page could be a good little project to get a new community designer to work alongside the website redesign project :)",melchoyce
6826,check for initial lowercase only for specific languages,Translate Site & Plugins,normal,defect (bug),,new,2023-03-02T23:21:26Z,2023-03-09T20:27:37Z,Nouns begin with a capital letter in german language. So a warning is issued every time a string is translated that starts with a noun.,timse201
7111,Checkbox in translation editor panel,Translate Site & Plugins,normal,feature request,,new,2023-07-01T06:21:28Z,2023-07-06T16:58:44Z,"I think that during translation review, when reviewing an individual string, it would be helpful to have the checkbox inside the edit panel.
When reviewing something from an individual string, you have to close the editor and then check the box to further process that translation along with others previously selected, to approve, etc.
The idea would be to keep the current checkboxes to the left of each translation string the same as now, and add the same checkbox to the individual translation panel as well, so you can check the checkbox from within the edit panel.
This would allow you to jump to the next translation string with the navigation arrows, without having to close the edit panel and select the checkbox on each edit.
I attach an image for better understanding.
Thanks",Marc4
7396,Child theme uploads bypass theme-check checks,Theme Directory,normal,defect (bug),,new,2024-01-04T02:36:39Z,2024-01-04T02:37:49Z,"When uploading a child theme, it intentionally ignores Theme Check errors, and allows the upload (even thought TC has said no). This is because many TC errors are not child-theme aware, and are not actually errors for a child theme at all.
This however ends up with some submissions getting past theme check and into Trac that probably shouldn't, for example, the following seen on a recent ticket:
> ERROR: ""Theme Name Here"" currently has 1,000+ active installations. Please check for name collisions outside of WordPress.org before approval.
Making TC fully child-theme aware is probably a bigger task, but we can probably start to block on specific checks such as the active-install check.",dd32
6988,Choosing a language,WordPress.tv,normal,defect (bug),,new,2023-05-16T10:11:18Z,2023-05-20T09:21:40Z,"Hello,
To make easier and avoid any duplicate languages when submitting a video, It would make sens to make the Language field as a checkbox or a select at https://wordpress.tv/submit-video/
This is the case for ""Location"" & ""Category"".
",sebastienserre
6079,Clearer thread URLs and email notifications,Support Forums,normal,enhancement,,new,2022-02-05T03:16:40Z,2023-05-30T00:51:02Z,"**Clearer URLs**
Support thread URLs do not contain the slug of the forum (e.g. plugin name) they apply to. This makes them less useful when trying to recall the issue involved, particularly after a pause in the discussion, and prevents the successful use of `site:` type Google searches.
Example: https://wordpress.org/support/topic/cant-save-settings-56/
Please consider replacing `topic` with the forum slug in support thread URLs.
Example: https://wordpress.org/support/youtube-embed-plus/cant-save-settings-56/
Alternative: Example: https://wordpress.org/support/plugin/youtube-embed-plus/cant-save-settings-56/
As a matter of fact, both of these already redirect successfully to the official URL. Why not have a more meaningful/useful official URL, or, at the very least, use it in email messages?
**Email Notifications**
Email notifications about thread updates also show no indication if the forum they're in. Again, this makes recall difficult sometimes.
Example: `[WordPress.org Forums] Can't Save Settings`
Forum notifications are sent from `WordPress.org Forums `, so the string prefix `[WordPress.org Forums] ` in the subject is redundant, and can be removed to make room for a forum identifier.
Using the forum name (e.g. Plugin: Embed Plus Plugin for YouTube, with YouTube Gallery, Channel, Playlist, Live Stream, Facade) may be too long, but slugs are normally OK, so a capitalized version of the forum slug would be better (e.g. Plugin: Youtube Embed Plus) for the email subject.
Example: `[Plugin: Youtube Embed Plus] Can't Save Settings`
The full name of the forum can then be added for reference in the body of the email.
Example: `Plugin: Embed Plus Plugin for YouTube, with YouTube Gallery, Channel, Playlist, Live Stream, Facade`",galbaras
7511,Code Block must be ltr in rtl locale,Support Forums,normal,defect (bug),,new,2024-03-09T10:54:05Z,2024-03-09T10:54:05Z,"Currently, Code Block are rtl in Persian support forum.\\
But for better experience and readability they must be ltr.",asadiy4n
4301,Coding standards: Need to use numeric values instead of keywords in CSS.,WordPress.tv,normal,defect (bug),tellyworth,reviewing,2019-03-18T12:44:21Z,2019-05-17T01:58:21Z,"I have noticed that, there are lots of occurrences of font-weight: bold; or font-weight: normal; in wordpress.tv.
As per the CSS Coding Standards:
>Font weights should be defined using numeric values (e.g. **400** instead of **normal**, **700** instead of **bold**).",jankimoradiya
5757,Color blind feature for translate.wordpress.org ?,Translate Site & Plugins,normal,enhancement,,new,2021-05-28T13:58:40Z,2022-03-01T12:21:33Z,"Lately when I'm going through all the waiting strings for all the plugins and themes in my locale, I notice that I sometimes have a hard time seeing the difference between the orange of fuzzy strings and the red of refused strings.
This becomes especially annoying when for a plugin suddenly 200+ strings go fuzzy, and you want to reject to completely redo them...
Personally, I'm not color-blind, but I do think that people being color-blind especially for red will have an even harder time seeing the difference. So, I think it would be cool to have a feature in your translation settings or something along those lines to change the colors to make things like written above easier when checked.",NekoJonez
6602,Comment previews can be inaccurate when they contain back slashes.,Make (Get Involved) / P2,low,defect (bug),,new,2022-11-28T04:57:11Z,2022-11-28T06:15:15Z,"On make/core I needed to leave a comment containing some regex: `/\*{1}\n`.
When viewing the comment using the preview tab, the above was displaying as `/*{1}n`, for the preview to display the code correctly I modified it to `/\\*{1}\\n`.
When submitting the comment, the comment was rendered as entered with the double back slashes.
I suspect it's a JavaScript escaping issue when rendering the preview. I was wrapping the regex in `` tags in case that makes a difference -- while testing it doesn't seem to.
(Aside: I know the `{1}` isn't required but I was including it to make a distinction :)",peterwilsoncc
681,Community profile badges disappear for WordCamp organisers of two different WordCamps,Profiles,normal,defect (bug),,new,2014-10-27T01:05:40Z,2021-06-07T19:37:39Z,"When a WordPress.org username gets added to the Organisers of a second WordCamp, the community profile badge disappears.
Here's the use case:
- I've been added as an organiser for WordCamp Sofia 2013 - http://2013.sofia.wordcamp.org/
- I am also an organiser of WordCamp Europe 2014 - http://2014.europe.wordcamp.org/
I noticed that my community badge had disappeared after my profile was added to the organisers of WordCamp Europe 2014. Adding a second entry for my profile as an organiser made the badge appear again. But then I was listed as an organiser for the same WordCamp twice on the Organisers page. Deleting the second profile got rid of the badge again.
Clearing the username, updating and then adding it again seemed to do the trick - the badge appeared again.
Tested it with JJJ at #wcsf14 contributor day who suggested it had something to do with the fact that WordCamp organisers are not supposed to be a part of more than one organising team. He advised me to file it here.
It's a cool bug.",petya
6734,Configurable welcome email automatically sent to new translators,Translate Site & Plugins,normal,feature request,,new,2023-02-06T18:31:44Z,2023-02-15T10:42:14Z,"It would be super productive if GTEs could write an email template (in HTML format) that would be automatically sent to any new translator right after their first contribution.
Something that would say:
''Did you know that there is documentation on the rules to follow… Your translations will be validated faster… Here are the names of the people responsible for your locale… You can find the typographical rules on this page, the glossary on this other page...''
The idea behind this would be to pass the correct guidelines to new contributors before they scatter piles of bad translations all over the place. Because there can be quite a long delay before an editor spots them, and in the meantime they will have done some damage.
If ever an email is not feasible, a welcome popup on Translate would be another solution. But still allowing the GTEs to edit the content as they can on the glossary.",Webaxones
7455,"Confusing experience when I click ""forums"" in the main site navigation",Support Forums,normal,enhancement,,new,2024-02-08T05:04:57Z,2024-02-08T05:04:57Z,"I couldn't find the context and therefore don't understand the reasoning, but I'm confused by our support/forum flow.
From the homepage, I open the menu and click ""forums"". I land on a page that says ""Support"", with a missable subnavigation indicator of ""forums"". The first information I see is not related to forums, it is general support information.
The top section is confusing because I clearly indicated that I want to see forums.
**Welcome to Support**
This takes me away from forums and shows me guidelines.
**Documentation**
This takes me away from forums completely.
**Get Involved**
Doesn't relate to my task of viewing forums.
I understand how we probably got here and this page makes sense if the link in the navigation is ""Support"" but since it's ""forums"" my expectations I have for what I'm about to see is completely different.
Assuming we are going to keep ""Forums"" in the navigation.....
I think the easy fix is to move the top section down below the forums. Additionally we should change ""Support"" as the subnav title to ""Forums"". The only other content on this sub site is relating to contributing in the forums.
",dufresnesteven
6607,Consider activating Jetpack Stats dashboard widget on Localized HelpHub sites,International Sites (Rosetta),normal,defect (bug),,new,2022-12-01T12:40:49Z,2023-06-01T10:27:42Z,"Hello,
Would it be possible to consider activating the ""Jetpack Stats"" dashboard widget on localized HelpHub websites (like for instance https://fr.wordpress.org/support/)?
It would be super useful for Local HelpHub managers to see what posts are popular and what posts are not, and to improve decision making about the architecture of our localized versions of HelpHub.
I think most localized HelpHub team would also welcome this improvement :)
Thanks!
''This ticket is a follow-up of a discussion between the French HelpHub team with @jdy68, @wplmillet, @jmsilcom, @gabinou7.''
''Also pinging @milana_cap as Docs team representative :)''",audrasjb
6851,Consider adding a visual representation of Rating trends for plugins.,Plugin Directory,normal,enhancement,,new,2023-03-13T00:06:19Z,2023-03-13T02:38:17Z,"We should consider showing Rating trends when viewing a specific plugin.
**Problem:**
It isn't easy to figure out if the current version is good or bad. Ratings provide a flat view of history. If a plugin started off with bad reviews, it could be punished indefinitely even if great effort and care are made to improve. Similarly, if a plugin has degraded in quality but received good ratings early on, it would continue to benefit from that period undeservingly.
",dufresnesteven
6556,Consider allowing Make teams to create block patterns,HelpHub (wordpress.org/documentation),normal,feature request,,new,2022-10-31T15:23:08Z,2022-11-01T14:13:24Z,"Block patterns seem a great way to create consistency and expedite content creation. There has been [https://github.com/WordPress/Documentation-Issue-Tracker/issues/474 recent discussion] on creating block patterns for the Docs team (HelpHub / Developer Hub). Block patterns would likely benefit other groups as well, e.g., Learn, WordPress.tv.
I'm wondering if there might be a way to have team-specific block patterns, which might leverage the current Pattern Directory editorial flow, or maybe a separate site instance should be created.
There are a few ways that this could be achieved, and I would likely lean on the knowledge of the maintainers of these sites.
**Option one:** spin up a separate Pattern Directory site specific to Make teams: ""Make Pattern Directory."" We could use the existing [https://github.com/WordPress/pattern-directory Pattern Directory codebase] as a great starting point.
Make team representatives would add contributors to the ""Make Pattern Directory."" Contributors could submit patterns for approval.
It may be advisable to have an additional taxonomy registered for block patterns, which would be tied to each team, e.g. Make Team category: Docs, Training, etc.
This taxonomy would allow triaging of new patterns to appropriate team representatives for approval ''and'' have the benefit of surfacing the patterns on each team's site when adding a block pattern. I believe this would require REST API integration for each team's WP.org theme, but I'm not entirely sure how each team's theme/site is organized.
[[Image(https://www.dropbox.com/s/apxbcy2djb1jnkj/Screen%20Shot%202022-10-31%20at%2010.22.04%20AM.png?dl=0)]]",colorful tones
7433,Consider removing logged in block when viewing support forums.,Support Forums,normal,enhancement,,new,2024-02-02T01:41:53Z,2024-02-08T04:45:41Z,"I'm not sure why we need to include a block in the support forum that lets me know I'm logged in and helps me log out.
The top admin bar has the same functionality.
Do we need it?",dufresnesteven
4111,Consider to audit the focus style across the .org network,General,normal,defect (bug),,new,2019-01-28T22:37:36Z,2019-01-28T22:37:36Z,"Keyboard users, or users who make a mixed use of a pointing device and keyboard, need to actually ''see'' where focus is to be able to navigate a web page using their keyboard.
The focus style is a necessary indication for these users. Great care has been taken in WordPress core and the bundled themes to make the focus style as good as possible, and there's still work to do to improve it. It would be great to see also the .org network sites taking care of the focus style.
For reference, this is also part of the WCAG recommendation:
Success Criterion 2.4.7 Focus Visible
https://www.w3.org/TR/WCAG21/#focus-visible
While a complete analysis of all the links and controls across all the .org network would be impossible for me, I've taken the time to volunteer and analyze the focus style only on the main navigation menu in the main .org sections.
To recap:
- Home: has focus style (browser native style)
- Showcase: no focus style `outline: none;`
- Themes: has focus style `outline: thin dotted;`
- Plugins: has focus style `outline: thin dotted;`
- Mobile: has focus style (browser native style)
- Support: has focus style `outline: thin dotted;`
- Get involved (Make): has focus style (browser native style)
- About: has focus style `outline: thin dotted;`
- Blog: has focus style (browser native style)
- Hosting: has focus style (browser native style)
Suggested:
- never reset the native outline style, unless that's meant to provide a better, improved focus style
- use a consistent style across all the pages: worth reminding the browsers native focus style greatly varies across operating systems and browsers
- buttons, form elements, and custom interactive elements need a focus style as well
- use a style that is compatible with Windows High Contrast mode, or provide one specifically for Windows High Contrast mode
Note: in Windows High Contrast mode, basically only `outline` and `border` work. In core, https://core.trac.wordpress.org/ticket/41286 introduced a specific style that uses a transparent outline, as already done for the new block editor Gutenberg.",afercia
4110,Consider to audit the headings hierarchy across the .org network,General,normal,defect (bug),,new,2019-01-28T22:17:23Z,2020-04-15T05:26:19Z,"Headings are important not only for semantics and SEO: they are actually used by screen reader users as the [https://webaim.org/projects/screenreadersurvey7/#finding predominant mechanism to find information on a page].
For better accessibility, SEO, and semantics there are some best known practices, also recommended by the core accessibility team:
- a main `h1` heading should be used to communicate the main page topic
- there should be only one `h1` in a page
- the main topic of a page is rarely the site title, this is maybe true only on the home page (and it's still matter of debate)
- in all the other pages, the main `h1` is meant to be used for that specific page topic
- headings needs to have a correct hierarchy: no levels should be skipped
There are different tools to check the headings structure of a page. For the purpose of this ticket, I've used the HeadingsMap Chrome extension. I've also collected a series of screenshots to illustrate the headings hierarchy in the main pages of the .org network as of today, January 28, 2018: https://cloudup.com/cCODexEIFbq
To recap:
- Home: two h1 and incorrect hierarchy
- Showcase: incorrect hierarchy
- Themes: two h1 and incorrect hierarchy
- Plugins: two h1
- Mobile: hierarchy OK but the main page topic is not a h1
- Support: two h1 and incorrect hierarchy
- Get involved (Make): two h1 and incorrect hierarchy
- About: two h1
- Blog: hierarchy OK but the main page topic is not a h1
- Hosting: hierarchy OK but the main page topic is not a h1
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 headings hierarchy is correct on all the network pages.",afercia
5581,Consolidating setup of local Dev environment documentation and testing instructions.,General,normal,task (blessed),,new,2021-01-20T19:38:57Z,2022-04-01T12:32:32Z,"There are several places that have the same kind of documentation for setting up a local dev environment. These exist in various degrees of completeness and quality. There is also a crossover of docs in regards to testing/contributing. It would be great to see if we can combine these efforts and create one central place for documentation for setting up a local dev environment + testing instructions.
Here is an example from the Block Editor Handbook:
https://developer.wordpress.org/block-editor/tutorials/devenv/#quick-start
+
Issue in relation to testing pull requests:
https://github.com/WordPress/gutenberg/issues/25202
Here is an example from a post on P2:
https://make.wordpress.org/core/2021/01/15/test-scrub-for-wordpress-5-7/
Core Handbook Getting Started
https://make.wordpress.org/core/handbook/tutorials/getting-started/#setting-up-a-local-server
https://github.com/WordPress/wordpress-develop
-------
Documentation we can easily update showing methods for WordPress core and Gutenberg. A document for setting up a local dev environment, and a document for testing trac tickets as well as Gutenberg Github pull requests.
Having an easy to follow step by step hand holding method with some short explanations and some troubleshooting tips would be a huge help to people at various skill levels. Making it easy for developers and non developers to follow.
",paaljoachim
6402,Content alignment Issue in Responsive,Support Forums,lowest,defect (bug),,new,2022-07-13T05:53:15Z,2022-07-13T06:01:48Z,"Hello Team,
In wordpress.org site on below link, found that contents are not properly aligned from left side for responsive mobile devices (767px and below).
Page URL: https://wordpress.org/support/welcome/
Please find Screenshot for the same
Thanks",varshil151189
6303,Content is currently hidden behind the footer,WordPress.tv,normal,defect (bug),,new,2022-05-05T12:38:06Z,2022-05-17T16:47:07Z,"The bottom page content is currently hidden behind the footer in small device
URL: https://wordpress.tv/subtitle/?video=72128",umesh84
3576,Content Limitations - custom CSS and aria-label,International Sites (Rosetta),normal,enhancement,,new,2018-04-16T12:08:11Z,2018-04-17T02:36:55Z,"See https://en-gb.wordpress.org/meetups/
There are a couple of things I'd like to improve here:
- consolidate the repeated `style` attributes for each `h3`, `ul`, and `li` into class selectors. There doesn't appear to be a way to define custom CSS (like WordCamp sites can), and `