__group__ ticket summary reporter component _version priority severity milestone type _status workflow _created modified _description _reporter 3 Days Ago 7530 More relevant block editor handbook search gaambo Developer Hub normal enhancement new 2024-03-25T08:47:02Z 2024-03-25T08:47:02Z "I really like the new design of the block editor handbook, but after using it a lot, I've got some feedback/ideas for better search experience: **1. Add keyboard shortcut for searching** On long pages (like a [https://developer.wordpress.org/block-editor/reference-guides/packages/packages-data/ package reference]), when you have scrolled down very far, getting back to the search field can be cumbersome. There's no ""back to top"" button and no keyboard shortcut for using the search field. A lot of developer documentation provide a Ctrl+K keyboard shortcut to open a search overlay or move focus to the search field. An ""internal"" example is [https://wordpress.github.io/wordpress-playground/ the WordPress Playground documentation] and another one [https://tailwindcss.com/ tailwind CSS]. I often find myself switching between different packages/references, and the block editor handbook with references for each package has a very big navigation menu - so anything that makes navigation easier with keyboard would be great. **2. Search Results: show matched text / jump to match** When searching for any keyword, the results do not show how/where the keyword was matched. When clicking on the result, the page opens at the top - requiring the user to use Ctrl+F on the page again. This once again relates to the references and pages being very long and therefore finding the matched keyword/paragraph hard. Example: Search for [https://developer.wordpress.org/block-editor/?s=useinnerblocksprops useInnerBlocksProps]. The first result is [https://developer.wordpress.org/block-editor/reference-guides/packages/packages-block-editor/ the @wordpress/block-editor package reference] and [https://developer.wordpress.org/block-editor/reference-guides/packages/packages-block-editor/#useinnerblocksprops useInnerBlocksProps] is at the very bottom of the page but the page loads at the top. [[Image(block-editor-handbook-results-innerblocks.png)]] I suggest two things: - Add an excerpt of the matched text/paragraph to the results view and use some styling (e.g. background color, bold) to highlight the keyword. - When clicking on the result, jump to the paragraph/headline the matched text was first found in. **3. More relevant search results** I don't know how the search results are sorted at the moment, but often times I find the more related results at the bottom instead of the top. Maybe we could add some ""weights"" to keywords? I don't know any technical details - if the editor handbook is built on a standard WP search - but a lot of developer documentation use algolia for that (again the [https://wordpress.github.io/wordpress-playground/ WordPress Playground docs] are an example for that). Or maybe usage of a keyword in a headline is more relevant than in a code example? We could also categorize the results into ""API reference"", ""guides"" (just like the main navigation bar on the side) Examples: - Search for [https://developer.wordpress.org/block-editor/?s=getentityrecords getEntityRecords]. The first result is the [https://developer.wordpress.org/block-editor/contributors/code/deprecations/ Deprecations] page. Which may be relevant, but I guess if I search for the exact method name, I'd want to see the documentation of that method, not of any deprecations. The next result is @wordpress/data - which just has an example of using the function, but not the docs. The real documentation of the function is actually just the fifth element. [[Image(block-editor-handbook-results-entityrecords.png)]] - Search for [https://developer.wordpress.org/block-editor/?s=useblockprops useBlockProps]. ""Edit and Save"" (4th), ""The block wrapper"" (5th) and the package (@wordpress/block-editor, 8th) are not the top results. Actually, ""RichText Reference"" comes before, which seems very unrelated. I've encountered this many times, but did not write down all the examples. I will extend this list of examples. " gaambo Old Tickets 7491 Improved Design of the Dropdown pitamdey General lowest defect (bug) new 2024-02-26T13:25:21Z 2024-03-20T18:29:28Z "Url : https://wordpress.org/about/features/ When we click the drop it does not show active. We can either add an active class or toggle the arrow there. It will make the design looks good" pitamdey Old Tickets 7489 Improve design of Cookies close & accept Popup pitamdey General lowest Improved Search defect (bug) new 2024-02-23T12:20:50Z 2024-03-20T18:29:27Z "URL : https://events.wordpress.org/ We can improve the design of the popup which shows for cookie accept and close. For example, we can add colour to a button and also apply a hover effect on that. Now it is very basic. " pitamdey Old Tickets 7457 Active Menu issue in mobile view harsh175 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 Old Tickets 7446 Improved Search Bar Filter Design in responsive pitamdey General lowest enhancement new 2024-02-07T04:52:48Z 2024-02-22T05:29:38Z "URL : https://wordpress.tv/?s= This is just for an improvement.In Responsive screen size under 768px when we toggle the filter option the icon on it should also toggle like an upward arrow and downward arrow I have attached screenshot for better understanding" pitamdey Old Tickets 7429 In Responsive mobile size the text is overlapping pitamdey General lowest defect (bug) new 2024-02-01T13:19:10Z 2024-02-01T13:19:10Z "URL : https://wordpress.org/support/topic/i-have-a-problem-to-access-to-wp-admin-network-in-wordpress-multisite/#new-post In the Responsive screen (375 px screen size ) the text is overlapping I have attached screenshot of the issue for better understanding " pitamdey Yesterday 7537 "Support Handbook menu says ""Support forums"" but redirects to `/documentation`" dufresnesteven Handbooks normal defect (bug) new 2024-03-28T05:08:48Z 2024-03-28T05:10:05Z Apart from the odd redirect from `/support` to `/documentation` which is addressed in a different tickert, this should link to `/support/forums/` based on the text. dufresnesteven Last Week 7520 Move Handbooks to GitHub to ease ability to contribute content oglekler Handbooks normal feature request new 2024-03-15T06:29:01Z 2024-03-28T08:02:55Z "I didn't find Make Handbooks at GitHub, so, it looks there are no easy way to raise ticket and make PR with proposed changes. Tickets in Trac are much less convenient and transparent. I propose to move all handbooks to GitHub and add at the bottom of each page a link to the source code, with a note that ""if you want to propose change to this page, please, create a PR""." oglekler Old Tickets 7480 Localization changes depending on whether you are logged in or not wildworks International Sites (Rosetta) normal defect (bug) new 2024-02-21T03:26:53Z 2024-02-21T09:04:51Z "On wordpress.org's Japanese site, I noticed that the display of the pages under the `support` directory changes greatly depending on whether the user is logged in or not. Using https://ja.wordpress.org/support/view/all-topics/ as an example, when a user is logged in, the following problem occurs. - Much of the page is not translated - Some links change to wordpress.org instead of ja.wordpress.org - The updated date and time of the forum are displayed as ""sometime ago"" and the correct updated date and time are not displayed. " wildworks Old Tickets 7478 Add option to deactivate glossary on pages benniledl Make (Get Involved) / P2 normal defect (bug) new dev-feedback 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 Old Tickets 7513 "Add ""My favorites"" functionality to the WordPress Photo Directory" nilovelez Photo Directory low feature request new 2024-03-11T13:45:45Z 2024-03-20T18:15:50Z "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 Old Tickets 7426 Add minimum word count for description benniledl Photo Directory normal defect (bug) new has-patch 2024-01-29T12:48:00Z 2024-03-20T01:40:05Z "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 Old Tickets 7440 Category to Planet.WordPress.org not working courane01 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 3 Days Ago 7533 feature request: API for Readme Validation bjorsch Plugin Directory normal feature request new 2024-03-25T16:59:09Z 2024-03-25T16:59:09Z "https://wordpress.org/plugins/developers/readme-validator/ is a useful tool. But when you have multiple people contributing to your plugin, it would be nice for validation of changes to the readme to be done by automated CI instead of having to have people visit that webpage. An API endpoint for validating a readme seems like the best option to achieve that. A wp-cli command or other standalone tool could also work, but since the validation needs to check taxonomies and users on wordpress.org anyway an API would seem to be more straightforward. Thanks!" bjorsch 3 Days Ago 7531 Hook automatic documentation coquardcyr Plugin Directory normal enhancement new 2024-03-25T13:17:32Z 2024-03-28T08:46:36Z "Hey, Currently as a developer the experience about searching hooks on an installed plugin is a pain. First when picking a new plugin on the marketplace nothing indicates to me if the plugin makes use of actions or filters to configure it to my needs. The only way to know is to download the plugin then open it in my IDE and each for each occurrence from the method ''apply_filters'' and ''do_action''. Then once the plugin is installed and I am using a filter or an action, it is not finished if there is an update and I want to make sure the developer from the plugin didn't remove or change the plugin. I need to jump again into the code and make sure hooks weren't touched. My idea to tackle that would be simple. On one hand I think this documentation is important for end users but on another one I don't want to make plugins developers waste a bunch of more time on it. That's why automation seems the good way to me as it will allow developers to be able to provide that in one command in the cli. To reduce the amount of memory that would be used on wordpress.org by that feature I would split it into two parts linked with a file as an interface between them describing hooks. Moreover the choice of a separation between the tools to make an interface which leaves room for other tools in the future as an IDE plugin and it also gives the opportunity for the developer to change the file generated in case there is an issue with the cli command. So for that feature we would have a cli command that generates a file describing the hooks from the plugins and another part about displaying information about hooks on the marketplace from wordpress.org using that file. For that cli part,I already started something here with my custom framework that could be seen as a poc: https://github.com/wp-launchpad/hooks-extractor However, it is based on regex and it seems like it has a lot of flaws so there is still room for improvement. For example, I guess another approach based on a tokenizer would work better. Concerning the generated documentation I got that repository which is not really related to the second part: https://github.com/wp-launchpad/hook-list Nevertheless it generates a small documentation from a yaml file which can be useful to display some information to the end user. The idea for that second part would be to have a list of hooks and their documentation for each plugin when the file is detected. This would also promote the usage from hooks through the community as they are not that much common. Then that file would also be reused inside the changelog to add hooks changes. Finally, it would be nice to have a way to filter on the marketplace between plugins that support that feature and the one who don’t as it will promote that practice even more As you can see there is a lot of room for improvement for that feature and I am not only accepting feedback about if this feature could be something good to the WordPress ecosystem but also suggestions to improve it. " coquardcyr Old Tickets 7505 Make it easier to unsubscribe from trac email notifications about plugins tobifjellner Plugin Directory normal defect (bug) new 2024-03-05T23:57:17Z 2024-03-06T01:33:50Z "Under a plugin's ""Development"" tab (for example: https://wordpress.org/plugins/health-check/#developers ) a logged-in user can accidentally get subscribed to email updates about the plugin from Plugins' Trac. One just needs to click once on ""email"" in the sentence ""...or subscribe to the development log by email or RSS."" and start receiving emails. 1. There should be a clearer indication of the current subscription status in the development page. 2. The emails from Trac should include information about where to unsubscribe. 3. There should be some place where a user could see all their current Trac subscriptions of this type, and perhaps one button to unsubscribe from them all. I'm filing this under ""plugins"", since the main UI for this problem is located there." tobifjellner Old Tickets 7490 Add Wistia shortcodes to be able to add Wistia videos to plugin readme.txt files alekv Plugin Directory lowest feature request new close 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 Old Tickets 7487 Feature to help plugin developers create blueprints for previews tellyworth Plugin Directory normal enhancement new 2024-02-23T05:53:59Z 2024-03-21T16:03:47Z "We should encourage plugin developers to create blueprint files for their plugins, so as to enable the Live Preview button (see #7251). A simple starting point for this would be to create a tool that will automatically generate a blueprint.json file. The plugin developer can then download the json file, make any necessary changes, and commit it to the assets folder (as described in https://make.wordpress.org/meta/2023/11/22/plugin-directory-preview-button-revisited/). Further improvements on this are easy to imagine, but I would propose starting simply and then iterating." tellyworth Old Tickets 7477 Introduce limits for readme field length dd32 Plugin Directory normal defect (bug) new has-patch 2024-02-20T04:13:37Z 2024-03-11T18:13:23Z "**In short: I propose limiting it to 1,500 words per section** ''Reasoning & the data'' While reviewing some search-related tickets I found a plugin that was appearing in results that it arguably shouldn't, and upon inspecting it, found that it was violating [https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/#12-public-facing-pages-on-wordpress-org-readmes-must-not-spam Guideline 12 ""do not spam""]. Upon reflection of this, and looking at data of all plugins, I feel we would be best placed to introduce limits to the readme content length, such as to limit spammy behaviour and reduce the impact it has upon the search results. **I propose limiting it to 1,500 words per section**, similar to how we already limit the `short description` to 150 characters, and assets to certain file-sizes. The choice of 1,500 is such that it means zero change to (literally) 99% of plugins, and 99.8% have less than 3,000 words. The final 0.2% of plugins are those who I would call out for being in blatant violation of the guideline, in one case, the readme is over 260KB amounting to over 26,000 individual words. This is not to say that a plugin with less than 1,500 words is not in violation of the guideline, this is only intended on being an absolute hard-limit. A plugin could violate it with a few hundred words. Once you start to exceed 1,500 however, it becomes increasingly hard to prove that it's for a humans benefit, and not to simply benefit search rankings. To put these numbers into perspective.. - an average book has between 250-300 words per page - an average readable computer print-out has 400-500 words per page, possibly up to 800 if you squeeze it in. - 26k words is between 30 and 80 printed sheets of paper." dd32 Old Tickets 7469 Update plugin list item design in plugin directory. dufresnesteven Plugin Directory normal enhancement new 2024-02-14T06:39:05Z 2024-03-12T05:27:54Z "The ""Card"" layout on the home page and in archives views feels dated and is hard to read. **Reduce the size of the thumbnail** The thumbnail is 128x128 and is overwhelming on first glance. Adding to the fact that many contain animations. The thumbnail is not the most important information on the page. I think display 75x75 is probably a better size. **Don't stack the excerpt on the right** Titles are pretty keyword heavy now and have become an eyesore. We need to do something about that with a more strategic approach. However, for now, the content doesn't need to be stuffed on the right side. We can put it below the thumbnail/image to make the more readable. **Use a more modern tile layout** The grey tile feels outdated. We recently introduced a card-like layout in https://developer.wordpress.org/. Can we just reuse those styles? " dufresnesteven Old Tickets 7465 "Plugins: Add interface for requesting plugin categorization in ""advanced tab""" dufresnesteven Plugin Directory normal enhancement assigned 2024-02-14T03:13:02Z 2024-02-21T19:22:32Z "Plugins in the directory can currently be part of 2 categorizations ""Community"" and ""Commercial"" (For more context: https://make.wordpress.org/plugins/2022/12/16/plugins-themes-categorization/). The plugin categories are displayed prominently in the directory as filters and on the plugin page itself. However, there aren't any instructions for authors to follow to get their plugins categorized other than the initial make post. (I think) Let's add a section to a plugin's advanced tab that either allows them to set their plugins category directly or emails `plugins@wordpress.org` on behalf of the plugin author. " dufresnesteven Old Tickets 7452 Plugins: Find a better way to surface plugin features. dufresnesteven Plugin Directory normal enhancement new 2024-02-08T04:31:58Z 2024-02-08T04:39:31Z "**High-level Problem**: User feedback suggests that the plugin directory doesn't provide a robust enough experience for users searching for plugins. So, we probably have to do two things to improve this: 1. Provide better search results and filtering in the directory (enabling this feature for API consumers as well). 2. Better highlight plugin features and reliability indicators. **Purpose**: Users have identified that they choose plugins based on the following criteria: - Does the plugin have the features they are looking for? - Is the plugin reliable? While we definitely need to address all the things mentioned above, the purpose of this ticket is to explore ways to help users identify which features a plugin supports. **What currently exists?** Users currently have to read the plugin readme to identify the features. There aren't any guidelines on including features in the readme but seasoned plugin authors in general know how to craft user & search friendly readme's and they typically provide an easy to identify list of features. The way the search algorithm works, it promotes the use of this feature list indirectly by matching it to user keyword searches but it's as simple as that. It doesn't know that it's a feature of the plugin. So if a user searches for the word ""map"", it would return plugins that use that word in a totally different context, like mapping authors to posts. I'll admit that example also unpacks a lot of different shortcomings, like bloated readmes, keyword stuffed plugin titles and lack of categorization but I think we can talk about this feature without talking about all those things. **Discussion?** What can we do to highlight features for plugins that we could use to provide better results and display them more prominently to users? **What about plugin previews?** Plugin previews are being worked on in https://meta.trac.wordpress.org/ticket/7251. These previews will provide a way to ""test"" plugin features and see them in action, but that would be used to support ideas we come up with here. (At least in how we are currently thinking about previews). Resources: - Plugin Readme: https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/ " dufresnesteven Old Tickets 7448 Plugins: Consider combining screenshot and banner. dufresnesteven Plugin Directory normal defect (bug) new 2024-02-07T06:51:50Z 2024-02-07T10:03:14Z "In looking through the meta ticket list... I don't see anything related to why we chose a banner for the first visual of the page and a screenshot section below. ( Maybe it's a legacy problem where the banner dimensions are not suitable for a rotatable screenshot preview?) The banner has become important in communicating plugin quality which slants the playing field towards commercially driven plugins and teams who have access to design teams. It's a common paradigm to show the banner with screenshots prominently on the page in the same interaction zone and we should do the same. Smaller plugin developers could focus on creating good, useful screenshots to communicate the value of their plugin as opposed to forcing together a banner image with their limited graphic design skills (speaking for myself). I mean, the counter argument is that they could provide a screenshot as their banner but with the way the experience is configured, that would be unpredictable." dufresnesteven Old Tickets 7499 Show Photo Directory contribution in Activity stream JeffPaul Profiles normal defect (bug) new 2024-02-29T19:58:01Z 2024-03-20T18:29:27Z "Akin to showing a Learn course completion or core commit prop in the activity stream, it would be great to similarly show an accepted Photo Directory contribution in that activity stream. Perhaps something formatted like: {{{#!php
  • ::before

    Contributed a photo Sidewalk sign with the text ""Leadership is the capacity to translate vision to reality"" on wordpress.org/photos

    }}} " JeffPaul Yesterday 7538 Instead Feed page , its showing HTML pranitdugad Support Forums low enhancement new 2024-03-28T06:39:46Z 2024-03-28T07:26:51Z "Whem clicked on Recent Posts or topic as shoen in below video its going On HTMl page. video url - https://drive.google.com/file/d/1kna0_iM8nvKcoxrhH-IqBaCUUYTPeV33/view?usp=sharing page url - https://wordpress.org/support/forum/installation/" pranitdugad 4-7 Days Ago 7529 New Theme Lacks Different Color for Visited Links macmanx Support Forums normal enhancement new 2024-03-23T19:17:19Z 2024-03-28T05:41:27Z "It would be nice if the new theme visually made a distinction between visited and not visited links. I know it sounds a bit old school, but from a moderator's perspective, it's a handy way to be aware of which threads we've already individually triaged. For example, in the no-replies attached screenshots, you can see where I left off as far as threads with no replies are concerned on old-theme, but not new-theme. And, in the all-topics attached screenshots, you can see which topics I still need to triage on old-theme, but not new-theme. A simple a:visited would make a world of difference. :) Thanks!" macmanx Old Tickets 7511 Code Block must be ltr in rtl locale asadiy4n Support Forums normal defect (bug) new 2024-03-09T10:54:05Z 2024-03-20T18:31:05Z "Currently, Code Block are rtl in Persian support forum.\\ But for better experience and readability they must be ltr." asadiy4n Old Tickets 7503 Create new 'Also Viewing' block and deprecate jQuery version adamwood Support Forums normal enhancement new 2024-03-03T22:43:21Z 2024-03-03T22:43:21Z "Based on [PR feedback]https://github.com/WordPress/wordpress.org/pull/201#discussion_r1509617058 Could you create a block for this? maybe with the Interactivity API? (the declarative structure of the interactivity api might not work nicely with the setInterval calls). Rather than checking for $localNavBar to split the behavior, the block theme would use the block version, and the jQuery version could be deprecated. " adamwood Old Tickets 7475 Search Button is not visible in Responsive screen size pitamdey Support Forums normal defect (bug) new 2024-02-19T10:04:09Z 2024-02-19T23:52:36Z "URL: https://wordpress.org/support/guidelines/#user-expectations The Search Button is visible in the desktop size but not visible under 767px screen size in responsive I have attached both screen screenshot for a better understanding" pitamdey Old Tickets 7466 " in breaks layout" takayukister 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 Old Tickets 7455 "Confusing experience when I click ""forums"" in the main site navigation" dufresnesteven 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 Old Tickets 7435 Extend Support & Forum threads content max-width to 1160px to match developer & documentation dufresnesteven Support Forums normal enhancement new 2024-02-02T02:42:17Z 2024-02-08T04:45:54Z "Support thread page content is restricted to `960px` which is based on older browser specs and makes some information hard to read. The time string in the forum table for example. The rest of our documentation and developer-related themes use `1160px` as the default content width. We should do that to the support forums for an immediate upgrade to legibility and would bring a more consistent look and feel. Changes: - Update it for the content. - Update it for the sub-navigation. - I would also like to see us apply the new styles to the sub nav similar to what we have done to the profiles page via https://meta.trac.wordpress.org/ticket/7175. I can open a new ticket for that if necessary. - Reduce the width of the sidebar is it will be longer than necessary." dufresnesteven Old Tickets 7434 Improve Support Forum side bar. dufresnesteven Support Forums normal enhancement new 2024-02-02T02:11:03Z 2024-02-08T04:45:48Z "As a user arriving from the plugin directory looking for support or to evaluate a plugin's support history, I am presented with a confusing and at first glance, redundant set of links in the support forum sidebar on the right. For example, visit any plugin support forum root. (ie: https://wordpress.org/support/plugin/contact-form-7/) Here is a textual representation of the sidebar: **Top Section** Plugin Image Plugin Name Frequently Asked Questions Support Threads Active Topics Unresolved Topics Reviews ... **Bottom Section** Views Topics with no replies Non-support topics Resolved topics Unresolved topics All topics **Observations** **Top Section** - ""Support Threads"" and ""Active Topics"" display a very similar list except ""Active topics"" doesn't show pinned results. Do we need both? **Bottom Section** - As a user seeking help or evaluating the plugin, I don't see how the ""View"" section provides any value. All the links navigate me away from this plugin and drop me in generic forums. **Solution** Don't show the view section when viewing plugins. If we must, only for admins. " dufresnesteven Old Tickets 7433 Consider removing logged in block when viewing support forums. dufresnesteven 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 Last Week 7524 Update Full Site Editing Tag for block themes annezazu Theme Directory normal enhancement new 2024-03-20T19:35:20Z 2024-03-28T03:02:08Z "Following on original efforts to add a block themes tab to the Theme Directory https://meta.trac.wordpress.org/ticket/6330 I'd like to propose we rename the ""full site editing"" tag to something more focused on site editor or site editing. Some ideas to start the convo: - Site Editor - Site Editor Enabled - Site Editor Support This is also in line with the broader community push to not use the ""Full site editing"" term: https://make.wordpress.org/updates/2022/11/04/site-editor-a-more-user-friendly-name/ and I worry folks will have a hard time making the connection to the Site Editor. " annezazu Old Tickets 7492 Button Alignment Issue on Small/Mobile Device devmuhib Theme Directory normal defect (bug) new has-patch 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 Last Week 7521 GitHub PR syncing: Delete trac comment if GitHub comment deleted dd32 Trac normal defect (bug) new 2024-03-20T01:46:28Z 2024-03-20T01:46:28Z "When a comment is made on a GitHub PR that's linked to a WordPress trac ticket, we sync the comment over. We don't currently delete comments from trac when they're removed from GitHub though; this happens due to two scenario's: - We hide the comment on GitHub (Spam, off-topic, etc) - GitHub removes all traces of the user (ie. Account removed due to spam) This causes spammy content from GitHub being live on WordPress.org trac's for longer than it should." dd32 Old Tickets 7508 Add 'sustainability' to the Ticket->focuses dropdown shortcode adamsilverstein Trac normal defect (bug) new has-patch 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 Old Tickets 7501 In Responsive view, preview section taking on half of screen width pranitdugad Trac lowest defect (bug) new 2024-03-01T09:59:39Z 2024-03-06T04:17:58Z In Responsive view, preview section taking on half of screen width which does not looks proper pranitdugad Old Tickets 7484 In ticking Listing Page, Custom query result content layout is not proper pranitdugad Trac lowest defect (bug) new 2024-02-22T03:21:21Z 2024-02-22T03:26:20Z "In ticking Listing Page, Custom query result content layout is not proper which does not look proper in both responsive and desktop devices Url- https://meta.trac.wordpress.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&status=reviewing&groupdesc=1&group=component&order=priority&row=description" pranitdugad Old Tickets 7470 In ticket details pages, Spacing issue between button in responsive view. pranitdugad Trac lowest defect (bug) new 2024-02-15T03:45:32Z 2024-02-15T03:45:32Z "In ticket details pages, Spacing issue between buttons at 375px or less mobile responsive view Page Url-https://meta.trac.wordpress.org/ticket/7454 " pranitdugad Old Tickets 7459 Enabling #enable-experimental-web-platform-features in Chromium breaks custom queries westonruter Trac lowest defect (bug) new 2024-02-09T18:11:29Z 2024-02-12T00:40:16Z "With the `#enable-experimental-web-platform-features` flag enabled in Chromium (both Chrome and Edge), attempting to do create a Custom Query (such as by Summary, Description, or Reporter) results in an error in the console: > Form submission failed, as the ') This was also reported [https://trac.edgewall.org/ticket/13141 upstream] to Trac directly 5 years ago, but closed as a Chrome-specific bug. Nevertheless, it seems this might not be the case as the [https://issues.chromium.org/issues/41450238 Chromium ticket] was closed as wontfix. I was able to fix the problem locally via [https://developer.chrome.com/docs/devtools/overrides Local Overrides] in Chrome DevTools. I modified https://s.w.org/style/trac/common/js/query.js?v=216 by simply supplying the missing ``: {{{ 44c44 < var e = $($.htmlFormat('', name)); }}}" westonruter Old Tickets 7442 GitHub PR images not displayed dd32 Trac normal defect (bug) new 2024-02-06T02:57:19Z 2024-02-15T03:21:07Z "As of a few weeks ago (at least) GitHub images in PRs are no longer being displayed on trac. For example: https://core.trac.wordpress.org/ticket/57600#comment:17 In that example, I've edited the first image listed from proxying via Jetpack Photon to using the image URL directly. This appears to be that the GitHub API is blocking Jetpack Photon from re-publishing the images. For example; https://i0.wp.com/github.com/WordPress/wordpress-develop/assets/519727/33fc163b-7526-4a7c-87c3-57e9214b8033 gives a 403 response. Looking at the Photon source, https://code.trac.wordpress.org/browser/photon/index.php#L294 we can see that the specific 403 presented means the upstream returned a 403 too. '''Why do we proxy images via Photon?''' Photon is in front of GitHub primarily as it doesn't expose CORS headers. Why do we need CORS headers? Well, because we have `` such that the embedded content isn't requested with credentials and doesn't attempt to display any external-url basic authentication prompts. Realistically, we can probably remove the usage of Photon here, by removing the use of `crossorigin=anonymous` for github.com, as we trust github not to present a HTTP Authorization request, and as the content is within an `` element there shouldn't be any possibility of malicious content within a GitHub attachment being able to be access the trac page DOM. I'm not 100% positive on that though. Trac does offer a safe list of URIs that should not get crossorigin=false attributes, we can possibly just add GitHub to that. upstream refs: https://trac.edgewall.org/changeset/15894 + https://trac.edgewall.org/changeset/16025" dd32 Old Tickets 7510 Contextual Search in Translation Consistency Tool Marc4 Translate Site & Plugins normal enhancement new 2024-03-09T08:49:24Z 2024-03-09T08:49:24Z "It would be interesting to extend the capabilities of the Translation Consistency Tool beyond the strict search for a keyword, being able to search for strings containing that word/s. This would allow you to see how that word/s has been translated within a various contexts. Currently, if search for ""lightbox"", the tool will show how the word lightbox has been translated in all cases where the translation string is just ""lightbox"", nothing before or after that word. You could simply allow the use of wildcards ""*"" before and after a keyword or add a new box with the text ""Contextual"", to show a list of strings where that keyword appears." Marc4 Old Tickets 7494 Translation Events akirk Translate Site & Plugins normal defect (bug) new 2024-02-28T11:57:55Z 2024-02-28T11:57:55Z "With [https://make.wordpress.org/polyglots/2024/02/28/translation-events-prototype/ Translation Events], we'll allow users to ""attend"" translation events during which their translation activity is recorded and counted for that event. This means that during and after the event it's visible how many people contributed with translations and reviews, and in which languages. To resolve this ticket, we'll want to ship the [https://github.com/WordPress/wporg-gp-translation-events/ gp-translation-events plugin] on translate.wordpress.org, and to [https://github.com/WordPress/wporg-gp-translation-events/blob/trunk/schema.sql create a table to store the attribution]. " akirk Old Tickets 7473 Some suggestions from the local glossary do not appear Marc4 Translate Site & Plugins normal defect (bug) new has-patch 2024-02-15T19:00:48Z 2024-02-23T10:41:24Z "For the past week or two, I've been noticing that some words from my localization glossary aren't showing up as suggestions in translation strings. In trying to find out why, in the Catalan localization, I've noticed that the glossary words not appearing as suggestions have a ""-"" in the ""Translation"" field (I imagine someone put a hyphen to avoid leaving the field empty). These entries were created in 2022, and until recently, the glossary suggestion appeared correctly, but for the past week or two, the suggestion hasn't been showing up when translating strings. If I create a new glossary entry and put ""-"" in the ""Translation"" field, it works correctly, even with other punctuation marks. The problem lies only with the old entries, and I'm not sure if it's just with ""-"" or also with other signs or symbols. I've tried removing the ""-"" from the ""Translation"" field by editing the entry, but the suggestion still doesn't appear. I've deleted the entry and recreated it, but it still doesn't show up. If I add another word to the original word, the suggestion is created. Could it be that another localization has ""-"" in the ""Translation"" field or another symbol and is experiencing the same issue? Does it make sense to avoid including only symbols? Only empty fields or text? Is it a punctuation problem or a recent change?" Marc4 Old Tickets 7496 In news Details pages, link on email social button goes blank. pranitdugad WordPress.org Site low defect (bug) new 2024-02-29T04:33:03Z 2024-02-29T04:33:03Z "In news Details pages, link on email social button goes blank as shown in video. page url - https://wordpress.org/news/2024/01/wordpress-6-4-3-maintenance-and-security-release/ video url- https://drive.google.com/file/d/1dqfLL7v-lFOTzWVbjNsfpqmNvUMt_La3/view?usp=sharing" pranitdugad Old Tickets 7482 Update WCAG version on Accessibility Page to match version indicated in WordPress Coding Standards alh0319 WordPress.org Site normal defect (bug) new 2024-02-21T04:34:51Z 2024-02-21T19:20:24Z "The Accessibility page at https://wordpress.org/about/accessibility/ says the following: ""WordPress aims to make the WordPress Admin and bundled themes fully WCAG 2.0 AA compliant where possible."" However, the [https://developer.wordpress.org/coding-standards/wordpress-coding-standards/accessibility/ WordPress Coding Standards] actually require code to conform to WCAG **2.1**. I expect this page was missed when the coding standards were last updated. Can someone please correct it to say 2.1 instead of 2.0?" alh0319 Old Tickets 7460 Use Imagick/ImageMagick instead of GD for the photo directory desrosj WordPress.org Site normal defect (bug) new dev-feedback 2024-02-09T18:36:37Z 2024-02-12T01:30:41Z "I noticed recently that a photo I submitted to the directory had less vibrant colors than the version I originally uploaded. I can't say with 100% certainty, but based on the metadata in the generated image files, it seems that w.org is using GD to process images and not `Imagick/ImageMagick`. For example, looking at the metadata for [https://pd.w.org/2024/02/86565be41d811edb2.64704135-rotated.jpeg this image] which is generated from the original, there is a `comment` metadata field with the value of `CREATOR: gd-jpeg v1.0 (using IJG JPEG v62), quality = 82`. The [https://pd.w.org/2024/02/86565be41d811edb2.64704135.jpeg original image] was created using an iPhone and has the `Display P3` color profile. In my testing, Imagick/ImageMagick preserves this profile when generating subsizes, thus preserving the original colors. GD however does not and instead assigns an `sRGB` color profile, causing the image to lose some of it's vibrancy. The iPhone has used the [DCI-P3 Display P3 profile (one that builds off of DCI-P3) since iPhone 7]. So it's highly likely a high percentage of the images in the photo directory are suffering from a loss of color quality when compared to how the contributor submitted them originally. In general, GD is also known for producing images of lesser quality than ImageMagick and having some odd nuances in handling color profiles. Would it be possible to use ImageMagick for the Photo Directory to better preserve the original colors in the submitted photos? And if so, would it be possible to regenerate the images uploaded so far in order to correct any loss of color caused to date due to switching color profiles?" desrosj