From noreply at wordpress.org Wed Dec 1 03:30:43 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 1 Dec 2021 03:30:43 +0000 (UTC) Subject: [wp-meta] [11349] sites/trunk/api.wordpress.org/public_html/events/1.0/index.php: Events API: Validate the request is valid before processing it. Message-ID: <20211201033043.B47461B004A7@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed Dec 1 05:40:03 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 1 Dec 2021 05:40:03 +0000 (UTC) Subject: [wp-meta] [11350] sites/trunk/wordpress.org/public_html/wp-content/plugins/support-forums/inc/class-hooks.php: Support Forums: Check that the topic date was parseable before using the resulting DateTime object, to avoid a PHP Fatal error on topic-less replies. Message-ID: <20211201054003.A3E351B004A7@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed Dec 1 06:14:52 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 01 Dec 2021 06:14:52 -0000 Subject: [wp-meta] [Making WordPress.org] #5970: The list of function name isn't readable properly. Message-ID: <052.ef94eedfe9aba272470c1f2d97f531c7@wordpress.org> #5970: The list of function name isn't readable properly. -------------------------+------------------------------------------------- Reporter: rima1889 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: | Keywords: has-screenshots has-dev-note dev- WordPress.org Site | feedback needs-design -------------------------+------------------------------------------------- I'm finding below issue on [https://developer.wordpress.org/reference/functions/]. 1) The style of function name hide **underscore**(_) because of style of **underline**( text-decoration: underline ). 2) The underline also display out of Functions name. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 1 06:36:43 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 01 Dec 2021 06:36:43 -0000 Subject: [wp-meta] [Making WordPress.org] #5970: The list of function name isn't readable properly. In-Reply-To: <052.ef94eedfe9aba272470c1f2d97f531c7@wordpress.org> References: <052.ef94eedfe9aba272470c1f2d97f531c7@wordpress.org> Message-ID: <067.cc0ddf8414b4ef36f490ffe067306260@wordpress.org> #5970: The list of function name isn't readable properly. -------------------------------------------------+------------------------- Reporter: rima1889 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: WordPress.org Site | Resolution: Keywords: has-dev-note dev-feedback needs- | design-feedback | -------------------------------------------------+------------------------- Changes (by rima1889): * keywords: has-screenshots has-dev-note dev-feedback needs-design => has- dev-note dev-feedback needs-design-feedback -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 1 06:50:03 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 01 Dec 2021 06:50:03 -0000 Subject: [wp-meta] [Making WordPress.org] #5970: The list of function name isn't readable properly. In-Reply-To: <052.ef94eedfe9aba272470c1f2d97f531c7@wordpress.org> References: <052.ef94eedfe9aba272470c1f2d97f531c7@wordpress.org> Message-ID: <067.11e34e58450becaf4a1f1b1d1ce2d0af@wordpress.org> #5970: The list of function name isn't readable properly. -----------------------------------+--------------------- Reporter: rima1889 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Developer Hub | Resolution: Keywords: needs-design-feedback | -----------------------------------+--------------------- Changes (by dd32): * keywords: has-dev-note dev-feedback needs-design-feedback => needs- design-feedback * component: WordPress.org Site => Developer Hub Comment: There's a potential that it's intended not to have underlines here, as there's already a dotted underline set on the :hover. I do actually have a uncommited diff to remove this underline already, but didn't move forward with it myself as it only fixes the function listing, and not all the other locations where function/class names are referenced as links with an underline (For example Return Values, and Related functions on individual function pages) {{{ #!diff Index: scss/main.scss =================================================================== --- scss/main.scss (revision 11348) +++ scss/main.scss (working copy) @@ -1063,8 +1063,12 @@ .arg-default { color: #000000; } - a:hover { - border-bottom: 1px dotted #21759b; + a { + text-decoration: none; + + &:hover { + border-bottom: 1px dotted #21759b; + } } } h2 { }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 1 17:39:13 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 01 Dec 2021 17:39:13 -0000 Subject: [wp-meta] [Making WordPress.org] #5970: The list of function name isn't readable properly. In-Reply-To: <052.ef94eedfe9aba272470c1f2d97f531c7@wordpress.org> References: <052.ef94eedfe9aba272470c1f2d97f531c7@wordpress.org> Message-ID: <067.92b05350d1831826070d1484852d1fc3@wordpress.org> #5970: The list of function name isn't readable properly. -----------------------------------+--------------------- Reporter: rima1889 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Developer Hub | Resolution: Keywords: needs-design-feedback | -----------------------------------+--------------------- Comment (by ryelle): Ideally links should have more than just color to differentiate them from surrounding text, so rather than removing the text-decoration, maybe try [https://developer.mozilla.org/en-US/docs/Web/CSS/text-underline-offset text-underline-offset]? `0.2em` seems like a good distance in playing with it in Inspector. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 1 21:40:37 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 01 Dec 2021 21:40:37 -0000 Subject: [wp-meta] [Making WordPress.org] #5960: Display Cli command in plugins and themes page In-Reply-To: <056.698892bec232182e1c46ccb78675b300@wordpress.org> References: <056.698892bec232182e1c46ccb78675b300@wordpress.org> Message-ID: <071.daed7b19fd695c88ba59e178d92c4eac@wordpress.org> #5960: Display Cli command in plugins and themes page --------------------------------+--------------------- Reporter: vijayhardaha | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: WordPress.org Site | Resolution: Keywords: | --------------------------------+--------------------- Comment (by tellyworth): Where would this appear in the page? How would we deal with local variations in CLI environment? `wp plugin install` vs `wp --url=example.com plugin install` vs `wp-env run "wp plugin install"` etc? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 1 21:41:20 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 01 Dec 2021 21:41:20 -0000 Subject: [wp-meta] [Making WordPress.org] #5960: Display Cli command in plugins and themes page In-Reply-To: <056.698892bec232182e1c46ccb78675b300@wordpress.org> References: <056.698892bec232182e1c46ccb78675b300@wordpress.org> Message-ID: <071.badf4928816e4cf0a27ce94183b1706b@wordpress.org> #5960: Display Cli command in plugins and themes page --------------------------------+--------------------- Reporter: vijayhardaha | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: WordPress.org Site | Resolution: Keywords: needs-design | --------------------------------+--------------------- Changes (by tellyworth): * keywords: => needs-design -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 1 22:48:34 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 1 Dec 2021 22:48:34 +0000 (UTC) Subject: [wp-meta] [11351] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-patterns: Pattern Directory: Sync with git WordPress/pattern-directory@6396ab0b4eb9f50e1f192097c94a064e90ab1805 Message-ID: <20211201224834.B65491B003D6@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed Dec 1 22:52:21 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 01 Dec 2021 22:52:21 -0000 Subject: [wp-meta] [Making WordPress.org] #5971: Plugin Directory: Custom Block Names not being listed right Message-ID: <051.5f0920c7082dd400163332aa9ca4044a@wordpress.org> #5971: Plugin Directory: Custom Block Names not being listed right ------------------------------+-------------------- Reporter: Ipstenu | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Keywords: ------------------------------+-------------------- This was reported by a plugin owner. In some cases, the plugin front-end page fails to show proper names of included blocks and instead just duplicates the plugin name. Examples: * https://wordpress.org/plugins/social-polls-by-opinionstage/ * https://wordpress.org/plugins/archivespress/ * https://wordpress.org/plugins/oer-curriculum/ In these cases, developers are not using blocks.json (for a number of valid reasons). Should there be a better fallback check here? Or should we just not list the blocks by name if we cannot find the name? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 1 23:12:17 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 01 Dec 2021 23:12:17 -0000 Subject: [wp-meta] [Making WordPress.org] #5960: Display Cli command in plugins and themes page In-Reply-To: <056.698892bec232182e1c46ccb78675b300@wordpress.org> References: <056.698892bec232182e1c46ccb78675b300@wordpress.org> Message-ID: <071.e07de58137040bcaae7af4e0cb300558@wordpress.org> #5960: Display Cli command in plugins and themes page --------------------------------+--------------------- Reporter: vijayhardaha | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: WordPress.org Site | Resolution: Keywords: needs-design | --------------------------------+--------------------- Changes (by vijayhardaha): * Attachment "Screenshot 2021-12-02 at 4.33.40 AM.png" added. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 1 23:24:51 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 01 Dec 2021 23:24:51 -0000 Subject: [wp-meta] [Making WordPress.org] #5960: Display Cli command in plugins and themes page In-Reply-To: <056.698892bec232182e1c46ccb78675b300@wordpress.org> References: <056.698892bec232182e1c46ccb78675b300@wordpress.org> Message-ID: <071.ea285021722a418714d371f0078edd16@wordpress.org> #5960: Display Cli command in plugins and themes page --------------------------------+--------------------- Reporter: vijayhardaha | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: WordPress.org Site | Resolution: Keywords: needs-design | --------------------------------+--------------------- Comment (by vijayhardaha): I was hoping to do something like the above attachment, it doesn't need to be the exact same. but the original need is to get plugin/theme slug quickly from the theme/plugin page. For example: on [Classic Widgets](https://wordpress.org/plugins/classic- widgets/) plugin page if I search for keyword `classic-widgets` I found 0 results. I cannot find the plugin/theme slug on the page in order to quickly install it via cli. That's why I am thinking if we can have a section either with `wp plugin install {{slug}}` or we can just have `{{slug}}` only somewhere on-page that can be easily copied either with a simple copy button or with selecting the text and copying it with normal copy method from any device. At the current time, If I have to get the theme/plugin slug I have to copy it from the URL which is not a good user experience from my personal point of view. Let me know if this information helps. Thanks -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 1 23:26:20 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 01 Dec 2021 23:26:20 -0000 Subject: [wp-meta] [Making WordPress.org] #5971: Plugin Directory: Custom Block Names not being listed right In-Reply-To: <051.5f0920c7082dd400163332aa9ca4044a@wordpress.org> References: <051.5f0920c7082dd400163332aa9ca4044a@wordpress.org> Message-ID: <066.11b2abef7867ef90e303d434c84ddab8@wordpress.org> #5971: Plugin Directory: Custom Block Names not being listed right ------------------------------+--------------------- Reporter: Ipstenu | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+--------------------- Comment (by ryelle): The `block.json` is the easiest way to get this info (since it's already in a format we can parse and get the value from directly). The next best way to get block titles is from the JS `registerBlockType` call (which is working for OER Curriculum's "Curriculum Thumbnail Block" block), but this is done with a regex, so it expects very specific formatting - the `title` must be the first value in the config object, with no comments/etc before it. The script also checks PHP files for `register_block_type`, but it doesn't even try to find a title. ([https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html /wp-content/plugins/plugin-directory/cli/class-import.php#L747 code source for finding blocks.]) Aside from improving that JS regex, what would be a better fallback? Maybe human-ify the block name, so it would go from `ryelle/recipe` to "Ryelle Recipe", `opinion-stage/block-os-poll` to "Opinion Stage Block Os Poll"? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 2 00:59:04 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 2 Dec 2021 00:59:04 +0000 (UTC) Subject: [wp-meta] [11352] sites/trunk/wordpress.org/public_html/wp-content: WordPress.org Learn: sync with GitHub Message-ID: <20211202005904.C9C291B0049F@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Thu Dec 2 01:02:41 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 02 Dec 2021 01:02:41 -0000 Subject: [wp-meta] [Making WordPress.org] #5970: The list of function name isn't readable properly. In-Reply-To: <052.ef94eedfe9aba272470c1f2d97f531c7@wordpress.org> References: <052.ef94eedfe9aba272470c1f2d97f531c7@wordpress.org> Message-ID: <067.1c3af54380813035fdc5a501b2a49450@wordpress.org> #5970: The list of function name isn't readable properly. -----------------------------------+--------------------- Reporter: rima1889 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Developer Hub | Resolution: Keywords: needs-design-feedback | -----------------------------------+--------------------- Comment (by dd32): Replying to [comment:3 ryelle]: > Ideally links should have more than just color to differentiate them from surrounding text Totally agreed. > maybe try [https://developer.mozilla.org/en-US/docs/Web/CSS/text- underline-offset text-underline-offset]? I didn't even know that was a thing :) That sounds like a perfect solution to me. Perhaps we could use something like `a.underscores { text-underline- offset: 0.2em; }` and apply that class where needed instead of trying to target things purely in CSS? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 2 01:08:36 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 02 Dec 2021 01:08:36 -0000 Subject: [wp-meta] [Making WordPress.org] #5971: Plugin Directory: Custom Block Names not being listed right In-Reply-To: <051.5f0920c7082dd400163332aa9ca4044a@wordpress.org> References: <051.5f0920c7082dd400163332aa9ca4044a@wordpress.org> Message-ID: <066.0712a53d4c99dc7e7ad0136f719586b2@wordpress.org> #5971: Plugin Directory: Custom Block Names not being listed right ------------------------------+--------------------- Reporter: Ipstenu | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+--------------------- Comment (by dd32): Replying to [comment:1 ryelle]: > The script also checks PHP files for `register_block_type`, but it doesn't even try to find a title. At the time of it being written, I'm almost certain that it didn't support the `title` arg, I recall that being a fairly annoying part of listing blocks as it was a situation of "Well, we know the block slug, but can't tell you what you'll see it as inside the editor". It's an even worse situation now though, as it accepts a `WP_Block_Type` object too, which we also can't parse out of it easily without running the plugin.. Unless we can do something like a regex similar to `WP_Block_Type\(.+slug=().+title=()` -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 2 02:42:02 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 2 Dec 2021 02:42:02 +0000 (UTC) Subject: [wp-meta] [11353] sites/trunk/api.wordpress.org/public_html/events/1.0/index.php: Events: pin SotW 2021. Message-ID: <20211202024202.9BAA41B0054B@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Thu Dec 2 07:52:06 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 02 Dec 2021 07:52:06 -0000 Subject: [wp-meta] [Making WordPress.org] #5971: Plugin Directory: Custom Block Names not being listed right In-Reply-To: <051.5f0920c7082dd400163332aa9ca4044a@wordpress.org> References: <051.5f0920c7082dd400163332aa9ca4044a@wordpress.org> Message-ID: <066.595e816bb66bf196b654915857a4591d@wordpress.org> #5971: Plugin Directory: Custom Block Names not being listed right ------------------------------+--------------------- Reporter: Ipstenu | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+--------------------- Comment (by GDragoN): My plugin ArchivesPress doesn't use block.json file because I need ServerSideRender and that can't be setup via block.json. What would happen if I just include block.json file for each block my plugin has, just include it, without loading it and using it anywhere in the code? Will the WordPress.org parse it, and will it throw some red flags because it is not used or something? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 2 11:44:02 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 02 Dec 2021 11:44:02 -0000 Subject: [wp-meta] [Making WordPress.org] #5971: Plugin Directory: Custom Block Names not being listed right In-Reply-To: <051.5f0920c7082dd400163332aa9ca4044a@wordpress.org> References: <051.5f0920c7082dd400163332aa9ca4044a@wordpress.org> Message-ID: <066.1fc82542c902f6ca8a9a607209f4894a@wordpress.org> #5971: Plugin Directory: Custom Block Names not being listed right ------------------------------+--------------------- Reporter: Ipstenu | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+--------------------- Comment (by Dudo): Same [https://wordpress.org/plugins/yet-another-stars-rating/ here] I'm not using (yet) block.json, and also I've two deprecated blocks that instead are using registerBlockType in JS and those two are working fine. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 2 12:21:35 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 02 Dec 2021 12:21:35 -0000 Subject: [wp-meta] [Making WordPress.org] #5081: Delete project's language pack when below specific percentage In-Reply-To: <064.245dfa84c5efeb46173106f976f93f14@wordpress.org> References: <064.245dfa84c5efeb46173106f976f93f14@wordpress.org> Message-ID: <079.1640a81fec81144c4cfff179e01f229a@wordpress.org> #5081: Delete project's language pack when below specific percentage --------------------------------------+---------------------- Reporter: felipeloureirosantos | Owner: (none) Type: enhancement | Status: closed Priority: normal | Milestone: Component: Translate Site & Plugins | Resolution: wontfix Keywords: | --------------------------------------+---------------------- Comment (by beqstjournals): WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. Features include a plugin architecture and a template system, referred to within WordPress as Themes. https://wskonnekt.com/ https://customuniversitypapers.com https://smartacademicwriting.com https://canadaenergysolution.ca/ WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. Features include a plugin architecture and a template system, referred to within WordPress as Themes. https://www.lieferreparatur.ch/ https://scoutmine.com/ http://ukbusinessideas.co.uk/ WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. Features include a plugin architecture and a template system, referred to within WordPress as Themes. https://www.timesofsports.com/ https://www.ukbusinessblog.co.uk/ https://www.thebusinessview.co.uk/ WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. Features include a plugin architecture and a template system, referred to within WordPress as Themes. https://www.tycoonstory.com/ https://matkinhnamquang.com/ https://gongkinhdep.com/ http://www.spotoninterpreting.com/ WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. Features include a plugin architecture and a template system, referred to within WordPress as Themes. https://www.tycoonstory.com/ http://plasticrypt.com/ WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. Features include a plugin architecture and a template system, referred to within WordPress as Themes. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 2 15:34:05 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 02 Dec 2021 15:34:05 -0000 Subject: [wp-meta] [Making WordPress.org] #5971: Plugin Directory: Custom Block Names not being listed right In-Reply-To: <051.5f0920c7082dd400163332aa9ca4044a@wordpress.org> References: <051.5f0920c7082dd400163332aa9ca4044a@wordpress.org> Message-ID: <066.677efd75bc0cfc8d0d574d8968351391@wordpress.org> #5971: Plugin Directory: Custom Block Names not being listed right ------------------------------+--------------------- Reporter: Ipstenu | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+--------------------- Comment (by ryelle): > What would happen if I just include block.json file for each block my plugin has, just include it, without loading it and using it anywhere in the code? That would work - if you don't [https://developer.wordpress.org/block- editor/reference-guides/block-api/block-metadata/#php-server-side load it in your plugin], it won't be read by WordPress. The Plugin Directory will read it to parse out the blocks, providing the title. In fact, if you wanted to just use block.json for the plugin directory, you only need to add the `name` and `title` fields. > I'm not using (yet) block.json, and also I've two deprecated blocks that instead are using registerBlockType in JS and those two are working fine. Yeah, the two deprecated blocks are registered with their titles in `registerBlockType`, but the rest of your blocks only define `edit` and `save` in the JS. If you added the title here too, it should pick it up– or use block.json. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 2 15:40:20 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 02 Dec 2021 15:40:20 -0000 Subject: [wp-meta] [Making WordPress.org] #5971: Plugin Directory: Custom Block Names not being listed right In-Reply-To: <051.5f0920c7082dd400163332aa9ca4044a@wordpress.org> References: <051.5f0920c7082dd400163332aa9ca4044a@wordpress.org> Message-ID: <066.c1ffa235800b240ead4d8f50867e719a@wordpress.org> #5971: Plugin Directory: Custom Block Names not being listed right ------------------------------+--------------------- Reporter: Ipstenu | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+--------------------- Comment (by Dudo): > Yeah, the two deprecated blocks are registered with their titles in registerBlockType, but the rest of your blocks only define edit and save in the JS. If you added the title here too, it should pick it up– or use block.json. Thanks for answer, I did already tried this, but it didn't work. You can see the commit [https://plugins.trac.wordpress.org/changeset/2628514/yet-another-stars- rating/trunk/admin/js/src/guten/blocks/overallRating.js?old=2584311&old_path =yet-another-stars- rating%2Ftrunk%2Fadmin%2Fjs%2Fsrc%2Fguten%2Fblocks%2FoverallRating.js here] -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 2 22:18:38 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 02 Dec 2021 22:18:38 -0000 Subject: [wp-meta] [Making WordPress.org] #5970: The list of function name isn't readable properly. In-Reply-To: <052.ef94eedfe9aba272470c1f2d97f531c7@wordpress.org> References: <052.ef94eedfe9aba272470c1f2d97f531c7@wordpress.org> Message-ID: <067.68a5c9cb5a7d6f9e5c842569d1fa00ed@wordpress.org> #5970: The list of function name isn't readable properly. -----------------------------------+--------------------- Reporter: rima1889 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Developer Hub | Resolution: Keywords: needs-design-feedback | -----------------------------------+--------------------- Comment (by ryelle): I think the `0.2em` offset is small enough that it would be fine to drop onto `.devhub-wrap .site-main a` for all devhub links, but a `has- underscores` class could be useful elsewhere (or `underscores`, IDK if we have a naming standard either way). -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 2 23:44:21 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 02 Dec 2021 23:44:21 -0000 Subject: [wp-meta] [Making WordPress.org] #5971: Plugin Directory: Custom Block Names not being listed right In-Reply-To: <051.5f0920c7082dd400163332aa9ca4044a@wordpress.org> References: <051.5f0920c7082dd400163332aa9ca4044a@wordpress.org> Message-ID: <066.0c35d41bdf57934a5f569f610c319676@wordpress.org> #5971: Plugin Directory: Custom Block Names not being listed right ------------------------------+--------------------- Reporter: Ipstenu | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+--------------------- Comment (by dd32): Replying to [comment:6 Dudo]: > > Yeah, the two deprecated blocks are registered with their titles in registerBlockType, but the rest of your blocks only define edit and save in the JS. If you added the title here too, it should pick it up– or use block.json. > > Thanks for answer, I did already tried this, but it didn't work. > You can see the commit [https://plugins.trac.wordpress.org/changeset/2628514/yet-another-stars- rating/trunk/admin/js/src/guten/blocks/overallRating.js?old=2584311&old_path =yet-another-stars- rating%2Ftrunk%2Fadmin%2Fjs%2Fsrc%2Fguten%2Fblocks%2FoverallRating.js here] It doesn't look like that's in your released version of the plugin, so it won't be being parsed at present. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 3 08:32:17 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 03 Dec 2021 08:32:17 -0000 Subject: [wp-meta] [Making WordPress.org] #5971: Plugin Directory: Custom Block Names not being listed right In-Reply-To: <051.5f0920c7082dd400163332aa9ca4044a@wordpress.org> References: <051.5f0920c7082dd400163332aa9ca4044a@wordpress.org> Message-ID: <066.c67495188463b1e731a86e269dfc67d4@wordpress.org> #5971: Plugin Directory: Custom Block Names not being listed right ------------------------------+--------------------- Reporter: Ipstenu | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+--------------------- Comment (by Dudo): > It doesn't look like that's in your released version of the plugin, so it won't be being parsed at present. Since it didn't work, I've [https://plugins.trac.wordpress.org/changeset/2633580/yet-another-stars- rating/trunk/admin/js/src/guten/blocks/overallRating.js?old=2628514&old_path =yet-another-stars- rating%2Ftrunk%2Fadmin%2Fjs%2Fsrc%2Fguten%2Fblocks%2FoverallRating.js removed it 2 weeks later]. I can insert it again, if you wish. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 3 09:42:55 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 03 Dec 2021 09:42:55 -0000 Subject: [wp-meta] [Making WordPress.org] #5779: theme.json strings not extracted for translation In-Reply-To: <053.56bce54a48952446173feb8f0d5cb070@wordpress.org> References: <053.56bce54a48952446173feb8f0d5cb070@wordpress.org> Message-ID: <068.bbbefc482e4ccec6454709a36559bb9b@wordpress.org> #5779: theme.json strings not extracted for translation --------------------------------------+------------------------- Reporter: oandregal | Owner: (none) Type: task | Status: closed Priority: normal | Milestone: Component: Translate Site & Plugins | Resolution: worksforme Keywords: | --------------------------------------+------------------------- Changes (by oandregal): * status: reopened => closed * resolution: => worksforme Comment: The internationalization process is working as expected, so I'm going to close it (not sure why I can't mark this as "fixed" so I'm marking it as "worksforme"). I've been looking at this with the help of @akirk and this is what happens: - How to search for strings coming from "theme.json": - term: "theme.json" - term scope: "any" - status: "Current/waiting/fuzzy + untranslated (All)". This is important. I've used "any" in some searches, which doesn't show you the strings for which there's no translation (so I wasn't getting results when there were some). This explains the weird results I got for Gutenberg. Doing that search I can confirm Gutenberg and other themes with theme.json I've checked work as expected, such as BlockBase and Mayland (blocks). Now, there's a different issue with a few themes that also have theme.json: their latest submission happened ''before'' the i18n process was set up to extract strings coming from theme.json. Hence, they don't have any strings coming from that source. This is the case of TT1-blocks and Armando, for example. As soon as they publish an update to the repo, the strings should come up. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 3 10:54:45 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 03 Dec 2021 10:54:45 -0000 Subject: [wp-meta] [Making WordPress.org] #5972: Enhancement:Add a dropdown to sort contributors within the plugin/theme project or change the sort to translation date Message-ID: <054.fb605c8b7ce5a10c00c0048a2b606847@wordpress.org> #5972: Enhancement:Add a dropdown to sort contributors within the plugin/theme project or change the sort to translation date --------------------------------------+-------------------- Reporter: psmits1567 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Translate Site & Plugins | Keywords: --------------------------------------+-------------------- Currently if you go into a project, the "Translation Contributer" are sorted by quantity of submitted strings. That is not practical, if you want to now who did the recent suggestions. Sometimes you have a long list of contributors where the one with the most translations is on top, but that can be 6 or more years ago. So I propose to either show the contributors on submit date, or add a dropdown so you can choose in which sequence they are shown. It is not of interest for reviewers to know who did the most translations. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 3 11:00:04 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 03 Dec 2021 11:00:04 -0000 Subject: [wp-meta] [Making WordPress.org] #5972: Enhancement:Add a dropdown to sort contributors within the plugin/theme project or change the sort to translation date In-Reply-To: <054.fb605c8b7ce5a10c00c0048a2b606847@wordpress.org> References: <054.fb605c8b7ce5a10c00c0048a2b606847@wordpress.org> Message-ID: <069.1e0e772a4c220ac62107d9b512c9c24f@wordpress.org> #5972: Enhancement:Add a dropdown to sort contributors within the plugin/theme project or change the sort to translation date --------------------------------------+--------------------- Reporter: psmits1567 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Translate Site & Plugins | Resolution: Keywords: | --------------------------------------+--------------------- Comment (by tobifjellner): I'd say it's often useful to immediately see who contributed the most strings. (They are typically good candidates to get promoted as PTE...) But a dropdown where I (in addition) could select to sort contributors in Alphabetical order. by latest contribution, or by most pending strings – would be nice. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 3 17:52:31 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 03 Dec 2021 17:52:31 -0000 Subject: [wp-meta] [Making WordPress.org] #1616: Remote CSS: Allow data URIs in CSS properties In-Reply-To: <050.1cfc506c9956e92fa2f2797d1e02b377@wordpress.org> References: <050.1cfc506c9956e92fa2f2797d1e02b377@wordpress.org> Message-ID: <065.9e7af33bdfd8bd5f6ea7fb7ffffdbfa1@wordpress.org> #1616: Remote CSS: Allow data URIs in CSS properties -------------------------------------+------------------------- Reporter: ryelle | Owner: (none) Type: defect | Status: closed Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: maybelater Keywords: has-patch | -------------------------------------+------------------------- Comment (by hermingonal): https://aeFoodreviewbloggerblogao.blogspot.com https://aethenewbiebloggerao.blogspot.com https://aonlineindianbloggershubao.blogspot.com https://aonlineeamericansupperbloggerao.blogspot.com https://aonlineeperfectaustralianbloggerao.blogspot.com https://abestthemostwantedbloggernowao.blogspot.com https://aehowyoudothatbloggersao.blogspot.com https://awhywearebestbloggernowao.blogspot.com https://abestetmedownslowlyao.blogspot.com https://aeRedditRefrencesbloggerao.blogspot.com https://aedigitalTeamworkbloggerao.blogspot.com https://aetheseoandwriteragencyao.blogspot.com https://aqTheclientproblemsolverao.blogspot.com https://aatheworldnewblogger.wordpressa.com https://asthewonderofworldbloggersao.blogspot.com https://astheestatementbloggerao.blogspot.com https://oanlinemobilesandgamesblogao.blogspot.com -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 3 21:27:30 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 03 Dec 2021 21:27:30 -0000 Subject: [wp-meta] [Making WordPress.org] #5973: Table of Contents contains too much Message-ID: <052.9096c201ce23b39ef09221a33d8110b6@wordpress.org> #5973: Table of Contents contains too much ---------------------------+----------------------------- Reporter: joyously | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Developer Hub | Keywords: has-screenshots ---------------------------+----------------------------- Looking at a Code Reference page for a function, like https://developer.wordpress.org/reference/functions/get_extended/ the table of Contents in the sidebar has a link to "Logged in as x. Log out?" and more text from the instructions about leaving feedback, which are not links, and don't belong there. It looks like the plugin looking at more than `the_content`. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 3 21:28:28 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 03 Dec 2021 21:28:28 -0000 Subject: [wp-meta] [Making WordPress.org] #5973: Table of Contents contains too much In-Reply-To: <052.9096c201ce23b39ef09221a33d8110b6@wordpress.org> References: <052.9096c201ce23b39ef09221a33d8110b6@wordpress.org> Message-ID: <067.c5e66b1c3fbfc716c03026f060d2a7d5@wordpress.org> #5973: Table of Contents contains too much -----------------------------+--------------------- Reporter: joyously | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Developer Hub | Resolution: Keywords: has-screenshots | -----------------------------+--------------------- Changes (by joyously): * Attachment "get_extended() Function WordPress Developer Resources-27.jpg" added. the extra stuff is in the sidebar at the bottom of CONTENTS -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 3 21:32:27 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 03 Dec 2021 21:32:27 -0000 Subject: [wp-meta] [Making WordPress.org] #5973: Table of Contents contains too much In-Reply-To: <052.9096c201ce23b39ef09221a33d8110b6@wordpress.org> References: <052.9096c201ce23b39ef09221a33d8110b6@wordpress.org> Message-ID: <067.8abc4baf0a0afd7bc86086fe894c957b@wordpress.org> #5973: Table of Contents contains too much -----------------------------+--------------------- Reporter: joyously | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Developer Hub | Resolution: Keywords: has-screenshots | -----------------------------+--------------------- Comment (by joyously): I just noticed that there are two sections at the bottom that are almost the same, for adding feedback. That extra might be where the ToC plugin is getting it from. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sat Dec 4 06:01:55 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 04 Dec 2021 06:01:55 -0000 Subject: [wp-meta] [Making WordPress.org] #2976: Create infographics to onboard new translation contributors In-Reply-To: <055.9618e654ac37f93d39786adfc4844b8d@wordpress.org> References: <055.9618e654ac37f93d39786adfc4844b8d@wordpress.org> Message-ID: <070.0c92d1fb70b558edc5b4f13df87f4dcd@wordpress.org> #2976: Create infographics to onboard new translation contributors ----------------------------------+------------------------- Reporter: CoachBirgit | Owner: (none) Type: task | Status: closed Priority: normal | Milestone: Component: wptranslationday.org | Resolution: worksforme Keywords: | ----------------------------------+------------------------- Comment (by wedding156): can we get this link from here? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sat Dec 4 06:02:31 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 04 Dec 2021 06:02:31 -0000 Subject: [wp-meta] [Making WordPress.org] #3474: Introduce `serve-happy` API endpoint In-Reply-To: <052.20d8b1b04484728a35d823b5061f62e7@wordpress.org> References: <052.20d8b1b04484728a35d823b5061f62e7@wordpress.org> Message-ID: <067.16f9fbd484edaa738bf490a90fe74840@wordpress.org> #3474: Introduce `serve-happy` API endpoint --------------------------------------+--------------------- Reporter: flixos90 | Owner: dd32 Type: task | Status: closed Priority: normal | Milestone: Component: API | Resolution: fixed Keywords: has-patch has-unit-tests | --------------------------------------+--------------------- Comment (by wedding156): can we get this link from here? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sat Dec 4 06:02:55 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 04 Dec 2021 06:02:55 -0000 Subject: [wp-meta] [Making WordPress.org] #2654: Improve Screenshot Slider Accessibility In-Reply-To: <057.3b8a418b9b1c0900ba95615fcec6f1a7@wordpress.org> References: <057.3b8a418b9b1c0900ba95615fcec6f1a7@wordpress.org> Message-ID: <072.6dfbe01b8d38d21fb2ed8daac8a1e8ac@wordpress.org> #2654: Improve Screenshot Slider Accessibility ------------------------------+------------------------- Reporter: kevinwhoffman | Owner: (none) Type: defect | Status: closed Priority: highest omg bbq | Milestone: Component: Plugin Directory | Resolution: maybelater Keywords: a11y-feedback | ------------------------------+------------------------- Changes (by wedding156): * priority: normal => highest omg bbq Comment: can we get this link from here? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sat Dec 4 11:28:45 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 04 Dec 2021 11:28:45 -0000 Subject: [wp-meta] [Making WordPress.org] #2654: Improve Screenshot Slider Accessibility In-Reply-To: <057.3b8a418b9b1c0900ba95615fcec6f1a7@wordpress.org> References: <057.3b8a418b9b1c0900ba95615fcec6f1a7@wordpress.org> Message-ID: <072.b31cdcde4020c9887000a91c92f6ac6d@wordpress.org> #2654: Improve Screenshot Slider Accessibility ------------------------------+------------------------- Reporter: kevinwhoffman | Owner: (none) Type: defect | Status: closed Priority: highest omg bbq | Milestone: Component: Plugin Directory | Resolution: maybelater Keywords: a11y-feedback | ------------------------------+------------------------- Comment (by wedding156): https://oanlinemobilesandgamesblogao.blogspot.com. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sun Dec 5 13:19:42 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Sun, 05 Dec 2021 13:19:42 -0000 Subject: [wp-meta] [Making WordPress.org] #2976: Create infographics to onboard new translation contributors In-Reply-To: <055.9618e654ac37f93d39786adfc4844b8d@wordpress.org> References: <055.9618e654ac37f93d39786adfc4844b8d@wordpress.org> Message-ID: <070.2d214675d201e08777c0e3095bcdde0a@wordpress.org> #2976: Create infographics to onboard new translation contributors ----------------------------------+------------------------- Reporter: CoachBirgit | Owner: (none) Type: task | Status: closed Priority: normal | Milestone: Component: wptranslationday.org | Resolution: worksforme Keywords: | ----------------------------------+------------------------- Comment (by magicboy156): https://aeFoodreviewbloggerblogao.blogspot.com -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 6 03:21:28 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 6 Dec 2021 03:21:28 +0000 (UTC) Subject: [wp-meta] [11354] sites/trunk/wordpress.org/public_html/wp-content/plugins/handbook/inc/table-of-contents.php: Handbooks, ToC: Be less greedy when matching headings within the content. Message-ID: <20211206032128.DB1F21B00488@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon Dec 6 03:21:34 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 06 Dec 2021 03:21:34 -0000 Subject: [wp-meta] [Making WordPress.org] #5963: ToC plugin doesn't support Gutenberg In-Reply-To: <048.f163c8caa2dac9d484ef3c85cec461a2@wordpress.org> References: <048.f163c8caa2dac9d484ef3c85cec461a2@wordpress.org> Message-ID: <063.143358bc33fd4b2c37c04eca2bd39e65@wordpress.org> #5963: ToC plugin doesn't support Gutenberg -----------------------+--------------------- Reporter: dd32 | Owner: dd32 Type: defect | Status: closed Priority: normal | Milestone: Component: Handbooks | Resolution: fixed Keywords: | -----------------------+--------------------- Comment (by dd32): In [changeset:"11354" 11354]: {{{ #!CommitTicketReference repository="" revision="11354" Handbooks, ToC: Be less greedy when matching headings within the content. [11341] didn't change the greedyness, but as it was now matching headings with attributes, it was matching too much on reference pages. Additionally, we now don't use style-only headings (those without text) as valid sections. See #5963. Fixes #5973. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 6 03:21:34 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 06 Dec 2021 03:21:34 -0000 Subject: [wp-meta] [Making WordPress.org] #5973: Table of Contents contains too much In-Reply-To: <052.9096c201ce23b39ef09221a33d8110b6@wordpress.org> References: <052.9096c201ce23b39ef09221a33d8110b6@wordpress.org> Message-ID: <067.39991cae13c2f79292e59e915a882a64@wordpress.org> #5973: Table of Contents contains too much -----------------------------+--------------------- Reporter: joyously | Owner: dd32 Type: defect | Status: closed Priority: normal | Milestone: Component: Developer Hub | Resolution: fixed Keywords: has-screenshots | -----------------------------+--------------------- Changes (by dd32): * owner: (none) => dd32 * status: new => closed * resolution: => fixed Comment: In [changeset:"11354" 11354]: {{{ #!CommitTicketReference repository="" revision="11354" Handbooks, ToC: Be less greedy when matching headings within the content. [11341] didn't change the greedyness, but as it was now matching headings with attributes, it was matching too much on reference pages. Additionally, we now don't use style-only headings (those without text) as valid sections. See #5963. Fixes #5973. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 6 04:04:20 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 6 Dec 2021 04:04:20 +0000 (UTC) Subject: [wp-meta] [11355] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-plugins/template-parts/section-blocks.php: Plugin Directory: Blocks: Support the object notation for block icons, which adds support for background/foreground colours. Message-ID: <20211206040420.2534F1B00488@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon Dec 6 05:56:05 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 6 Dec 2021 05:56:05 +0000 (UTC) Subject: [wp-meta] [11356] sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-learn/inc/locale.php: WordPress.org Learn: sync with GitHub Message-ID: <20211206055605.B59A31B00587@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon Dec 6 16:07:08 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 6 Dec 2021 16:07:08 +0000 (UTC) Subject: [wp-meta] [11357] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-patterns/package.json: Pattern Directory: Sync with git WordPress/pattern-directory@da2251ece4a3017fae5c0cf5ecc59ecbcec012b5 Message-ID: <20211206160708.4CA681B003BE@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon Dec 6 17:58:18 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 06 Dec 2021 17:58:18 -0000 Subject: [wp-meta] [Making WordPress.org] #5974: Add linode to list of trademarks Message-ID: <059.6ede5fada2cb49359be16ef2a6960669@wordpress.org> #5974: Add linode to list of trademarks -----------------------------+---------------------- Reporter: jtremblaylinode | Owner: Ipstenu Type: task | Status: assigned Priority: normal | Milestone: Component: General | Keywords: -----------------------------+---------------------- We'd like to request the addition of `linode-` to the list of trademarked terms that cannot be used as prefixes for plugin slugs in the WordPress plugin repository. As I understand it, that list is maintained here: https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html /wp-content/plugins/plugin-directory/shortcodes/class-upload- handler.php#L438 I'm not sure if there are any requirements for which companies/trademarks get added to that list. Let me know if you need further information. We appreciate your consideration. Thanks! -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 6 18:04:09 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 06 Dec 2021 18:04:09 -0000 Subject: [wp-meta] [Making WordPress.org] #5974: Add linode to list of trademarks In-Reply-To: <059.6ede5fada2cb49359be16ef2a6960669@wordpress.org> References: <059.6ede5fada2cb49359be16ef2a6960669@wordpress.org> Message-ID: <074.9b0be4a56d62c7b49680b5ea29ab9c85@wordpress.org> #5974: Add linode to list of trademarks -----------------------------+------------------------- Reporter: jtremblaylinode | Owner: Ipstenu Type: task | Status: closed Priority: normal | Milestone: Component: General | Resolution: maybelater Keywords: | -----------------------------+------------------------- Changes (by Ipstenu): * status: assigned => closed * resolution: => maybelater Comment: Can you please email `plugins at wordpress.org` to discuss this? If it's determined this is the best course of action, we will reopen this ticket, but in general, we're only doing this IF things are being abused, or we have reason to believe they will be. The proper method would be to talk to us first :) -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 7 00:16:34 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 7 Dec 2021 00:16:34 +0000 (UTC) Subject: [wp-meta] [11358] sites/trunk/common/includes/slack/announce/config.php: Slack: Grant announce privilege to 7 users for #openverse, per zackkrida. Message-ID: <20211207001634.25D5E1B004F3@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Tue Dec 7 04:24:04 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 7 Dec 2021 04:24:04 +0000 (UTC) Subject: [wp-meta] [11359] sites/trunk/api.wordpress.org/public_html/dotorg/slack/trac-bot.php: Slack: Trac: SlackTracBot: Avoid throwing Warnings & Notices when a commit is mentioned in a Slack channel without a ticket reference. Message-ID: <20211207042404.3109F1B003FE@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Fri Dec 10 00:46:32 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 10 Dec 2021 00:46:32 -0000 Subject: [wp-meta] [Making WordPress.org] #5975: Plugin Directory: Show name of committer being removed in JavaScript confirmation. Message-ID: <057.e675d7bf02e16e2bdbaab096660694d4@wordpress.org> #5975: Plugin Directory: Show name of committer being removed in JavaScript confirmation. ------------------------------+-------------------- Reporter: peterwilsoncc | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Keywords: ------------------------------+-------------------- When removing a committer from a plugin, a JavaScript confirmation is shown with the text generic text "Are you sure you would like to remove this committer?" (or similar). To avoid mistakes, it would be helpful if the confirmation included the committers name and/or username. Something along the lines of "Are you sure you would like to remove @peterwilsoncc's commit access?" An alternative may be to highlight the committer's name in yellow while the confirmation dialog is open. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 10 01:42:05 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 10 Dec 2021 01:42:05 -0000 Subject: [wp-meta] [Making WordPress.org] #5975: Plugin Directory: Show name of committer being removed in JavaScript confirmation. In-Reply-To: <057.e675d7bf02e16e2bdbaab096660694d4@wordpress.org> References: <057.e675d7bf02e16e2bdbaab096660694d4@wordpress.org> Message-ID: <072.f6e4373faef3a09d9dcf7e5d6b5af8b2@wordpress.org> #5975: Plugin Directory: Show name of committer being removed in JavaScript confirmation. ------------------------------+--------------------- Reporter: peterwilsoncc | Owner: (none) Type: enhancement | Status: new Priority: high | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+--------------------- Changes (by dd32): * priority: normal => high Comment: Every confirmation message on the plugin-author facing options screen needs better confirmations (That default to aborting the process). We'd be better off migrating all the destructive actions to an inline modal confirming the action with a full description. (I consider adding/removing committers to be potentially destructive) I'm shifting this to priority:high because it'll make plugin reviewers lives easier if they don't have to fix problems plugin authors accidentally cause due to bad author actions/confirmations, and accidentally removing/adding the wrong people to be a committer could have all sorts of unforeseen issues. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sun Dec 12 09:54:54 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Sun, 12 Dec 2021 09:54:54 -0000 Subject: [wp-meta] [Making WordPress.org] #5976: Translate database maybe corrupt as it shows duplicate originals with "current" state Message-ID: <054.a165d17ab302775ee8aa07310aa462db@wordpress.org> #5976: Translate database maybe corrupt as it shows duplicate originals with "current" state --------------------------------------+-------------------- Reporter: psmits1567 | Owner: (none) Type: defect | Status: new Priority: high | Milestone: Component: Translate Site & Plugins | Keywords: --------------------------------------+-------------------- The last two months I encountered several projects with a higher percentage completed as are within the project. There is shown a percentage of 103 % with the following project https://translate.wordpress.org/projects/wp-plugins/xml-sitemap- feed/stable/nl/default/?filters%5Btranslated%5D=yes&filters%5Bstatus%5D=current The amount of translated records is incorrect Filter ↓ • Sort ↓ • All (159) • Translated (164) • Untranslated (0) • Waiting (0) • Fuzzy (0) • Warnings (0) To solve this you need to reject the original with the wrong translation. It appears to me that the state of the previous translation is not set to "old" That results in two records with state "current" I have left this project in the state it currently is. Check this original https://translate.wordpress.org/projects/wp-plugins/xml-sitemap- feed/stable/nl/default/?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=2146435&filters%5Btranslation_id%5D=56179538 -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 13 04:18:52 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 13 Dec 2021 04:18:52 -0000 Subject: [wp-meta] [Making WordPress.org] #5977: Move the position of terms description at the top of the commercial themes page Message-ID: <054.d72d7022b0cf14f7f6fd629cb0ae4d67@wordpress.org> #5977: Move the position of terms description at the top of the commercial themes page -----------------------------+----------------------- Reporter: bijayyadav | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Theme Directory | Keywords: has-patch -----------------------------+----------------------- While I was checking the terms of the commercial themes page, I was not able to figure it out at first. I had to scroll the whole page to find it. I think, it's better to move the description to the top of the page and it will be easy to access. See the screenshot how it looks like after moving it to the top section. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 13 04:19:08 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 13 Dec 2021 04:19:08 -0000 Subject: [wp-meta] [Making WordPress.org] #5977: Move the position of terms description at the top of the commercial themes page In-Reply-To: <054.d72d7022b0cf14f7f6fd629cb0ae4d67@wordpress.org> References: <054.d72d7022b0cf14f7f6fd629cb0ae4d67@wordpress.org> Message-ID: <069.af697242df079899c0449aad90d4f29b@wordpress.org> #5977: Move the position of terms description at the top of the commercial themes page -----------------------------+--------------------- Reporter: bijayyadav | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Theme Directory | Resolution: Keywords: has-patch | -----------------------------+--------------------- Changes (by bijayyadav): * Attachment "Screenshot_7.jpg" added. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 13 04:35:07 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 13 Dec 2021 04:35:07 -0000 Subject: [wp-meta] [Making WordPress.org] #5977: Move the position of terms description at the top of the commercial themes page In-Reply-To: <054.d72d7022b0cf14f7f6fd629cb0ae4d67@wordpress.org> References: <054.d72d7022b0cf14f7f6fd629cb0ae4d67@wordpress.org> Message-ID: <069.bca73629b42d10bdc6c95e0a8ea5a518@wordpress.org> #5977: Move the position of terms description at the top of the commercial themes page -----------------------------+--------------------- Reporter: bijayyadav | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Theme Directory | Resolution: Keywords: has-patch | -----------------------------+--------------------- Changes (by bijayyadav): * Attachment "commercial-themes-page-description-position-changed.patch" added. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 13 05:18:37 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 13 Dec 2021 05:18:37 -0000 Subject: [wp-meta] [Making WordPress.org] #5978: Create a better way to trac SVN props and contributions Message-ID: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> #5978: Create a better way to trac SVN props and contributions -----------------------------+-------------------- Reporter: dd32 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Version Control | Keywords: -----------------------------+-------------------- Currently core compiles a list of props for each release at the end of the release, this is based on parsing the git log for props, and then manually correcting all the items within that doesn't quite parse right. Something I've wanted to do for a while, is to add realtime props to SVN to profile.wordpress.org, which requires having this data in a database that we can query.. something which we haven't had with the previous method of gathering props. It would also be nice to be able to generate certain "reports" for various uses, and to be able to highlight contributors for whom have either been typo'd in commit messages, or where the actual contributors name isn't able to be linked to a WordPress.org user. The commits to follow are something I've been tweaking slightly for a few weeks, and applies to develop.svn and meta.svn initially. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 13 05:22:29 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 13 Dec 2021 05:22:29 +0000 (UTC) Subject: [wp-meta] [11360] sites/trunk/wordpress.org/public_html/wp-content/plugins: Trac / SVN / Make: Monitor develop.svn.wordpress.org & meta.svn.wordpress.org and import revisions into a custom table, parsing out prop'd users. Message-ID: <20211213052229.AACCE1B0049F@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon Dec 13 05:22:34 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 13 Dec 2021 05:22:34 -0000 Subject: [wp-meta] [Making WordPress.org] #5978: Create a better way to trac SVN props and contributions In-Reply-To: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> References: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> Message-ID: <063.224d2dce224a404f709c59883edeca39@wordpress.org> #5978: Create a better way to trac SVN props and contributions -----------------------------+--------------------- Reporter: dd32 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Version Control | Resolution: Keywords: | -----------------------------+--------------------- Comment (by dd32): In [changeset:"11360" 11360]: {{{ #!CommitTicketReference repository="" revision="11360" Trac / SVN / Make: Monitor develop.svn.wordpress.org & meta.svn.wordpress.org and import revisions into a custom table, parsing out prop'd users. Included are various reports and some work to capture typo's of prop'd users. The code is definately not DRY, clean, or named properly - but it works. See #5978. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 13 05:24:09 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 13 Dec 2021 05:24:09 +0000 (UTC) Subject: [wp-meta] [11361] sites/trunk/wordpress.org/public_html/wp-content/plugins: Revert [11360]. Message-ID: <20211213052409.E002D1B0049F@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon Dec 13 05:41:16 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 13 Dec 2021 05:41:16 +0000 (UTC) Subject: [wp-meta] [11362] sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-trac-watcher: Trac / SVN / Make: Monitor develop.svn.wordpress.org & meta.svn.wordpress.org and import revisions into a custom table, parsing out prop'd users. Message-ID: <20211213054116.1D0CC1B0049F@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon Dec 13 05:41:21 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 13 Dec 2021 05:41:21 -0000 Subject: [wp-meta] [Making WordPress.org] #5978: Create a better way to trac SVN props and contributions In-Reply-To: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> References: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> Message-ID: <063.62c6ca2669965cbf9174a88de4bfff85@wordpress.org> #5978: Create a better way to trac SVN props and contributions -----------------------------+--------------------- Reporter: dd32 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Version Control | Resolution: Keywords: | -----------------------------+--------------------- Comment (by dd32): In [changeset:"11362" 11362]: {{{ #!CommitTicketReference repository="" revision="11362" Trac / SVN / Make: Monitor develop.svn.wordpress.org & meta.svn.wordpress.org and import revisions into a custom table, parsing out prop'd users. Included are various reports and some work to capture typo's of prop'd users. The code is definitely not DRY, clean, or named properly - but it works. See #5978. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 13 07:06:14 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 13 Dec 2021 07:06:14 +0000 (UTC) Subject: [wp-meta] [11363] sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-trac-watcher: SVN Watching: Some tweaks to the matching rules. Message-ID: <20211213070614.81E0C1B00420@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon Dec 13 07:06:19 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 13 Dec 2021 07:06:19 -0000 Subject: [wp-meta] [Making WordPress.org] #5978: Create a better way to trac SVN props and contributions In-Reply-To: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> References: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> Message-ID: <063.05182719a2fedb6ac89758437367f402@wordpress.org> #5978: Create a better way to trac SVN props and contributions -----------------------------+--------------------- Reporter: dd32 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Version Control | Resolution: Keywords: | -----------------------------+--------------------- Comment (by dd32): In [changeset:"11363" 11363]: {{{ #!CommitTicketReference repository="" revision="11363" SVN Watching: Some tweaks to the matching rules. See #5978. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 13 08:34:37 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 13 Dec 2021 08:34:37 +0000 (UTC) Subject: [wp-meta] [11364] sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-trac-watcher/admin/reports-page.php: SVN Watcher: Fix some bugs in the reports. Message-ID: <20211213083437.E29771B00420@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon Dec 13 08:34:42 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 13 Dec 2021 08:34:42 -0000 Subject: [wp-meta] [Making WordPress.org] #5978: Create a better way to trac SVN props and contributions In-Reply-To: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> References: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> Message-ID: <063.dfda13d75545196e6cdf4b50e50f6877@wordpress.org> #5978: Create a better way to trac SVN props and contributions -----------------------------+--------------------- Reporter: dd32 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Version Control | Resolution: Keywords: | -----------------------------+--------------------- Comment (by dd32): In [changeset:"11364" 11364]: {{{ #!CommitTicketReference repository="" revision="11364" SVN Watcher: Fix some bugs in the reports. See #5978. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 13 08:51:25 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 13 Dec 2021 08:51:25 -0000 Subject: [wp-meta] [Making WordPress.org] #5977: Move the position of terms description at the top of the commercial themes page In-Reply-To: <054.d72d7022b0cf14f7f6fd629cb0ae4d67@wordpress.org> References: <054.d72d7022b0cf14f7f6fd629cb0ae4d67@wordpress.org> Message-ID: <069.6e11b6221d0d6fdde07a9f8d4aeffd18@wordpress.org> #5977: Move the position of terms description at the top of the commercial themes page -----------------------------+--------------------- Reporter: bijayyadav | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Theme Directory | Resolution: Keywords: has-patch | -----------------------------+--------------------- Comment (by kafleg): Hello @bijayyadav Thank you for creating this ticket and a warm welcome to meta. I was feeling something similar that some theme authors didn't follow these terms while submitting the request to add their site. Instead of adding terms at the top, we can add a link at the top section scroll down to the detailed terms section. Thank you -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 13 14:01:59 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 13 Dec 2021 14:01:59 -0000 Subject: [wp-meta] [Making WordPress.org] #5979: The table of contents is no longer displayed Message-ID: <049.9aaca62b39053f997dc881c771a25b80@wordpress.org> #5979: The table of contents is no longer displayed ---------------------+-------------------- Reporter: jdy68 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: HelpHub | Keywords: ---------------------+-------------------- I'm co-leader of the French WordPress documentation and I've noticed for a few weeks that when we publish new translated posts, the posts don't offer the table of contents anymore. For example: https://fr.wordpress.org/support/article/appearance-customize-screen/ published on October 29, 2021 displays the table of contents but https://fr.wordpress.org/support/article/theme-base-sur-des-blocs/ published on October 31 no longer displays it. All posts published after October 31, 2021 no longer show the table of contents. I observe the same problem for some posts in the English documentation. For example: https://wordpress.org/support/article/new-to-wordpress-where- to-start/ or https://wordpress.org/support/article/wordpress-features/ Moreover, as soon as you update a post (older) which displayed the table of contents, once the update is done the table of contents is not displayed anymore. Example: https://fr.wordpress.org/support/article/glossary/ modified today December 6, 2021. I tried to compare these posts to see what could be a problem, and I don't see anything different in the Hn tags. Example for h2 and h3 tags: in https://fr.wordpress.org/support/article/appearance-customize-screen/

