{5} Accepted, Active Tickets by Owner (Full Description) (52 matches)
List tickets accepted, group by ticket owner. This report demonstrates the use of full-row display.
DrewAPicture (1 match)
Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#1866 | Add a basic "suggest an edit" workflow to the handbooks plugin | Handbooks | enhancement | 07/29/2016 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
We've talked about this quite a bit in the context of DevHub where User Contributed Notes are occasionally used as a feedback mechanism. Basically, we need a way for docs consumers to report problems or suggest edits of published documentation on .org. The initial proposal would be to build or use something akin to Post Forking on the front-end of handbooks and eventually other places like DevHub or HelpHub. Personally I don't think an MVP has to be a complete solution, it mostly needs to cover the rift drawn between moving away from the Codex where any user could edit anything to the now largely closed systems on .org. I think starting with the handbooks would be the way to go. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Otto42 (5 matches) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4825 | Add Enterprise content to wordpress.org | General | Q1 | enhancement | 11/05/2019 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The Enterprise Growth council has been working on content geared toward enterprise decision-makers as a companion to the content the Growth Council created in 2018. This is essentially a microsite that will live at wordpress.org/enterprise. All the content and designs required for this is here: https://drive.google.com/open?id=1lRpTt88b5bcdbiClPNZwmVP6w1q1QGFJ and here: https://docs.google.com/spreadsheets/d/1uPa6m2hVb4Oz-qOvTEDn2FUC1-uBRVoDvohc7YNmYRY/edit#gid=0 Any additional coordination with the council can take place in #council-ops https://wordpress.slack.com/archives/C9GG77GRJ |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4123 | Proposal to improve the main navigation menu accessibility | General | defect | 01/29/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Several HTML5 sectioning elements automatically create ARIA landmark regions. Landmark regions are exposed to assistive technologies and allow users to quickly find information in a page. Ideally, all content in a web page should be wrapped within landmark regions. For now, I'd like to propose to focus on the navigation menu.
In this specific case it's important to know that
In the wp.org network, some sections don't use Other sections do use navigation landmarks but not for the main menu. For example, the Themes section has two of them: Same in the Plugin section sub-pages: For clarity, these are respectively:
Besides technical details, the most important navigation (the main one) doesn't use a navigation landmark. Wrapping the main menu in a
Note: when in a page there are multiple landmarks of the same type, it's important to use an Suggested:
Optionally:
Note about the wording:
When screen readers encounter a |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#2699 | Add a new role to the forums: plugin/theme support | Support Forums | enhancement | 04/07/2017 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Plugin and theme authors currently have the power to mark threads as resolved within their own support forum, which is great. Problem description However, some of the larger plugin/theme shops have a support team to help out on their own support forums. I think it would be useful to be able to recognize those people in the support forums, like we’re able to recognize authors. Proposal So what I would like to propose is adding a new role: Plugin/Theme Support. Everyone with this role should have rights to mark topics within their own support forum as resolved, and should not be affected by posting speed limitations for their own support forum. This role should also show in the forums as ‘Support’, similar to author. The reason why I propose a new role, instead of adding the capability to the contributor role is because, in my opinion, they serve a different purpose. Let me explain. A contributor is someone who helped your open source project forward. This can be by providing feedback, writing code, creating images, doing marketing or being a friend of the project, for example. Someone working on support does contribute his/her (paid) time to your project and is in that way a contributor. However, I think there are more than enough valid use cases where you don’t want someone who contributed code (for example) once to be able to close support request on behalf of the author. That’s why I think having a separate support role would be viable. It would show the community that this person is vetted and answering on behalf of the plugin/theme author. Related ticket This proposal is related to ticket #2598. Managing support role Of course, it should be possible for plugin authors to manage the list of support people. I see two reasonable ways to do so, which should be mutually exclusive.
One way is by adding the usernames to the Showing support staff To be transparent about this, we’d probably also need a place to list people in the support role. This could be the Advanced View page, or even the plugin page itself. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#3973 | Search enhancement request so that HelpHub contents will be included in the result | HelpHub | enhancement | 12/03/2018 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
If you use the search bar on https://wordpress.org/support, you will see that it neither includes HelpHub articles nor excludes Codex ones. I feel that we should well be
Also, search bar should say "Search documentation and forums" or something along those lines and not just forums? Releated discussion in Slack https://wordpress.slack.com/archives/C02RP4WU5/p1543850975111100 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4184 | Add a robots.txt disallow all rule to ps.w.org | Version Control | defect | 02/18/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Replace the contents of https://ps.w.org/robots.txt with:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
SergeyBiryukov (6 matches) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#20 | Possible for user's to break layout when adding forum posts | Support Forums | defect | 07/17/2013 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
When a user wraps text in their forum posts with "<li>" tags - The layout of the page breaks. For an example of this see - http://wordpress.org/support/topic/please-ignore-just-testing-something?replies=1#post-4430248 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#2204 | Forum RSS Feed Issues | Support Forums | defect | 11/03/2016 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The RSS feeds generated by the new Plugin Directory platform have a number of drawbacks/defects compared to the feeds that were generated by the old platform.
Minor notes:
In short, RSS updates should contain:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4403 | Make -- posts missing the ID called comments | Make (Get Involved) / P2 | defect | 04/25/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
When subscribed to a Make blog, the email sent when a post is published has a link called "See all comments", and it has a fragment ID of Here is an example from the email https://make.wordpress.org/core/2019/04/25/site-health-check-in-5-2/#comments |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4499 | Prevent tall screenshots overflowing container | Theme Directory | defect | 06/07/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Sometimes theme authors accidentally add screenshots which are too tall for the theme directory, see the below slack conversation for an example, we should limit the height of screenshots. https://wordpress.slack.com/archives/C02RP4Y3K/p1559876587250600 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4695 | Add FAQPage schema markup to plugin pages | Plugin Directory | defect | 08/20/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Plugin pages, like https://wordpress.org/plugins/autoptimize/, often contain FAQ content. When this is the case, we should output FAQ schema markup, with an aim to encourage Google to show FAQ questions+answers in the search results (therefore achieving extra visibility and clickthrough-rates). Approach
Example output{ "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{ "@type": "Question", "name": "What does the plugin do to help speed up my site?", "acceptedAnswer": { "@type": "Answer", "text": "It concatenates all scripts and styles, minifies and compresses them, adds expires headers, caches them, and moves styles to the page head, and scripts (optionally) to the footer. It also minifies the HTML code itself, making your page really lightweight." } }, { "@type": "Question", "name": "But I’m on HTTP/2, so I don’t need Autoptimize?", "acceptedAnswer": { "@type": "Answer", "text": "HTTP/2 is a great step forward for sure, reducing the impact of multiple requests from the same server significantly by using the same connection to perform several concurrent requests. That being said, <a href="http://engineering.khanacademy.org/posts/js-packaging-http2.htm">concatenation of CSS/ JS can still make a lot of sense</a>, as described in <a href="https://css-tricks.com/http2-real-world-performance-test-analysis/">this css-tricks.com article</a> and this <a href="http://calendar.perfplanet.com/2015/packaging-for-performance/">blogpost from one of the Ebay engineers</a>. The conclusion; configure, test, reconfigure, retest, tweak and look what works best in your context. Maybe it’s just HTTP/2, maybe it’s HTTP/2 + aggregation and minification, maybe it’s HTTP/2 + minification (which AO can do as well, simply untick the “aggregate JS-files” and/ or “aggregate CSS-files” options). And Autoptimize can do a lot more then “just” optimizing your JS & 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
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#3954 | Support Forums: Add counters to moderation links | Support Forums | enhancement | 11/24/2018 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
@sevlad suggested adding counters to moderation links that require an action, see an example screenshot. For a quick access from any page, it might also be a good idea to add these links under "My Account" in admin bar, as a follow-up to [6303]. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
coffee2code (3 matches) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4277 | Profile template meta tweaks | Profiles | enhancement | 03/15/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
<meta property="og:type" content="profile" /> <meta property="og:title" content="{{Full Name}} - WordPress user profile" /> <meta property="og:description" content="{{Meta description}}" /> <meta property="og:url" content="{{URL}}" /> <meta property="og:site_name" content="WordPress" /> <meta property="og:image" content="{{Gravatar Large Image}}" /> <meta property="profile:username" content="{{Username}}" /> |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#1424 | Automate meta contributor badge assignment when receiving props | Profiles | defect | 12/01/2015 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Profile badges don't seem to automatically appear for all areas. My core and plugins badges appeared on my profile on their own (as far as I can tell), but my Speaker badge had to be added manually with some difficulty, and my Meta badge hasn't appeared at all after getting first props a few weeks ago (see [2016]). |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4280 | Add schema markup to profile templates | Profiles | defect | 03/15/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The following code should be adapted and added to profile templates (values from https://profiles.wordpress.org/jonoaldersonwp/ used for reference). <script type="application/ld+json"> { "@context":"https://schema.org", "@graph":[ { "@type":"Organization", "@id":"https://wordpress.org/#organization", "url":"https://wordpress.org/", "name":"WordPress", "logo":{ "@type":"ImageObject", "@id":"https://wordpress.org/#logo", "url":"https://s.w.org/style/images/about/WordPress-logotype-wmark.png" }, "sameAs":[ "https://www.facebook.com/WordPress/", "https://twitter.com/WordPress", "https://en.wikipedia.org/wiki/WordPress" ] }, { "@type":"WebSite", "@id":"https://wordpress.org/#website", "url":"https://wordpress.org/", "name":"WordPress.org", "publisher":{ "@id":"https://wordpress.org/#organization" } }, { "@type":"ProfilePage", "@id":"https://profiles.wordpress.org/jonoaldersonwp/#webpage", "url":"https://profiles.wordpress.org/jonoaldersonwp/", "inLanguage":"en", "name":"{{Page title}}", "description":"{{Meta description}}", "isPartOf":{ "@id":"https://wordpress.org/#website" } }, { "@type":"Person", "@id":"https://profiles.wordpress.org/jonoaldersonwp/#profile", "name":"Jono Alderson", "image":"https://secure.gravatar.com/avatar/beed0f5ca54ae221655b9f30a1f6fe66?s=200&d=mm&r=g", "jobTitle":"Special Ops", "worksFor": { "@type":"Organization", "name":"Yoast" }, "sameAs": [ "https://www.facebook.com/jonathan.alderson", "https://www.linkedin.com/in/jonoalderson/", "https://twitter.com/jonoalderson" ], "mainEntityOfPage": { "@id" : "https://profiles.wordpress.org/jonoaldersonwp/#webpage" } } ] } </script>
NOTE: Optional nodes (like NOTE: https://meta.trac.wordpress.org/ticket/4277 changes the title and description contents; values here should also change and use the new values specified in #4277.
NOTE: https://meta.trac.wordpress.org/ticket/4278 is required to retrieve/set social profiles in the
NOTE: If |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
coreymckrill (6 matches) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#3003 | Tagregator - Twitter resets settings randomly | WordCamp Site & Plugins | defect | 07/26/2017 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Hello, While I was working on these tickets: #2100 and #2907 I've noticed that my error log was getting grumpy and I saw this error:
For some reason when you view the results page on the front end the twitter module bugs out randomly ( not all times ) and after that php error all the settings are getting reset so you are losing all login information etc. I haven't been able to find out why. @dipeshkakadiya is on it for a solution so we can implement it on gwtd3 new website as well. Pointers for devs: Grab the /trunk of Tagregator through svn, apply the extra patches to have the latest as they have not been implemented yet and then work on this ticket. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4243 | Clarify Payment Gateway Account Settings for CampTix | WordCamp Site & Plugins | enhancement | 03/06/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The option "None" for Tickets >> Setup >> Predefined Account is unclear - this seems like there would be no payment gateway if that setting is chosen, which makes it unclear how you can access the custom gateway settings. Changing this label to "Custom Account" or "Local Payment Account" would be clearer. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#2894 | Admin Flags: Internationalise the post-status-change label | WordCamp Site & Plugins | defect | 06/22/2017 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
When toggling a status in the Flag section, the toggle afterwards is missing the capitalisation, this is because it just sets the label afterwards to the command, rather than the textual label for it. The attached patch adds internationalised Enable/Disable text which it switches in/out instead of using the command. It's hard-coded inline with the JS, as that's the format of the current JS and changing it up further probably deserves a rethink of the entire flagging UI and storage. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#2923 | Layout / Responsive issue on Opera for Android (Central Wordcamp) | WordCamp Site & Plugins | defect | 07/04/2017 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Hi guy's, This is the first time I write a ticket here. Do not hesitate to give me advice if it is not the usual way to fill a ticket. I would like to bring to your attention that there are problems about the layout on the website https://central.wordcamp.org/ for Opera users on Android. Here is an example on this screenshot, but there are probably others : I posted this info on slack yesterday and @coreymckrill recommended me filling a ticket here. Regards, Jason |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#2849 | Add sessions list and other details to speaker pages | WordCamp Site & Plugins | enhancement | 06/05/2017 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
For the new CampSite theme we had the idea to include a speakers bio page with an improved sessions list not only showing the session title, but also an excerpt as well as links to the slides and WordPress.tv video. We decided against a page template and rather add this additional markup to the post types plugin. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#3122 | Documentation for prefilling coupon field in CampTix via query string | WordCamp Site & Plugins | enhancement | 09/11/2017 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
To save time and avoid typos, it would be great to support a means of that prefilling the coupon field. For example: city.wordcamp.org/tickets?coupon=2017volunteer Volunteers, sponsors, speakers, organizers, scholarship recipients, and others rely on coupon codes, and this would enable organizers to ensure they get the coupon code right on the first try. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dd32 (12 matches) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4331 | News archive templates should use canonical URL tags | General | defect | 03/26/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Individual news articles (like https://wordpress.org/news/2019/01/wordpress-5-0-3-maintenance-release/) correctly use canonical URL tags. However, archives / the homepage / categories do not. E.g., https://wordpress.org/news/, https://wordpress.org/news/page/2/, https://wordpress.org/news/category/testing/ should all have/use canonical URL tags. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4839 | Update themes upload page | Theme Directory | enhancement | 11/12/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Current page https://wordpress.org/themes/upload/ is a mix of content from the admin and page template. This makes the site non-translatable, which can be a problem as presented here https://sv.wordpress.org/themes/upload/ The patch I've created will add all the content in the page template.
Another bug this fixes is the fact that the
I'll submit a patch that covers When this will be applied, the content on the page should be removed (aside from the shortcode which should remain). |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#1639 | Themes Trac browser does not display UTF-8 text correctly | Trac | Q1 | defect | 03/19/2016 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
On Core and Plugins Trac, UTF-8 text is displayed correctly: https://core.trac.wordpress.org/browser/tags/4.4.2/tests/phpunit/tests/pomo/po.php#L115 https://plugins.trac.wordpress.org/browser/edit-parent-comment-id/tags/0.3/edit-parent-comment-id-ru_RU.po#L24 On Themes Trac that's not the case, looks like ISO-8859-1 is the default encoding there: https://themes.trac.wordpress.org/browser/zalive/1.3.4/languages/ru_RU.po#L20 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#2508 | bbPress and Meta Trac should be able to change closed tickets resolution reason | Trac | defect | 02/16/2017 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
If a ticket on bbPress or Meta Trac is closed with a particular resolution the resolution cannot be changed without reopening the ticket: eg: bbPress Trac (Meta is identical): BuddyPress and Core Tracs can change resolution withot reopening the ticket: Taking a punt that the following code needs to be added to bbPress and Meta Trac "workflow-*.ini" files. I know bbPress and BuddyPress "workflow-*.ini" files are yet to be open sourced, presuming the same for meta: Via: https://meta.trac.wordpress.org/browser/sites/trunk/trac.wordpress.org/conf/workflow-core.ini#L64 # Once the ticket is closed # - reopen # - change the resolution to something else ... ... change_resolution = closed -> closed change_resolution.name = change the resolution, set change_resolution.operations = set_resolution change_resolution.permissions = TICKET_EDIT_DESCRIPTION change_resolution.default = -31 Aside: It wouldn't hurt to add the "mark as duplicate" section also ;) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#2931 | Plugin Directory: Incorrect parsing of code blocks | Plugin Directory | defect | 07/05/2017 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The description for Theme Check plugin appears to be parsed incorrectly (see the screenshot).
The first code sample lacks the code formatting. In the Examples: `define( 'TC_PRE', 'Theme Review:[[br]] - Themes should be reviewed using "define(\'WP_DEBUG\', true);" in wp-config.php[[br]] - Themes should be reviewed using the test data from the Theme Checklists (TC) ----- ' );` `define( 'TC_POST', 'Feel free to make use of the contact details below if you have any questions, comments, or feedback:[[br]] [[br]] * Leave a comment on this ticket[[br]] * Send an email to the Theme Review email list[[br]] * Use the #wordpress-themes IRC channel on Freenode.' );` |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4245 | HTTP requests to pingomatic.com should 301 to the HTTPS equivalent | SSL | defect | 03/07/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
E.g., http://pingomatic.com/ should redirect to https://pingomatic.com/ http://pingomatic.com/stats/?cat=dog should redirect to https://pingomatic.com/stats/?cat=dog |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4360 | Trac throwing errors about missing or invalid form token/secure cookies on ticket updates | Trac | defect | 04/03/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Trac has been directing people to an error page when they try to submit comments or updates to tickets. I first seen this problem mentioned on March 30th.
The message reads The submissions are coming from pages that are https in the browser though and cookies are enabled. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4611 | Update 'Tickets requesting UI or UX feedback' report name to 'Tickets requesting design feedback' | Trac | defect | 07/17/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Hello,
With The link for the page goes here - https://core.trac.wordpress.org/tickets/ux-feedback *Am wondering if the URL should also change. I couldn't find the string in the meta repo but am happy to write a patch if someone can poitn me in the right direction. Thanks |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4656 | Plugin Directory: Check for slug conflicts before accepting | Plugin Directory | defect | 08/02/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This is done in themes, but needs to happen in plugins as well. If someone uploads a plugin with a proposed slug that is already in use, we need to have the plugin FAIL. This would prevent people from uploading their free plugin with the same name as their pro one and goofing all their users. The breakpoint should be 50 users. This would also need a tool on the admin end so we can see what's going on (much like we have for author cards). This WILL NOT fix a problem if we manually rename a slug per their request, but if we have the tool at least we'll be able to see why :/ |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4555 | Plugin Directory Administration: Mass Email Tool | Plugin Directory | enhancement | 06/26/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
We need an admin-only tool that will allow us to mass-email plugins. One exists but currently can only be run by a server admin, which limits usability. 1) Provide a list of plugins 2) Provide an email subject and body with basic substitutions 3) The tool would then email everyone with commit access and listed owner the message Substitutions needed: %USER_EMAIL% %USER_DISPLAY_NAME% %PLUGIN_URL% With Helpscout you can pre-fill everything BUT the body: https://docs.helpscout.com/article/119-pre-fill So it doesn't look like we can use that for our bulk-mail tool. If it's secure and has the capability to be given a usable UX, whatever tool is used on the back-end should be fine. Limiting the number of plugins mailed at a time is also fine. Handling more than 50 of those at a stretch is usually pretty annoying anyway :) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4326 | Support forum URLs should enforce a trailing slash via a 301 redirect | Support Forums | defect | 03/26/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
E.g., https://wordpress.org/support/view/plugin-committer/corylamleorg should 301 to https://wordpress.org/support/view/plugin-committer/corylamleorg/ https://wordpress.org/support/view/plugin-committer/corylamleorg/page/2 should 301 to https://wordpress.org/support/view/plugin-committer/corylamleorg/page/2/. https://wordpress.org/support/view/no-replies should 301 to https://wordpress.org/support/view/no-replies/ |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4559 | Dedicated robots.txt file for translate.wordpress.org | Translate Site & Plugins | enhancement | 06/28/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This consumes huge amounts of crawl budget, for relatively little return. We'd like to block crawling of it entirely, via robots.txt. At the moment, it shares a robots.txt with other wordpress.org domains, which makes this impossible. Can we give it a dedicated robots.txt file, which is separate from other sites, with the following contents: User-agent: * Disallow: /* Noindex: /* Allow: /$ NB: We'll need to be absolutely certain that this is a standalone file, and doesn't bleed through to any other WP domains/contexts, or we'll cause the end of the world.
If/when this is complete, the |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dufresnesteven (2 matches) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4120 | Proposal to change the headings hierarchy in the About section | General | defect | 01/29/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Splitting this out from #4110. The headings hierarchy in the About section has room for improvements for better SEO and accessibility:
In the main page, the headings hierarchy looks pretty good with one exception: as mentioned in #4112 the logo shouldn't be a
Same in the sub-pages: there should be only one In some of the sub-pages, for example:
The headings within the content are
Testimonials page:
On https://wordpress.org/about/testimonials/ it would be nice to have a Note: In the statistics page, it would be nice to have headings before each graph section. Also, it would be great to have an alternative representation of the graphs in the form of data tables, but this is out of the scope of this ticket. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4888 | Caption overflow in screenshots of plugin single page | Plugin Directory | defect | 12/04/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
I'm having an design issue with a screenshot of a plugin WP Two Factor Authentication with Telegram. I just update the screenshots and captions and saw that the captions stay behind the thumbnails when overflow the 600px limit given to the CSS class .plugin-screenshots .image-gallery-slides, wouldn't it be better if the text pushes down to avoid this defect? Here's the defect: I changed the value to 650px just for testing purposses and works great: |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
iandunn (1 match) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#2823 | Improve IP Geolocation Results | Events API | defect | 05/11/2017 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
There are a couple problems with our current data set. They're not strictly related to each other, but I'm creating a single ticket for this because I'm guessing that the solution to both will be the same: switch from our current data source to a better one.
It looks like our database was updated recently (March 2017), but I can't find any info on where the original data comes from. @dd32, @tellyworth, do either of you know? Do you have any thoughts on other potential sources? |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
netweb (1 match) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#2537 | Support Forums: Audit Log for Mod Actions | Support Forums | enhancement | 02/27/2017 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
It would be helpful if the forums logged who marked a post resolved (or unresovled) as well as closed etc. From a moderator perspective, this would help track down plugin developers (for example) who automate resolving tickets. It would also mean we'd know who to ping if someone closed a post without a comment. Example:
or
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ocean90 (3 matches) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#668 | Open-source News Theme | General | enhancement | 10/23/2014 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
While we were building the new bbPress theme we discovered that the WordPress theme live on https://wordpress.org/news/ would've been the best starting point. We now had to hack together stuff from various places. Wouldn't it make sense to open-source that theme used at /news/ as well? |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4535 | Delete "Hello World" posts (and tidy up empty blogs) | International Sites (Rosetta) | enhancement | 06/26/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Various Rosetta sites have a blog with a "Hello World" post. These should be deleted. Because of the incorrect hreflang setup on these sites, these posts cause an absolute SEO nightmare as Google seeks out their (non-existent) siblings across the whole network. E.g., https://tg.wordpress.org/2012/08/23/hello-world/ https://tt.wordpress.org/2014/07/08/hello-world/ https://fao.wordpress.org/2016/07/20/hello-world/ https://dzo.wordpress.org/2015/02/24/hello-world/ https://kab.wordpress.org/2015/02/24/hello-world/ https://sa.wordpress.org/2011/07/26/hello-world/ https://hau.wordpress.org/2016/07/15/hello-world/ https://bre.wordpress.org/2015/07/17/hello-world/ https://ak.wordpress.org/2016/03/05/hello-world/ https://es-pr.wordpress.org/2016/03/05/hello-world/ https://rup.wordpress.org/2016/03/05/hello-world/ I don't have an easy way of finding them all from the outside-in - I'm hoping that these should be easy to round up? It's also worth considering that in many cases, these are the only blog posts on these blogs. E.g., https://dzo.wordpress.org/news/, https://bre.wordpress.org/news/ When that's the case and we're removing them, can we also please:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4289 | Delete placeholder pages | International Sites (Rosetta) | defect | 03/15/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The following legacy pages should be deleted, and 301'd to a sensible location. May also need removing from nav, if this isn't automatic. Likely going to need to do a few passes of these for ones I miss in the initial sweep... Might also be some duplicates. 'Welcome' flavours (should 301 to site root): https://fuc.wordpress.org/txt-welcome/ https://frp.wordpress.org/txt-welcome/ https://kab.wordpress.org/txt-welcome/ https://tg.wordpress.org/txt-welcome/ https://li.wordpress.org/txt-welcome/ https://nl.wordpress.org/txt-welcome/ https://tt.wordpress.org/txt-welcome/ https://la.wordpress.org/txt-welcome/ https://la.wordpress.org/txt-welcome/ https://si.wordpress.org/txt-welcome/ https://am.wordpress.org/txt-welcome/ https://es-cr.wordpress.org/txt-welcome/ https://lin.wordpress.org/txt-welcome/ https://sq.wordpress.org/txt-welcome/ https://es-ar.wordpress.org/txt-welcome/ https://oci.wordpress.org/txt-welcome/ https://br.wordpress.org/txt-welcome/ https://de-ch.wordpress.org/txt-welcome/ https://cn.wordpress.org/txt-welcome/ https://nb.wordpress.org/txt-welcome/ https://bre.wordpress.org/txt-welcome/ https://gd.wordpress.org/txt-welcome/ https://el.wordpress.org/txt-welcome/ https://hr.wordpress.org/txt-welcome/ https://cs.wordpress.org/txt-welcome/ https://es-mx.wordpress.org/txt-welcome/ https://is.wordpress.org/txt-welcome/ https://bg.wordpress.org/txt-welcome/ https://it.wordpress.org/txt-welcome/ https://it.wordpress.org/txt-welcome/logowordcamp/ https://lv.wordpress.org/txt-welcome/ https://bn.wordpress.org/txt-welcome/ https://ms.wordpress.org/txt-welcome/ https://fy.wordpress.org/txt-welcome/ https://uz.wordpress.org/txt-welcome/ https://ug.wordpress.org/txt-welcome/ https://as.wordpress.org/txt-welcome/ https://mr.wordpress.org/txt-welcome/ https://ky.wordpress.org/txt-welcome/ https://dv.wordpress.org/txt-welcome/ 'Install' flavours (should 301 to the local 'download' page if it exists, and the root if not): https://rhg.wordpress.org/txt-install/ https://en-gb.wordpress.org/txt-install/ https://ku.wordpress.org/txt-install-2/ https://fr.wordpress.org/txt-install/ https://da.wordpress.org/txt-install/ https://li.wordpress.org/txt-install/ https://el.wordpress.org/txt-install/ https://eu.wordpress.org/txt-install/ https://srd.wordpress.org/txt-install/ https://so.wordpress.org/txt-install/ https://so.wordpress.org/txt-install/ https://kab.wordpress.org/txt-install/ https://tw.wordpress.org/txt-install/ https://fi.wordpress.org/txt-install/ https://haz.wordpress.org/txt-install/ https://de-ch.wordpress.org/txt-install/ https://os.wordpress.org/txt-install/ https://es-ar.wordpress.org/txt-install/ https://mr.wordpress.org/txt-install/ https://es-mx.wordpress.org/txt-install/ https://es-co.wordpress.org/txt-install/ https://gl.wordpress.org/txt-install/ https://nn.wordpress.org/txt-install/ https://jv.wordpress.org/txt-install/ https://mk.wordpress.org/txt-install/ https://fy.wordpress.org/txt-install/ https://id.wordpress.org/txt-install/ https://ido.wordpress.org/txt-install/ https://ms.wordpress.org/txt-install/ https://sw.wordpress.org/txt-install/ https://ca.wordpress.org/txt-install/ https://kn.wordpress.org/txt-install/ https://azb.wordpress.org/txt-install/ https://sq.wordpress.org/txt-install/ https://tl.wordpress.org/txt-install/ https://zh-hk.wordpress.org/txt-install/ https://es-cr.wordpress.org/txt-install/ https://pl.wordpress.org/txt-install/ https://ko.wordpress.org/txt-install/ https://oci.wordpress.org/txt-install/ https://ky.wordpress.org/txt-install/ https://fa-af.wordpress.org/txt-install/ https://th.wordpress.org/txt-install/ https://bn.wordpress.org/txt-install/ https://as.wordpress.org/txt-install/ https://pan.wordpress.org/txt-install/ https://az-tr.wordpress.org/txt-install/ https://lin.wordpress.org/txt-install/ https://vi.wordpress.org/txt-install/ https://fr-be.wordpress.org/txt-install/ https://ka.wordpress.org/txt-install/ https://xho.wordpress.org/txt-install/ https://hu.wordpress.org/txt-install/ https://fr-ca.wordpress.org/txt-install/ https://is.wordpress.org/txt-install/ https://dzo.wordpress.org/txt-install/ https://sv.wordpress.org/txt-install/ https://ko.wordpress.org/txt-install/ https://sr.wordpress.org/txt-install/ https://co.wordpress.org/txt-install/ https://bre.wordpress.org/txt-install/ https://hr.wordpress.org/txt-install/ https://hr.wordpress.org/txt-install/clean-install/ https://hr.wordpress.org/txt-install/upgrade/ https://gu.wordpress.org/txt-install/ https://km.wordpress.org/txt-install/ https://ar.wordpress.org/txt-install/ https://fa.wordpress.org/txt-install/ https://it.wordpress.org/txt-install/ https://su.wordpress.org/txt-install/ https://tuk.wordpress.org/txt-install/ https://sa.wordpress.org/txt-install/ https://bs.wordpress.org/txt-install/ https://kir.wordpress.org/txt-install/ https://yor.wordpress.org/txt-install/ https://br.wordpress.org/txt-install/ https://nb.wordpress.org/txt-install/ https://tt.wordpress.org/txt-install/ https://ta.wordpress.org/txt-install/ https://uk.wordpress.org/txt-install/ https://snd.wordpress.org/txt-install/ https://arq.wordpress.org/txt-install/ https://tg.wordpress.org/txt-install/ https://twd.wordpress.org/txt-install/ https://eo.wordpress.org/txt-install/ https://ur.wordpress.org/txt-install/ https://hr.wordpress.org/txt-install/clean-install/ https://ug.wordpress.org/txt-install/ https://bcc.wordpress.org/txt-install/ https://khk.wordpress.org/txt-install/ https://ory.wordpress.org/txt-install/ 'Themes' themes https://ml.wordpress.org/Themes/ 'Sample page' variants https://snd.wordpress.org/sample-page/ https://tzm.wordpress.org/sample-page/ https://rup.wordpress.org/sample-page/ https://az-tr.wordpress.org/sample-page/ https://os.wordpress.org/sample-page/ https://lin.wordpress.org/sample-page/ https://twd.wordpress.org/sample-page/ https://fur.wordpress.org/sample-page/ https://sa.wordpress.org/sample-page/ https://pan.wordpress.org/sample-page/ https://la.wordpress.org/sample-page/ https://as.wordpress.org/sample-page/ https://bre.wordpress.org/sample-page/ https://fuc.wordpress.org/sample-page/ https://tt.wordpress.org/sample-page/ https://azb.wordpress.org/sample-page/ 'Releases' variants https://cs.wordpress.org/releases/ 'Contact' variants https://es-pr.wordpress.org/contact/ https://ur.wordpress.org/contact/ https://kal.wordpress.org/contact/ https://eu.wordpress.org/argitaraketak/ https://dzo.wordpress.org/contact/ https://scn.wordpress.org/contact/ https://ps.wordpress.org/contact/ https://es-mx.wordpress.org/contact/ https://km.wordpress.org/contact/ https://tah.wordpress.org/contact/ https://ta.wordpress.org/contact/ https://snd.wordpress.org/contact/ https://kir.wordpress.org/contact/ https://sna.wordpress.org/contact/ https://dv.wordpress.org/contact/ https://rhg.wordpress.org/contact/ https://mlt.wordpress.org/kuntatt/ https://frp.wordpress.org/contact/ https://yor.wordpress.org/contact/ https://arq.wordpress.org/contact/ https://sa.wordpress.org/contact/ https://oci.wordpress.org/contact/ https://ido.wordpress.org/contact/ https://lo.wordpress.org/contact/ https://rup.wordpress.org/contact/ https://la.wordpress.org/contact/ https://fao.wordpress.org/contact/ https://kn.wordpress.org/contact/ https://me.wordpress.org/contact/ https://os.wordpress.org/contact/ https://li.wordpress.org/contact/ https://twd.wordpress.org/contact/ https://es-ar.wordpress.org/contact/ https://as.wordpress.org/contact/ https://ltz.wordpress.org/contact/ https://pan.wordpress.org/contact/ https://mya.wordpress.org/contact/ https://en-gb.wordpress.org/contact/ https://ory.wordpress.org/contact/ https://az.wordpress.org/contact/ https://tg.wordpress.org/contact/ https://te.wordpress.org/contact/ https://mri.wordpress.org/contact/ https://khk.wordpress.org/contact/ https://kin.wordpress.org/contact/ https://tuk.wordpress.org/contact/ https://az-tr.wordpress.org/contact/ https://mk.wordpress.org/contact/ https://ast.wordpress.org/contact/ https://gu.wordpress.org/contact/ https://bre.wordpress.org/contact/ https://am.wordpress.org/contact/ https://mg.wordpress.org/contact/ https://mr.wordpress.org/contact/ https://lin.wordpress.org/contact/ https://hat.wordpress.org/contact/ https://ary.wordpress.org/contact/ https://co.wordpress.org/contact/ |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
tellyworth (12 matches) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#2467 | Plugins not showing on plugin-install screen | Plugin Directory | Plugin Directory v3.0 | defect | 02/02/2017 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Not sure if this is a Meta issue, nevertheless, it could be related to the plugins directory. I was doing a plugin search on plugin-install screen of a 4.7.2 site and got a strange behaviour: the search didn't return all the items available. The number is right – 5 items –, but I can only see 4 items on te screen: http://g.recordit.co/yMeHcCzUSY.gif |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4126 | "Special contributions" template leaks PII | Codex | defect | 01/30/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
E.g., https://codex.wordpress.org/Special:Contributions/Jany2786@gmail.com This template should have a meta robots value of 'noindex, follow'. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4109 | Skip to content link missing in many pages or not working properly | General | defect | 01/28/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
"Skip links" are one of the most simple and better known ways to improve accessibility for keyboard users and assistive technologies users. They allow to bypass blocks of content that are repeated on multiple pages, typically: navigation menus. They're implemented since years in WordPress core and the bundled themes. They're also part of the WCAG recommendation: Success Criterion 2.4.1 Bypass Blocks https://www.w3.org/TR/WCAG21/#bypass-blocks In order to be effective, a skip link used to bypass the top navigation needs to:
Far from pretending to be a complete analysis of all the .org network pages, I've gone through the main pages linked in the main navigation menus. To recap:
I realize the .org network is made of different templates coming from different sources and I guess it's a complicated setup. However, it would be great to make sure the skip to content link is actually present in all pages and works properly. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4253 | Plugins API `query_plugins` produces wrong number of results | Plugin Directory | defect | 03/09/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The
So, if you limit the
We are hitting this issue with the WP-CLI |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4259 | No Twitter Card Found | Developer Hub | defect | 03/11/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Hello, There's no Twitter Card found for https://developer.wordpress.org/ on sub-pages. INFO: Page fetched successfully INFO: 6 metatags were found ERROR: No card found (Card error) https://cards-dev.twitter.com/validator |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4306 | Plugin Admin: Update Plugin Stats Report to use HelpScout | Plugin Directory | defect | 03/20/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Currently Stats_Report (plugins/plugin-directory/tools/class-stats-report.php) checks SupportPress We've moved so we'll need to update those checks to use (I think) the API for HelpScout https://developer.helpscout.com/mailbox-api/endpoints/conversations/list/ |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#1278 | Plugins Install API: Add ability to order results | API | enhancement | 10/01/2015 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Copied over from #wp12696: Replying to apeatling:
Reply from Otto:
Now that the arguments for |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#2320 | Global stats for GlotPress to identify possible future GTE | Translate Site & Plugins | enhancement | 12/08/2016 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
On some locales (like Catalan), most of the translations are done by 3-4 people (with 2 of them being GTE), even if according to https://translate.wordpress.org/locale/ca there are 10 GTE, and almost a 100 contributors. This is a problem not only because it simply doesn't scale (with the amount of strings that themes & plugins have, 3-4 people are not enough), but also because is extremely hard for GTEs to identify "active" contributors to help and guide them so they become one day GTE, and for contributors to find active GTE so their strings get approved and don't stay forever as pending. Ideally, there should be a way of "filtering" the teams page (https://make.wordpress.org/polyglots/teams/?locale=ca) with some kind of "active" filter, with active being a rule such as "has translated/reviewed more than X strings (could be 0) in the last 3-4 months". That could help to really asses the health of a team, as you could quickly identify how many people is actively contributing to the project. Also, if that filter included some kind of aggregated cross-project stats (similar to the ones you get "per-project" in translate.wp.org), pointing to the projects they contributed, it would be easier to "measure" the amount of contributions people is doing: I, as a GTE, am more in validating strings translated by someone who contributes regularly than strings from someone who only translated 1 string two months ago. Computing such a huge amount of stats won't be light in terms of resources, but in order to be useful, these stats don't need to be "live": a weekly update would be more than enough to get a sense of the current state. This would also give extra visibility to the health of the team, on top of the "activeness" filter: knowing there are 100 people active when 99 of them only have translated one string isn't a sign of healthy at all. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#4478 | Add an `.editorconfig` file to the root of the meta repo | General | enhancement | 05/27/2019 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Adding the https://core.trac.wordpress.org/browser/trunk/.editorconfig file to the root of the meta repo should help avoid basic coding standards issues when contributing to the meta team.
Using the same |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#815 | Forums to Support Syntax Highlighting | Support Forums | Q1 | enhancement | 01/15/2015 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Quite often we're sharing code snippets to help our users when providing support. I would love to see the support forums support syntax highlighting. In it's current implementation it's not incredibly helpful to the end user. Here's an example: https://wordpress.org/support/topic/reorder-posts-in-collection?replies=4 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#2107 | Prevent posting 10k lines of logs in replies, recommend Pastebin or GitHub gists | Support Forums | Q1 | enhancement | 10/04/2016 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
To provide debugging information some users post their full logs in a reply. These can be up to 10k lines which makes reading the page really annoying because you have to scroll like 5 minutes. Examples:
I suggest to prevent posting replies which have more than X chars/words/lines and to recommend using a service like Pastebin or GitHub gists. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#2260 | Support Forums - Support three backticks | Support Forums | Q1 | enhancement | 11/21/2016 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Since people are getting more and more used to slack and markdown and the three backticks for code blocks, we should consider supporting that in bbPress |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||