__group__ ticket summary component version milestone type owner status created _changetime _description _reporter Active Tickets 5322 Paginated states of topics should append a trailing slash Support Forums defect (bug) tellyworth accepted 2020-07-21T08:47:35Z 2021-03-10T21:24:24Z Paginated states of topics, like https://wordpress.org/support/topic/can-you-use-gutenberg-blocks-w-o-the-visual-editor/page/2, should forcibly append a trailing slash via a 301 redirect. jonoaldersonwp Active Tickets 7141 Huge Emojis in Support Forum Support Forums defect (bug) dd32 accepted 2023-07-14T11:02:16Z 2023-07-27T01:50:10Z "For the past few days we've been seeing huge emojis in the support forum (basically they have no width set and the full image size is showing. [[Image(https://prnt.sc/cWAjuDkhAh-1)]] I'm not sure where this CSS should be added but something like this fixes the issue: {{{ #bbpress-forums div.bbp-reply-content img.emoji { width: 1em; vertical-align: middle; } }}} " talextech Active Tickets 5618 Require ToS/Privacy at login and record acceptance Login & Authentication enhancement dd32 accepted 2021-02-12T02:29:16Z 2021-11-17T05:46:57Z "For legal reasons it is necessary that WordPress.org enforces acceptance of a ToS and Privacy Policy at login, and record the date and version of the policy most recently accepted by each user. This means: * The login form will need to include a checkbox such as `[ ] I have read and accept the terms of service and privacy policy` with appropriate links. * Failure to check the box will prevent login. * Login sessions should remain capped at 2 weeks to ensure all active users regularly accept new terms. * On successful login, a usermeta or similar value should be set recording the timestamp and version of the ToS and Privacy policy documents (perhaps the currently deployed svn rev# for each?) * It should probably also record the rev # of the login form and theme, since that may be relevant info. " tellyworth Active Tickets 2699 Add a new role to the forums: plugin/theme support Support Forums 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 Active Tickets 4825 Add Enterprise content to wordpress.org General Q1 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 Active Tickets 1424 Automate meta contributor badge assignment when receiving props Profiles 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 Active Tickets 4123 Proposal to improve the main navigation menu accessibility General defect (bug) Otto42 accepted 2019-01-29T18:14:14Z 2023-06-13T06:25:20Z "Several [https://www.w3.org/TR/wai-aria-practices-1.1/#html5-sectioning-elements HTML5 sectioning elements] automatically create [https://www.w3.org/TR/wai-aria-1.1/#landmark_roles ARIA landmark regions]. Landmark regions are exposed to assistive technologies and allow users to quickly find information in a page. Ideally, all content in a web page should be wrapped within landmark regions. For now, I'd like to propose to focus on the navigation menu. In this specific case it's important to know that `