basic-use

How to open the customization tool

in https://fr.wordpress.org/support/article/theme-base-sur-des-blocs/

What is a block-based theme ?

Editing templates via the Dashboard Templates screen

Finally, the style of the level 3 headings is different depending on whether the post displays a table of contents or not. If the post doesn’t have a table of contents, the h3 headings are capitalized. I can provide the source of posts that don’t have a table of contents or search for other information if needed. With @audrasjb, we think that the problem comes from an incompatibility between WP 5.9 and the extension that creates the table of contents. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 13 14:41:08 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 13 Dec 2021 14:41:08 -0000 Subject: [wp-meta] [Making WordPress.org] #5979: The table of contents is no longer displayed In-Reply-To: <049.9aaca62b39053f997dc881c771a25b80@wordpress.org> References: <049.9aaca62b39053f997dc881c771a25b80@wordpress.org> Message-ID: <064.e8ca42d457470d753cc25c809546ffc3@wordpress.org> #5979: The table of contents is no longer displayed -----------------------+--------------------- Reporter: jdy68 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: HelpHub | Resolution: Keywords: has-patch | -----------------------+--------------------- Comment (by audrasjb): The above PR replace the existing regex to also match headings with attributes. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 13 21:00:47 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 13 Dec 2021 21:00:47 -0000 Subject: [wp-meta] [Making WordPress.org] #2821: Plugin Directory: Plugin slug should be Latin Characters Only In-Reply-To: <051.25e027265662218e64083f79ba18e777@wordpress.org> References: <051.25e027265662218e64083f79ba18e777@wordpress.org> Message-ID: <066.7dc876d26718bcfe43e5359a7d047e11@wordpress.org> #2821: Plugin Directory: Plugin slug should be Latin Characters Only ---------------------------------------+----------------------------------- Reporter: Ipstenu | Owner: tellyworth Type: defect | Status: closed Priority: normal | Milestone: Plugin Directory | v3.0 Component: Plugin Directory | Resolution: fixed Keywords: has-patch has-screenshots | ---------------------------------------+----------------------------------- Comment (by pmpr): Can I submit my plugin with English-only latin characters slug (Plugin Name:), but choose a non-English Name or Title to be shown on plugin download page? Something like this: https://wordpress.org/plugins/persian-woocommerce/ -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 14 00:49:47 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 14 Dec 2021 00:49:47 -0000 Subject: [wp-meta] [Making WordPress.org] #5979: The table of contents is no longer displayed In-Reply-To: <049.9aaca62b39053f997dc881c771a25b80@wordpress.org> References: <049.9aaca62b39053f997dc881c771a25b80@wordpress.org> Message-ID: <064.500bfb5531769099d4f9647de17132a9@wordpress.org> #5979: The table of contents is no longer displayed -----------------------+--------------------- Reporter: jdy68 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: HelpHub | Resolution: Keywords: has-patch | -----------------------+--------------------- Comment (by dd32): I tackled this slightly different via #5963 - instead of just matching the headings, I respected the settings that Gutenberg can apply to the heading (Including custom ID, classes, styles, etc). Somewhat annoyingly, these two plugins are the exact same plugin, the one in use here seems to be the code that the Handbook TOC is based on, but wrapped into a bigger plugin.. I think? I can't be too sure.. I can't tell who the original author was. I'm going to replace the Support HelpHub plugin with the Handbook variant instead, so that we only have to update one plugin. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 14 01:26:20 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 14 Dec 2021 01:26:20 +0000 (UTC) Subject: [wp-meta] [11365] sites/trunk/wordpress.org/public_html/wp-content/plugins/support-helphub: Support: HelpHub: Attempt to replace the TOC plugin within the HelpHub site with the original WordPress.org-supported TOC plugin it was based on. Message-ID: <20211214012620.7C4791B0052F@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Tue Dec 14 01:26:25 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 14 Dec 2021 01:26:25 -0000 Subject: [wp-meta] [Making WordPress.org] #5963: ToC plugin doesn't support Gutenberg In-Reply-To: <048.f163c8caa2dac9d484ef3c85cec461a2@wordpress.org> References: <048.f163c8caa2dac9d484ef3c85cec461a2@wordpress.org> Message-ID: <063.e227fbe3016e319159ac77c7991b5def@wordpress.org> #5963: ToC plugin doesn't support Gutenberg -----------------------+--------------------- Reporter: dd32 | Owner: dd32 Type: defect | Status: closed Priority: normal | Milestone: Component: Handbooks | Resolution: fixed Keywords: | -----------------------+--------------------- Comment (by dd32): In [changeset:"11365" 11365]: {{{ #!CommitTicketReference repository="" revision="11365" Support: HelpHub: Attempt to replace the TOC plugin within the HelpHub site with the original WordPress.org-supported TOC plugin it was based on. The HelpHub plugin was based on the Handbooks plugin, but customised and further plugin-ised, resulting in two different plugins on WordPress.org doing the same thing, in different ways. This is an attempt to make it easier to sync the Handbook plugin changes to Support pages. See #5979, #5963. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 14 01:26:25 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 14 Dec 2021 01:26:25 -0000 Subject: [wp-meta] [Making WordPress.org] #5979: The table of contents is no longer displayed In-Reply-To: <049.9aaca62b39053f997dc881c771a25b80@wordpress.org> References: <049.9aaca62b39053f997dc881c771a25b80@wordpress.org> Message-ID: <064.b9c15e1a2d1ef6cfe44c0b434ac2a12f@wordpress.org> #5979: The table of contents is no longer displayed -----------------------+--------------------- Reporter: jdy68 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: HelpHub | Resolution: Keywords: has-patch | -----------------------+--------------------- Comment (by dd32): In [changeset:"11365" 11365]: {{{ #!CommitTicketReference repository="" revision="11365" Support: HelpHub: Attempt to replace the TOC plugin within the HelpHub site with the original WordPress.org-supported TOC plugin it was based on. The HelpHub plugin was based on the Handbooks plugin, but customised and further plugin-ised, resulting in two different plugins on WordPress.org doing the same thing, in different ways. This is an attempt to make it easier to sync the Handbook plugin changes to Support pages. See #5979, #5963. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 14 01:30:57 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 14 Dec 2021 01:30:57 +0000 (UTC) Subject: [wp-meta] [11366] sites/trunk/wordpress.org/public_html/wp-content/plugins: Handbooks / HelpHub: Internationalise the Title & Top links, allowing HelpHub to translate it with a different text-domain. Message-ID: <20211214013057.EBF491B0052F@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Tue Dec 14 01:31:03 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 14 Dec 2021 01:31:03 -0000 Subject: [wp-meta] [Making WordPress.org] #5979: The table of contents is no longer displayed In-Reply-To: <049.9aaca62b39053f997dc881c771a25b80@wordpress.org> References: <049.9aaca62b39053f997dc881c771a25b80@wordpress.org> Message-ID: <064.2ce222452af509cbfd50f0628c2725da@wordpress.org> #5979: The table of contents is no longer displayed -----------------------+--------------------- Reporter: jdy68 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: HelpHub | Resolution: Keywords: has-patch | -----------------------+--------------------- Comment (by dd32): In [changeset:"11366" 11366]: {{{ #!CommitTicketReference repository="" revision="11366" Handbooks / HelpHub: Internationalise the Title & Top links, allowing HelpHub to translate it with a different text-domain. See #5979. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 14 01:34:22 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 14 Dec 2021 01:34:22 +0000 (UTC) Subject: [wp-meta] [11367] sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-trac-watcher/admin/reports-page.php: SVN Watcher: Remove an unused variable causing a PHP Notice. Message-ID: <20211214013422.5696D1B0052F@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Tue Dec 14 01:34:27 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 14 Dec 2021 01:34:27 -0000 Subject: [wp-meta] [Making WordPress.org] #5978: Create a better way to trac SVN props and contributions In-Reply-To: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> References: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> Message-ID: <063.eb17896cc01fe2ea26e3e7a0882cb997@wordpress.org> #5978: Create a better way to trac SVN props and contributions -----------------------------+--------------------- Reporter: dd32 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Version Control | Resolution: Keywords: | -----------------------------+--------------------- Comment (by dd32): In [changeset:"11367" 11367]: {{{ #!CommitTicketReference repository="" revision="11367" SVN Watcher: Remove an unused variable causing a PHP Notice. See #5978. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 14 01:37:15 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 14 Dec 2021 01:37:15 +0000 (UTC) Subject: [wp-meta] [11368] sites/trunk/wordpress.org/public_html/wp-content/plugins/support-helphub/inc/handbook-toc/index.php: HelpHub: Avoid a Fatal error with the TOC when both the Handbook and Support plugins are active on a site (For example, Rosetta team sites, which previously had two TOC plugins?) Message-ID: <20211214013715.C8C971B0052F@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Tue Dec 14 01:37:21 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 14 Dec 2021 01:37:21 -0000 Subject: [wp-meta] [Making WordPress.org] #5979: The table of contents is no longer displayed In-Reply-To: <049.9aaca62b39053f997dc881c771a25b80@wordpress.org> References: <049.9aaca62b39053f997dc881c771a25b80@wordpress.org> Message-ID: <064.e4925d6006bcd306e1bc1814b0693520@wordpress.org> #5979: The table of contents is no longer displayed -----------------------+--------------------- Reporter: jdy68 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: HelpHub | Resolution: Keywords: has-patch | -----------------------+--------------------- Comment (by dd32): In [changeset:"11368" 11368]: {{{ #!CommitTicketReference repository="" revision="11368" HelpHub: Avoid a Fatal error with the TOC when both the Handbook and Support plugins are active on a site (For example, Rosetta team sites, which previously had two TOC plugins?) See #5979. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 14 02:10:17 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 14 Dec 2021 02:10:17 -0000 Subject: [wp-meta] [Making WordPress.org] #5979: The table of contents is no longer displayed In-Reply-To: <049.9aaca62b39053f997dc881c771a25b80@wordpress.org> References: <049.9aaca62b39053f997dc881c771a25b80@wordpress.org> Message-ID: <064.181abf333c090340fe856a236913d191@wordpress.org> #5979: The table of contents is no longer displayed -----------------------+--------------------- Reporter: jdy68 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: HelpHub | Resolution: Keywords: has-patch | -----------------------+--------------------- Comment (by dd32): And even more annoyingly, while the Handbooks TOC plugin has some inline CSS, it's not actually the CSS used for styling the TOC listing! That's defined per-theme! This seems to be working, and makes it much easier to sync changes between them. I think we're going to need to migrate this TOC plugin to an actual plugin, rather than just a handbook/helphub bundled plugin, as it's also needed for Learn, and potentially other places too.. Or maybe it'd make sense as a published Block instead... -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 14 03:54:49 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 14 Dec 2021 03:54:49 -0000 Subject: [wp-meta] [Making WordPress.org] #5978: Create a better way to trac SVN props and contributions In-Reply-To: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> References: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> Message-ID: <063.34bf55cbc9d71fafbf84bc815ac58c73@wordpress.org> #5978: Create a better way to trac SVN props and contributions -----------------------------+--------------------- Reporter: dd32 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Version Control | Resolution: Keywords: | -----------------------------+--------------------- Comment (by dd32): {{{ In r18068-dotorg: Profiles: Include changesets that users are mentioned in on Core/Meta SVN in their profile feed. See https://meta.trac.wordpress.org/ticket/5978 }}} A good example of this is https://profiles.wordpress.org/costdev/ for Core, and https://profiles.wordpress.org/jonoaldersonwp/ for Meta/Core. For committers, here's some direct links to the edit screen (You need posting permission for the make site) - https://make.wordpress.org/core/wp-admin/admin.php?page=props-edit-core - https://make.wordpress.org/meta/wp-admin/admin.php?page=props-edit-meta There's not exactly many instructions, but it's impossible to break - worst case you have to hit reparse on the commit or re-edit all the props. There's nothing preventing it being expanded to BuddyPress & bbPress SVNs, other than not knowing where to show the UI's, and adding a BP/BB version extraction function :) It's built around SVN, but there's no reason it couldn't import a Git repo, other than non-sequential commit numbers, and if hosted by GitHub (for example) the usernames not matching dotorg usernames. Although, that being said, if a linked W.org linked GitHub is mentioned in a SVN commit at present, that's picked up, so we could probably make it work. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 14 04:39:01 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 14 Dec 2021 04:39:01 +0000 (UTC) Subject: [wp-meta] [11369] sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-trac-watcher/admin: SVN Watcher: Reports: Avoid some PHP Notices, and compress the versions contributed to table. Message-ID: <20211214043901.971DE1B0052F@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Tue Dec 14 04:39:06 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 14 Dec 2021 04:39:06 -0000 Subject: [wp-meta] [Making WordPress.org] #5978: Create a better way to trac SVN props and contributions In-Reply-To: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> References: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> Message-ID: <063.a119f6c40a4bf180e0921334d02d0c32@wordpress.org> #5978: Create a better way to trac SVN props and contributions -----------------------------+--------------------- Reporter: dd32 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Version Control | Resolution: Keywords: | -----------------------------+--------------------- Comment (by dd32): In [changeset:"11369" 11369]: {{{ #!CommitTicketReference repository="" revision="11369" SVN Watcher: Reports: Avoid some PHP Notices, and compress the versions contributed to table. Instead of showing `3.0, 3.1, .... 5.8` just show `3.0-5.8`. See #5978. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 14 05:20:19 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 14 Dec 2021 05:20:19 +0000 (UTC) Subject: [wp-meta] [11370] sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-trac-watcher/admin: SVN Watcher: Reports: Add an 'unknown props' report, simpler view to scan for known typos. Message-ID: <20211214052019.A6C1F1B0052F@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Tue Dec 14 05:20:24 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 14 Dec 2021 05:20:24 -0000 Subject: [wp-meta] [Making WordPress.org] #5978: Create a better way to trac SVN props and contributions In-Reply-To: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> References: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> Message-ID: <063.93492aa6265aeee0e6370c8353807daf@wordpress.org> #5978: Create a better way to trac SVN props and contributions -----------------------------+--------------------- Reporter: dd32 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Version Control | Resolution: Keywords: | -----------------------------+--------------------- Comment (by dd32): In [changeset:"11370" 11370]: {{{ #!CommitTicketReference repository="" revision="11370" SVN Watcher: Reports: Add an 'unknown props' report, simpler view to scan for known typos. See #5978. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 02:47:06 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 15 Dec 2021 02:47:06 +0000 (UTC) Subject: [wp-meta] [11371] sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-trac-watcher: SVN Watcher: Some performance improvements for the admin view & reports. Message-ID: <20211215024706.1D0A21B005BD@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed Dec 15 02:47:11 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 02:47:11 -0000 Subject: [wp-meta] [Making WordPress.org] #5978: Create a better way to trac SVN props and contributions In-Reply-To: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> References: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> Message-ID: <063.107f7422bfcf280320172120f539da09@wordpress.org> #5978: Create a better way to trac SVN props and contributions -----------------------------+--------------------- Reporter: dd32 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Version Control | Resolution: Keywords: | -----------------------------+--------------------- Comment (by dd32): In [changeset:"11371" 11371]: {{{ #!CommitTicketReference repository="" revision="11371" SVN Watcher: Some performance improvements for the admin view & reports. This reduces the queries by removing oEmbed processing of commit messages, caching users in bulk, avoiding PHP Notices, documenting some things, skipping the UI if revisions/props aren't imported for a SVN. See #5978. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 04:38:09 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 15 Dec 2021 04:38:09 +0000 (UTC) Subject: [wp-meta] [11372] sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-trac-watcher: SVN Watcher: Move the Trac importer from running within profiles.wordpress.org into this plugin. Message-ID: <20211215043809.E445D1B005BD@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed Dec 15 04:38:14 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 04:38:14 -0000 Subject: [wp-meta] [Making WordPress.org] #5978: Create a better way to trac SVN props and contributions In-Reply-To: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> References: <048.c26b4730e6c05e1e936d91900d6a53b4@wordpress.org> Message-ID: <063.968e52be4b5a7ceb4e44a761cf423304@wordpress.org> #5978: Create a better way to trac SVN props and contributions -----------------------------+--------------------- Reporter: dd32 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Version Control | Resolution: Keywords: | -----------------------------+--------------------- Comment (by dd32): In [changeset:"11372" 11372]: {{{ #!CommitTicketReference repository="" revision="11372" SVN Watcher: Move the Trac importer from running within profiles.wordpress.org into this plugin. The Trac importer was previously running as part of profiles, but was sporadic due to the different cron setup of the various WordPress.org multisites. This brings over the code to here, leaving profiles just consuming the data instead. See #5978. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 05:46:33 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 05:46:33 -0000 Subject: [wp-meta] [Making WordPress.org] #5937: Extend the possibility for leaving a plugin or theme review In-Reply-To: <051.84b82fc73f2109364396c7df3f06619d@wordpress.org> References: <051.84b82fc73f2109364396c7df3f06619d@wordpress.org> Message-ID: <066.bf75af9701296c728b3577dda59dc593@wordpress.org> #5937: Extend the possibility for leaving a plugin or theme review -------------------------+--------------------- Reporter: Clorith | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: | -------------------------+--------------------- Comment (by dd32): **This is just me thinking aloud, nothing solid or set in stone here**, there are a number of things related to this that I've removed as unrelated. Regardless of how it's implemented, this is something that I've talked with various people over the years multiple times, many plugins/themes get next to no reviews, which negatively affects WordPress.org's ability to use review data for ranking/search/sorting/highlighting purposes. We could also benefit from it for things like Blocks, Patterns, and Photos shown directly within the editor where we'll unfortunately need a way to allow someone to flag/report items directly from their editor instance, even if they don't have a WordPress.org account. There are a number of ways we could offer this including: - oAuth flow against their site, which potentially means us having an access token for their site temporarily.. - Private .org API which allows a WordPress site to submit reviews/flags about an item, with a callback built in so that .org can verify that the site who is who it said it is. - Private .org API which is the same as above, but returns a special URL which can be presented to the user in an iframe, allowing them to review an item: - (Name + Email or Login button) + Site (hard-coded) + Item (plugin X, hard-coded) + Review Text - For "high risk" reviews/browsers/whatever it can then go to pending + email confirmation - if it's deemed "low risk" published as-is until flagged by someone (effectively, public unless anyone logged in says "uhh" at which point it goes to modlook) Now that I think about it more, the final option there is probably the most ideal for a review, while the second is probably the best for a "flag this item" action. We have some flags we can use here, not all of which will be super helpful.. - Whether the site has submitted reviews before, Whether the Name+Email provided has submitted them before, etc. - reCaptcha is in use on WordPress.org login, but misses a bunch of things. If we had an iFrame that the review was submitted through we'd be able to validate that. - On login, we have some heuristics around email addresses, manual blacklists, and a few other tools which could be leveraged. That would allow extra heuristics to be applied to what will effectively be a public "comment" that's not as easily accessed as comment forms.. - Akismet, since as I just realised, it's effectively a comment.. - WordPress.org stats can probably give some kind of "Is Site URL A in good standing" based on how long the site's hashed ID has existed, there's bound to be some clashes but few enough to matter. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 05:51:38 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 05:51:38 -0000 Subject: [wp-meta] [Making WordPress.org] #5957: Remove Community Team P2 automated "Weekly Updates" posts In-Reply-To: <050.88b8029e7ce85443b6f2faf8fd567cdc@wordpress.org> References: <050.88b8029e7ce85443b6f2faf8fd567cdc@wordpress.org> Message-ID: <065.e236ff53769387a73b4e79e83152edd6@wordpress.org> #5957: Remove Community Team P2 automated "Weekly Updates" posts --------------------------------------+--------------------- Reporter: sippis | Owner: (none) Type: defect | Status: closed Priority: normal | Milestone: Component: Make (Get Involved) / P2 | Resolution: fixed Keywords: | --------------------------------------+--------------------- Changes (by dd32): * status: new => closed * resolution: => fixed Comment: I've disabled the prompt. I've left the code in place, and just commented out the action for now, incase someone needs it in the future. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 05:53:33 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 05:53:33 -0000 Subject: [wp-meta] [Making WordPress.org] #5924: Update WordPress Forum Guidelines | Links to Other Resources In-Reply-To: <052.2fb3d6fe53f8bb1066c6b92ad807c009@wordpress.org> References: <052.2fb3d6fe53f8bb1066c6b92ad807c009@wordpress.org> Message-ID: <067.45bc0e3a9d5d61484c87281c95b2e289@wordpress.org> #5924: Update WordPress Forum Guidelines | Links to Other Resources ----------------------------+--------------------- Reporter: jetxpert | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: 2nd-opinion | ----------------------------+--------------------- Changes (by dd32): * component: General => Support Forums -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 05:57:49 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 05:57:49 -0000 Subject: [wp-meta] [Making WordPress.org] #5897: Sort the teams drop-down on /meetings In-Reply-To: <056.252239fb68eca5128427552f328d8563@wordpress.org> References: <056.252239fb68eca5128427552f328d8563@wordpress.org> Message-ID: <071.626f064f86bd961360ede3fc96bd28f9@wordpress.org> #5897: Sort the teams drop-down on /meetings --------------------------+-------------------------------- Reporter: tobifjellner | Owner: (none) Type: enhancement | Status: closed Priority: normal | Milestone: Component: General | Resolution: reported-upstream Keywords: | --------------------------+-------------------------------- Changes (by dd32): * status: new => closed * resolution: => reported-upstream Comment: Migrated this up to the GitHub repo for the plugin: https://github.com/WordPress/meeting-calendar/issues/126 -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 05:58:00 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 05:58:00 -0000 Subject: [wp-meta] [Making WordPress.org] #5897: Sort the teams drop-down on /meetings In-Reply-To: <056.252239fb68eca5128427552f328d8563@wordpress.org> References: <056.252239fb68eca5128427552f328d8563@wordpress.org> Message-ID: <071.7f06c91ccabd096c25c1b77a60f8b874@wordpress.org> #5897: Sort the teams drop-down on /meetings --------------------------------------+-------------------------------- Reporter: tobifjellner | Owner: (none) Type: enhancement | Status: closed Priority: normal | Milestone: Component: Make (Get Involved) / P2 | Resolution: reported-upstream Keywords: | --------------------------------------+-------------------------------- Changes (by dd32): * component: General => Make (Get Involved) / P2 -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 06:12:14 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 06:12:14 -0000 Subject: [wp-meta] [Making WordPress.org] #5890: Advanced view - Add support reps - non-ascii character display fails In-Reply-To: <050.ab734b3f003383b27aa58828cf1042e0@wordpress.org> References: <050.ab734b3f003383b27aa58828cf1042e0@wordpress.org> Message-ID: <065.97ae1087f4331557e5ef7abda081887c@wordpress.org> #5890: Advanced view - Add support reps - non-ascii character display fails ------------------------------+--------------------- Reporter: knutsp | Owner: (none) Type: defect | Status: closed Priority: low | Milestone: Component: Plugin Directory | Resolution: fixed Keywords: | ------------------------------+--------------------- Changes (by dd32): * status: new => closed * resolution: => fixed Comment: This appears to have been related to bad user data - The user in questions name wasn't showing up in many places due to broken utf8 characters. That includes on their WordPress.org profile, support forum profile, and getting eaten by `wp_json_encode()` which has some UTF8 protections built in. I've re-saved their profile, which has caused their display name to show up correctly everywhere (such as on profiles.w.org) and also when being added to a plugin. Unfortunately I'm not sure how best to locate other accounts that suffer it, as character sets are hard.. I'm going to close this one as fixed though, if other users are affected by this, hit save on your WordPress.org profile and see if that fixes the bad data. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 06:14:50 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 06:14:50 -0000 Subject: [wp-meta] [Making WordPress.org] #5883: Add Classic Widgets to the Featured Plugin list In-Reply-To: <051.28f9d405c2ae2f3b9c28fc8b0d920b76@wordpress.org> References: <051.28f9d405c2ae2f3b9c28fc8b0d920b76@wordpress.org> Message-ID: <066.f05b7dda163f7a414f21145cd7790e5c@wordpress.org> #5883: Add Classic Widgets to the Featured Plugin list ---------------------+--------------------- Reporter: desrosj | Owner: (none) Type: defect | Status: closed Priority: normal | Milestone: Component: API | Resolution: fixed Keywords: | ---------------------+--------------------- Changes (by dd32): * status: new => closed * resolution: => fixed Comment: https://wordpress.org/plugins/classic-widgets/ is now in https://wordpress.org/plugins/browse/featured/ Future requests could probably be directed to #pluginreview on slack or plugins@ for a quicker response, incase the ticket gets missed again. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 06:15:46 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 06:15:46 -0000 Subject: [wp-meta] [Making WordPress.org] #5849: Add tag to automated weekly Community post In-Reply-To: <050.c666be0393c579ad26d549fb1afeb20f@wordpress.org> References: <050.c666be0393c579ad26d549fb1afeb20f@wordpress.org> Message-ID: <065.50788737c209bff51b33175b696d671f@wordpress.org> #5849: Add tag to automated weekly Community post --------------------------------------+---------------------- Reporter: RMarks | Owner: (none) Type: enhancement | Status: closed Priority: normal | Milestone: Component: Make (Get Involved) / P2 | Resolution: invalid Keywords: | --------------------------------------+---------------------- Changes (by dd32): * status: new => closed * resolution: => invalid Comment: weekly posts are no more. #5957 -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 06:32:40 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 06:32:40 -0000 Subject: [wp-meta] [Making WordPress.org] #5782: Button texts becomes blurry when a user search for that text on WP.org sites In-Reply-To: <059.c10846cf7f2dcf7cc5d1a8dd6c4e9a2f@wordpress.org> References: <059.c10846cf7f2dcf7cc5d1a8dd6c4e9a2f@wordpress.org> Message-ID: <074.ef843c58864eb0cca7295fb33b8762ca@wordpress.org> #5782: Button texts becomes blurry when a user search for that text on WP.org sites --------------------------------+---------------------- Reporter: alanjacobmathew | Owner: (none) Type: enhancement | Status: closed Priority: low | Milestone: Component: WordPress.org Site | Resolution: wontfix Keywords: | --------------------------------+---------------------- Changes (by dd32): * status: new => closed * resolution: => wontfix Comment: Unfortunately Browsers don't appear to offer any way to style these search highlights. `::selection` is available for text-selections, but not search highlights. The only fix here would be to remove the `text-shadow` on the buttons, which isn't ideal.. although it's not the worst. The good news is that the upcoming (2022) new WordPress.org style uses a different style of button that isn't affected by this. Unfortunately I'm going to close this as wontfix for now, unless someone comes along with a quick fix. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 06:33:49 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 06:33:49 -0000 Subject: [wp-meta] [Making WordPress.org] #5777: WordPress.org Serbian Translation - Wrong version on the download button In-Reply-To: <057.51152fd4d0c12530440909d4439d9b1f@wordpress.org> References: <057.51152fd4d0c12530440909d4439d9b1f@wordpress.org> Message-ID: <072.9a79b4e3204a0457a45a57d477338f84@wordpress.org> #5777: WordPress.org Serbian Translation - Wrong version on the download button -------------------------------------------+--------------------- Reporter: igorradovanov | Owner: (none) Type: defect | Status: closed Priority: normal | Milestone: Component: International Sites (Rosetta) | Resolution: fixed Keywords: | -------------------------------------------+--------------------- Changes (by dd32): * status: new => closed * resolution: => fixed -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 06:46:45 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 15 Dec 2021 06:46:45 +0000 (UTC) Subject: [wp-meta] [11373] sites/trunk/wordpress.org/public_html/wp-content/plugins: Consistently link to `https://profiles.wordpress.org/$user/` with a trailing slash. Message-ID: <20211215064646.01B7C1B00420@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed Dec 15 06:46:50 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 06:46:50 -0000 Subject: [wp-meta] [Making WordPress.org] #5810: Enforce a trailing slash on user profile links In-Reply-To: <058.110e8432f78a84cedf96ecbf48c5d5cb@wordpress.org> References: <058.110e8432f78a84cedf96ecbf48c5d5cb@wordpress.org> Message-ID: <073.2a317ed5dc8ae9dba3437fd2279067d6@wordpress.org> #5810: Enforce a trailing slash on user profile links -----------------------------+--------------------- Reporter: jonoaldersonwp | Owner: (none) Type: defect | Status: new Priority: lowest | Milestone: Component: General | Resolution: Keywords: seo performance | -----------------------------+--------------------- Comment (by dd32): In [changeset:"11373" 11373]: {{{ #!CommitTicketReference repository="" revision="11373" Consistently link to `https://profiles.wordpress.org/$user/` with a trailing slash. See #5810. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 06:53:38 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 15 Dec 2021 06:53:38 +0000 (UTC) Subject: [wp-meta] [11374] sites/trunk/wordpress.org/public_html/wp-content/plugins: Consistently link to `https://profiles.wordpress.org/$user/` with a trailing slash. Message-ID: <20211215065338.D03DB1B00420@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed Dec 15 06:53:43 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 06:53:43 -0000 Subject: [wp-meta] [Making WordPress.org] #5810: Enforce a trailing slash on user profile links In-Reply-To: <058.110e8432f78a84cedf96ecbf48c5d5cb@wordpress.org> References: <058.110e8432f78a84cedf96ecbf48c5d5cb@wordpress.org> Message-ID: <073.e59bd5086eae3ed26302a5e62030de98@wordpress.org> #5810: Enforce a trailing slash on user profile links -----------------------------+--------------------- Reporter: jonoaldersonwp | Owner: (none) Type: defect | Status: new Priority: lowest | Milestone: Component: General | Resolution: Keywords: seo performance | -----------------------------+--------------------- Comment (by dd32): In [changeset:"11374" 11374]: {{{ #!CommitTicketReference repository="" revision="11374" Consistently link to `https://profiles.wordpress.org/$user/` with a trailing slash. Part 2. See #5810. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 06:56:47 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 15 Dec 2021 06:56:47 +0000 (UTC) Subject: [wp-meta] [11375] sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-gp-customizations/inc/class-plugin.php: Consistently link to `https://profiles.wordpress.org/$user/` with a trailing slash. Message-ID: <20211215065647.6D7801B00420@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed Dec 15 06:56:52 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 06:56:52 -0000 Subject: [wp-meta] [Making WordPress.org] #5810: Enforce a trailing slash on user profile links In-Reply-To: <058.110e8432f78a84cedf96ecbf48c5d5cb@wordpress.org> References: <058.110e8432f78a84cedf96ecbf48c5d5cb@wordpress.org> Message-ID: <073.502ca6097de8fd13eb448094c0d7d739@wordpress.org> #5810: Enforce a trailing slash on user profile links -----------------------------+--------------------- Reporter: jonoaldersonwp | Owner: (none) Type: defect | Status: new Priority: lowest | Milestone: Component: General | Resolution: Keywords: seo performance | -----------------------------+--------------------- Comment (by dd32): In [changeset:"11375" 11375]: {{{ #!CommitTicketReference repository="" revision="11375" Consistently link to `https://profiles.wordpress.org/$user/` with a trailing slash. Part 3. See #5810. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 07:16:15 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 15 Dec 2021 07:16:15 +0000 (UTC) Subject: [wp-meta] [11376] sites/trunk: Consistently link to `https://profiles.wordpress.org/$user/` with a trailing slash. Message-ID: <20211215071615.22DC61B00420@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed Dec 15 07:16:20 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 07:16:20 -0000 Subject: [wp-meta] [Making WordPress.org] #5810: Enforce a trailing slash on user profile links In-Reply-To: <058.110e8432f78a84cedf96ecbf48c5d5cb@wordpress.org> References: <058.110e8432f78a84cedf96ecbf48c5d5cb@wordpress.org> Message-ID: <073.39bbde90b3696af4e4ad72561598dc38@wordpress.org> #5810: Enforce a trailing slash on user profile links -----------------------------+--------------------- Reporter: jonoaldersonwp | Owner: (none) Type: defect | Status: new Priority: lowest | Milestone: Component: General | Resolution: Keywords: seo performance | -----------------------------+--------------------- Comment (by dd32): In [changeset:"11376" 11376]: {{{ #!CommitTicketReference repository="" revision="11376" Consistently link to `https://profiles.wordpress.org/$user/` with a trailing slash. Part 4. See #5810. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 07:28:55 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 15 Dec 2021 07:28:55 +0000 (UTC) Subject: [wp-meta] [11377] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-developer/inc/handbooks.php: Developer: Link credit @mention's to profiles.wordpress.org with a trailing slash. Message-ID: <20211215072855.57F421B00420@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed Dec 15 07:29:00 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 07:29:00 -0000 Subject: [wp-meta] [Making WordPress.org] #5810: Enforce a trailing slash on user profile links In-Reply-To: <058.110e8432f78a84cedf96ecbf48c5d5cb@wordpress.org> References: <058.110e8432f78a84cedf96ecbf48c5d5cb@wordpress.org> Message-ID: <073.fd735d7e11099da4ab47b89533548278@wordpress.org> #5810: Enforce a trailing slash on user profile links -----------------------------+--------------------- Reporter: jonoaldersonwp | Owner: (none) Type: defect | Status: new Priority: lowest | Milestone: Component: General | Resolution: Keywords: seo performance | -----------------------------+--------------------- Comment (by dd32): In [changeset:"11377" 11377]: {{{ #!CommitTicketReference repository="" revision="11377" Developer: Link credit @mention's to profiles.wordpress.org with a trailing slash. See #5810. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 08:05:19 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 08:05:19 -0000 Subject: [wp-meta] [Making WordPress.org] #5810: Enforce a trailing slash on user profile links In-Reply-To: <058.110e8432f78a84cedf96ecbf48c5d5cb@wordpress.org> References: <058.110e8432f78a84cedf96ecbf48c5d5cb@wordpress.org> Message-ID: <073.a422af96602b7b693da92bbed1b81715@wordpress.org> #5810: Enforce a trailing slash on user profile links -----------------------------+----------------------- Reporter: jonoaldersonwp | Owner: dd32 Type: defect | Status: accepted Priority: lowest | Milestone: Component: General | Resolution: Keywords: seo performance | -----------------------------+----------------------- Changes (by dd32): * owner: (none) => dd32 * status: new => accepted Comment: The only things not done above are rosetta/localised blogposts: > Props lists in articles, like in https://en- au.wordpress.org/2016/12/07/wordpress-4-7-vaughan/ These aren't too hard to update, but there's a lot of sites that could have them in their post_content, which isn't a task for today. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 08:07:56 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 08:07:56 -0000 Subject: [wp-meta] [Making WordPress.org] #5810: Enforce a trailing slash on user profile links In-Reply-To: <058.110e8432f78a84cedf96ecbf48c5d5cb@wordpress.org> References: <058.110e8432f78a84cedf96ecbf48c5d5cb@wordpress.org> Message-ID: <073.2cfae6f0f5c671a7e923320f80127e9f@wordpress.org> #5810: Enforce a trailing slash on user profile links -----------------------------+----------------------- Reporter: jonoaldersonwp | Owner: dd32 Type: defect | Status: accepted Priority: lowest | Milestone: Component: General | Resolution: Keywords: seo performance | -----------------------------+----------------------- Comment (by jonoaldersonwp): Oh wow, amazing work! :) -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 08:18:07 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 08:18:07 -0000 Subject: [wp-meta] [Making WordPress.org] #5842: CSS issue in Contributor Training Quiz Buttons In-Reply-To: <054.793fb87fa2dc1b3a8ea867514811ff47@wordpress.org> References: <054.793fb87fa2dc1b3a8ea867514811ff47@wordpress.org> Message-ID: <069.b7975c973fb26b6ce2502a943d433f94@wordpress.org> #5842: CSS issue in Contributor Training Quiz Buttons --------------------------------+--------------------- Reporter: circlecube | Owner: (none) Type: defect | Status: closed Priority: normal | Milestone: Component: WordPress.org Site | Resolution: fixed Keywords: has-screenshots | --------------------------------+--------------------- Changes (by dd32): * status: new => closed * resolution: => fixed Comment: Thanks @circlecube - Sorry it took so long for a response to this ticket :( I've updated the site using a similar style to what you proposed, it already had the lesson/course one there, so I've just merged it in there. {{{ .lesson a.button, .course a.button, .quiz .wp-block-buttons .wp-block-button button { height: auto; } }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 16:44:45 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 16:44:45 -0000 Subject: [wp-meta] [Making WordPress.org] #5980: Typo Message-ID: <057.dcd08fd8a97dac715f2ea43e5458b149@wordpress.org> #5980: Typo -----------------------------+----------------------------- Reporter: topher1kenobe | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Photo Directory | Keywords: has-copy-review -----------------------------+----------------------------- On the form for submitting an image there's this line: Photo must not contain indentifiable faces. Should be identifiable. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 20:55:04 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 20:55:04 -0000 Subject: [wp-meta] [Making WordPress.org] #5980: Typo In-Reply-To: <057.dcd08fd8a97dac715f2ea43e5458b149@wordpress.org> References: <057.dcd08fd8a97dac715f2ea43e5458b149@wordpress.org> Message-ID: <072.c320a82d8f7cbd6a61701e6cd0dd58fe@wordpress.org> #5980: Typo -----------------------------+--------------------- Reporter: topher1kenobe | Owner: (none) Type: defect | Status: closed Priority: normal | Milestone: Component: Photo Directory | Resolution: fixed Keywords: has-copy-review | -----------------------------+--------------------- Changes (by coffee2code): * status: new => closed * resolution: => fixed Comment: Thanks for the report! Fixed in [18086-dotorg]. > Photo Directory, Uploads: Fix typo and change a word. > > Props topher1kenobe. > Fixes #5980. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 22:01:06 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 22:01:06 -0000 Subject: [wp-meta] [Making WordPress.org] #5981: Photos submitted to https://wordpress.org/photos/ should appear on profiles Message-ID: <050.8944ba2fc6795cc953a14cb6657d5977@wordpress.org> #5981: Photos submitted to https://wordpress.org/photos/ should appear on profiles -------------------------+-------------------- Reporter: jorbin | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Profiles | Keywords: -------------------------+-------------------- In order to recognize people who add Photos, the event should be on someone's profile and there should be a "photo contributor" badge. it would also be great if there was a "Photos" tab similar to plugins. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 15 22:19:33 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 15 Dec 2021 22:19:33 -0000 Subject: [wp-meta] [Making WordPress.org] #5981: Photos submitted to https://wordpress.org/photos/ should appear on profiles In-Reply-To: <050.8944ba2fc6795cc953a14cb6657d5977@wordpress.org> References: <050.8944ba2fc6795cc953a14cb6657d5977@wordpress.org> Message-ID: <065.0f7135fa3b43814ac729b6931c76b33b@wordpress.org> #5981: Photos submitted to https://wordpress.org/photos/ should appear on profiles -------------------------+--------------------- Reporter: jorbin | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Profiles | Resolution: Keywords: | -------------------------+--------------------- Comment (by coffee2code): Those are all indeed in the plan! -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 16 00:34:00 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 16 Dec 2021 00:34:00 -0000 Subject: [wp-meta] [Making WordPress.org] #5846: WPTV: Subtitle attachment info stays even after subtitle file is removed In-Reply-To: <047.dc3f52bd6500e7327987b8770826d160@wordpress.org> References: <047.dc3f52bd6500e7327987b8770826d160@wordpress.org> Message-ID: <062.f3a8f90cde5b32a2a79fd3dfd55799ec@wordpress.org> #5846: WPTV: Subtitle attachment info stays even after subtitle file is removed --------------------------+--------------------- Reporter: Nao | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: WordPress.tv | Resolution: Keywords: | --------------------------+--------------------- Comment (by tellyworth): Is there an easy technical fix that would clear the postmeta automatically when the file is deleted or missing? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 16 03:00:59 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 16 Dec 2021 03:00:59 +0000 (UTC) Subject: [wp-meta] [11378] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-login/functions.php: Login: Disable the Core login language selector, through a rather low-level filter. Message-ID: <20211216030059.4F4501B004F3@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Thu Dec 16 03:01:04 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 16 Dec 2021 03:01:04 -0000 Subject: [wp-meta] [Making WordPress.org] #5850: Show Password feature not appearing on WP login page In-Reply-To: <059.526f8570aaa175f7b9e68e03863e5b16@wordpress.org> References: <059.526f8570aaa175f7b9e68e03863e5b16@wordpress.org> Message-ID: <074.dfc8cb3dacab9ece9ea0ecc996eec26e@wordpress.org> #5850: Show Password feature not appearing on WP login page ------------------------------------+--------------------- Reporter: alanjacobmathew | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Login & Authentication | Resolution: Keywords: | ------------------------------------+--------------------- Comment (by dd32): In [changeset:"11378" 11378]: {{{ #!CommitTicketReference repository="" revision="11378" Login: Disable the Core login language selector, through a rather low- level filter. There are no filters available to disable the login language selector, so instead we make WordPress believe there are no languages available on the front-end wp-login.php display, which hides the selector, but still loads our custom login localisation files. See #5850. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 16 03:29:41 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 16 Dec 2021 03:29:41 +0000 (UTC) Subject: [wp-meta] [11379] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-login: Login: Replace the call to `wp_login_form()` with a static form so that we can customise the content. Message-ID: <20211216032941.95C351B00426@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Thu Dec 16 03:29:46 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 16 Dec 2021 03:29:46 -0000 Subject: [wp-meta] [Making WordPress.org] #5850: Show Password feature not appearing on WP login page In-Reply-To: <059.526f8570aaa175f7b9e68e03863e5b16@wordpress.org> References: <059.526f8570aaa175f7b9e68e03863e5b16@wordpress.org> Message-ID: <074.66a4ecd1af10b7f4b6efebc6f49d412e@wordpress.org> #5850: Show Password feature not appearing on WP login page ------------------------------------+--------------------- Reporter: alanjacobmathew | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Login & Authentication | Resolution: Keywords: | ------------------------------------+--------------------- Comment (by dd32): In [changeset:"11379" 11379]: {{{ #!CommitTicketReference repository="" revision="11379" Login: Replace the call to `wp_login_form()` with a static form so that we can customise the content. `wp_login_form()` isn't the same as `wp-login.php` and isn't as easy to customise; By removing it we'll be able to add things that `wp-login.php` has such as a show password button. See #5850. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 16 04:11:42 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 16 Dec 2021 04:11:42 +0000 (UTC) Subject: [wp-meta] [11380] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-login: Login: Add a 'show password' / 'hide password' button to password inputs, for consistency with wp-login.php. Message-ID: <20211216041142.20F7A1B004F3@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Thu Dec 16 04:11:47 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 16 Dec 2021 04:11:47 -0000 Subject: [wp-meta] [Making WordPress.org] #5850: Show Password feature not appearing on WP login page In-Reply-To: <059.526f8570aaa175f7b9e68e03863e5b16@wordpress.org> References: <059.526f8570aaa175f7b9e68e03863e5b16@wordpress.org> Message-ID: <074.09dd4971bd82f94515d4dd08773fdaea@wordpress.org> #5850: Show Password feature not appearing on WP login page ------------------------------------+--------------------- Reporter: alanjacobmathew | Owner: dd32 Type: defect | Status: closed Priority: normal | Milestone: Component: Login & Authentication | Resolution: fixed Keywords: | ------------------------------------+--------------------- Changes (by dd32): * owner: (none) => dd32 * status: new => closed * resolution: => fixed Comment: In [changeset:"11380" 11380]: {{{ #!CommitTicketReference repository="" revision="11380" Login: Add a 'show password' / 'hide password' button to password inputs, for consistency with wp-login.php. Fixes #5850. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 16 04:21:13 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 16 Dec 2021 04:21:13 +0000 (UTC) Subject: [wp-meta] [11381] sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/shortcodes/class-readme-validator.php: Plugin Directory: Readme Validator: Protect inputs against vulnerability scanners sending junk inputs. Message-ID: <20211216042113.5F7A91B004F3@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Thu Dec 16 04:26:35 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 16 Dec 2021 04:26:35 -0000 Subject: [wp-meta] [Making WordPress.org] #5982: Browse Source menu in themes trac page showing 502 Bad Gateway Message-ID: <050.b3b54be7d3c90c817e4fee2a4ebb7664@wordpress.org> #5982: Browse Source menu in themes trac page showing 502 Bad Gateway -------------------------+------------------------------------------------- Reporter: kafleg | Owner: (none) Type: defect | Status: new Priority: high | Milestone: Component: Trac | Keywords: needs-patch 2nd-opinion has- | screenshots needs-testing -------------------------+------------------------------------------------- Go to https://themes.trac.wordpress.org/ and click on the `Browse Source` menu and wait for some time. Instead of loading the page, we can see `502 Bad Gateway`. The direct link of that page is, https://themes.trac.wordpress.org/browser -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 16 04:26:45 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 16 Dec 2021 04:26:45 -0000 Subject: [wp-meta] [Making WordPress.org] #5982: Browse Source menu in themes trac page showing 502 Bad Gateway In-Reply-To: <050.b3b54be7d3c90c817e4fee2a4ebb7664@wordpress.org> References: <050.b3b54be7d3c90c817e4fee2a4ebb7664@wordpress.org> Message-ID: <065.16be65e3f2450b4452e6448b17ce40f8@wordpress.org> #5982: Browse Source menu in themes trac page showing 502 Bad Gateway -------------------------------------------------+------------------------- Reporter: kafleg | Owner: (none) Type: defect | Status: new Priority: high | Milestone: Component: Trac | Resolution: Keywords: needs-patch 2nd-opinion has- | screenshots needs-testing | -------------------------------------------------+------------------------- Changes (by kafleg): * Attachment "502badgateway.png" added. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 16 04:54:21 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 16 Dec 2021 04:54:21 -0000 Subject: [wp-meta] [Making WordPress.org] #5852: Adding Pronouns field on the W.org profile In-Reply-To: <064.4ebb2f9e599398b9dc17c034d3613fd2@wordpress.org> References: <064.4ebb2f9e599398b9dc17c034d3613fd2@wordpress.org> Message-ID: <079.3091995f5fe47b9aa44e6e90fb1eb2f8@wordpress.org> #5852: Adding Pronouns field on the W.org profile ----------------------------------+--------------------- Reporter: felipeloureirosantos | Owner: (none) Type: enhancement | Status: new Priority: low | Milestone: Component: Profiles | Resolution: Keywords: 2nd-opinion close | ----------------------------------+--------------------- Changes (by dd32): * keywords: => 2nd-opinion close Comment: I'm not sure I see the real point in asking/collecting/displaying personal details such as gender/pronoun preferences on WordPress.org. The WordPress.org profiles are intended to be a snapshot of ones activity on WordPress.org and their position in the community, not their personal life/details. If someone were to wish to clarify it for those they're communicating with, they can do that through the existing freeform name/nickname fields, for example `John Doe (they/him)`, or within their profile bio (if they chose to add one). There aren't many other places where it would make sense to display that either. Slack is kind of special, a 3rd party application, and a different form of communication and more personal 1:1 than the rest of WordPress.org.. WordPress.org simply chose to not disable the slack pronoun field (although slack defaulted to disabled, to avoid pushing features out to enterprises who didn't want it). I've heard from some community members in the past that the WordPress ecosystem has been one of the most welcoming tech communities they'd interacted with, purely because their gender and identity wasn't ever an issue, they didn't have to state who they are or that despite their appearance they identified differently, just that they're here to help. When this is merged to WordPress core, and/or gender-based translation support is added, it may make more sense then.[[BR]] Until then, IMHO this is probably a `maybelater` ticket, even purely for respecting ones privacy by not collecting data we don't need to know, while acknowledging that those who wish/need to state it somewhere, can already do so as mentioned above. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 16 04:56:14 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 16 Dec 2021 04:56:14 -0000 Subject: [wp-meta] [Making WordPress.org] #5982: Browse Source menu in themes trac page showing 502 Bad Gateway In-Reply-To: <050.b3b54be7d3c90c817e4fee2a4ebb7664@wordpress.org> References: <050.b3b54be7d3c90c817e4fee2a4ebb7664@wordpress.org> Message-ID: <065.5d07ce357a109c89a9793c9e11d4967d@wordpress.org> #5982: Browse Source menu in themes trac page showing 502 Bad Gateway -------------------------------------------------+------------------------- Reporter: kafleg | Owner: (none) Type: defect | Status: closed Priority: high | Milestone: Component: Trac | Resolution: duplicate Keywords: needs-patch 2nd-opinion has- | screenshots needs-testing | -------------------------------------------------+------------------------- Changes (by dd32): * status: new => closed * resolution: => duplicate Comment: The browser link probably just needs removing.. Closing as a duplicate of #4861 though. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 16 04:57:30 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 16 Dec 2021 04:57:30 -0000 Subject: [wp-meta] [Making WordPress.org] #1639: Themes Trac browser does not display UTF-8 text correctly In-Reply-To: <058.02b6120490346ff36855bbab3cf3faf8@wordpress.org> References: <058.02b6120490346ff36855bbab3cf3faf8@wordpress.org> Message-ID: <073.ea6aed59c4425678ee9719ccff66198b@wordpress.org> #1639: Themes Trac browser does not display UTF-8 text correctly ----------------------------+--------------------- Reporter: SergeyBiryukov | Owner: dd32 Type: defect | Status: closed Priority: normal | Milestone: Q1 Component: Trac | Resolution: fixed Keywords: | ----------------------------+--------------------- Changes (by dd32): * keywords: pending-systems => * status: accepted => closed * resolution: => fixed -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 16 05:37:01 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 16 Dec 2021 05:37:01 -0000 Subject: [wp-meta] [Making WordPress.org] #4861: Themes Trac doesn't like the Browser In-Reply-To: <055.b1967b1e66c33f6ad6c7831a21d90dea@wordpress.org> References: <055.b1967b1e66c33f6ad6c7831a21d90dea@wordpress.org> Message-ID: <070.fcc962cebff14b92bbd4145aa7f86b7f@wordpress.org> #4861: Themes Trac doesn't like the Browser ---------------------------------------------+--------------------- Reporter: wpamitkumar | Owner: (none) Type: defect | Status: new Priority: lowest | Milestone: Component: Trac | Resolution: Keywords: has-screenshots pending-systems | ---------------------------------------------+--------------------- Changes (by dd32): * keywords: has-screenshots => has-screenshots pending-systems * priority: low => lowest Comment: Upstream ticket from 15 years ago for paging: https://trac.edgewall.org/ticket/6101 We've already dealt with this for the Plugins trac by redirecting `/browser$` to the plugins homepage, I guess we'll do the same for themes. I considered just removing the Browser menu item, but that doesn't do much for the other links to the page, so the plugins option seems better. Created a systems request: https://make.wordpress.org/systems/2021/12/16 /disable-themes-trac-browser-for-root-index/ -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 16 06:05:51 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 16 Dec 2021 06:05:51 -0000 Subject: [wp-meta] [Making WordPress.org] #3459: Update good-first-bugs auto-claiming process In-Reply-To: <052.3bdfe3057573fefa334a7af5219eb6fb@wordpress.org> References: <052.3bdfe3057573fefa334a7af5219eb6fb@wordpress.org> Message-ID: <067.0b72bafa11cae4cb20a16fc027ba6200@wordpress.org> #3459: Update good-first-bugs auto-claiming process -------------------------+--------------------- Reporter: jbpaul17 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Trac | Resolution: Keywords: needs-patch | -------------------------+--------------------- Changes (by dd32): * Attachment "3459.diff" added. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 16 06:06:51 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 16 Dec 2021 06:06:51 -0000 Subject: [wp-meta] [Making WordPress.org] #3459: Update good-first-bugs auto-claiming process In-Reply-To: <052.3bdfe3057573fefa334a7af5219eb6fb@wordpress.org> References: <052.3bdfe3057573fefa334a7af5219eb6fb@wordpress.org> Message-ID: <067.bc7c2bb526d78acc768a89988d53accd@wordpress.org> #3459: Update good-first-bugs auto-claiming process -------------------------------------------+--------------------- Reporter: jbpaul17 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Trac | Resolution: Keywords: needs-patch reporter-feedback | -------------------------------------------+--------------------- Changes (by dd32): * keywords: needs-patch => needs-patch reporter-feedback Comment: @jbpaul17 Is this still something that is wanted by the Core team, do you know? This hasn't been implemented due to trac limitations, namely that AFAIK the `has-patch` keyword isn't added automatically and the [https://meta.trac.wordpress.org/browser/sites/trunk/trac.wordpress.org/conf /workflow-core.ini trac workflow for core] can only really do it based on capabilities. What we could do, if is still wanted, is allow all users to self-assign tickets (ALL tickets, even if not flagged as good-first-bug, not adding a patch, etc, although the UI could be hidden via JS and only show the option when all the conditions are met..) something like [attachment:"3459.diff"], which would prevent people taking ownership of other tickets, but anyone could claim a ticket without the JS I mentioned above. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 16 06:37:45 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 16 Dec 2021 06:37:45 -0000 Subject: [wp-meta] [Making WordPress.org] #3058: Missing commits from the bbPress Git mirror In-Reply-To: <050.fbaba2dd5ca6c8d752fc36e354ee210e@wordpress.org> References: <050.fbaba2dd5ca6c8d752fc36e354ee210e@wordpress.org> Message-ID: <065.e91d16dee39ab72b58303d879eeb708b@wordpress.org> #3058: Missing commits from the bbPress Git mirror -----------------------------+------------------------- Reporter: netweb | Owner: (none) Type: defect | Status: closed Priority: normal | Milestone: Component: Version Control | Resolution: worksforme Keywords: | -----------------------------+------------------------- Changes (by dd32): * status: new => closed * resolution: => worksforme Comment: Went to take a look if this is still an issue.. it is, but it's not. Some "null commits" such as https://bbpress.trac.wordpress.org/changeset/31 don't show up in git because well.. they can't.. there's nothing there. But the original command here only covered commits to `trunk` rather than to branches. Eg: {{{ $ git remote -v origin git://bbpress.git.wordpress.org/ (fetch) origin git://bbpress.git.wordpress.org/ (push) $ git shortlog -s | cut -f1 | paste -s -d+ - | bc 6409 $ git shortlog -s --all | cut -f1 | paste -s -d+ - | bc 7283 $ svn log https://bbpress.svn.wordpress.org --limit 1 | grep ^r r7229 | johnjamesjacoby | 2021-11-29 15:28:59 +0000 (Mon, 29 Nov 2021) | 3 lines }}} So based on that, there's MORE commits to Git than to SVN.. which is probably due to commits to multiple branches in SVN being multiple commits in git? Which is confirmed by: {{{ $ git log --all 2>&1 | grep 'git-svn-id' | cut -d: -f2-3 | cut -d' ' -f2 | cut -d'@' -f2 | sort | uniq -c | sort | tail -n10 2 1790 2 1900 2 1901 2 5446 2 5611 2 5970 2 5990 2 6825 3 5698 5 5690 }}} https://bbpress.trac.wordpress.org/changeset/5690 is referenced by 5 Git commits, as it touched 5 different git branches. Closing as worksforme. Re-open if you can point to a missing commit. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 16 06:48:54 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 16 Dec 2021 06:48:54 -0000 Subject: [wp-meta] [Making WordPress.org] #5534: Add limits to prevent high-triggering notifications In-Reply-To: <048.59f9f11955877ab567f8c65564a014ee@wordpress.org> References: <048.59f9f11955877ab567f8c65564a014ee@wordpress.org> Message-ID: <063.449a7dbf6340b91935c3dfce774f90c0@wordpress.org> #5534: Add limits to prevent high-triggering notifications ---------------------+--------------------- Reporter: dd32 | Owner: (none) Type: defect | Status: closed Priority: high | Milestone: Component: General | Resolution: fixed Keywords: | ---------------------+--------------------- Changes (by dd32): * status: new => closed * resolution: => fixed Comment: I've done some work on this recently, including: * Notifications: Add an unsubscription and notification management link to the footer of matcher notification emails. * Notifications: Add a enable/disable functionality, to allow temporarily disabling notifications without deleting them. * Notifications: Record a lifetime hitcounter for matchers in the DB * Notifications: Include a more specific reason why they're getting the email in the notification emails. > For example, there's a user with a matcher for 'WordPress', and two for other common terms such as 'Help', 'Login', 'Music', 'Google', '404', etc. There was also a matcher for 'the' which was being triggered thousands of times a day :) That has since been disabled. After disabling the worst notification offenders, the number of matchers triggers are significantly reduced. But there are still some that are getting hit ~25 times a day. I'm marking this as fixed for now. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 16 06:49:37 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 16 Dec 2021 06:49:37 -0000 Subject: [wp-meta] [Making WordPress.org] #5295: Error message to be improved when trying to submit an empty review In-Reply-To: <058.6f672191131c27749bb96368367b0f8c@wordpress.org> References: <058.6f672191131c27749bb96368367b0f8c@wordpress.org> Message-ID: <073.f26b420b75d1f57bf792b515f106667b@wordpress.org> #5295: Error message to be improved when trying to submit an empty review ----------------------------+--------------------- Reporter: Hareesh Pillai | Owner: (none) Type: enhancement | Status: new Priority: low | Milestone: Component: Support Forums | Resolution: Keywords: needs-patch | ----------------------------+--------------------- Changes (by dd32): * component: General => Support Forums -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 16 07:07:11 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 16 Dec 2021 07:07:11 +0000 (UTC) Subject: [wp-meta] [11382] sites/trunk/wordpress.org/public_html/wp-content/plugins/support-forums/inc/class-ratings-compat.php: Support Forums: Update two errors on the review form to reference review rather than topic. Message-ID: <20211216070711.CEECC1B003B5@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Thu Dec 16 07:07:17 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 16 Dec 2021 07:07:17 -0000 Subject: [wp-meta] [Making WordPress.org] #5295: Error message to be improved when trying to submit an empty review In-Reply-To: <058.6f672191131c27749bb96368367b0f8c@wordpress.org> References: <058.6f672191131c27749bb96368367b0f8c@wordpress.org> Message-ID: <073.29e22d5334556bfec925f731baf60c93@wordpress.org> #5295: Error message to be improved when trying to submit an empty review ----------------------------+--------------------- Reporter: Hareesh Pillai | Owner: dd32 Type: enhancement | Status: closed Priority: low | Milestone: Component: Support Forums | Resolution: fixed Keywords: needs-patch | ----------------------------+--------------------- Changes (by dd32): * owner: (none) => dd32 * status: new => closed * resolution: => fixed Comment: In [changeset:"11382" 11382]: {{{ #!CommitTicketReference repository="" revision="11382" Support Forums: Update two errors on the review form to reference review rather than topic. Fixes #5295. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 16 07:37:44 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 16 Dec 2021 07:37:44 +0000 (UTC) Subject: [wp-meta] [11383] sites/trunk/wordpress.org/public_html/wp-content/plugins/support-forums/inc/class-ratings-compat.php: Support Forums: Block links in reviews, force the reviewer to remove the links, and ultimately send the review to the moderation queue anyway. Message-ID: <20211216073744.5CC8D1B0042E@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Thu Dec 16 07:37:49 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 16 Dec 2021 07:37:49 -0000 Subject: [wp-meta] [Making WordPress.org] #5748: Block ability to add links in reviews In-Reply-To: <053.3e10995ab181290c8e508ee7c28ddb11@wordpress.org> References: <053.3e10995ab181290c8e508ee7c28ddb11@wordpress.org> Message-ID: <068.c3740713d0e632fe4fe74c1f2a335965@wordpress.org> #5748: Block ability to add links in reviews ----------------------------+--------------------- Reporter: sterndata | Owner: dd32 Type: enhancement | Status: closed Priority: normal | Milestone: Component: Support Forums | Resolution: fixed Keywords: has-patch | ----------------------------+--------------------- Changes (by dd32): * owner: (none) => dd32 * status: new => closed * resolution: => fixed Comment: In [changeset:"11383" 11383]: {{{ #!CommitTicketReference repository="" revision="11383" Support Forums: Block links in reviews, force the reviewer to remove the links, and ultimately send the review to the moderation queue anyway. If it turns out that reviewers seem to behave themselves, and remove the links (instead of evading the check), we can remove the moderation queue check. Fixes #5748. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 16 07:57:18 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 16 Dec 2021 07:57:18 -0000 Subject: [wp-meta] [Making WordPress.org] #5748: Block ability to add links in reviews In-Reply-To: <053.3e10995ab181290c8e508ee7c28ddb11@wordpress.org> References: <053.3e10995ab181290c8e508ee7c28ddb11@wordpress.org> Message-ID: <068.a96efb261996fe2f3ac16de3217bb1b8@wordpress.org> #5748: Block ability to add links in reviews ----------------------------+----------------------- Reporter: sterndata | Owner: dd32 Type: enhancement | Status: reopened Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: has-patch | ----------------------------+----------------------- Changes (by dd32): * status: closed => reopened * resolution: fixed => Comment: I don't think this will catch edits to topics.. so.. I should probably also add a similar check blocking links in edits to reviews. There's also the author replying to the review with a followup with the links in it, which seems less of a problem, but probably shouldn't be allowed either? But if a plugin/theme author asks for follow up information and effectively turns the review into a support thread... don't really want to penalise the review author for that.. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 16 15:55:04 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 16 Dec 2021 15:55:04 -0000 Subject: [wp-meta] [Making WordPress.org] #5983: Define faces? Message-ID: <057.1fa0600d34287d8dc5d55fcc16f384c4@wordpress.org> #5983: Define faces? -----------------------------+-------------------- Reporter: topher1kenobe | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Photo Directory | Keywords: -----------------------------+-------------------- This might be pedantic, feel free to close, but there's an item that says "Photo must not contain identifiable faces." I just uploaded a pic of some goats, and their faces are very identifiable. Do we want to say: "Photo must not contain identifiable human faces." ? I realize it might seem ridiculous, but I don't know if it matters to people who don't speak English well. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 16 23:56:38 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 16 Dec 2021 23:56:38 +0000 (UTC) Subject: [wp-meta] [11384] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-learn-2020: WordPress.org Learn: sync with GitHub. Message-ID: <20211216235638.A32211B0042E@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Fri Dec 17 03:54:01 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Fri, 17 Dec 2021 03:54:01 +0000 (UTC) Subject: [wp-meta] [11385] sites/trunk/wordpress.org/public_html/wp-content/plugins/support-forums/inc/class-ratings-compat.php: Support Forums: When sending reviews to the moderation queue, add a postmeta value so we can review them at a later date. Message-ID: <20211217035401.6D7931B00553@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Fri Dec 17 03:54:06 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 17 Dec 2021 03:54:06 -0000 Subject: [wp-meta] [Making WordPress.org] #5748: Block ability to add links in reviews In-Reply-To: <053.3e10995ab181290c8e508ee7c28ddb11@wordpress.org> References: <053.3e10995ab181290c8e508ee7c28ddb11@wordpress.org> Message-ID: <068.239de12e935748fc07d55dcf251f1210@wordpress.org> #5748: Block ability to add links in reviews ----------------------------+----------------------- Reporter: sterndata | Owner: dd32 Type: enhancement | Status: reopened Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: has-patch | ----------------------------+----------------------- Comment (by dd32): In [changeset:"11385" 11385]: {{{ #!CommitTicketReference repository="" revision="11385" Support Forums: When sending reviews to the moderation queue, add a postmeta value so we can review them at a later date. Follow up to [11383]. See #5748. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 17 04:49:41 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 17 Dec 2021 04:49:41 -0000 Subject: [wp-meta] [Making WordPress.org] #5756: Activity log is not populated when a topic title consists of only emoji In-Reply-To: <053.7188c26d18306ef47a754ccbd436c0de@wordpress.org> References: <053.7188c26d18306ef47a754ccbd436c0de@wordpress.org> Message-ID: <068.5e3cfe4d3e29447739016fc10c5dd7bf@wordpress.org> #5756: Activity log is not populated when a topic title consists of only emoji -----------------------+--------------------- Reporter: bradparbs | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Profiles | Resolution: Keywords: | -----------------------+--------------------- Changes (by dd32): * component: Plugin Directory => Profiles Comment: > -1 Unable to save activity Looks like this is caused by WPDB rejecting the DB Insert via `wpdb->strip_invalid_text_from_query`: > WPOrg_Profiles_Activity_Handler->handle_forum_activity, bp_activity_add, BP_Activity_Activity->save, hyperdb->query, wpdb->strip_invalid_text_from_query, wpdb->get_table_charset, wpdb->get_results, hyperdb->query The fields in this case are `CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci` and the connection should be `utf8mb4`, so I'm not quite sure what the issue is.. unless it needs to be upgraded to `utf8mb4_unicode_520_ci`.. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 17 04:55:45 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 17 Dec 2021 04:55:45 -0000 Subject: [wp-meta] [Making WordPress.org] #5765: Don't load the theme filters interface on individual theme pages In-Reply-To: <058.a3b822168ba893bfc4f9235ec9a6a2c4@wordpress.org> References: <058.a3b822168ba893bfc4f9235ec9a6a2c4@wordpress.org> Message-ID: <073.6ddabde4bd1b5cb47dd7601c049615b4@wordpress.org> #5765: Don't load the theme filters interface on individual theme pages -----------------------------+---------------------- Reporter: jonoaldersonwp | Owner: (none) Type: defect | Status: closed Priority: normal | Milestone: Component: Theme Directory | Resolution: wontfix Keywords: seo | -----------------------------+---------------------- Changes (by dd32): * status: new => closed * resolution: => wontfix Comment: This is the way that the JS client is built, the rendered output is required for the JS to work correctly. If you load a search, and then browse to a theme, you'll see that the search results stay in the DOM as well. This isn't going to change until the Theme Directory theme is rewritten from scratch in something other than Backbone. The only options available to fix this currently is to remove the JS, which we won't be doing at this time. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 17 05:07:12 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 17 Dec 2021 05:07:12 -0000 Subject: [wp-meta] [Making WordPress.org] #5825: Pledges Page Design Issue In-Reply-To: <056.86184e8057449c2be039e419a68bce94@wordpress.org> References: <056.86184e8057449c2be039e419a68bce94@wordpress.org> Message-ID: <071.9495fbb367eae5a6487c6d3c1883986b@wordpress.org> #5825: Pledges Page Design Issue -------------------------------------------------+------------------------- Reporter: mvsavaliya24 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: needs-patch dev-feedback has- | screenshots needs-design-feedback | -------------------------------------------------+------------------------- Comment (by dd32): > => Image hover effect is not proper on the Pledged Contributors profile Similar to #4918. > => When I clicked in Search Box, the size of the search box is get reduced > => When I clicked in the Email Address box under the Email updates, Email address box size gets reduced I can't duplicate these. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 17 05:07:20 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 17 Dec 2021 05:07:20 -0000 Subject: [wp-meta] [Making WordPress.org] #5825: Pledges Page Design Issue In-Reply-To: <056.86184e8057449c2be039e419a68bce94@wordpress.org> References: <056.86184e8057449c2be039e419a68bce94@wordpress.org> Message-ID: <071.8d5b4b5cb22794faf0c2bafa5dab24df@wordpress.org> #5825: Pledges Page Design Issue -------------------------------------------------+------------------------- Reporter: mvsavaliya24 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Make (Get Involved) / P2 | Resolution: Keywords: needs-patch dev-feedback has- | screenshots needs-design-feedback | -------------------------------------------------+------------------------- Changes (by dd32): * component: General => Make (Get Involved) / P2 -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 17 05:07:57 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Fri, 17 Dec 2021 05:07:57 +0000 (UTC) Subject: [wp-meta] [11386] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-breathe: Make: Disable the Gravbatar hover oval shaped previews again. Message-ID: <20211217050757.6FFD11B00553@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Fri Dec 17 05:08:02 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 17 Dec 2021 05:08:02 -0000 Subject: [wp-meta] [Making WordPress.org] #5825: Pledges Page Design Issue In-Reply-To: <056.86184e8057449c2be039e419a68bce94@wordpress.org> References: <056.86184e8057449c2be039e419a68bce94@wordpress.org> Message-ID: <071.d8aeab8ca5a133f82c3564d658a547a7@wordpress.org> #5825: Pledges Page Design Issue -------------------------------------------------+------------------------- Reporter: mvsavaliya24 | Owner: dd32 Type: enhancement | Status: closed Priority: normal | Milestone: Component: Make (Get Involved) / P2 | Resolution: fixed Keywords: needs-patch dev-feedback has- | screenshots needs-design-feedback | -------------------------------------------------+------------------------- Changes (by dd32): * owner: (none) => dd32 * status: new => closed * resolution: => fixed Comment: In [changeset:"11386" 11386]: {{{ #!CommitTicketReference repository="" revision="11386" Make: Disable the Gravbatar hover oval shaped previews again. See #4918. Fixes #5825. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 17 05:08:02 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 17 Dec 2021 05:08:02 -0000 Subject: [wp-meta] [Making WordPress.org] #4918: Gravatar doesn't retain shape on hover on o2 sites In-Reply-To: <053.8d1920c228acd72b2947727abe0cafc2@wordpress.org> References: <053.8d1920c228acd72b2947727abe0cafc2@wordpress.org> Message-ID: <068.f01ec93f62785362788d0e71466e703a@wordpress.org> #4918: Gravatar doesn't retain shape on hover on o2 sites -----------------------------------------+--------------------- Reporter: ankitmaru | Owner: dd32 Type: defect | Status: closed Priority: low | Milestone: Component: Make (Get Involved) / P2 | Resolution: fixed Keywords: has-screenshots needs-patch | -----------------------------------------+--------------------- Comment (by dd32): In [changeset:"11386" 11386]: {{{ #!CommitTicketReference repository="" revision="11386" Make: Disable the Gravbatar hover oval shaped previews again. See #4918. Fixes #5825. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 17 06:07:10 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Fri, 17 Dec 2021 06:07:10 +0000 (UTC) Subject: [wp-meta] [11387] sites/trunk/jobs.wordpress.net/public_html/wp-content/themes/jobswp/content-post-job.php: Jobs: Correct the FAQ link on the job submission confirm screen. Message-ID: <20211217060710.EFD201B00553@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Fri Dec 17 09:39:42 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 17 Dec 2021 09:39:42 -0000 Subject: [wp-meta] [Making WordPress.org] #5984: Display unwanted image on the Block Editor Handbook Message-ID: <052.9d6ddaca723621e2aa103a7addd4870a@wordpress.org> #5984: Display unwanted image on the Block Editor Handbook -------------------------+------------------------------------------------- Reporter: rima1889 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Keywords: needs-docs has-dev-note has- | screenshots -------------------------+------------------------------------------------- I've found on the **Block Editor Handbook** display image of "Code is Poetry" on the description. Reference: https://developer.wordpress.org/block-editor/reference-guides/packages /packages-shortcode/ https://developer.wordpress.org/block-editor/reference-guides/packages /packages-api-fetch/https://developer.wordpress.org/block-editor /reference-guides/packages/packages-compose/ [[Image(https://www.awesomescreenshot.com/image/18734425?key=995892f28bdbb23628ab05c2dc89ee0e)]] -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 17 10:10:12 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 17 Dec 2021 10:10:12 -0000 Subject: [wp-meta] [Making WordPress.org] #5984: Display unwanted image on the Block Editor Handbook In-Reply-To: <052.9d6ddaca723621e2aa103a7addd4870a@wordpress.org> References: <052.9d6ddaca723621e2aa103a7addd4870a@wordpress.org> Message-ID: <067.969998c7bb8d57696314d0d0e1353f0b@wordpress.org> #5984: Display unwanted image on the Block Editor Handbook -----------------------------------------------------+--------------------- Reporter: rima1889 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: needs-docs has-dev-note has-screenshots | -----------------------------------------------------+--------------------- Comment (by Otto42): Not an accident, it's in the actual source documentation: https://github.com/WordPress/gutenberg/blob/trunk/packages/compose/README.md https://github.com/WordPress/gutenberg/blob/trunk/packages/shortcode/README.md -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 17 17:35:06 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 17 Dec 2021 17:35:06 -0000 Subject: [wp-meta] [Making WordPress.org] #5985: Use caption in ALT text for single photos Message-ID: <053.b9d799e6bcf8e295b94fa1ca06f09776@wordpress.org> #5985: Use caption in ALT text for single photos -----------------------------+------------------------- Reporter: alexstine | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Photo Directory | Keywords: needs-patch -----------------------------+------------------------- Is it possible to use the image caption as image ALT text? If you view a single image like this one: https://wordpress.org/photos/photo/44161bb082/#main Google Chrome tries to announce to screen readers what the image appears to be but the caption gives a better description. Temporarily, should use the caption for ALT text until ALT text can be provided on upload. I tried to track down the theme to make a patch, but it seems it is not open sourced: https://meta.svn.wordpress.org/sites/trunk/wordpress.org/public_html/wp- content/themes/pub/ -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 17 17:43:27 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 17 Dec 2021 17:43:27 -0000 Subject: [wp-meta] [Making WordPress.org] #5985: Accessibility: Use caption in ALT text for single photos (was: Use caption in ALT text for single photos) In-Reply-To: <053.b9d799e6bcf8e295b94fa1ca06f09776@wordpress.org> References: <053.b9d799e6bcf8e295b94fa1ca06f09776@wordpress.org> Message-ID: <068.f4eced93b183b769a4cf6c5c2d75b911@wordpress.org> #5985: Accessibility: Use caption in ALT text for single photos -----------------------------+--------------------- Reporter: alexstine | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Photo Directory | Resolution: Keywords: needs-patch | -----------------------------+--------------------- -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 17 17:44:11 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 17 Dec 2021 17:44:11 -0000 Subject: [wp-meta] [Making WordPress.org] #5986: Improve image markup Message-ID: <058.169324b5420ab8c5ad18b75a764ca3d1@wordpress.org> #5986: Improve image markup -----------------------------+----------------------------- Reporter: jonoaldersonwp | Owner: (none) Type: defect | Status: new Priority: high | Milestone: Component: Photo Directory | Keywords: performance seo -----------------------------+----------------------------- Images in grid displays like the one on https://wordpress.org/photos/ and https://wordpress.org/photos/photo/ should: - Use `loading="lazy"` and `decoding="async"` - Use an `srcset` attribute, providing multiple `w` variants, targeting 1x, 1.5x, 2x variations. - Use a `sizes `attribute describing the optimal sizing (optionally using a simplified value of `295px`). - Use an `alt` attribute of the image caption. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 17 17:45:05 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 17 Dec 2021 17:45:05 -0000 Subject: [wp-meta] [Making WordPress.org] #5986: Improve image markup In-Reply-To: <058.169324b5420ab8c5ad18b75a764ca3d1@wordpress.org> References: <058.169324b5420ab8c5ad18b75a764ca3d1@wordpress.org> Message-ID: <073.d4ee5a26d921a4c35b09f8d79d49806a@wordpress.org> #5986: Improve image markup -----------------------------+--------------------- Reporter: jonoaldersonwp | Owner: (none) Type: defect | Status: new Priority: high | Milestone: Component: Photo Directory | Resolution: Keywords: performance seo | -----------------------------+--------------------- Description changed by jonoaldersonwp: Old description: > Images in grid displays like the one on https://wordpress.org/photos/ and > https://wordpress.org/photos/photo/ should: > > - Use `loading="lazy"` and `decoding="async"` > - Use an `srcset` attribute, providing multiple `w` variants, targeting > 1x, 1.5x, 2x variations. > - Use a `sizes `attribute describing the optimal sizing (optionally using > a simplified value of `295px`). > - Use an `alt` attribute of the image caption. New description: Images in grid displays like the one on https://wordpress.org/photos/ and https://wordpress.org/photos/photo/ and https://wordpress.org/photos/author/anariel-design/ should: - Use `loading="lazy"` and `decoding="async"` - Use an `srcset` attribute, providing multiple `w` variants, targeting 1x, 1.5x, 2x variations. - Use a `sizes `attribute describing the optimal sizing (optionally using a simplified value of `295px`). - Use an `alt` attribute of the image caption. -- -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 17 22:00:58 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Fri, 17 Dec 2021 22:00:58 +0000 (UTC) Subject: [wp-meta] [11388] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg: WordPress.org Base Theme: Enable new global header/footer behind flag. Message-ID: <20211217220058.4024A1B0039F@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Sat Dec 18 17:44:31 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 18 Dec 2021 17:44:31 -0000 Subject: [wp-meta] [Making WordPress.org] #5864: WordPress.org/about page broken link to fork of b2/cafelog In-Reply-To: <055.092017f9aacd07ec7654e751b59cc42c@wordpress.org> References: <055.092017f9aacd07ec7654e751b59cc42c@wordpress.org> Message-ID: <070.e7c8ec5bc0432e53b0047c773f8acc94@wordpress.org> #5864: WordPress.org/about page broken link to fork of b2/cafelog --------------------------------+--------------------- Reporter: corenominal | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: WordPress.org Site | Resolution: Keywords: | --------------------------------+--------------------- Changes (by hasanuzzamanshamim): * Attachment "5864.diff" added. Patch created, Correct URL found from https://ma.tt/2021/05/wordpress-18/ -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sat Dec 18 17:46:08 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 18 Dec 2021 17:46:08 -0000 Subject: [wp-meta] [Making WordPress.org] #5864: WordPress.org/about page broken link to fork of b2/cafelog In-Reply-To: <055.092017f9aacd07ec7654e751b59cc42c@wordpress.org> References: <055.092017f9aacd07ec7654e751b59cc42c@wordpress.org> Message-ID: <070.55c571192c34923c5e50d82966af8fdc@wordpress.org> #5864: WordPress.org/about page broken link to fork of b2/cafelog --------------------------------+--------------------- Reporter: corenominal | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: WordPress.org Site | Resolution: Keywords: has-patch | --------------------------------+--------------------- Changes (by hasanuzzamanshamim): * keywords: => has-patch -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sat Dec 18 19:24:19 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 18 Dec 2021 19:24:19 -0000 Subject: [wp-meta] [Making WordPress.org] #2129: bbPress.org forum profiles should have a link to the WP.org profile In-Reply-To: <050.985cd3a49c540bf3d52523ab88155de5@wordpress.org> References: <050.985cd3a49c540bf3d52523ab88155de5@wordpress.org> Message-ID: <065.4577323bc81672179ab736118f51bc44@wordpress.org> #2129: bbPress.org forum profiles should have a link to the WP.org profile ----------------------------------------+--------------------- Reporter: netweb | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: buddypress.org | Resolution: Keywords: needs-patch good-first-bug | ----------------------------------------+--------------------- Changes (by hasanuzzamanshamim): * Attachment "2129.diff" added. WordPress.org profile linked for forum profile. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sat Dec 18 19:26:00 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 18 Dec 2021 19:26:00 -0000 Subject: [wp-meta] [Making WordPress.org] #2129: bbPress.org forum profiles should have a link to the WP.org profile In-Reply-To: <050.985cd3a49c540bf3d52523ab88155de5@wordpress.org> References: <050.985cd3a49c540bf3d52523ab88155de5@wordpress.org> Message-ID: <065.65fdd3a665a59bb4a2e6df556a0cb048@wordpress.org> #2129: bbPress.org forum profiles should have a link to the WP.org profile --------------------------------------+--------------------- Reporter: netweb | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: buddypress.org | Resolution: Keywords: good-first-bug has-patch | --------------------------------------+--------------------- Changes (by hasanuzzamanshamim): * keywords: needs-patch good-first-bug => good-first-bug has-patch -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 20 00:55:50 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 20 Dec 2021 00:55:50 -0000 Subject: [wp-meta] [Making WordPress.org] #5984: Display unwanted image on the Block Editor Handbook In-Reply-To: <052.9d6ddaca723621e2aa103a7addd4870a@wordpress.org> References: <052.9d6ddaca723621e2aa103a7addd4870a@wordpress.org> Message-ID: <067.e96d3226427ca3d9a78f6e410417034b@wordpress.org> #5984: Display unwanted image on the Block Editor Handbook -----------------------------------------------------+--------------------- Reporter: rima1889 | Owner: dd32 Type: enhancement | Status: closed Priority: normal | Milestone: Component: General | Resolution: fixed Keywords: needs-docs has-dev-note has-screenshots | -----------------------------------------------------+--------------------- Changes (by dd32): * owner: (none) => dd32 * status: new => closed * resolution: => fixed Comment: In [changeset:"11389" 11389]: {{{ #!CommitTicketReference repository="" revision="11389" Developer: Block Handbook: Strip the Gutenberg packages `Code is Poetry` footer from the import to developer.wordpress.org. See https://github.com/WordPress/gutenberg/blob/trunk/packages/README.md Props rima1889 for reporting. Fixes #5984. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 20 00:55:45 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 20 Dec 2021 00:55:45 +0000 (UTC) Subject: [wp-meta] [11389] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-developer/inc/import-block-editor.php: Developer: Block Handbook: Strip the Gutenberg packages `Code is Poetry` footer from the import to developer.wordpress.org. Message-ID: <20211220005545.BB7BC1B00420@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon Dec 20 00:58:41 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 20 Dec 2021 00:58:41 -0000 Subject: [wp-meta] [Making WordPress.org] #4861: Themes Trac doesn't like the Browser In-Reply-To: <055.b1967b1e66c33f6ad6c7831a21d90dea@wordpress.org> References: <055.b1967b1e66c33f6ad6c7831a21d90dea@wordpress.org> Message-ID: <070.b2e656afc6b380af6c9559c1545a226f@wordpress.org> #4861: Themes Trac doesn't like the Browser ---------------------------------------------+--------------------- Reporter: wpamitkumar | Owner: (none) Type: defect | Status: closed Priority: lowest | Milestone: Component: Trac | Resolution: fixed Keywords: has-screenshots pending-systems | ---------------------------------------------+--------------------- Changes (by dd32): * status: new => closed * resolution: => fixed Comment: Requests to the Themes index on themes.trac now redirects to w.org/themes: {{{ $ curl -Is https://themes.trac.wordpress.org/browser/ | grep ^location location: https://wordpress.org/themes/ }}} This is what we do for Plugins, and is better than the 502. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 20 07:21:54 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 20 Dec 2021 07:21:54 +0000 (UTC) Subject: [wp-meta] [11390] sites/trunk/wordpress.org/public_html/wp-content/plugins: Handbooks: Table of Contents: The first `` element on the page may not be the one we wish to duplicate, if we've removed a HTML-only heading from the content. Message-ID: <20211220072154.7A54F1B001A4@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon Dec 20 14:25:46 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 20 Dec 2021 14:25:46 +0000 (UTC) Subject: [wp-meta] [11391] sites/trunk/common/includes/slack/announce/config.php: Slack: Add shetheliving to #performance announce. Message-ID: <20211220142546.7ADC11B00405@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon Dec 20 15:01:33 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 20 Dec 2021 15:01:33 -0000 Subject: [wp-meta] [Making WordPress.org] #5987: Add images to RSS Message-ID: <057.47df870bf13edac3b910522b06eff27c@wordpress.org> #5987: Add images to RSS -----------------------------+-------------------- Reporter: topher1kenobe | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Photo Directory | Keywords: -----------------------------+-------------------- I'd love to have the images attached to the RSS feeds on the site, so I can follow a particular creator, like this: https://wordpress.org/photos/author/topher1kenobe/feed/ And even more valuable, follow search results like this: https://wordpress.org/photos/feed/?s=grass -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 20 23:34:13 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 20 Dec 2021 23:34:13 -0000 Subject: [wp-meta] [Making WordPress.org] #5988: Contribution History for Photos Message-ID: <054.5e6548e82fcaec54f3bd1c28ca2d1e9b@wordpress.org> #5988: Contribution History for Photos -------------------------+-------------------- Reporter: lukecarbis | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Profiles | Keywords: -------------------------+-------------------- Your WordPress.org profile should include your Photos contribution history, including: - A contribution badge - New photos appear in the Activity Feed - A new Photos sidebar section below Plugins and Themes -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 20 23:34:38 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 20 Dec 2021 23:34:38 -0000 Subject: [wp-meta] [Making WordPress.org] #5988: Contribution History for Photos In-Reply-To: <054.5e6548e82fcaec54f3bd1c28ca2d1e9b@wordpress.org> References: <054.5e6548e82fcaec54f3bd1c28ca2d1e9b@wordpress.org> Message-ID: <069.84deb0a4b0f436d7c0ac3d62e9f3f257@wordpress.org> #5988: Contribution History for Photos -------------------------+--------------------- Reporter: lukecarbis | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Profiles | Resolution: Keywords: | -------------------------+--------------------- Changes (by lukecarbis): * Attachment "Screen Shot 2021-12-21 at 09.30.35.png" added. Mockup of a photos badge using the 'camera' dashicon. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 20 23:39:04 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 20 Dec 2021 23:39:04 -0000 Subject: [wp-meta] [Making WordPress.org] #5988: Contribution History for Photos In-Reply-To: <054.5e6548e82fcaec54f3bd1c28ca2d1e9b@wordpress.org> References: <054.5e6548e82fcaec54f3bd1c28ca2d1e9b@wordpress.org> Message-ID: <069.55f8ebae7362d7706cf0efe803732266@wordpress.org> #5988: Contribution History for Photos -------------------------+------------------------ Reporter: lukecarbis | Owner: (none) Type: enhancement | Status: closed Priority: normal | Milestone: Component: Profiles | Resolution: duplicate Keywords: | -------------------------+------------------------ Changes (by dd32): * status: new => closed * resolution: => duplicate Comment: Duplicate of #5981. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 21 01:03:30 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 21 Dec 2021 01:03:30 -0000 Subject: [wp-meta] [Making WordPress.org] #5989: Add strikethrough support to Block Editor handbook Message-ID: <048.6e63422434a7be0ba2f571c3cb2f4768@wordpress.org> #5989: Add strikethrough support to Block Editor handbook ---------------------+-------------------- Reporter: mkaz | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: General | Keywords: ---------------------+-------------------- We want the markdown in block editor handbook to support double tildes for strikethrough. https://github.com/WordPress/wordpress.org/pull/47 -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 21 01:43:37 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 21 Dec 2021 01:43:37 -0000 Subject: [wp-meta] [Making WordPress.org] #5989: Add strikethrough support to Block Editor handbook In-Reply-To: <048.6e63422434a7be0ba2f571c3cb2f4768@wordpress.org> References: <048.6e63422434a7be0ba2f571c3cb2f4768@wordpress.org> Message-ID: <063.87d23c20358c8507def143c7449d2a29@wordpress.org> #5989: Add strikethrough support to Block Editor handbook -----------------------+----------------------- Reporter: mkaz | Owner: dd32 Type: defect | Status: accepted Priority: normal | Milestone: Component: Handbooks | Resolution: Keywords: has-patch | -----------------------+----------------------- Changes (by dd32): * owner: (none) => dd32 * status: new => accepted * component: General => Handbooks -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 21 01:50:11 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 21 Dec 2021 01:50:11 +0000 (UTC) Subject: [wp-meta] [11392] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-developer/inc/import-block-editor.php: Handbooks: Block Editor: Apply strikethrough markdown formatting, as MarkdownExtra doesn't support it. Message-ID: <20211221015011.EC5A91B004E3@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Tue Dec 21 01:50:17 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 21 Dec 2021 01:50:17 -0000 Subject: [wp-meta] [Making WordPress.org] #5989: Add strikethrough support to Block Editor handbook In-Reply-To: <048.6e63422434a7be0ba2f571c3cb2f4768@wordpress.org> References: <048.6e63422434a7be0ba2f571c3cb2f4768@wordpress.org> Message-ID: <063.f52ad8dbc405695648b6ef1d6237f9d9@wordpress.org> #5989: Add strikethrough support to Block Editor handbook -----------------------+--------------------- Reporter: mkaz | Owner: dd32 Type: defect | Status: closed Priority: normal | Milestone: Component: Handbooks | Resolution: fixed Keywords: has-patch | -----------------------+--------------------- Changes (by dd32): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"11392" 11392]: {{{ #!CommitTicketReference repository="" revision="11392" Handbooks: Block Editor: Apply strikethrough markdown formatting, as MarkdownExtra doesn't support it. Props mkaz. Closes https://github.com/WordPress/wordpress.org/pull/47. Fixes #5989. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 21 09:05:21 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 21 Dec 2021 09:05:21 -0000 Subject: [wp-meta] [Making WordPress.org] #5983: Define faces? In-Reply-To: <057.1fa0600d34287d8dc5d55fcc16f384c4@wordpress.org> References: <057.1fa0600d34287d8dc5d55fcc16f384c4@wordpress.org> Message-ID: <072.589b9fb57b34bcf76d1cd6d4dccae1c2@wordpress.org> #5983: Define faces? -----------------------------+-------------------------- Reporter: topher1kenobe | Owner: coffee2code Type: defect | Status: accepted Priority: normal | Milestone: Component: Photo Directory | Resolution: Keywords: | -----------------------------+-------------------------- Changes (by coffee2code): * owner: (none) => coffee2code * status: new => accepted -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 21 09:06:55 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 21 Dec 2021 09:06:55 -0000 Subject: [wp-meta] [Making WordPress.org] #5983: Define faces? In-Reply-To: <057.1fa0600d34287d8dc5d55fcc16f384c4@wordpress.org> References: <057.1fa0600d34287d8dc5d55fcc16f384c4@wordpress.org> Message-ID: <072.dd775dec477704b857949abf15e744a4@wordpress.org> #5983: Define faces? -----------------------------+-------------------------- Reporter: topher1kenobe | Owner: coffee2code Type: defect | Status: closed Priority: normal | Milestone: Component: Photo Directory | Resolution: fixed Keywords: | -----------------------------+-------------------------- Changes (by coffee2code): * status: accepted => closed * resolution: => fixed Comment: Fixed in [18107-dotorg]: > Photo Directory, Rejection/Uploads: Specify identifiable _human_ faces as not being permitted. > > Props topher1kenobe. > Fixes #5983. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 21 23:50:23 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 21 Dec 2021 23:50:23 -0000 Subject: [wp-meta] [Making WordPress.org] #5990: Profiles advertise broken oembed endpoints Message-ID: <054.f68fc809d762848f81c98230a1b0fe42@wordpress.org> #5990: Profiles advertise broken oembed endpoints ------------------------+-------------------- Reporter: tellyworth | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Profiles | Keywords: ------------------------+-------------------- Profiles currently advertise two oembed endpoints: {{{ }}} Neither of these seem to work. Both produce output like this, regardless of the URL parameter: {{{ {"code":"oembed_invalid_url","message":"Not Found","data":{"status":404}} }}} Ideally, we should make oembed work. Worst case, stop advertising broken links. Loosely related: #613. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 22 02:08:56 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 22 Dec 2021 02:08:56 +0000 (UTC) Subject: [wp-meta] [11393] sites/trunk/wordpress.org/public_html/wp-content/plugins/official-wordpress-events: Official WordPress Events: Upgrade the Meetup.com client to query via a new GraphQL API, as the REST API is being deprecated by meetup.com. Message-ID: <20211222020856.89EEA1B004BE@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed Dec 22 02:35:20 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 22 Dec 2021 02:35:20 +0000 (UTC) Subject: [wp-meta] [11394] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-login/functions.php: Login: Disable the login language selector using the new filter. Message-ID: <20211222023520.5C6721B004BE@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed Dec 22 03:18:57 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 22 Dec 2021 03:18:57 +0000 (UTC) Subject: [wp-meta] [11395] sites/trunk/wordpress.org/public_html/wp-content/plugins/official-wordpress-events/meetup/class-meetup-client.php: Official WordPress Events: Ignore the correct lat/lng/lon fields for Online Events. Message-ID: <20211222031857.224DE1B004BE@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed Dec 22 06:44:03 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 22 Dec 2021 06:44:03 +0000 (UTC) Subject: [wp-meta] [11396] sites/trunk/wordpress.org/public_html/wp-content/plugins/support-helphub/inc/handbook-toc: Support Forums: Restore the HelpHub TOC on pages, rather than just using it for HelpHub content. Message-ID: <20211222064403.DAECE1B003A7@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed Dec 22 07:06:37 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 22 Dec 2021 07:06:37 -0000 Subject: [wp-meta] [Making WordPress.org] #5991: Handbook TOC can get confused with badly nested headers Message-ID: <048.017c22fd9d812ea57e814d085d48135b@wordpress.org> #5991: Handbook TOC can get confused with badly nested headers -----------------------+-------------------- Reporter: dd32 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Handbooks | Keywords: -----------------------+-------------------- The Handbook TOC code is used in Handbooks and in HelpHub. Today I ran into this article which has a bad TOC: https://wordpress.org/support/article/using-filezilla/ {{{

Why would I want to download FileZilla?

Setting Up the Options

Connecting

Troubleshooting

Resources

}}} which results in a TOC of: {{{

Topics

  • Setting Up the Options
  • Connecting
  • Troubleshooting
  • Resources
    • }}} Obviously the structure of the headings in the source is incorrect, but we can probably account for this in the TOC plugin -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 22 07:47:51 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 22 Dec 2021 07:47:51 +0000 (UTC) Subject: [wp-meta] [11397] sites/trunk/common/includes/slack/announce/config.php: Slack: Grant Vlad `/here` for #polyglots. Message-ID: <20211222074751.799DE1B003A7@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed Dec 22 09:03:45 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 22 Dec 2021 09:03:45 -0000 Subject: [wp-meta] [Making WordPress.org] #5971: Plugin Directory: Custom Block Names not being listed right In-Reply-To: <051.5f0920c7082dd400163332aa9ca4044a@wordpress.org> References: <051.5f0920c7082dd400163332aa9ca4044a@wordpress.org> Message-ID: <066.858085110b89cada06d76395f4d3c15e@wordpress.org> #5971: Plugin Directory: Custom Block Names not being listed right ------------------------------+--------------------- Reporter: Ipstenu | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+--------------------- Comment (by hztyfoon): I've got this issue too. Plugin link : https://wordpress.org/plugins /essential-blocks It used to show like https://prnt.sc/22rwmxp But after I've included `block.json` for all the blocks in the last release and now the lists totally disappeared. Can anyone tell me what I'm doing wrong here or how can I make it so that all the blocks will show in that list correctly? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 22 09:04:01 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 22 Dec 2021 09:04:01 +0000 (UTC) Subject: [wp-meta] [11398] sites/trunk/wordpress.org/public_html/wp-content/plugins/official-wordpress-events/meetup/class-meetup-client.php: Official WordPress Events: Meetup Class: Fix some bugs, make some tweaks, add some compatibility. Message-ID: <20211222090401.B5CA21B003A7@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed Dec 22 09:44:34 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 22 Dec 2021 09:44:34 +0000 (UTC) Subject: [wp-meta] [11399] sites/trunk/wordpress.org/public_html/wp-content/plugins/official-wordpress-events: Official WordPress Events: Sync Meetup_Client with upstream WordCamp client, remove milliseconds from API. Message-ID: <20211222094434.D45641B003A7@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed Dec 22 14:33:56 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 22 Dec 2021 14:33:56 -0000 Subject: [wp-meta] [Making WordPress.org] #5992: Currenty if you as PTE/GTE reject a translation it is only deleted from one branch (default or dev) Message-ID: <054.941807e789502dbbb3590eea34e84f06@wordpress.org> #5992: Currenty if you as PTE/GTE reject a translation it is only deleted from one branch (default or dev) --------------------------------------+-------------------- Reporter: psmits1567 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Translate Site & Plugins | Keywords: --------------------------------------+-------------------- With the current version of GlotPress, if you reject a translation as PTE/GTE, then this record is only rejected within one branch (default or dev). That causes double work to remove it from the other branch (default or dev) as well. It would be nice when a translation is rejected, the same original with exactly the SAME translation should also be rejected within the other branch. When a GTE/PTE adds a translation it is copied to the other branch as well, so why not reject a record in the other branch as well (provided the translation is exactly the same) -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 22 15:44:55 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 22 Dec 2021 15:44:55 -0000 Subject: [wp-meta] [Making WordPress.org] #5992: Currenty if you as PTE/GTE reject a translation it is only deleted from one branch (default or dev) In-Reply-To: <054.941807e789502dbbb3590eea34e84f06@wordpress.org> References: <054.941807e789502dbbb3590eea34e84f06@wordpress.org> Message-ID: <069.dc549e5c6bbfb2a86bb1d40b820c5616@wordpress.org> #5992: Currenty if you as PTE/GTE reject a translation it is only deleted from one branch (default or dev) --------------------------------------+--------------------- Reporter: psmits1567 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Translate Site & Plugins | Resolution: Keywords: | --------------------------------------+--------------------- Comment (by NekoJonez): Shouldn't we ALSO report this upstream? For GlotPress too? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 22 16:25:32 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 22 Dec 2021 16:25:32 -0000 Subject: [wp-meta] [Making WordPress.org] #5992: Currenty if you as PTE/GTE reject a translation it is only deleted from one branch (default or dev) In-Reply-To: <054.941807e789502dbbb3590eea34e84f06@wordpress.org> References: <054.941807e789502dbbb3590eea34e84f06@wordpress.org> Message-ID: <069.108c3b01b16c462e2879bbca8dc3c52e@wordpress.org> #5992: Currenty if you as PTE/GTE reject a translation it is only deleted from one branch (default or dev) --------------------------------------+--------------------- Reporter: psmits1567 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Translate Site & Plugins | Resolution: Keywords: | --------------------------------------+--------------------- Comment (by psmits1567): Did report it in glotpress channel, but the tag should notify the glotpress team as well -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 22 18:17:43 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 22 Dec 2021 18:17:43 +0000 (UTC) Subject: [wp-meta] [11400] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-learn-2020: WordPress.org Learn: Sync with GitHub Message-ID: <20211222181743.6035C1B003A7@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed Dec 22 18:19:10 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 22 Dec 2021 18:19:10 +0000 (UTC) Subject: [wp-meta] [11401] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-breathe/style.css: Breathe: Unset styles that shouldn't affect the 2021 global header. Message-ID: <20211222181910.E17B31B003A7@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed Dec 22 18:22:01 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 22 Dec 2021 18:22:01 +0000 (UTC) Subject: [wp-meta] [11402] sites/trunk: Theme: Enable testing new header on w.org sandboxes Message-ID: <20211222182201.2A30D1B003A7@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed Dec 22 19:12:52 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 22 Dec 2021 19:12:52 -0000 Subject: [wp-meta] [Making WordPress.org] #5993: Plugin Directory: Add checkbox on submission page Message-ID: <051.f8a46a5eaebfdbc4cdb24d6938f8f564@wordpress.org> #5993: Plugin Directory: Add checkbox on submission page ------------------------------+-------------------- Reporter: Ipstenu | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Keywords: ------------------------------+-------------------- Add a checkbox to the submission page that requires confirmation the submitter is: 1. Submitting their own work 2. Agrees to follow the developer guidelines It can link to https://developer.wordpress.org/plugins/wordpress-org /detailed-plugin-guidelines/ for edification. Something like... {{{ I confirm this plugin is my own, original, work, and complies to all the Plugin Developer Guidelines. }}} This will act, in part, as a self-protection for people who later argue they didn't agree to the guidelines. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 23 06:32:14 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 23 Dec 2021 06:32:14 -0000 Subject: [wp-meta] [Making WordPress.org] #5993: Plugin Directory: Add checkbox on submission page In-Reply-To: <051.f8a46a5eaebfdbc4cdb24d6938f8f564@wordpress.org> References: <051.f8a46a5eaebfdbc4cdb24d6938f8f564@wordpress.org> Message-ID: <066.4693769703fe6c600d7a2d0728568e56@wordpress.org> #5993: Plugin Directory: Add checkbox on submission page ------------------------------+--------------------- Reporter: Ipstenu | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+--------------------- Changes (by dd32): * Attachment "Screen Shot 2021-12-23 at 4.31.48 pm.png" added. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 23 06:32:17 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 23 Dec 2021 06:32:17 -0000 Subject: [wp-meta] [Making WordPress.org] #5993: Plugin Directory: Add checkbox on submission page In-Reply-To: <051.f8a46a5eaebfdbc4cdb24d6938f8f564@wordpress.org> References: <051.f8a46a5eaebfdbc4cdb24d6938f8f564@wordpress.org> Message-ID: <066.3c2c1ffe382df05d3cc94ea5e1aeb84c@wordpress.org> #5993: Plugin Directory: Add checkbox on submission page ------------------------------+--------------------- Reporter: Ipstenu | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+--------------------- Comment (by dd32): After chatting with others, the wording here might open more questions from some that doesn't quite meet the intention, it might seem nitpicky, but when being overly explicit it seems worth it. > I confirm this plugin is my own, original, work - "It's mine, but I forked JangaBlocks! It's a new work and I've given attribution, but it's not entirely my original work?" - "I wrote this plugin, but it uses a variety of CC0 licensed works that I didn't author?" - "Oh yes I clicked that, because it's my plugin, but I just wanted you to review it so we could get autoupdates on our site!" (okay, this is stretching it.. but..) - "The plugin is written by others at the company.. not me? I'm just the Open Source rep!" I went with a more generic text on the [https://wordpress.org/themes/upload/ Themes upload page]: > [] I have permission to upload this theme to WordPress.org for others to use and share. > [] The theme complies with all Theme Guidelines. > [] The theme, and all included assets, are licenced as GPL or are under a GPL compatible license. Perhaps for consistency we can just tweak that for plugins a little? > [] I have read the Frequently Asked Questions. > [] This plugin complies with all Plugin Guidelines. > [] I have permission to upload this plugin to WordPress.org for others to use and share. > [] This plugin, all included libraries, and other included assets are licenced as GPL or are under a GPL compatible license. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 23 06:32:55 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 23 Dec 2021 06:32:55 -0000 Subject: [wp-meta] [Making WordPress.org] #5993: Plugin Directory: Add checkbox on submission page In-Reply-To: <051.f8a46a5eaebfdbc4cdb24d6938f8f564@wordpress.org> References: <051.f8a46a5eaebfdbc4cdb24d6938f8f564@wordpress.org> Message-ID: <066.463d204dc1a76d4c776de5d131d253ab@wordpress.org> #5993: Plugin Directory: Add checkbox on submission page ------------------------------+--------------------- Reporter: Ipstenu | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+--------------------- Changes (by dd32): * Attachment "Screen Shot 2021-12-23 at 4.32.40 pm.png" added. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 23 15:56:05 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 23 Dec 2021 15:56:05 -0000 Subject: [wp-meta] [Making WordPress.org] #5994: The main RSS feed is empty Message-ID: <057.afb9b8953c43c3db140d226ba9b1ecf6@wordpress.org> #5994: The main RSS feed is empty -----------------------------+-------------------- Reporter: topher1kenobe | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Photo Directory | Keywords: -----------------------------+-------------------- The page source links to https://wordpress.org/photos/feed/, but there are no items in that feed at all. I think there should be. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 23 16:45:26 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 23 Dec 2021 16:45:26 -0000 Subject: [wp-meta] [Making WordPress.org] #5995: Theme Block Pattern Demo Message-ID: <053.8512d65ae2ee97b57e13f45308e2fe6f@wordpress.org> #5995: Theme Block Pattern Demo -----------------------------+-------------------- Reporter: courane01 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Theme Directory | Keywords: -----------------------------+-------------------- It would be delightful when browsing themes in the directory to get a sense of all block patterns that come with a theme. Can this be improved via the theme demo interface? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 23 16:50:13 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 23 Dec 2021 16:50:13 -0000 Subject: [wp-meta] [Making WordPress.org] #5995: Theme Block Pattern Demo In-Reply-To: <053.8512d65ae2ee97b57e13f45308e2fe6f@wordpress.org> References: <053.8512d65ae2ee97b57e13f45308e2fe6f@wordpress.org> Message-ID: <068.8e82f6aa362f5c9eaae7ca0b4b70cf94@wordpress.org> #5995: Theme Block Pattern Demo -----------------------------+--------------------- Reporter: courane01 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Theme Directory | Resolution: Keywords: | -----------------------------+--------------------- Comment (by kafleg): Isn't this is similar with this tickets, htttps://meta.trac.wordpress.org/ticket/30 https://meta.trac.wordpress.org/ticket/969 -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 23 16:50:19 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 23 Dec 2021 16:50:19 -0000 Subject: [wp-meta] [Making WordPress.org] #5996: Theme Repo - Customizer likeness phased out Message-ID: <053.cfc64af919e7fa5a201cfe8159f1b919@wordpress.org> #5996: Theme Repo - Customizer likeness phased out -----------------------------+-------------------- Reporter: courane01 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Theme Directory | Keywords: -----------------------------+-------------------- As block themes come to the theme repo, can we revise the left panel in theme demos to look less like the Customizer? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 23 17:36:27 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 23 Dec 2021 17:36:27 -0000 Subject: [wp-meta] [Making WordPress.org] #5997: Photo Directory: Submission form delivering errors Message-ID: <055.ff178cc9ff8187865a9a6fe7234f677a@wordpress.org> #5997: Photo Directory: Submission form delivering errors -----------------------------+-------------------- Reporter: maverick3x6 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Photo Directory | Keywords: -----------------------------+-------------------- Hey folks. I've been trying to submit photos to the photo directory. After I complete the form and hit submit, the page loads (I'm assuming it's uploading my photo), and then I'm delivered to this error: {{{ ERR_HTTP2_PING_FAILED The webpage at https://wordpress.org/photos/wp-admin/admin-ajax.php might be temporarily down or it may have moved permanently to a new web address. }}} Unsure it it's helpful, but my photos are generally 10+ MB each. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 23 17:37:27 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 23 Dec 2021 17:37:27 -0000 Subject: [wp-meta] [Making WordPress.org] #5997: Photo Directory: Submission form delivering errors In-Reply-To: <055.ff178cc9ff8187865a9a6fe7234f677a@wordpress.org> References: <055.ff178cc9ff8187865a9a6fe7234f677a@wordpress.org> Message-ID: <070.ab5c5cd1ffaf3f26fb60ea078f2849ef@wordpress.org> #5997: Photo Directory: Submission form delivering errors -----------------------------+--------------------- Reporter: maverick3x6 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Photo Directory | Resolution: Keywords: | -----------------------------+--------------------- Changes (by maverick3x6): * Attachment "Screen Shot 2021-12-23 at 12.20.21 PM.png" added. Display of the error -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 23 17:38:32 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 23 Dec 2021 17:38:32 -0000 Subject: [wp-meta] [Making WordPress.org] #5993: Plugin Directory: Add checkbox on submission page In-Reply-To: <051.f8a46a5eaebfdbc4cdb24d6938f8f564@wordpress.org> References: <051.f8a46a5eaebfdbc4cdb24d6938f8f564@wordpress.org> Message-ID: <066.9565eaba801448e250c4a3fc77e8ff9e@wordpress.org> #5993: Plugin Directory: Add checkbox on submission page ------------------------------+--------------------- Reporter: Ipstenu | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+--------------------- Comment (by Ipstenu): I like that better than my idea :) Excellent! This is great! -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 23 17:51:40 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 23 Dec 2021 17:51:40 -0000 Subject: [wp-meta] [Making WordPress.org] #5997: Photo Directory: Submission form delivering errors In-Reply-To: <055.ff178cc9ff8187865a9a6fe7234f677a@wordpress.org> References: <055.ff178cc9ff8187865a9a6fe7234f677a@wordpress.org> Message-ID: <070.0836e09796f2684514b197dac90aa8b5@wordpress.org> #5997: Photo Directory: Submission form delivering errors -----------------------------+--------------------- Reporter: maverick3x6 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Photo Directory | Resolution: Keywords: | -----------------------------+--------------------- Comment (by maverick3x6): I tested this in Chrome and Firefox. Firefox worked fine, so this may be related to Chrome, specifically. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 24 01:47:13 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 24 Dec 2021 01:47:13 -0000 Subject: [wp-meta] [Making WordPress.org] #5997: Photo Directory: Submission form delivering errors In-Reply-To: <055.ff178cc9ff8187865a9a6fe7234f677a@wordpress.org> References: <055.ff178cc9ff8187865a9a6fe7234f677a@wordpress.org> Message-ID: <070.85add950525c7064075007bf29afc997@wordpress.org> #5997: Photo Directory: Submission form delivering errors -----------------------------+--------------------- Reporter: maverick3x6 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Photo Directory | Resolution: Keywords: | -----------------------------+--------------------- Comment (by dd32): Replying to [comment:1 maverick3x6]: > I tested this in Chrome and Firefox. Firefox worked fine, so this may be related to Chrome, specifically. This is definitely a Chrome thing, and has been seen on WordPress.tv uploads too occasionally (Which is to WordPress.com servers, not WordPress.org), as well as on other websites that accept uploads. I've not seen anyone actually be able to reproduce it when trying to, and from all I've read, my understanding is that it's an issue with a network timeout in the Chrome SPDY HTTP implementation. Specifically Chrome sends a "ping" packet at the start and end of a upload, and if either of those get lost or not returned that error is raised. The only thing in common between this and WordPress.tv is... Chrome, nginx, WordPress, and admin-ajax.php, I don't ''think'' it'd be something related to admin-ajax, because this error is likely raised before the request ever gets to PHP, so it's probably somewhere in the Chrome => network => nginx stack.. and probably not going to be easily fixed here.. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 24 01:59:19 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Fri, 24 Dec 2021 01:59:19 +0000 (UTC) Subject: [wp-meta] [11403] sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/shortcodes/class-upload.php: Plugin Directory: Upload: Add a series of requires checkboxes to the upload screen to ensure that uploaders have read and hopefully grasp the plugin guidelines and the purpose of uploading plugins. Message-ID: <20211224015919.954B01B00488@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Fri Dec 24 01:59:24 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 24 Dec 2021 01:59:24 -0000 Subject: [wp-meta] [Making WordPress.org] #5993: Plugin Directory: Add checkbox on submission page In-Reply-To: <051.f8a46a5eaebfdbc4cdb24d6938f8f564@wordpress.org> References: <051.f8a46a5eaebfdbc4cdb24d6938f8f564@wordpress.org> Message-ID: <066.e5edd116bb163fc1294dd9bd3f0d9df9@wordpress.org> #5993: Plugin Directory: Add checkbox on submission page ------------------------------+--------------------- Reporter: Ipstenu | Owner: dd32 Type: enhancement | Status: closed Priority: normal | Milestone: Component: Plugin Directory | Resolution: fixed Keywords: | ------------------------------+--------------------- Changes (by dd32): * owner: (none) => dd32 * status: new => closed * resolution: => fixed Comment: In [changeset:"11403" 11403]: {{{ #!CommitTicketReference repository="" revision="11403" Plugin Directory: Upload: Add a series of requires checkboxes to the upload screen to ensure that uploaders have read and hopefully grasp the plugin guidelines and the purpose of uploading plugins. Fixes #5993. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 24 05:02:37 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 24 Dec 2021 05:02:37 -0000 Subject: [wp-meta] [Making WordPress.org] #5998: Hosting test results "Failed" for tests that do not perform assertions. Message-ID: <051.63caf2f1b52d74feb3ae226a401d30e0@wordpress.org> #5998: Hosting test results "Failed" for tests that do not perform assertions. ---------------------+-------------------- Reporter: costdev | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: General | Keywords: ---------------------+-------------------- Several hosts have raised concerns about the "Failed" status showing on the [https://make.wordpress.org/hosting/test-results/ Hosting Test Results] page. A recent commit in Core revealed test methods that do not perform assertions. Investigation and resolution of these test methods is ongoing. However, in looking at the markup of the "Failed" status: {{{ title="13432 tests, 0 failed, 30 errors" }}} From what I can tell: 1. Risky tests are marked as errors. 2. Errors create a "Failed" result. Is this the intended behaviour, or can risky tests like these be excluded so as not to create concern with hosts? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 24 22:08:30 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 24 Dec 2021 22:08:30 -0000 Subject: [wp-meta] [Making WordPress.org] #3459: Update good-first-bugs auto-claiming process In-Reply-To: <052.3bdfe3057573fefa334a7af5219eb6fb@wordpress.org> References: <052.3bdfe3057573fefa334a7af5219eb6fb@wordpress.org> Message-ID: <067.ca77334bea9d6a0a4be6d4cedbcaae8c@wordpress.org> #3459: Update good-first-bugs auto-claiming process -------------------------------------------+--------------------- Reporter: jbpaul17 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Trac | Resolution: Keywords: needs-patch reporter-feedback | -------------------------------------------+--------------------- Comment (by JeffPaul): @dd32 I think this would still be a worthwhile addition, but I'll get it added to a devchat agenda in the new year and confirm more clearly. Thanks for the effort on this, its greatly appreciated, have a safe end of the year and a happy new year! -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 27 00:02:54 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 27 Dec 2021 00:02:54 -0000 Subject: [wp-meta] [Making WordPress.org] #5999: Bump recommended MySQL and MariaDB versions Message-ID: <058.88e0ec98340465c18d6d34f760f06bf8@wordpress.org> #5999: Bump recommended MySQL and MariaDB versions --------------------------------+-------------------- Reporter: SergeyBiryukov | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: WordPress.org Site | Keywords: --------------------------------+-------------------- Background: #4248, #WP41490. The [https://wordpress.org/about/requirements/ Requirements] page currently lists MySQL 5.6 or greater and MariaDB 10.1 or greater as recommended. In https://core.trac.wordpress.org/ticket/41490#comment:11, @JavierCasares pointed out that these versions are no longer supported and should be bumped to MySQL 5.7 and MariaDB 10.2. Per the [https://mariadb.org/about/#maintenance-policy MariaDB maintenance policy], support for version 10.2 ends in May 2022, at which point this should be revisited again. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 27 06:38:21 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 27 Dec 2021 06:38:21 -0000 Subject: [wp-meta] [Making WordPress.org] #6000: WordPress.tv audio does not work when downloading med and high quality video Message-ID: <059.0ec353aa9fb99a7ff6fabbfa1d346417@wordpress.org> #6000: WordPress.tv audio does not work when downloading med and high quality video -----------------------------+-------------------- Reporter: alanjacobmathew | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: WordPress.tv | Keywords: -----------------------------+-------------------- Issue: Downloading wp.tv videos in high quality and medium quality does not support audio. == How To Reproduce: * Open any [https://wordpress.tv/2021/12/15/matt-mullenweg-2021-state-of- the-word/ wp.tv video] * Go to the download section and open 'High' and 'Med' resolution. * Play the video online or download it. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 27 16:07:32 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 27 Dec 2021 16:07:32 -0000 Subject: [wp-meta] [Making WordPress.org] #6001: Lack of Context for Docs (no learning path) under https://wordpress.org/support/ Message-ID: <056.b600c05e9a96d6bc527e7a83921c7329@wordpress.org> #6001: Lack of Context for Docs (no learning path) under https://wordpress.org/support/ --------------------------+-------------------- Reporter: juanmaguitar | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: HelpHub | Keywords: --------------------------+-------------------- **Issue Description** When we visit a doc like [Blocks](https://wordpress.org/support/article/blocks/) there are no resources to follow a "learning path" ![diagram docs blocks](https://user- images.githubusercontent.com/422576/147488372-9bfdf277-04ea-4313-9a62-2c2cc7bb1415.png) So when a user get to this documents there is no answer to the questions: Where am i? Where should I go next? What should I have read before? **URL of the Page with the Issue** This one is an example https://wordpress.org/support/article/blocks/ but any page under https://wordpress.org/support/ have the same problem **Why is this a problem?** Because I think is super hard for any user to learn about any of the topics provided in the docs if they cannot establish an order and hierarchy of the docs they are reading **Suggested Fix** - Establish a clear hierarchy of docs and categories - Highlight in the sidebar the category the current document belongs to - Suggest knowledge recommended to understand the current document - Suggest docs to read after reading the current document - Highlight in the top bar where we are -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 27 18:32:30 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 27 Dec 2021 18:32:30 +0000 (UTC) Subject: [wp-meta] [11404] sites/trunk/wordpress.org/public_html: Hosting: Convert static page to WP to enable new header/footer. Message-ID: <20211227183230.DF4211B00412@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon Dec 27 19:20:18 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 27 Dec 2021 19:20:18 -0000 Subject: [wp-meta] [Making WordPress.org] #6002: "for" element on labels failing to allow people to click the label to activate the checkbox Message-ID: <057.934d4df9bd374c9694f426b530f1a2d2@wordpress.org> #6002: "for" element on labels failing to allow people to click the label to activate the checkbox -----------------------------+-------------------- Reporter: topher1kenobe | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Photo Directory | Keywords: -----------------------------+-------------------- When I click on a label on the submission form, I expect it to activate the checkbox, but it doesn't, despite the HTML being proper. Firefox 95 on MacOS 11.6 -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 27 19:20:41 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 27 Dec 2021 19:20:41 -0000 Subject: [wp-meta] [Making WordPress.org] #6002: "for" element on labels failing to allow people to click the label to activate the checkbox In-Reply-To: <057.934d4df9bd374c9694f426b530f1a2d2@wordpress.org> References: <057.934d4df9bd374c9694f426b530f1a2d2@wordpress.org> Message-ID: <072.570799fa184523ec4f286667ef65f4ed@wordpress.org> #6002: "for" element on labels failing to allow people to click the label to activate the checkbox -----------------------------+--------------------- Reporter: topher1kenobe | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Photo Directory | Resolution: Keywords: | -----------------------------+--------------------- Changes (by topher1kenobe): * Attachment "CleanShot 2021-12-27 at 14.16.59 at 2x.png" added. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon Dec 27 20:37:57 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 27 Dec 2021 20:37:57 +0000 (UTC) Subject: [wp-meta] [11405] sites/trunk/wordpress.org/public_html: Mobile: Convert static page to WP to enable new header/footer. Message-ID: <20211227203757.210F51B00412@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon Dec 27 21:05:09 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 27 Dec 2021 21:05:09 +0000 (UTC) Subject: [wp-meta] [11406] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/css: Mobile: Wrap app links to allow room for text on small viewports. Message-ID: <20211227210509.482201B00412@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Tue Dec 28 10:00:27 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 28 Dec 2021 10:00:27 -0000 Subject: [wp-meta] [Making WordPress.org] #6003: W3C CSS syntax for pseudo element in meta Message-ID: <057.43361c3fda9288af0ae93ca7768429ca@wordpress.org> #6003: W3C CSS syntax for pseudo element in meta ----------------------------+----------------------- Reporter: multidots1896 | Owner: (none) Type: defect | Status: new Priority: high | Milestone: Component: buddypress.org | Keywords: has-patch ----------------------------+----------------------- I have checking in meta sites, and moving in buddypress.org in that bb- base theme has found a pseudo element structure in style.css file. on their for pseudo element like :after and :before single-colon syntax was used but this type of syntax was used in CSS1 and CSS2. In latest CSS3 level we used double colon notation for pseudo element (::after and ::before). -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 28 10:02:06 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 28 Dec 2021 10:02:06 -0000 Subject: [wp-meta] [Making WordPress.org] #6003: W3C CSS syntax for pseudo element in meta In-Reply-To: <057.43361c3fda9288af0ae93ca7768429ca@wordpress.org> References: <057.43361c3fda9288af0ae93ca7768429ca@wordpress.org> Message-ID: <072.41d84d5a023219ea23ca9cd4252eaa53@wordpress.org> #6003: W3C CSS syntax for pseudo element in meta ----------------------------+--------------------- Reporter: multidots1896 | Owner: (none) Type: defect | Status: new Priority: high | Milestone: Component: buddypress.org | Resolution: Keywords: has-patch | ----------------------------+--------------------- Changes (by multidots1896): * Attachment "6003.patch" added. added patch for this ticket where i modify css -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 28 10:34:47 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 28 Dec 2021 10:34:47 -0000 Subject: [wp-meta] [Making WordPress.org] #6004: Translate: Rephrase error messge when saving changed string status fails. Message-ID: <056.e1e209b49d30e5a6241904d8e54a9fae@wordpress.org> #6004: Translate: Rephrase error messge when saving changed string status fails. --------------------------------------+-------------------- Reporter: tobifjellner | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Translate Site & Plugins | Keywords: --------------------------------------+-------------------- Sometimes a translation editor (PTE/GTE) suddenly gets the message "Error setting the status!" when they try to approve or reject a pending translation. In all cases I've seen so far, plugin slug contained something about ads and the problem disappeared as soon as the GTE deactivated the ad-blocker in their browser. Obviously there might be other reasons, but it would probably be good to rephrase this string into: "Error setting the status, perhaps your adblocker is active." Thanks @aliceorru for the reminder and the screenshot -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 28 10:35:05 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 28 Dec 2021 10:35:05 -0000 Subject: [wp-meta] [Making WordPress.org] #6004: Translate: Rephrase error messge when saving changed string status fails. In-Reply-To: <056.e1e209b49d30e5a6241904d8e54a9fae@wordpress.org> References: <056.e1e209b49d30e5a6241904d8e54a9fae@wordpress.org> Message-ID: <071.3b23444918686042d4717fa5473ccdd7@wordpress.org> #6004: Translate: Rephrase error messge when saving changed string status fails. --------------------------------------+--------------------- Reporter: tobifjellner | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Translate Site & Plugins | Resolution: Keywords: | --------------------------------------+--------------------- Changes (by tobifjellner): * Attachment "2021-12-28.png" added. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 28 11:46:58 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 28 Dec 2021 11:46:58 -0000 Subject: [wp-meta] [Making WordPress.org] #6004: Translate: Rephrase error messge when saving changed string status fails. In-Reply-To: <056.e1e209b49d30e5a6241904d8e54a9fae@wordpress.org> References: <056.e1e209b49d30e5a6241904d8e54a9fae@wordpress.org> Message-ID: <056.e1e209b49d30e5a6241904d8e54a9fae@wordpress.org> #6004: Translate: Rephrase error messge when saving changed string status fails. --------------------------------------+--------------------- Reporter: tobifjellner | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Translate Site & Plugins | Resolution: Keywords: | --------------------------------------+--------------------- Changes (by tobifjellner): * Attachment "2021-12-28.png" removed. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 28 11:46:58 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 28 Dec 2021 11:46:58 -0000 Subject: [wp-meta] [Making WordPress.org] #6004: Translate: Rephrase error messge when saving changed string status fails. In-Reply-To: <056.e1e209b49d30e5a6241904d8e54a9fae@wordpress.org> References: <056.e1e209b49d30e5a6241904d8e54a9fae@wordpress.org> Message-ID: <071.96bcbdf54103ce83232e3e1a8299e093@wordpress.org> #6004: Translate: Rephrase error messge when saving changed string status fails. --------------------------------------+--------------------- Reporter: tobifjellner | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Translate Site & Plugins | Resolution: Keywords: | --------------------------------------+--------------------- Changes (by tobifjellner): * Attachment "2021-12-28.png" added. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 28 16:54:08 2021 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 28 Dec 2021 16:54:08 +0000 (UTC) Subject: [wp-meta] [11407] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main: WordPress.org Main Theme: Requirements: Bump the recommended MySQL and MariaDB versions. Message-ID: <20211228165408.EF7AB1B003CB@svn1.ord.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Tue Dec 28 16:54:14 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 28 Dec 2021 16:54:14 -0000 Subject: [wp-meta] [Making WordPress.org] #5999: Bump recommended MySQL and MariaDB versions In-Reply-To: <058.88e0ec98340465c18d6d34f760f06bf8@wordpress.org> References: <058.88e0ec98340465c18d6d34f760f06bf8@wordpress.org> Message-ID: <073.46b2143108e59efb9c60143d85b914f5@wordpress.org> #5999: Bump recommended MySQL and MariaDB versions --------------------------------+----------------------------- Reporter: SergeyBiryukov | Owner: SergeyBiryukov Type: defect | Status: closed Priority: normal | Milestone: Component: WordPress.org Site | Resolution: fixed Keywords: | --------------------------------+----------------------------- Changes (by SergeyBiryukov): * owner: (none) => SergeyBiryukov * status: new => closed * resolution: => fixed Comment: In [changeset:"11407" 11407]: {{{ #!CommitTicketReference repository="" revision="11407" WordPress.org Main Theme: Requirements: Bump the recommended MySQL and MariaDB versions. * MySQL 5.6 has reached EOL (“End of Life”) in February 2021. The recommended minimum is bumped to 5.7 for now. * MariaDB 10.1 has reached EOL in October 2020. The recommended minimum is bumped to 10.2 for now. Follow-up to [8726], [9358]. Props JavierCasares, SergeyBiryukov. Fixes #5999. See #WP41490. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 28 17:01:24 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 28 Dec 2021 17:01:24 -0000 Subject: [wp-meta] [Making WordPress.org] #6005: Improve sorting on language page of project Message-ID: <053.346ab04e687e219ee3db67dd52e84b61@wordpress.org> #6005: Improve sorting on language page of project -------------------------+-------------------- Reporter: NekoJonez | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Keywords: -------------------------+-------------------- On project pages like these ones: https://translate.wordpress.org/projects /wp-plugins/wd-google-maps/ (Just a random example) I find it quite annoying that the locale's after the ones where at least one string is translated are in a somewhat random order. I would love to see them in an alphabetized order. I think the order should be, and each "group" first depending on the completion % and then alphabetized: 1) The locales with 100%, everything. 2) The locales with the highest completion % 3) The locales with 0% completion, but with waiting strings (why are these at the bottom anyways?) 4) The locales with 0% completion and no waiting strings. I think this will make it easier for translators who work in various variants of locales or for multiple locales to find the ones they are looking for. 4) -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue Dec 28 17:01:49 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 28 Dec 2021 17:01:49 -0000 Subject: [wp-meta] [Making WordPress.org] #6005: Improve sorting on language page of project In-Reply-To: <053.346ab04e687e219ee3db67dd52e84b61@wordpress.org> References: <053.346ab04e687e219ee3db67dd52e84b61@wordpress.org> Message-ID: <068.1e362b30919d26b843f7892f29a4c911@wordpress.org> #6005: Improve sorting on language page of project --------------------------------------+--------------------- Reporter: NekoJonez | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: Translate Site & Plugins | Resolution: Keywords: | --------------------------------------+--------------------- Changes (by NekoJonez): * component: General => Translate Site & Plugins Comment: Forgot to set the right component, my mistake. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 29 10:58:55 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 29 Dec 2021 10:58:55 -0000 Subject: [wp-meta] [Making WordPress.org] #6006: When a normal translator suggests a translation with a wrong url in it, then there is no "discard" option within the message Message-ID: <054.10276669c9f1866d046760b9b1e64bc6@wordpress.org> #6006: When a normal translator suggests a translation with a wrong url in it, then there is no "discard" option within the message --------------------------------------+-------------------- Reporter: psmits1567 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Translate Site & Plugins | Keywords: --------------------------------------+-------------------- This is not consistent with the behavior when a PTE/GTE adds a translation. The current behavior is saving the record first then give a warning. It does not matter which roll you have. The difference is that a PTE/GTE gets the opportunity to "Discard" the message, after which the editor is cleared from the warning. If a normal translator suggests a translation with a wrong URL, only the warning is show but no "Discard" link. The problem for a normal translator is, that the editor screen is altered so the translation is moved downwards. It would be better to make it consistent, so also a normal translator can discard the message, and gets the full editor screen back. Maybe also the text could be improved by adding "Please correct your error and suggest/save again" -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 29 11:35:40 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 29 Dec 2021 11:35:40 -0000 Subject: [wp-meta] [Making WordPress.org] #6007: You are able to accept fuzzy plural translations with an empty translation. Message-ID: <053.a2d77bbcada515abaeb795cc7bbc9afa@wordpress.org> #6007: You are able to accept fuzzy plural translations with an empty translation. --------------------------------------+-------------------- Reporter: NekoJonez | Owner: (none) Type: defect | Status: new Priority: high | Milestone: Component: Translate Site & Plugins | Keywords: --------------------------------------+-------------------- Today I wanted to test something... What would happen if you accepted a fuzzy translation with plurals where one of the translations was empty. It gets accepted and becomes the current. I think this is a bug and it shouldn't be allowed to happen. https://translate.wordpress.org/projects/wp-plugins/customer-reviews- woocommerce/stable/nl/default/?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=7564712&sort%5Bby%5D=translation_date_added&sort%5Bhow%5D=asc <- test string. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 29 13:31:02 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 29 Dec 2021 13:31:02 -0000 Subject: [wp-meta] [Making WordPress.org] #6008: In wordpress.org showcase theme having uneven slider height Message-ID: <057.a0d4ec0eb84577762cb6cc5167288ea6@wordpress.org> #6008: In wordpress.org showcase theme having uneven slider height ---------------------------+----------------------- Reporter: multidots1896 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Showcase | Keywords: has-patch ---------------------------+----------------------- I have found one issue in wordpress.org showcase theme Url:[https://wordpress.org/showcase/] In showcase page wpsc hero slider shows uneven height when sliding items. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 29 13:31:50 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 29 Dec 2021 13:31:50 -0000 Subject: [wp-meta] [Making WordPress.org] #6008: In wordpress.org showcase theme having uneven slider height In-Reply-To: <057.a0d4ec0eb84577762cb6cc5167288ea6@wordpress.org> References: <057.a0d4ec0eb84577762cb6cc5167288ea6@wordpress.org> Message-ID: <072.3cbf28f4606893f795f1575884600f15@wordpress.org> #6008: In wordpress.org showcase theme having uneven slider height ---------------------------+--------------------- Reporter: multidots1896 | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Showcase | Resolution: Keywords: has-patch | ---------------------------+--------------------- Changes (by multidots1896): * Attachment "6008.patch" added. added patch -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 29 15:16:13 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 29 Dec 2021 15:16:13 -0000 Subject: [wp-meta] [Making WordPress.org] #6009: Log-in should redirect back to the origin page in Forums Message-ID: <059.88a79212c86f654cd69a61f3262c2d69@wordpress.org> #6009: Log-in should redirect back to the origin page in Forums -----------------------------+-------------------- Reporter: alanjacobmathew | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Support Forums | Keywords: -----------------------------+-------------------- Currently login from support forums takes you back to the homepage, which is extra work for the user. == How To Reproduce * Make sure you are not logged in * Visit the support forum ([https://wordpress.org/support/topic/404-page-49/ here]) * Click on 'Login to see the link' or the login button on right corner, or 'You must be logged in to reply this topic' * All 3 login instances takes the user to the home page. The very reason the user logged in there is either to view the link, or to reply on the topic, but get's redirected to home page. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 29 15:58:16 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 29 Dec 2021 15:58:16 -0000 Subject: [wp-meta] [Making WordPress.org] #6009: Log-in should redirect back to the origin page in Forums In-Reply-To: <059.88a79212c86f654cd69a61f3262c2d69@wordpress.org> References: <059.88a79212c86f654cd69a61f3262c2d69@wordpress.org> Message-ID: <074.3bd6d962283e5e93d0267a519d15a4e7@wordpress.org> #6009: Log-in should redirect back to the origin page in Forums -----------------------------+--------------------- Reporter: alanjacobmathew | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | -----------------------------+--------------------- Comment (by Otto42): Can't reproduce this. Logging in there (in an incog window for testing) causes it to redirect back to the forum support topic. Are you blocking the Referer header, perhaps with some privacy software? The login page checks the referer header, using `wp_get_referer()` and sets a redirect_to parameter on the login page, to take you back to where you were. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed Dec 29 16:45:20 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 29 Dec 2021 16:45:20 -0000 Subject: [wp-meta] [Making WordPress.org] #6009: Log-in should redirect back to the origin page in Forums In-Reply-To: <059.88a79212c86f654cd69a61f3262c2d69@wordpress.org> References: <059.88a79212c86f654cd69a61f3262c2d69@wordpress.org> Message-ID: <074.738f32c52c0a162652311c174c54cfeb@wordpress.org> #6009: Log-in should redirect back to the origin page in Forums -----------------------------+--------------------- Reporter: alanjacobmathew | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | -----------------------------+--------------------- Comment (by alanjacobmathew): Seems like the issue exists only on Brave Browser. Seems fine with edge. But how does the redirects work properly from [https://core.trac.wordpress.org], [https://meta.trac.wodpress.org] and [https://wordpress.org/support/article/twenty-twenty-one/ Support Documentation] even when using Brave. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 30 00:14:47 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 30 Dec 2021 00:14:47 -0000 Subject: [wp-meta] [Making WordPress.org] #6009: Log-in should redirect back to the origin page in Forums In-Reply-To: <059.88a79212c86f654cd69a61f3262c2d69@wordpress.org> References: <059.88a79212c86f654cd69a61f3262c2d69@wordpress.org> Message-ID: <074.98c5be0761102f97a0b0118202760d35@wordpress.org> #6009: Log-in should redirect back to the origin page in Forums -----------------------------+---------------------- Reporter: alanjacobmathew | Owner: (none) Type: defect | Status: closed Priority: normal | Milestone: Component: Support Forums | Resolution: invalid Keywords: | -----------------------------+---------------------- Changes (by Otto42): * status: new => closed * resolution: => invalid Comment: I can't answer that because I don't use Brave it know the details of what it does. But in the end, we can only fix things for standard browser behavior, and sending referer headers is normal and has been for many decades. I'm going to mark this invalid for now, but if anybody has suggestions on better ways to do things, please comment. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu Dec 30 00:22:39 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 30 Dec 2021 00:22:39 -0000 Subject: [wp-meta] [Making WordPress.org] #6009: Log-in should redirect back to the origin page in Forums In-Reply-To: <059.88a79212c86f654cd69a61f3262c2d69@wordpress.org> References: <059.88a79212c86f654cd69a61f3262c2d69@wordpress.org> Message-ID: <074.9889a31d5af1fb91bfe5ff13dc3ab231@wordpress.org> #6009: Log-in should redirect back to the origin page in Forums -----------------------------+---------------------- Reporter: alanjacobmathew | Owner: (none) Type: defect | Status: closed Priority: normal | Milestone: Component: Support Forums | Resolution: invalid Keywords: | -----------------------------+---------------------- Comment (by Otto42): Just to add to this, some of the various sites explicitly add the redirect_to value in the path to login.w, which will be used instead of the referer. That may be why some of the Trac sites work, because they have explicit code to force the issue. This is because those sites aren't using WordPress, so we have special code on them to force these things to work properly. Nevertheless, privacy blocking browsers will always cause these kinds of weird issues everywhere, in general, especially when they are trying too hard. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 31 09:51:53 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 31 Dec 2021 09:51:53 -0000 Subject: [wp-meta] [Making WordPress.org] #6010: Twenty Twenty One theme customizer color mode setting having properly not applying effects on block Message-ID: <057.a2053b95410fd340996f17a7a4e376c7@wordpress.org> #6010: Twenty Twenty One theme customizer color mode setting having properly not applying effects on block ---------------------------+----------------------------------------- Reporter: multidots1896 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Keywords: needs-patch has-screenshots ---------------------------+----------------------------------------- Twenty Twenty One theme customizer color mode setting having properly not applying effects on block in wp cover block which i highlighted in the screenshot has not properly applying dark background effect. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 31 09:52:17 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 31 Dec 2021 09:52:17 -0000 Subject: [wp-meta] [Making WordPress.org] #6010: Twenty Twenty One theme customizer color mode setting having properly not applying effects on block In-Reply-To: <057.a2053b95410fd340996f17a7a4e376c7@wordpress.org> References: <057.a2053b95410fd340996f17a7a4e376c7@wordpress.org> Message-ID: <072.6e7926c6d9c285dbe830a39c6fb2b11d@wordpress.org> #6010: Twenty Twenty One theme customizer color mode setting having properly not applying effects on block -----------------------------------------+--------------------- Reporter: multidots1896 | Owner: (none) Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: needs-patch has-screenshots | -----------------------------------------+--------------------- Changes (by multidots1896): * Attachment "Customize_ wpcontribution – Just another WordPress site.png" added. attached screenshot of ticket -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 31 10:07:52 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 31 Dec 2021 10:07:52 -0000 Subject: [wp-meta] [Making WordPress.org] #6010: Twenty Twenty One theme customizer color mode setting having properly not applying effects on block In-Reply-To: <057.a2053b95410fd340996f17a7a4e376c7@wordpress.org> References: <057.a2053b95410fd340996f17a7a4e376c7@wordpress.org> Message-ID: <072.da5ea53f7fe2027be152e5054fa3475e@wordpress.org> #6010: Twenty Twenty One theme customizer color mode setting having properly not applying effects on block -----------------------------------------+---------------------- Reporter: multidots1896 | Owner: (none) Type: enhancement | Status: closed Priority: normal | Milestone: Component: General | Resolution: invalid Keywords: needs-patch has-screenshots | -----------------------------------------+---------------------- Changes (by Otto42): * status: new => closed * resolution: => invalid Comment: This is the meta trac, used for tracking issues with the wordpress.org website itself. The 2021 theme is not yet released and still in development, and when it is released, it will be part of core, so should be properly reported in the https://core.trac.wordpress.org, not here. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 31 18:34:16 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 31 Dec 2021 18:34:16 -0000 Subject: [wp-meta] [Making WordPress.org] #6011: list item display issue Message-ID: <060.88036cce235dc9b3c407761d8629f55c@wordpress.org> #6011: list item display issue ------------------------------+----------------------------- Reporter: jigar bhanushali | Owner: (none) Type: defect | Status: new Priority: high | Milestone: Component: Handbooks | Keywords: has-screenshots ------------------------------+----------------------------- In Handbook of Changing File Permissions the li item bullet shows without any content there. Ref: https://wordpress.org/support/article/changing-file-permissions/ -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 31 18:34:28 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 31 Dec 2021 18:34:28 -0000 Subject: [wp-meta] [Making WordPress.org] #6011: list item display issue In-Reply-To: <060.88036cce235dc9b3c407761d8629f55c@wordpress.org> References: <060.88036cce235dc9b3c407761d8629f55c@wordpress.org> Message-ID: <075.315a4db3d5460e085267aabe326aebab@wordpress.org> #6011: list item display issue ------------------------------+--------------------- Reporter: jigar bhanushali | Owner: (none) Type: defect | Status: new Priority: high | Milestone: Component: Handbooks | Resolution: Keywords: has-screenshots | ------------------------------+--------------------- Changes (by jigar bhanushali): * Attachment "d9a506c1-69bb-439d-83f0-ee685f9e87bd.jfif" added. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 31 18:41:13 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 31 Dec 2021 18:41:13 -0000 Subject: [wp-meta] [Making WordPress.org] #6011: list item display issue In-Reply-To: <060.88036cce235dc9b3c407761d8629f55c@wordpress.org> References: <060.88036cce235dc9b3c407761d8629f55c@wordpress.org> Message-ID: <075.a93d1d5a8478a06ab23d91cee53b92fa@wordpress.org> #6011: list item display issue ------------------------------+--------------------- Reporter: jigar bhanushali | Owner: (none) Type: defect | Status: new Priority: high | Milestone: Component: Handbooks | Resolution: Keywords: has-screenshots | ------------------------------+--------------------- Comment (by sterndata): fixed (at least, the bullet in the UNIX area) -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri Dec 31 18:42:40 2021 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 31 Dec 2021 18:42:40 -0000 Subject: [wp-meta] [Making WordPress.org] #6011: list item display issue In-Reply-To: <060.88036cce235dc9b3c407761d8629f55c@wordpress.org> References: <060.88036cce235dc9b3c407761d8629f55c@wordpress.org> Message-ID: <075.f9dc3ec183856b27aa54b35501a4cfd8@wordpress.org> #6011: list item display issue ------------------------------+--------------------- Reporter: jigar bhanushali | Owner: (none) Type: defect | Status: new Priority: high | Milestone: Component: Handbooks | Resolution: Keywords: has-screenshots | ------------------------------+--------------------- Comment (by sterndata): However, note that the link for "UNIX Permissions" is to http://www.washington.edu/computing/unix/permissions.html which is a 404. -- Ticket URL: Making WordPress.org Making WordPress.org