From noreply at wordpress.org  Mon Jan  4 23:41:00 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  4 Jan 2021 23:41:00 +0000 (UTC)
Subject: [wp-meta] [10548]
 sites/trunk/api.wordpress.org/public_html/events/1.0: Events: Create
 permenant function for pinning one-off events.
Message-ID: <20210104234100.7C2D61B0033C@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210104/ae71ce6b/attachment.html>

From noreply at wordpress.org  Mon Jan  4 23:41:06 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  4 Jan 2021 23:41:06 +0000 (UTC)
Subject: [wp-meta] [10549]
 sites/trunk/api.wordpress.org/public_html/events/1.0/index.php: Events: Pin
 online WordCamps for their entire country.
Message-ID: <20210104234106.F1BD81B0042E@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210104/2ff01f03/attachment.html>

From noreply at wordpress.org  Tue Jan  5 05:01:42 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 05 Jan 2021 05:01:42 -0000
Subject: [wp-meta] [Making WordPress.org] #5559: Images from CDN are not
 opening by link after clicking on them in HelpHub articles in attending to
 zoom them
In-Reply-To: <052.c78f8a97ac2b20b6018d3b06dae345fa@wordpress.org>
References: <052.c78f8a97ac2b20b6018d3b06dae345fa@wordpress.org>
Message-ID: <067.35ea0309e293ba02d1425f825cbd65d0@wordpress.org>

#5559: Images from CDN are not opening by link after clicking on them in HelpHub
articles in attending to zoom them
----------------------+---------------------
 Reporter:  oglekler  |       Owner:  (none)
     Type:  defect    |      Status:  new
 Priority:  normal    |   Milestone:
Component:  HelpHub   |  Resolution:
 Keywords:            |
----------------------+---------------------

Comment (by dufresnesteven):

 Hi!

 It appears like the link and the image src differ.

 <a href="https://i2.wp.com/wp-helphub.com/wp-content/uploads/2016/07
 /760px-options-general.png">
 <img src="https://i2.wp.com/wordpress.org/support/files/2018/11/760px-
 options-general.png" />

 The anchor href should be updated. With that change, I'm not sure other
 updates are not needed since the built-in browser image viewer should kick
 in as usual. Thoughts?

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5559#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan  5 20:11:38 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  5 Jan 2021 20:11:38 +0000 (UTC)
Subject: [wp-meta] [10550]
 sites/trunk/api.wordpress.org/public_html/events/1.0/index.php: Events: Use
 `HOUR_IN_SECONDS` constant for readability.
Message-ID: <20210105201138.345DD1B000EE@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210105/5d2e81e8/attachment.html>

From noreply at wordpress.org  Tue Jan  5 20:11:44 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  5 Jan 2021 20:11:44 +0000 (UTC)
Subject: [wp-meta] [10551]
 sites/trunk/api.wordpress.org/public_html/events/1.0/tests/test-index-phpunit.php:
 Events: Add Seattle IP to track geolocation regressions.
Message-ID: <20210105201144.AFAD01B000EE@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210105/00a980d4/attachment.html>

From noreply at wordpress.org  Tue Jan  5 23:25:38 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  5 Jan 2021 23:25:38 +0000 (UTC)
Subject: [wp-meta] [10552]
 sites/trunk/common/includes/slack/announce/config.php: Slack: Announce: Add
 erica to the list of community wranglers,
 for `/here` access in #training and other related channels.
Message-ID: <20210105232538.4AA3D1B000EE@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210105/f8765b1a/attachment.html>

From noreply at wordpress.org  Tue Jan  5 23:59:33 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 05 Jan 2021 23:59:33 -0000
Subject: [wp-meta] [Making WordPress.org] #5559: Images from CDN are not
 opening by link after clicking on them in HelpHub articles in attending to
 zoom them
In-Reply-To: <052.c78f8a97ac2b20b6018d3b06dae345fa@wordpress.org>
References: <052.c78f8a97ac2b20b6018d3b06dae345fa@wordpress.org>
Message-ID: <067.5acce366a1be067289a82870fb519d25@wordpress.org>

#5559: Images from CDN are not opening by link after clicking on them in HelpHub
articles in attending to zoom them
----------------------+---------------------
 Reporter:  oglekler  |       Owner:  (none)
     Type:  defect    |      Status:  new
 Priority:  normal    |   Milestone:
Component:  HelpHub   |  Resolution:
 Keywords:            |
----------------------+---------------------

Comment (by dd32):

 Having `wp-helphub.com` in the content has been an ongoing problem..

 Here's a list of all the articles which contain it:
 https://wordpress.org/support/?p=10851459       before-you-
 create-a-network
 https://wordpress.org/support/?p=10841662       common-wordpress-errors
 https://wordpress.org/support/?p=10450778       creating-a-search-page
 https://wordpress.org/support/?p=10849381       settings-general-screen
 https://wordpress.org/support/?p=10851401       test-driving-wordpress
 https://wordpress.org/support/?p=10863612       twenty-fifteen
 https://wordpress.org/support/?p=10778661       users-your-profile-screen
 https://wordpress.org/support/?p=10813583       wordpress-backups
 https://wordpress.org/support/?p=10776396       writing-posts
 https://wordpress.org/support/?p=10851309       settings-permalinks-screen
 https://wordpress.org/support/?p=10848222       settings-writing-screen
 https://wordpress.org/support/?p=10840288       twenty-sixteen

 Find-replace unfortunately doesn't work, as the `<a>` needs to be updated
 interactively to link to the correct content.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5559#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan  6 01:24:36 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 06 Jan 2021 01:24:36 -0000
Subject: [wp-meta] [Making WordPress.org] #5562: Events: Exact city matches
 fail because of state abbreviations
Message-ID: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>

#5562: Events: Exact city matches fail because of state abbreviations
------------------------+--------------------
 Reporter:  iandunn     |      Owner:  (none)
     Type:  defect      |     Status:  new
 Priority:  normal      |  Milestone:
Component:  Events API  |   Keywords:
------------------------+--------------------
 These two searches (and probably many others) return the "wrong" Chicago.

 Instead of Chicago, Illinois
 ([https://www.geonames.org/4887398/chicago.html Geonames ID 4887398]) they
 return cities with an alternate name of Chicago, with a much smaller
 population. It may even match some buildings with population `0` that are
 [https://www.geonames.org/export/codes.html classified as `P.PPL`]?


 *
 https://api.wordpress.org/events/1.0/?number=5&ip=127.0.0.0&locale=en_US&timezone=America/Los_Angeles&location=chicago
 - returns Craigmont, Idaho (
 [https://www.geonames.org/5590063/craigmont.html Geonames ID 5590063] )
 *
 https://api.wordpress.org/events/1.0/?number=5&ip=127.0.0.0&locale=en_US&timezone=America/Chicago&location=chicago
 - returns `Chicago and Northwestern Railroad Station` in Kenosha,
 Wisconsin [https://www.geonames.org/5248432/chicago.html Geonames ID
 5248432]

 I've added some PHPUnit cases in r10553 (xref r10544 for info on the new
 test suite).

 It looks like the problem may be related to how cities are now being
 imported into `geonames_summary.name` as `Chicago, IL` instead of the
 canonical `Chicago` in `geonames.name`. So, they fail the exact-match
 search, and the fuzzy search turns up the less-desirable result.

 Possibly related to #3728, #5117, r16728-dotorg

 I'll look into it more tomorrow, but wanted to document what I've found so
 far. CC @dd32

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5562>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan  6 01:25:07 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  6 Jan 2021 01:25:07 +0000 (UTC)
Subject: [wp-meta] [10553]
 sites/trunk/api.wordpress.org/public_html/events/1.0/tests/test-index-phpunit.php:
 Events: Add failing tests to show exact-match bug.
Message-ID: <20210106012507.08C2B1B001BB@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210106/eea977ff/attachment.html>

From noreply at wordpress.org  Wed Jan  6 01:25:11 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 06 Jan 2021 01:25:11 -0000
Subject: [wp-meta] [Making WordPress.org] #5562: Events: Exact city
 matches fail because of state abbreviations
In-Reply-To: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
References: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
Message-ID: <066.4deb9e00ae75c6010a0226c3215adffe@wordpress.org>

#5562: Events: Exact city matches fail because of state abbreviations
------------------------+---------------------
 Reporter:  iandunn     |       Owner:  (none)
     Type:  defect      |      Status:  new
 Priority:  normal      |   Milestone:
Component:  Events API  |  Resolution:
 Keywords:              |
------------------------+---------------------

Comment (by iandunn):

 In [changeset:"10553" 10553]:
 {{{
 #!CommitTicketReference repository="" revision="10553"
 Events: Add failing tests to show exact-match bug.

 See #5562.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5562#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan  6 01:27:45 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 06 Jan 2021 01:27:45 -0000
Subject: [wp-meta] [Making WordPress.org] #5562: Events: Exact city
 matches fail because of state abbreviations
In-Reply-To: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
References: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
Message-ID: <066.387e1eb20f1df957fab6ee24ebb3c17c@wordpress.org>

#5562: Events: Exact city matches fail because of state abbreviations
------------------------+---------------------
 Reporter:  iandunn     |       Owner:  (none)
     Type:  defect      |      Status:  new
 Priority:  normal      |   Milestone:
Component:  Events API  |  Resolution:
 Keywords:              |
------------------------+---------------------
Description changed by iandunn:

Old description:

> These two searches (and probably many others) return the "wrong" Chicago.
>
> Instead of Chicago, Illinois
> ([https://www.geonames.org/4887398/chicago.html Geonames ID 4887398])
> they return cities with an alternate name of Chicago, with a much smaller
> population. It may even match some buildings with population `0` that are
> [https://www.geonames.org/export/codes.html classified as `P.PPL`]?
>

> *
> https://api.wordpress.org/events/1.0/?number=5&ip=127.0.0.0&locale=en_US&timezone=America/Los_Angeles&location=chicago
> - returns Craigmont, Idaho (
> [https://www.geonames.org/5590063/craigmont.html Geonames ID 5590063] )
> *
> https://api.wordpress.org/events/1.0/?number=5&ip=127.0.0.0&locale=en_US&timezone=America/Chicago&location=chicago
> - returns `Chicago and Northwestern Railroad Station` in Kenosha,
> Wisconsin [https://www.geonames.org/5248432/chicago.html Geonames ID
> 5248432]
>
> I've added some PHPUnit cases in r10553 (xref r10544 for info on the new
> test suite).
>
> It looks like the problem may be related to how cities are now being
> imported into `geonames_summary.name` as `Chicago, IL` instead of the
> canonical `Chicago` in `geonames.name`. So, they fail the exact-match
> search, and the fuzzy search turns up the less-desirable result.
>
> Possibly related to #3728, #5117, r16728-dotorg
>
> I'll look into it more tomorrow, but wanted to document what I've found
> so far. CC @dd32

New description:

 These two searches (and probably many others) return the "wrong" Chicago.

 Instead of Chicago, Illinois
 ([https://www.geonames.org/4887398/chicago.html Geonames ID 4887398]) they
 return cities with an alternate name of Chicago, with a much smaller
 population. It may even match some buildings with population `0` that are
 [https://www.geonames.org/export/codes.html classified as `P.PPL`]?


 *
 https://api.wordpress.org/events/1.0/?number=5&ip=127.0.0.0&locale=en_US&timezone=America/Los_Angeles&location=chicago
 - returns Craigmont, Idaho (
 [https://www.geonames.org/5590063/craigmont.html Geonames ID 5590063] )
 *
 https://api.wordpress.org/events/1.0/?number=5&ip=127.0.0.0&locale=en_US&timezone=America/Chicago&location=chicago
 - returns `Chicago and Northwestern Railroad Station` in Kenosha,
 Wisconsin [https://www.geonames.org/5248432/chicago.html Geonames ID
 5248432]

 I've added some PHPUnit cases in r10553 (xref r10544 and r16810-dotorg for
 info on the new test suite).

 It looks like the problem may be related to how cities are now being
 imported into `geonames_summary.name` as `Chicago, IL` instead of the
 canonical `Chicago` in `geonames.name`. So, they fail the exact-match
 search, and the fuzzy search turns up the less-desirable result.

 Possibly related to #3728, #5117, r16728-dotorg

 I'll look into it more tomorrow, but wanted to document what I've found so
 far. CC @dd32

--

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5562#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan  6 01:29:00 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 06 Jan 2021 01:29:00 -0000
Subject: [wp-meta] [Making WordPress.org] #5562: Events: Exact city
 matches fail because of state abbreviations
In-Reply-To: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
References: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
Message-ID: <066.e825959285c1ef2c3526706108c16a31@wordpress.org>

#5562: Events: Exact city matches fail because of state abbreviations
------------------------+---------------------
 Reporter:  iandunn     |       Owner:  (none)
     Type:  defect      |      Status:  new
 Priority:  normal      |   Milestone:
Component:  Events API  |  Resolution:
 Keywords:              |
------------------------+---------------------

Comment (by dd32):

 > It looks like the problem may be related to how cities are now being
 imported into `geonames_summary.name` as `Chicago, IL` instead of the
 canonical `Chicago` in `geonames.name`. So, they fail the exact-match
 search, and the fuzzy search turns up the less-desirable result.

 As per r16728-dotorg the `Chicago, IL` entry should be added ''in addition
 to'' the canonical `Chicago` one. I'll review the queries and results
 today though to triple check that it's working how I intended it to..

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5562#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan  6 01:30:34 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 06 Jan 2021 01:30:34 -0000
Subject: [wp-meta] [Making WordPress.org] #5562: Events: Exact city
 matches fail because of state abbreviations
In-Reply-To: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
References: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
Message-ID: <066.e05c600b5d901a9a6dfb0e3d7579906d@wordpress.org>

#5562: Events: Exact city matches fail because of state abbreviations
------------------------+---------------------
 Reporter:  iandunn     |       Owner:  (none)
     Type:  defect      |      Status:  new
 Priority:  normal      |   Milestone:
Component:  Events API  |  Resolution:
 Keywords:              |
------------------------+---------------------

Comment (by iandunn):

 Ah, I missed that, thanks!

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5562#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan  6 10:16:36 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 06 Jan 2021 10:16:36 -0000
Subject: [wp-meta] [Making WordPress.org] #5562: Events: Exact city
 matches fail because of state abbreviations
In-Reply-To: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
References: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
Message-ID: <066.43f4801d194fa61d4c3858cee200d376@wordpress.org>

#5562: Events: Exact city matches fail because of state abbreviations
------------------------+---------------------
 Reporter:  iandunn     |       Owner:  (none)
     Type:  defect      |      Status:  new
 Priority:  normal      |   Milestone:
Component:  Events API  |  Resolution:
 Keywords:              |
------------------------+---------------------

Comment (by dd32):

 Apologies for the rambling comment @iandunn.. I'm just working through it
 and noting my thought process for myself..

 After looking into this, there's several things happening:
  1. There was a data error, in that some of the source data had invalid
 UTF8 data which caused only partial Chicago data to be imported.

 I've re-imported the data after fixing the issues (not all committed yet)
 which results in a more complete data set, but still 'invalid' responses.

 Replying to [ticket:5562 iandunn]:
 > *
 https://api.wordpress.org/events/1.0/?number=5&ip=127.0.0.0&locale=en_US&timezone=America/Los_Angeles&location=chicago
 - returns Craigmont, Idaho (
 [https://www.geonames.org/5590063/craigmont.html Geonames ID 5590063] )

 2. This looks correct with the current logic. Yes, hang on, let me
 explain..

  - Timezone trumps population, #3367 comes into play here.
  - Alternate names are treated as the same level of priority as
 "preferred" names

 I don't think timezone should be a trump here in every case, but rather
 only when it's a preferred name (ie. Portland, OR / Portland, ME).

 The Chicago examples has come up due to the greater number of cities after
 #3728, it looks like most of the chicago entries are ''probably''
 alternate names (There's Chicago's in every US timezone, just like there's
 a Portland in each timezone).

 As part of that, I've rebuilt the table again, this time marking alternate
 names as alts, so that preferred names can be prioritised.. Unfortunately
 I've done something wrong, and the `alt` field didn't get filled
 correctly, but from what I can tell, it'll fix these two examples and a
 few others I've been able to come up with.

 I'll loop back to this tomorrow, but if you want to Ian, you can run
 queries against the `geoname_summary_20210106082158` table to test with.
 Adding `ORDER BY alt ASC` to the start of the order by's seems to do the
 trick (Test failures such as `Dona ana` are due to the alt flag failure I
 mentioned above)

 I've struggled to test it with PHPUnit, as it keeps running out of memory
 and requires PHPUnit8 by looks (Not 6, 7, or 9 as I had installed)..

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5562#comment:5>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan  6 13:50:28 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 06 Jan 2021 13:50:28 -0000
Subject: [wp-meta] [Making WordPress.org] #5563: I a translation file is
 imported that contains wrong placeholders the line is not rejected.
Message-ID: <054.693d259f4f715effff6fe69cef76e827@wordpress.org>

#5563: I a translation file is imported that contains wrong placeholders the line
is not rejected.
--------------------------------------+--------------------------
 Reporter:  psmits1567                |      Owner:  (none)
     Type:  enhancement               |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:  needs-design
--------------------------------------+--------------------------
 Currently, if you import a file that contains a translation where the
 placeholder is not properly formatted, the line is not rejected but
 inserted and creates a waiting record with warning.
 Looking at the daily number of errors passing by, it would be better to
 reject those lines instead of inserting them with an error.
 The person that imports translations is responsible to import properly
 formatted strings. Now as a PTE or GTE you have to either correct those
 lines or remove them. Because obviously they are not corrected by the
 person that imports them
 Examples "% s", "% 1 $ s", "% d", "% 2 $ s"
 If rejected indicate the number of lines rejected, and a hint of the
 rejected reason.
 E.g. "Import has finished with errors in XXX lines, containing wrong
 formatted placeholders!"

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5563>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan  6 16:53:32 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 06 Jan 2021 16:53:32 -0000
Subject: [wp-meta] [Making WordPress.org] #5562: Events: Exact city
 matches fail because of state abbreviations
In-Reply-To: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
References: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
Message-ID: <066.d1125f634972f8d50cb3a5dcf772b7d5@wordpress.org>

#5562: Events: Exact city matches fail because of state abbreviations
------------------------+---------------------
 Reporter:  iandunn     |       Owner:  (none)
     Type:  defect      |      Status:  new
 Priority:  normal      |   Milestone:
Component:  Events API  |  Resolution:
 Keywords:              |
------------------------+---------------------

Comment (by iandunn):

 Ah, yes, complexity abounds :) Thanks for digging into it!

 Weighting the preferred name sounds like a good approach. I'll play around
 a bit with that too, and see if I can add some more tests around the
 various situations.

 Although, this might be a reason to revisit the idea of switching to an
 external API to handle this kind of thing. I remember Josepha and I looked
 into Google's Geocoding API after the WP 4.8 release; I'll try to find the
 details of where that left off.

 Another idea: Instead of the API trying and pick the perfect match, maybe
 it should just return all the likely ones, and Core could give the user a
 dropdown to pick the right one. [https://developers.google.com/places/web-
 service/autocomplete Google's Places Autocomplete API] is designed for
 that (h/t https://developers.google.com/maps/documentation/geocoding/best-
 practices).

 ---

 I initially had problems getting PHPUnit working on my sandbox, but it's
 working well for me now, using v9.5. If you're running into the same
 problems I was, disabling xdebug should fix it. Check out the new readme
 file in the API root if you haven't already, it has some details.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5562#comment:6>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan  6 17:31:47 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 06 Jan 2021 17:31:47 -0000
Subject: [wp-meta] [Making WordPress.org] #5562: Events: Exact city
 matches fail because of state abbreviations
In-Reply-To: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
References: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
Message-ID: <066.10a1a171dd072c2328843bf26369163a@wordpress.org>

#5562: Events: Exact city matches fail because of state abbreviations
------------------------+---------------------
 Reporter:  iandunn     |       Owner:  (none)
     Type:  defect      |      Status:  new
 Priority:  normal      |   Milestone:
Component:  Events API  |  Resolution:
 Keywords:              |
------------------------+---------------------

Comment (by iandunn):

 `--process-isolation` can also help for PHPUnit, but I've only found it
 necessary when using the watch task.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5562#comment:7>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan  7 00:14:21 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 07 Jan 2021 00:14:21 -0000
Subject: [wp-meta] [Making WordPress.org] #5563: I a translation file is
 imported that contains wrong placeholders the line is not rejected.
In-Reply-To: <054.693d259f4f715effff6fe69cef76e827@wordpress.org>
References: <054.693d259f4f715effff6fe69cef76e827@wordpress.org>
Message-ID: <069.5f8a3f177bb3d29f0d528365c61a30e0@wordpress.org>

#5563: I a translation file is imported that contains wrong placeholders the line
is not rejected.
--------------------------------------+---------------------
 Reporter:  psmits1567                |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------
Changes (by dd32):

 * keywords:  needs-design =>


Comment:

 > The person that imports translations is responsible to import properly
 formatted strings. Now as a PTE or GTE you have to either correct those
 lines or remove them. Because obviously they are not corrected by the
 person that imports them
 > Examples "% s", "% 1 $ s", "% d", "% 2 $ s"

 Whenever you see spaces after/around those placeholders like that, you can
 bet it's a machine translated (probably Google Translate) translation.

 My understanding was that importing/uploading of strings required a higher
 level of access though? As in, regular accounts shouldn't have the ability
 to upload accounts, and if a PTE is processing uploads such as this they
 probably shouldn't have the status for that language they're not
 reviewing?

 Possibly a dup of #4171

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5563#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan  7 04:29:54 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  7 Jan 2021 04:29:54 +0000 (UTC)
Subject: [wp-meta] [10554]
 sites/trunk/api.wordpress.org/public_html/events/1.0: Events API: When
 determining a location,
 preference non-alternate names and populated areas over alternate names /
 unpopulated locations.
Message-ID: <20210107042954.BB10F1B0038F@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210107/4338fb6e/attachment.html>

From noreply at wordpress.org  Thu Jan  7 04:29:59 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 07 Jan 2021 04:29:59 -0000
Subject: [wp-meta] [Making WordPress.org] #5562: Events: Exact city
 matches fail because of state abbreviations
In-Reply-To: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
References: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
Message-ID: <066.8d2d391b85029bb209163c4754355a11@wordpress.org>

#5562: Events: Exact city matches fail because of state abbreviations
------------------------+---------------------
 Reporter:  iandunn     |       Owner:  dd32
     Type:  defect      |      Status:  closed
 Priority:  normal      |   Milestone:
Component:  Events API  |  Resolution:  fixed
 Keywords:              |
------------------------+---------------------
Changes (by dd32):

 * owner:  (none) => dd32
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"10554" 10554]:
 {{{
 #!CommitTicketReference repository="" revision="10554"
 Events API: When determining a location, preference non-alternate names
 and populated areas over alternate names / unpopulated locations.

 Fixes #5562.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5562#comment:8>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan  7 05:50:27 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  7 Jan 2021 05:50:27 +0000 (UTC)
Subject: [wp-meta] [10555]
 sites/trunk/api.wordpress.org/public_html/events/1.0/index.php: Events API:
 Avoid a PHP Warning when invalid UTF8 character sequences are encountered.
Message-ID: <20210107055027.6C5261B0038F@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210107/7c32a4fc/attachment.html>

From noreply at wordpress.org  Thu Jan  7 07:17:46 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 07 Jan 2021 07:17:46 -0000
Subject: [wp-meta] [Making WordPress.org] #5563: I a translation file is
 imported that contains wrong placeholders the line is not rejected.
In-Reply-To: <054.693d259f4f715effff6fe69cef76e827@wordpress.org>
References: <054.693d259f4f715effff6fe69cef76e827@wordpress.org>
Message-ID: <069.bd1c1e62941df148d1538aceba911d0a@wordpress.org>

#5563: I a translation file is imported that contains wrong placeholders the line
is not rejected.
--------------------------------------+---------------------
 Reporter:  psmits1567                |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------

Comment (by psmits1567):

 It is related, but a more progressive approach. The number of warning
 records is huge, so we need to really concider to make a decision about
 this.

 Maybe also consider to not save records that have a missing/wrong
 placeholder. Currrently if you are manually translating, a warning is
 given. But the record is stored and creates a warning in polyglots warning
 channel. If you do not have PTE or GTE capability,you cannot correct it.
 Hence a PTE or GTE needs to correct it.Just generate a warning without
 saving the record, would cause less records in the database and less
 waiting stringd, and less work for the PTE/GTE

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5563#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan  7 13:32:57 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 07 Jan 2021 13:32:57 -0000
Subject: [wp-meta] [Making WordPress.org] #5564: WordPress.org secret-key
 service output does not follow coding standards
Message-ID: <054.2c643a246d5c7c0215b143203ed7e23e@wordpress.org>

#5564: WordPress.org secret-key service output does not follow coding standards
-------------------------+--------------------
 Reporter:  johnpgreen   |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:
Component:  General      |   Keywords:
-------------------------+--------------------
 The output generated by the WordPress.org secret-key service
 (https://api.wordpress.org/secret-key/1.1/salt/) outputs PHP that doesn't
 conform to the WordPress PHP Coding Standards.

 Specifically, "[u]nless otherwise specified, parentheses should have
 spaces inside of them." (https://make.wordpress.org/core/handbook/best-
 practices/coding-standards/php/#space-usage)

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5564>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan  7 19:07:12 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 07 Jan 2021 19:07:12 -0000
Subject: [wp-meta] [Making WordPress.org] #4487: Set the codex to
 readonly
In-Reply-To: <051.3cea0a15d04c8a963647fe1d9be86eac@wordpress.org>
References: <051.3cea0a15d04c8a963647fe1d9be86eac@wordpress.org>
Message-ID: <066.0fa4e18fc5ce48d0bbc7a00b2408e364@wordpress.org>

#4487: Set the codex to readonly
---------------------+---------------------
 Reporter:  Clorith  |       Owner:  (none)
     Type:  task     |      Status:  new
 Priority:  normal   |   Milestone:
Component:  HelpHub  |  Resolution:
 Keywords:           |
---------------------+---------------------

Comment (by macmanx):

 It's been over a year since the last update here, and a spam dump was just
 cleared out of the Managing Plugins page.

 Any update on this particular aspect?

 With less eyes on the Codex these days, spam can linger far longer, thus
 damaging WordPress's perception to folks who find our docs there via
 search engines. Managing Plugins was one of our most popular docs, and in
 this case, the spam lingered for 3 weeks:
 https://codex.wordpress.org/index.php?title=Managing_Plugins&action=historysubmit&type=revision&diff=170673&oldid=170634

 I understand we can't close the Codex totally since pages must still be
 transferred, but simply setting the Codex to read-only would be a huge
 help in limiting spam.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4487#comment:9>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan  7 22:02:35 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 07 Jan 2021 22:02:35 -0000
Subject: [wp-meta] [Making WordPress.org] #5565: Plugin Directory: Adding
 abused term
Message-ID: <051.8c0474f09bdede1a47b772308205f96d@wordpress.org>

#5565: Plugin Directory: Adding abused term
------------------------------+-----------------------
 Reporter:  Ipstenu           |      Owner:  (none)
     Type:  defect            |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:  has-patch
------------------------------+-----------------------
 Adding a new term to be blocked on plugin submission to help protect
 trademarks.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5565>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan  7 22:03:28 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 07 Jan 2021 22:03:28 -0000
Subject: [wp-meta] [Making WordPress.org] #5565: Plugin Directory:
 Adding abused term
In-Reply-To: <051.8c0474f09bdede1a47b772308205f96d@wordpress.org>
References: <051.8c0474f09bdede1a47b772308205f96d@wordpress.org>
Message-ID: <066.01e6078e2657dbd5cf3f2fdc03f47852@wordpress.org>

#5565: Plugin Directory: Adding abused term
------------------------------+---------------------
 Reporter:  Ipstenu           |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  has-patch         |
------------------------------+---------------------
Changes (by Ipstenu):

 * Attachment "5565.diff" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5565>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan  7 22:04:33 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  7 Jan 2021 22:04:33 +0000 (UTC)
Subject: [wp-meta] [10556]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/shortcodes/class-upload-handler.php:
 Plugin Directory: Add new plugin to the protected names
Message-ID: <20210107220433.816C51B001A4@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210107/9530efb1/attachment.html>

From noreply at wordpress.org  Thu Jan  7 22:04:37 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 07 Jan 2021 22:04:37 -0000
Subject: [wp-meta] [Making WordPress.org] #5565: Plugin Directory:
 Adding abused term
In-Reply-To: <051.8c0474f09bdede1a47b772308205f96d@wordpress.org>
References: <051.8c0474f09bdede1a47b772308205f96d@wordpress.org>
Message-ID: <066.b4acd7f50afc1e33a64f60e62b740012@wordpress.org>

#5565: Plugin Directory: Adding abused term
------------------------------+----------------------
 Reporter:  Ipstenu           |       Owner:  Ipstenu
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:  has-patch         |
------------------------------+----------------------
Changes (by Ipstenu):

 * owner:  (none) => Ipstenu
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"10556" 10556]:
 {{{
 #!CommitTicketReference repository="" revision="10556"
 Plugin Directory: Add new plugin to the protected names

 adding wp-mail-smtp, which is easy to miss.

 Fixes #5565
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5565#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan  7 22:25:00 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  7 Jan 2021 22:25:00 +0000 (UTC)
Subject: [wp-meta] [10557]
 sites/trunk/api.wordpress.org/public_html/events/1.0: Events: Weight
 country over preferred name when ordering.
Message-ID: <20210107222500.99CB61B001A4@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210107/3d6fee07/attachment-0001.html>

From noreply at wordpress.org  Thu Jan  7 22:25:05 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 07 Jan 2021 22:25:05 -0000
Subject: [wp-meta] [Making WordPress.org] #5562: Events: Exact city
 matches fail because of state abbreviations
In-Reply-To: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
References: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
Message-ID: <066.419c4bb5a7995acae0daac49479a2f5c@wordpress.org>

#5562: Events: Exact city matches fail because of state abbreviations
------------------------+---------------------
 Reporter:  iandunn     |       Owner:  dd32
     Type:  defect      |      Status:  closed
 Priority:  normal      |   Milestone:
Component:  Events API  |  Resolution:  fixed
 Keywords:              |
------------------------+---------------------

Comment (by iandunn):

 In [changeset:"10557" 10557]:
 {{{
 #!CommitTicketReference repository="" revision="10557"
 Events: Weight country over preferred name when ordering.

 See #5562.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5562#comment:9>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan  7 22:31:22 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 07 Jan 2021 22:31:22 -0000
Subject: [wp-meta] [Making WordPress.org] #5562: Events: Exact city
 matches fail because of state abbreviations
In-Reply-To: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
References: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
Message-ID: <066.56f609a9b6692cc814faad085b7aba4d@wordpress.org>

#5562: Events: Exact city matches fail because of state abbreviations
------------------------+---------------------
 Reporter:  iandunn     |       Owner:  dd32
     Type:  defect      |      Status:  closed
 Priority:  normal      |   Milestone:
Component:  Events API  |  Resolution:  fixed
 Keywords:              |
------------------------+---------------------

Comment (by iandunn):

 Kudos for the fix :)

 I found one problem with the new ranking, but fixed it in r10557.

 What's the reason to import entries with `population = 0`?

 I opened a #core52249 for the idea about showing users multiple potential
 locations.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5562#comment:10>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan  7 22:36:01 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 07 Jan 2021 22:36:01 -0000
Subject: [wp-meta] [Making WordPress.org] #4487: Set the codex to
 readonly
In-Reply-To: <051.3cea0a15d04c8a963647fe1d9be86eac@wordpress.org>
References: <051.3cea0a15d04c8a963647fe1d9be86eac@wordpress.org>
Message-ID: <066.5116faa9fb54ec9977704ac40439c95e@wordpress.org>

#4487: Set the codex to readonly
-----------------------------+-----------------------
 Reporter:  Clorith          |       Owner:  dd32
     Type:  task             |      Status:  accepted
 Priority:  normal           |   Milestone:
Component:  HelpHub          |  Resolution:
 Keywords:  pending-systems  |
-----------------------------+-----------------------
Changes (by dd32):

 * keywords:   => pending-systems
 * owner:  (none) => dd32
 * status:  new => accepted


Comment:

 Removing edit rights for regular users was started in November, It's just
 pending a systems deploy.

 https://make.wordpress.org/systems/2020/11/11/could-i-get-a-deploy/

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4487#comment:10>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan  7 22:47:38 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 07 Jan 2021 22:47:38 -0000
Subject: [wp-meta] [Making WordPress.org] #5562: Events: Exact city
 matches fail because of state abbreviations
In-Reply-To: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
References: <051.5e8fdca3d11168de7c85d36bfeaf87bf@wordpress.org>
Message-ID: <066.f6efc38eefe19ec041244c51e4da9809@wordpress.org>

#5562: Events: Exact city matches fail because of state abbreviations
------------------------+---------------------
 Reporter:  iandunn     |       Owner:  dd32
     Type:  defect      |      Status:  closed
 Priority:  normal      |   Milestone:
Component:  Events API  |  Resolution:  fixed
 Keywords:              |
------------------------+---------------------

Comment (by dd32):

 Replying to [comment:10 iandunn]:
 > What's the reason to import entries with `population = 0`?

 Quite simply, the population figures aren't available for every location,
 they're available for ''most'' locations, but not all.

 For reference, only 10% of the current non-alternate name records have a
 population of greater than 0.
 Previous to #3728 it looks like it was in the range of 75% had a
 population count > 0.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5562#comment:11>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan  7 22:54:03 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 07 Jan 2021 22:54:03 -0000
Subject: [wp-meta] [Making WordPress.org] #5564: WordPress.org
 secret-key service output does not follow coding standards
In-Reply-To: <054.2c643a246d5c7c0215b143203ed7e23e@wordpress.org>
References: <054.2c643a246d5c7c0215b143203ed7e23e@wordpress.org>
Message-ID: <069.482b00073888f89a3ffe1261ffe0412f@wordpress.org>

#5564: WordPress.org secret-key service output does not follow coding standards
-------------------------+---------------------
 Reporter:  johnpgreen   |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  API          |  Resolution:
 Keywords:  close        |
-------------------------+---------------------
Changes (by dd32):

 * keywords:   => close
 * component:  General => API


Comment:

 IMHO: The salt API should never be used directly, but it exists for legacy
 reasons.  It's primarily only used by those who create a `wp-config.php`
 file manually, and even then I question how many actually use it.

 Unfortunately the output cannot be changed, as WordPress expects it to be
 in the current format: https://core.trac.wordpress.org/browser/trunk/src
 /wp-admin/setup-config.php?marks=348-351#L335

 Actually, I guess I could fix the API output.. but it would require
 violating a different coding standards rule, `SECURE_AUTH_SALT` would have
 to live without having a space after the comma in the `define()`.

 While I could bump the version to `1.2` it doesn't seem to serve much
 purpose in doing so, as it should be rare that the API is needed anymore.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5564#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan  7 23:43:52 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 07 Jan 2021 23:43:52 -0000
Subject: [wp-meta] [Making WordPress.org] #5564: WordPress.org
 secret-key service output does not follow coding standards
In-Reply-To: <054.2c643a246d5c7c0215b143203ed7e23e@wordpress.org>
References: <054.2c643a246d5c7c0215b143203ed7e23e@wordpress.org>
Message-ID: <069.d74196893afc100729dfcda1921a83db@wordpress.org>

#5564: WordPress.org secret-key service output does not follow coding standards
-------------------------+---------------------
 Reporter:  johnpgreen   |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  API          |  Resolution:
 Keywords:  close        |
-------------------------+---------------------

Comment (by johnpgreen):

 Ok, I think I may be confused.

 If this only exists for legacy reasons, why is it still referenced in `wp-
 config-sample.php` in the WordPress download?

 What is the modern alternative to the API?

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5564#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan  8 00:16:29 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 08 Jan 2021 00:16:29 -0000
Subject: [wp-meta] [Making WordPress.org] #5564: WordPress.org
 secret-key service output does not follow coding standards
In-Reply-To: <054.2c643a246d5c7c0215b143203ed7e23e@wordpress.org>
References: <054.2c643a246d5c7c0215b143203ed7e23e@wordpress.org>
Message-ID: <069.fac69c99ddbf00203311bc187968def8@wordpress.org>

#5564: WordPress.org secret-key service output does not follow coding standards
-------------------------+---------------------
 Reporter:  johnpgreen   |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  API          |  Resolution:
 Keywords:  close        |
-------------------------+---------------------

Comment (by dd32):

 Replying to [comment:2 johnpgreen]:
 > What is the modern alternative to the API?

 Using `wp-admin/setup-config.php` :)

 It still exists within wp-config-sample.php for those who setup their wp-
 config files manually. Ideally, one would not rely upon a remote API to
 generate these keys though, and would simply replace `put your unique
 phrase here` with "random junk" `dlfksghjarsel524w09e80e9d u30jqc3iw3a-
 ds0c3j9m9-cj` (a keyboard mash) which is arguably as secure, if not more
 so, than using the remote API.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5564#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan  8 00:52:43 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 08 Jan 2021 00:52:43 -0000
Subject: [wp-meta] [Making WordPress.org] #5564: WordPress.org
 secret-key service output does not follow coding standards
In-Reply-To: <054.2c643a246d5c7c0215b143203ed7e23e@wordpress.org>
References: <054.2c643a246d5c7c0215b143203ed7e23e@wordpress.org>
Message-ID: <069.a6ab53f6d08561d29ac78f7ea2237d42@wordpress.org>

#5564: WordPress.org secret-key service output does not follow coding standards
-------------------------+---------------------
 Reporter:  johnpgreen   |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  API          |  Resolution:
 Keywords:  close        |
-------------------------+---------------------

Comment (by johnpgreen):

 Gotcha. Thanks, Dion!

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5564#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan  8 02:25:26 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  8 Jan 2021 02:25:26 +0000 (UTC)
Subject: [wp-meta] [10558]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-developer/inc:
 Developer Theme: Avoid some PHP warnings/notices,
 `is_singular()` doesn't always mean there's a singular post available...
Message-ID: <20210108022526.CB4991B003D4@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210108/5b8ed000/attachment.html>

From noreply at wordpress.org  Fri Jan  8 15:28:29 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 08 Jan 2021 15:28:29 -0000
Subject: [wp-meta] [Making WordPress.org] #5566: Plugin search feed URLs
 should 404
Message-ID: <058.fd75444d198cd966a8677da75fce149e@wordpress.org>

#5566: Plugin search feed URLs should 404
------------------------------+--------------------
 Reporter:  jonoaldersonwp    |      Owner:  (none)
     Type:  defect            |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:  seo
------------------------------+--------------------
 URLs like https://wordpress.org/plugins/search/cross-rss/feed/ and
 https://wordpress.org/plugins/search/cross-rss/feed/rss2/ return an empty
 response and 200 status.

 They should return a 404 response, and the 404 template.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5566>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan  8 15:56:38 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 08 Jan 2021 15:56:38 -0000
Subject: [wp-meta] [Making WordPress.org] #5567: Adapt the page title on
 filtered plugin review archives
Message-ID: <058.4ea44ce5802bfed57506a9f3575f1ea9@wordpress.org>

#5567: Adapt the page title on filtered plugin review archives
------------------------------+--------------------
 Reporter:  jonoaldersonwp    |      Owner:  (none)
     Type:  defect            |     Status:  new
 Priority:  lowest            |  Milestone:
Component:  Plugin Directory  |   Keywords:
------------------------------+--------------------
 URLs like https://wordpress.org/support/plugin/gutenberg/reviews/?filter=4
 should take the 'score' filter into account in the page title.

 Alter the template as follows:

 From: <title>[%plugin_name%] Reviews (%star% stars only) - page %page%
 &#124; WordPress.org</title>
 To: <title>[%plugin_name%] Reviews (%star% stars only) - page %page%
 &#124; WordPress.org</title>

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5567>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan  8 15:57:39 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 08 Jan 2021 15:57:39 -0000
Subject: [wp-meta] [Making WordPress.org] #5567: Adapt the page title on
 filtered plugin review archives
In-Reply-To: <058.4ea44ce5802bfed57506a9f3575f1ea9@wordpress.org>
References: <058.4ea44ce5802bfed57506a9f3575f1ea9@wordpress.org>
Message-ID: <073.7a77915367237d05b2cf4fbbe9e525fe@wordpress.org>

#5567: Adapt the page title on filtered plugin review archives
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  lowest          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------
Changes (by jonoaldersonwp):

 * component:  Plugin Directory => Support Forums


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5567#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan  8 16:02:20 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 08 Jan 2021 16:02:20 -0000
Subject: [wp-meta] [Making WordPress.org] #5567: Adapt the page title on
 filtered plugin review archives
In-Reply-To: <058.4ea44ce5802bfed57506a9f3575f1ea9@wordpress.org>
References: <058.4ea44ce5802bfed57506a9f3575f1ea9@wordpress.org>
Message-ID: <073.ece1d7206daf5bf692d901120a0c08df@wordpress.org>

#5567: Adapt the page title on filtered plugin review archives
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  lowest          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------

Comment (by joyously):

 The `From` and `To` look the same to me.
 What am I missing?

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5567#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan  8 16:08:37 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 08 Jan 2021 16:08:37 -0000
Subject: [wp-meta] [Making WordPress.org] #5567: Adapt the page title on
 filtered plugin review archives
In-Reply-To: <058.4ea44ce5802bfed57506a9f3575f1ea9@wordpress.org>
References: <058.4ea44ce5802bfed57506a9f3575f1ea9@wordpress.org>
Message-ID: <073.30e1f1917beffebd5e6ba6fa0b0c5ae5@wordpress.org>

#5567: Adapt the page title on filtered plugin review archives
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  lowest          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------

Old description:

> URLs like
> https://wordpress.org/support/plugin/gutenberg/reviews/?filter=4 should
> take the 'score' filter into account in the page title.
>
> Alter the template as follows:
>
> From: <title>[%plugin_name%] Reviews (%star% stars only) - page %page%
> &#124; WordPress.org</title>
> To: <title>[%plugin_name%] Reviews (%star% stars only) - page %page%
> &#124; WordPress.org</title>

New description:

 URLs like https://wordpress.org/support/plugin/gutenberg/reviews/?filter=4
 should take the 'score' filter into account in the page title.

 Alter the template as follows:

 From: <title>[%plugin_name%] Reviews - page %page% &#124;
 WordPress.org</title>
 To: <title>[%plugin_name%] Reviews (%star% stars only) - page %page%
 &#124; WordPress.org</title>

--

Comment (by jonoaldersonwp):

 Oops. Updated.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5567#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan  8 16:08:55 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 08 Jan 2021 16:08:55 -0000
Subject: [wp-meta] [Making WordPress.org] #5567: Adapt the page title on
 filtered plugin review archives
In-Reply-To: <058.4ea44ce5802bfed57506a9f3575f1ea9@wordpress.org>
References: <058.4ea44ce5802bfed57506a9f3575f1ea9@wordpress.org>
Message-ID: <073.6208866e0f567a024f7b7850b9047d35@wordpress.org>

#5567: Adapt the page title on filtered plugin review archives
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  lowest          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------
Description changed by jonoaldersonwp:

Old description:

> URLs like
> https://wordpress.org/support/plugin/gutenberg/reviews/?filter=4 should
> take the 'score' filter into account in the page title.
>
> Alter the template as follows:
>
> From: <title>[%plugin_name%] Reviews - page %page% &#124;
> WordPress.org</title>
> To: <title>[%plugin_name%] Reviews (%star% stars only) - page %page%
> &#124; WordPress.org</title>

New description:

 URLs like https://wordpress.org/support/plugin/gutenberg/reviews/?filter=4
 should take the 'score' filter into account in the page title.

 Alter the template as follows:

 From: `<title>[%plugin_name%] Reviews - page %page% &#124;
 WordPress.org</title>`
 To: `<title>[%plugin_name%] Reviews (%star% stars only) - page %page%
 &#124; WordPress.org</title>`

--

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5567#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan  8 19:31:26 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  8 Jan 2021 19:31:26 +0000 (UTC)
Subject: [wp-meta] [10559]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/front-page.php:
 w.org Homepage: Link to _user_ documentation rather than developer.
Message-ID: <20210108193126.186771B00386@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210108/0c0a0231/attachment-0001.html>

From noreply at wordpress.org  Fri Jan  8 21:00:21 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 08 Jan 2021 21:00:21 -0000
Subject: [wp-meta] [Making WordPress.org] #5568: Plugin Directory: Do not
 display author names if there are no committers
Message-ID: <051.2fabbe1e976feda072481d1eb143be44@wordpress.org>

#5568: Plugin Directory: Do not display author names if there are no committers
------------------------------+-------------------------------------
 Reporter:  Ipstenu           |      Owner:  (none)
     Type:  defect            |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:  has-patch needs-testing
------------------------------+-------------------------------------
 There are a few reasons why there would be no committers to a plugin, but
 the primary are:

 * Authors are banned (if so, we do not wish to give them free advertising)
 * Author has request a GDPR removal (if so, we should make sure we don't
 accidentally display information they wish removed)

 This is not a perfect fix, nor does it address all concerns, but it is a
 start.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5568>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan  8 21:01:08 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 08 Jan 2021 21:01:08 -0000
Subject: [wp-meta] [Making WordPress.org] #5568: Plugin Directory: Do
 not display author names if there are no committers
In-Reply-To: <051.2fabbe1e976feda072481d1eb143be44@wordpress.org>
References: <051.2fabbe1e976feda072481d1eb143be44@wordpress.org>
Message-ID: <066.339101ac2e526833603a92e5080cd0e0@wordpress.org>

#5568: Plugin Directory: Do not display author names if there are no committers
-------------------------------------+---------------------
 Reporter:  Ipstenu                  |       Owner:  (none)
     Type:  defect                   |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  Plugin Directory         |  Resolution:
 Keywords:  has-patch needs-testing  |
-------------------------------------+---------------------
Changes (by Ipstenu):

 * Attachment "5568.diff" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5568>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan  8 21:59:07 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  8 Jan 2021 21:59:07 +0000 (UTC)
Subject: [wp-meta] [10560] sites/trunk/wordpress.org/public_html/style:
 Style: Update styles for Mobile page in r16840
Message-ID: <20210108215907.D27D91B00386@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210108/a4f6bded/attachment-0001.html>

From noreply at wordpress.org  Fri Jan  8 22:06:08 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  8 Jan 2021 22:06:08 +0000 (UTC)
Subject: [wp-meta] [10561]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/front-page.php:
 w.org Homepage: Link directly to Swag store.
Message-ID: <20210108220608.35C601B00386@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210108/3313b830/attachment.html>

From noreply at wordpress.org  Fri Jan  8 23:58:07 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  8 Jan 2021 23:58:07 +0000 (UTC)
Subject: [wp-meta] [10562]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main:
 wporg-main: Move hosting section above downloads for UX.
Message-ID: <20210108235807.2FB251B00386@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210108/153f99fc/attachment-0001.html>

From noreply at wordpress.org  Sat Jan  9 00:01:54 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat,  9 Jan 2021 00:01:54 +0000 (UTC)
Subject: [wp-meta] [10563]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/functions.php:
 wporg-main: Use dynamic cachebuster for convenience.
Message-ID: <20210109000154.49AB31B00412@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210109/530dd6b3/attachment.html>

From noreply at wordpress.org  Sun Jan 10 04:08:25 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 10 Jan 2021 04:08:25 -0000
Subject: [wp-meta] [Making WordPress.org] #5569: rest api not returns all
 information about some embedded objects of post
Message-ID: <059.18c8141395161774fad9d130aed387f5@wordpress.org>

#5569: rest api not returns all information about some embedded objects of post
-----------------------------+--------------------
 Reporter:  sashakozlovskiy  |      Owner:  (none)
     Type:  defect           |     Status:  new
 Priority:  normal           |  Milestone:
Component:  General          |   Keywords:
-----------------------------+--------------------
 When i want to get all information,for example,about category of post,i
 can get only name and id of category. But i want to get also description
 of category. Yes,i know,that i can do aditional http request,using
 category id,but why for author i have this information,but for category
 and may be for tag - not? Please fix this issue in your rest api. Also i
 have field links,but i don't want to have this in json. Why in json i get
 it? You can see example of this  issues in link https://опиши-мне.рф/wp-
 json/wp/v2/posts/1935?_fields=id,title&_embed=author,wp:term. Thank you
 for your reply.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5569>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sun Jan 10 06:50:41 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 10 Jan 2021 06:50:41 -0000
Subject: [wp-meta] [Making WordPress.org] #5569: rest api not returns
 all information about some embedded objects of post
In-Reply-To: <059.18c8141395161774fad9d130aed387f5@wordpress.org>
References: <059.18c8141395161774fad9d130aed387f5@wordpress.org>
Message-ID: <074.8a7250789e23e34fcdb1224fe78f9482@wordpress.org>

#5569: rest api not returns all information about some embedded objects of post
-----------------------------+----------------------
 Reporter:  sashakozlovskiy  |       Owner:  (none)
     Type:  defect           |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  General          |  Resolution:  invalid
 Keywords:                   |
-----------------------------+----------------------
Changes (by Otto42):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 This is the meta trac. If you have issues with the REST API and the data
 it returns, then that is part of the WordPress core and would go on the
 core.trac instead.

 However, the category data would not be returned with the post because
 it's not information that is about the post, but about the category. This
 seems unlikely to get any traction, since the purpose of having them
 separate is so that you don't request excessive amounts of data all at
 once.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5569#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sun Jan 10 15:40:30 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 10 Jan 2021 15:40:30 -0000
Subject: [wp-meta] [Making WordPress.org] #5570: Plugins API - inconsistent
 results for short_description if being trimmed.
Message-ID: <056.ca4336df3a2aba7b940af656eb0546a9@wordpress.org>

#5570: Plugins API - inconsistent results for short_description if being trimmed.
--------------------------+--------------------
 Reporter:  polevaultweb  |      Owner:  (none)
     Type:  defect        |     Status:  new
 Priority:  normal        |  Milestone:
Component:  API           |   Keywords:
--------------------------+--------------------
 My plugin has a short description longer than 150 characters in the
 readme.txt (due to the ampersand being turned into it's HTML entity taking
 it over the limit).

 However, the API request for 'plugin_information' returns different
 results for the short_description at different times of the day.


 {{{
 curl --location -g --request GET
 'https://api.wordpress.org/plugins/info/1.2/?action=plugin_information&request[slug
 ]=wp-user-manager&request[fields]=short_description'
 }}}


 It can return:

 **The most customizable profiles &amp; community builder WordPress plugin
 with front-end login, registration, profile customization and content
 restrict &hellip;
 **
 Which is 150 chars if you don't count ' &hellip;'

 But then a later call to the API returns:

 **The most customizable profiles &amp; community builder WordPress plugin
 with front-end login, registration, profile customization&hellip;**

 It feels like some double trimming is happening somewhere along the line.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5570>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sun Jan 10 17:23:08 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 10 Jan 2021 17:23:08 -0000
Subject: [wp-meta] [Making WordPress.org] #5569: rest api not returns
 all information about some embedded objects of post
In-Reply-To: <059.18c8141395161774fad9d130aed387f5@wordpress.org>
References: <059.18c8141395161774fad9d130aed387f5@wordpress.org>
Message-ID: <074.47008dcb13d1ac80f5c69073f9437214@wordpress.org>

#5569: rest api not returns all information about some embedded objects of post
-----------------------------+----------------------
 Reporter:  sashakozlovskiy  |       Owner:  (none)
     Type:  defect           |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  General          |  Resolution:  invalid
 Keywords:                   |
-----------------------------+----------------------

Comment (by sashakozlovskiy):

 Ok,please give me link on which i can report issue to wordpress api. As
 for data,according to documentation,i can return all data about other
 object,if i will use _embed argument,as in my example.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5569#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 11 00:56:23 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 11 Jan 2021 00:56:23 -0000
Subject: [wp-meta] [Making WordPress.org] #5570: Plugins API -
 inconsistent results for short_description if being trimmed.
In-Reply-To: <056.ca4336df3a2aba7b940af656eb0546a9@wordpress.org>
References: <056.ca4336df3a2aba7b940af656eb0546a9@wordpress.org>
Message-ID: <071.95e2e5ed6c09ff9f148beec47438e884@wordpress.org>

#5570: Plugins API - inconsistent results for short_description if being trimmed.
------------------------------+-----------------------
 Reporter:  polevaultweb      |       Owner:  dd32
     Type:  defect            |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------
Changes (by dd32):

 * owner:  (none) => dd32
 * status:  new => accepted
 * component:  API => Plugin Directory


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5570#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 11 01:04:00 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 11 Jan 2021 01:04:00 -0000
Subject: [wp-meta] [Making WordPress.org] #5568: Plugin Directory: Do
 not display author names if there are no committers
In-Reply-To: <051.2fabbe1e976feda072481d1eb143be44@wordpress.org>
References: <051.2fabbe1e976feda072481d1eb143be44@wordpress.org>
Message-ID: <066.d3446b46a18ea24139fd65796557eba0@wordpress.org>

#5568: Plugin Directory: Do not display author names if there are no committers
-------------------------------------+---------------------
 Reporter:  Ipstenu                  |       Owner:  (none)
     Type:  defect                   |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  Plugin Directory         |  Resolution:
 Keywords:  has-patch needs-testing  |
-------------------------------------+---------------------

Comment (by dd32):

 > Authors are banned
 > Author has request a GDPR removal

 Under what scenario's do plugins stay open in those cases?

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5568#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 11 01:23:33 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 11 Jan 2021 01:23:33 -0000
Subject: [wp-meta] [Making WordPress.org] #5569: rest api not returns
 all information about some embedded objects of post
In-Reply-To: <059.18c8141395161774fad9d130aed387f5@wordpress.org>
References: <059.18c8141395161774fad9d130aed387f5@wordpress.org>
Message-ID: <074.3ea407aff719723a39f4669f022becf9@wordpress.org>

#5569: rest api not returns all information about some embedded objects of post
-----------------------------+----------------------
 Reporter:  sashakozlovskiy  |       Owner:  (none)
     Type:  defect           |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  General          |  Resolution:  invalid
 Keywords:                   |
-----------------------------+----------------------

Comment (by dd32):

 Enhancements and bugs in WordPress "core" can be filed through
 https://core.trac.wordpress.org/

 Support requests should be directed to
 https://wordpress.org/support/forums/

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5569#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 11 01:43:43 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 11 Jan 2021 01:43:43 +0000 (UTC)
Subject: [wp-meta] [10564]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/class-plugin-directory.php:
 Plugin Directory: When disabling RSS feeds,
 handle situations where `redirect_canonical()` has no canonical location for
 the request.
Message-ID: <20210111014343.E18BB1B0054A@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210111/db3a3bf8/attachment.html>

From noreply at wordpress.org  Mon Jan 11 01:43:48 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 11 Jan 2021 01:43:48 -0000
Subject: [wp-meta] [Making WordPress.org] #5566: Plugin search feed URLs
 should 404
In-Reply-To: <058.fd75444d198cd966a8677da75fce149e@wordpress.org>
References: <058.fd75444d198cd966a8677da75fce149e@wordpress.org>
Message-ID: <073.9316aefc1d15843a27adbcc2ba489700@wordpress.org>

#5566: Plugin search feed URLs should 404
------------------------------+---------------------
 Reporter:  jonoaldersonwp    |       Owner:  dd32
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:  seo               |
------------------------------+---------------------
Changes (by dd32):

 * owner:  (none) => dd32
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"10564" 10564]:
 {{{
 #!CommitTicketReference repository="" revision="10564"
 Plugin Directory: When disabling RSS feeds, handle situations where
 `redirect_canonical()` has no canonical location for the request.

 See [6855].
 Fixes #5566.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5566#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 11 02:34:52 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 11 Jan 2021 02:34:52 +0000 (UTC)
Subject: [wp-meta] [10565]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/readme/class-parser.php:
 Plugin Driectory: Readme: When trimming the short_description to length,
 decode HTML entities first to limit it to displayed length rather than
 computed length.
Message-ID: <20210111023452.3A54A1B0054A@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210111/43ac445d/attachment.html>

From noreply at wordpress.org  Mon Jan 11 02:34:56 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 11 Jan 2021 02:34:56 -0000
Subject: [wp-meta] [Making WordPress.org] #5570: Plugins API -
 inconsistent results for short_description if being trimmed.
In-Reply-To: <056.ca4336df3a2aba7b940af656eb0546a9@wordpress.org>
References: <056.ca4336df3a2aba7b940af656eb0546a9@wordpress.org>
Message-ID: <071.db2bb7d552ca838b6eb20b14a2eb8b26@wordpress.org>

#5570: Plugins API - inconsistent results for short_description if being trimmed.
------------------------------+-----------------------
 Reporter:  polevaultweb      |       Owner:  dd32
     Type:  defect            |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by dd32):

 In [changeset:"10565" 10565]:
 {{{
 #!CommitTicketReference repository="" revision="10565"
 Plugin Driectory: Readme: When trimming the short_description to length,
 decode HTML entities first to limit it to displayed length rather than
 computed length.

 This also ensures that the `&hellip;` is only applied after a shortened
 string, and restores the functionality to limit it to a full setence if
 one ends between characters 120-150.

 See #5570.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5570#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 11 02:46:11 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 11 Jan 2021 02:46:11 -0000
Subject: [wp-meta] [Making WordPress.org] #5570: Plugins API -
 inconsistent results for short_description if being trimmed.
In-Reply-To: <056.ca4336df3a2aba7b940af656eb0546a9@wordpress.org>
References: <056.ca4336df3a2aba7b940af656eb0546a9@wordpress.org>
Message-ID: <071.6a39fff618f607f1f564ce3446bda03e@wordpress.org>

#5570: Plugins API - inconsistent results for short_description if being trimmed.
------------------------------+-----------------------
 Reporter:  polevaultweb      |       Owner:  dd32
     Type:  defect            |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by dd32):

 I'm unable to find any double trimming, as the trimming only happens at
 plugin import stage, not during the API requests.. I'm going to leave this
 ticket open though and keep running some API requests to see if it can be
 caught.

 If you see it happen again, checking what this other API returns might be
 useful:
 {{{
 curl --silent 'https://wordpress.org/plugins/wp-json/plugins/v1/plugin/wp-
 user-manager' | jq .short_description
 }}}

 In [10565] above I did alter the import process to account for encoded
 HTML entities in the determination of whether it needs to trim or not,
 it's still counted during the actual trimming, just not during the
 determination of whether to do so.

 {{{
 $ curl --silent --location -g --request GET
 'https://api.wordpress.org/plugins/info/1.2/?action=plugin_information&request[slug
 ]=wp-user-manager&request[fields]=short_description' | jq
 .short_description

 "The most customizable profiles &amp; community builder WordPress plugin
 with front-end login, registration, profile customization and content
 restriction."
 }}}

 I had considered that maybe the scenario here was a bad translation, but
 it doesn't look like this plugin has any translated descriptions, and
 looking at other translated plugins, the short_description translations
 aren't trimmed to 150char, eg, Hello Dolly spanish at 157char:
 {{{
 $ curl --silent --location -g --request GET
 'https://api.wordpress.org/plugins/info/1.2/?action=plugin_information&request[slug
 ]=hello-dolly&request[fields]=short_description&request[locale]=es_ES' |
 jq .short_description
 "Esto no es solo un plugin, simboliza la esperanza y entusiasmo de toda
 una generación resumidos en las dos palabras más famosas cantadas por
 Louis Armstrong."
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5570#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 11 02:54:15 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 11 Jan 2021 02:54:15 +0000 (UTC)
Subject: [wp-meta] [10566]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/readme/class-parser.php:
 Plugin Directory: Readme parser: Don't attempt to pass too-long-a-string to
 `file_exists()` to avoid PHP warnings.
Message-ID: <20210111025415.18F411B0054A@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210111/6d3c3410/attachment.html>

From noreply at wordpress.org  Mon Jan 11 04:17:14 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 11 Jan 2021 04:17:14 -0000
Subject: [wp-meta] [Making WordPress.org] #5568: Plugin Directory: Do
 not display author names if there are no committers
In-Reply-To: <051.2fabbe1e976feda072481d1eb143be44@wordpress.org>
References: <051.2fabbe1e976feda072481d1eb143be44@wordpress.org>
Message-ID: <066.dbbf3329582a0e0c4d07e9f7e5ac3c95@wordpress.org>

#5568: Plugin Directory: Do not display author names if there are no committers
-------------------------------------+---------------------
 Reporter:  Ipstenu                  |       Owner:  (none)
     Type:  defect                   |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  Plugin Directory         |  Resolution:
 Keywords:  has-patch needs-testing  |
-------------------------------------+---------------------

Comment (by Ipstenu):

 Never. Or at least I can't think of any, but the name still shows up on a
 closed plugin. It's fine to have them on most closed plugins (esp. 'By
 Author Req'), or any time a temp-closure happens (security related, or for
 people who ignore email warnings and need a more stern poke).

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5568#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 11 06:41:24 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 11 Jan 2021 06:41:24 -0000
Subject: [wp-meta] [Making WordPress.org] #2203: Consider Removing
 WordPress Ideas
In-Reply-To: <051.0ba22403eed18b31ec27847850401cc4@wordpress.org>
References: <051.0ba22403eed18b31ec27847850401cc4@wordpress.org>
Message-ID: <066.c8ae7efb76888da692eec71688dc7851@wordpress.org>

#2203: Consider Removing WordPress Ideas
---------------------+---------------------
 Reporter:  macmanx  |       Owner:  (none)
     Type:  task     |      Status:  closed
 Priority:  normal   |   Milestone:
Component:  General  |  Resolution:  fixed
 Keywords:           |
---------------------+---------------------
Changes (by dd32):

 * keywords:  neso needs-patch =>
 * status:  new => closed
 * resolution:   => fixed


Comment:

 A redirect was added on 2020-11-07.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/2203#comment:9>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 11 06:41:52 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 11 Jan 2021 06:41:52 +0000 (UTC)
Subject: [wp-meta] [10567]
 sites/trunk/wordpress.org/public_html/wp-content/mu-plugins/pub/wporg-redirects.php:
 Redirects: Add a WordPress.org/ideas/ redirect to the WordPress.org
 redirection plugin to mirror existing redirects.
Message-ID: <20210111064152.7D42C1B00379@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210111/c0d033d2/attachment.html>

From noreply at wordpress.org  Mon Jan 11 06:41:56 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 11 Jan 2021 06:41:56 -0000
Subject: [wp-meta] [Making WordPress.org] #2203: Consider Removing
 WordPress Ideas
In-Reply-To: <051.0ba22403eed18b31ec27847850401cc4@wordpress.org>
References: <051.0ba22403eed18b31ec27847850401cc4@wordpress.org>
Message-ID: <066.d34b91ef5fe56c94cc0663fc820d0c8e@wordpress.org>

#2203: Consider Removing WordPress Ideas
---------------------+---------------------
 Reporter:  macmanx  |       Owner:  (none)
     Type:  task     |      Status:  closed
 Priority:  normal   |   Milestone:
Component:  General  |  Resolution:  fixed
 Keywords:           |
---------------------+---------------------

Comment (by dd32):

 In [changeset:"10567" 10567]:
 {{{
 #!CommitTicketReference repository="" revision="10567"
 Redirects: Add a WordPress.org/ideas/ redirect to the WordPress.org
 redirection plugin to mirror existing redirects.

 See #2203/
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/2203#comment:10>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 11 06:45:22 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 11 Jan 2021 06:45:22 -0000
Subject: [wp-meta] [Making WordPress.org] #5554: Mobile Responsive Issue
In-Reply-To: <050.c492f40a9ff039295597030179f72f50@wordpress.org>
References: <050.c492f40a9ff039295597030179f72f50@wordpress.org>
Message-ID: <065.039a2a31df3431b33221cd8218b91112@wordpress.org>

#5554: Mobile Responsive Issue
-----------------------------------------+---------------------
 Reporter:  urvik1                       |       Owner:  (none)
     Type:  defect                       |      Status:  new
 Priority:  normal                       |   Milestone:
Component:  WordPress.org Site           |  Resolution:
 Keywords:  needs-patch has-screenshots  |
-----------------------------------------+---------------------

Comment (by dufresnesteven):

 Hi @urvik1!

 Thanks for submitting a ticket.

 I'm not certain there is a unified approach to 'mobilizing' tables on
 .ORG. I'll look around to see if we have any code to re-use.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5554#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 11 06:46:47 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 11 Jan 2021 06:46:47 -0000
Subject: [wp-meta] [Making WordPress.org] #5551: Exclude github-actions
 bot comments from Trac
In-Reply-To: <051.d78f41eac9a773c320387db9791c959a@wordpress.org>
References: <051.d78f41eac9a773c320387db9791c959a@wordpress.org>
Message-ID: <066.6eb561bec9431b8e6d8a984bbd93d759@wordpress.org>

#5551: Exclude github-actions bot comments from Trac
-------------------------+---------------------
 Reporter:  desrosj      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  Trac         |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by dufresnesteven):

 @dd32 Anything left to do?

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5551#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 11 06:48:02 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 11 Jan 2021 06:48:02 -0000
Subject: [wp-meta] [Making WordPress.org] #5551: Exclude github-actions
 bot comments from Trac
In-Reply-To: <051.d78f41eac9a773c320387db9791c959a@wordpress.org>
References: <051.d78f41eac9a773c320387db9791c959a@wordpress.org>
Message-ID: <066.cf3d1ccfe64e6c6fccd2bce0f4313056@wordpress.org>

#5551: Exclude github-actions bot comments from Trac
-------------------------+---------------------
 Reporter:  desrosj      |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Trac         |  Resolution:  fixed
 Keywords:               |
-------------------------+---------------------
Changes (by dd32):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Nope, I assume it's working, that's probably why I left it open.

 @desrosj Please re-open if this didn't fix it!

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5551#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 11 14:17:33 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 11 Jan 2021 14:17:33 -0000
Subject: [wp-meta] [Making WordPress.org] #5545: Add announce to new
 feature-notifications host
In-Reply-To: <050.8705e37d5ef708dd94b0055215d17a5b@wordpress.org>
References: <050.8705e37d5ef708dd94b0055215d17a5b@wordpress.org>
Message-ID: <065.6139a8f953d41a0218536b7e200649df@wordpress.org>

#5545: Add announce to new feature-notifications host
-------------------------+---------------------
 Reporter:  psykro       |       Owner:  (none)
     Type:  defect       |      Status:  new
 Priority:  normal       |   Milestone:
Component:  Slack & IRC  |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by loganfive):

 /bump Still need access please.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5545#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 11 14:33:27 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 11 Jan 2021 14:33:27 -0000
Subject: [wp-meta] [Making WordPress.org] #5570: Plugins API -
 inconsistent results for short_description if being trimmed.
In-Reply-To: <056.ca4336df3a2aba7b940af656eb0546a9@wordpress.org>
References: <056.ca4336df3a2aba7b940af656eb0546a9@wordpress.org>
Message-ID: <071.dc8d4caebdb4bf9a7beda8592baf9e4b@wordpress.org>

#5570: Plugins API - inconsistent results for short_description if being trimmed.
------------------------------+-----------------------
 Reporter:  polevaultweb      |       Owner:  dd32
     Type:  defect            |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by polevaultweb):

 @dd32 thanks for looking into this.

 Running my CURL command today gets the shorter incorrect result
 http://g.recordit.co/uUBcRRVjMM.gif

 Running your command with the different API returns the full data

 ❯ curl --silent 'https://wordpress.org/plugins/wp-json/plugins/v1/plugin
 /wp-user-manager' | jq .short_description
 "The most customizable profiles &amp; community builder WordPress plugin
 with front-end login, registration, profile customization and content
 restriction."

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5570#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 11 14:49:47 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 11 Jan 2021 14:49:47 -0000
Subject: [wp-meta] [Making WordPress.org] #5554: Mobile Responsive Issue
In-Reply-To: <050.c492f40a9ff039295597030179f72f50@wordpress.org>
References: <050.c492f40a9ff039295597030179f72f50@wordpress.org>
Message-ID: <065.43402ba2b61ef720b14cb44848e75bdf@wordpress.org>

#5554: Mobile Responsive Issue
-----------------------------------------+---------------------
 Reporter:  urvik1                       |       Owner:  (none)
     Type:  defect                       |      Status:  new
 Priority:  normal                       |   Milestone:
Component:  WordPress.org Site           |  Resolution:
 Keywords:  needs-patch has-screenshots  |
-----------------------------------------+---------------------

Comment (by urvik1):

 @dufresnesteven
 https://www.screenpresso.com/=1fNMb
 Please also review the video.
 Thank you.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5554#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 11 15:47:00 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 11 Jan 2021 15:47:00 -0000
Subject: [wp-meta] [Making WordPress.org] #5570: Plugins API -
 inconsistent results for short_description if being trimmed.
In-Reply-To: <056.ca4336df3a2aba7b940af656eb0546a9@wordpress.org>
References: <056.ca4336df3a2aba7b940af656eb0546a9@wordpress.org>
Message-ID: <071.079b46d55609960bcdb84fabc924c662@wordpress.org>

#5570: Plugins API - inconsistent results for short_description if being trimmed.
------------------------------+-----------------------
 Reporter:  polevaultweb      |       Owner:  dd32
     Type:  defect            |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by polevaultweb):

 Weirdly, the plugin_information API request just briefly returned the full
 non trimmed content, then on the next request went back to the incorrect
 shorter text

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5570#comment:5>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 12 00:25:59 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 12 Jan 2021 00:25:59 +0000 (UTC)
Subject: [wp-meta] [10568]
 sites/trunk/common/includes/slack/announce/config.php: Slack: Grant Garrett
 slack `/here` access for #feature-notifications.
Message-ID: <20210112002559.6BA7D1B004BE@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210112/9fab5696/attachment.html>

From noreply at wordpress.org  Tue Jan 12 00:26:04 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 12 Jan 2021 00:26:04 -0000
Subject: [wp-meta] [Making WordPress.org] #5545: Add announce to new
 feature-notifications host
In-Reply-To: <050.8705e37d5ef708dd94b0055215d17a5b@wordpress.org>
References: <050.8705e37d5ef708dd94b0055215d17a5b@wordpress.org>
Message-ID: <065.f5950ca40edf9e22abe1f6af279d1068@wordpress.org>

#5545: Add announce to new feature-notifications host
-------------------------+---------------------
 Reporter:  psykro       |       Owner:  dd32
     Type:  defect       |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Slack & IRC  |  Resolution:  fixed
 Keywords:               |
-------------------------+---------------------
Changes (by dd32):

 * owner:  (none) => dd32
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"10568" 10568]:
 {{{
 #!CommitTicketReference repository="" revision="10568"
 Slack: Grant Garrett slack `/here` access for #feature-notifications.

 Fixes #5545.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5545#comment:5>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 12 01:22:14 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 12 Jan 2021 01:22:14 +0000 (UTC)
Subject: [wp-meta] [10569]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/theme-directory/class-wporg-themes-upload.php:
 Theme Directory: Correct an incorrect variable name in an error message.
Message-ID: <20210112012214.8C7151B004BE@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210112/857c78e0/attachment-0001.html>

From noreply at wordpress.org  Tue Jan 12 01:45:56 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 12 Jan 2021 01:45:56 +0000 (UTC)
Subject: [wp-meta] [10570]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/theme-directory:
 Theme Directory: Avoid two PHP Notices when uplaoding a brand new theme.
Message-ID: <20210112014556.6ADAC1B00607@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210112/15e44050/attachment.html>

From noreply at wordpress.org  Tue Jan 12 06:20:21 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 12 Jan 2021 06:20:21 +0000 (UTC)
Subject: [wp-meta] [10571]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/cli/class-import.php:
 Plugin Directory: Use the name from the stable readme instead of the trunk
 readme, as not all plugins have a trunk readme (really,
 it's not actually required, you can just use tags).
Message-ID: <20210112062021.1A3B11B004BE@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210112/409fcc29/attachment.html>

From noreply at wordpress.org  Tue Jan 12 17:14:31 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 12 Jan 2021 17:14:31 -0000
Subject: [wp-meta] [Making WordPress.org] #5571: PoC - Redirections for
 WordPress.org
Message-ID: <057.ddb467051c2bd2dd61c764f5942db572@wordpress.org>

#5571: PoC - Redirections for WordPress.org
--------------------------------------+--------------------
 Reporter:  JavierCasares             |      Owner:  (none)
     Type:  enhancement               |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Make (Get Involved) / P2  |   Keywords:
--------------------------------------+--------------------
 From the Spanish Community we have the need to make redirections of some
 obsolete pages to point to new pages with a new URL or new content at
 es.wordpress.org.

 Bearing in mind that there is no redirection system, I propose this proof
 of concept of how a simple redirection system could be proposed (NOTE: my
 knowledge of WordPress plugin development is limited, but I have people
 who could propose something much more serious and that complies with the
 PHPCS).

 The idea of the Plugin is simple. On the one hand, in the pages, create a
 metabox in which you can indicate the new destination URL. It is saved,
 and if when loading the page, that metabox is detected in the page, the
 redirection is done.

 I know that this situation has been raised previously by other people to
 Meta, both by the Spanish team and by other teams, so if the idea is
 valid, I can work on evolving this system to be 100% compatible.

 I leave a link from the Git where you can see the PoC
 [https://github.com/javiercasares/meta-redirection]

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5571>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 12 17:25:26 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 12 Jan 2021 17:25:26 -0000
Subject: [wp-meta] [Making WordPress.org] #5571: PoC - Redirections for
 WordPress.org
In-Reply-To: <057.ddb467051c2bd2dd61c764f5942db572@wordpress.org>
References: <057.ddb467051c2bd2dd61c764f5942db572@wordpress.org>
Message-ID: <072.7894ff5ca15e520d03c28502327316d1@wordpress.org>

#5571: PoC - Redirections for WordPress.org
--------------------------------------+---------------------
 Reporter:  JavierCasares             |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:  dev-feedback              |
--------------------------------------+---------------------
Changes (by estelaris):

 * keywords:   => dev-feedback


Comment:

 @dd32 could this solve the issue I raised in #5519?

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5571#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 12 18:20:30 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 12 Jan 2021 18:20:30 -0000
Subject: [wp-meta] [Making WordPress.org] #5572: Plugin FAQ anchor links get
 broken when used in a forum post
Message-ID: <055.4bde25634acd359aba1c7bd54d41e16b@wordpress.org>

#5572: Plugin FAQ anchor links get broken when used in a forum post
----------------------------+--------------------
 Reporter:  johnbillion     |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+--------------------
 I've noticed that when I copy a URL to a plugin FAQ and paste it in a
 support forum reply, it gets broken. The copied link is correct and works,
 it just gets mangled when saved in the forum reply.

 Latest example here: https://wordpress.org/support/topic/tracking-user-
 switching/#post-13898580

 This is an affected link, seems to work okay in Trac:
 https://wordpress.org/plugins/user-
 switching/#%0Aare%20any%20plugin%20actions%20called%20when%20a%20user%20switches%20account%3F%0A

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5572>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 12 18:28:07 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 12 Jan 2021 18:28:07 -0000
Subject: [wp-meta] [Making WordPress.org] #5572: Plugin FAQ anchor links
 get broken when used in a forum post
In-Reply-To: <055.4bde25634acd359aba1c7bd54d41e16b@wordpress.org>
References: <055.4bde25634acd359aba1c7bd54d41e16b@wordpress.org>
Message-ID: <070.d51a046a92a4d9e07a00e76c9d544f47@wordpress.org>

#5572: Plugin FAQ anchor links get broken when used in a forum post
----------------------------+---------------------
 Reporter:  johnbillion     |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------

Comment (by diddledan):

 The forum is stripping the `%0A` encoded character at the beginning and
 end of the fragment in the URL. `%0A` is the encoded newline character. I
 think the forum is correct, here, and the fix should be applied to the
 plugin pages to `trim()` the FAQ titles before encoding/escaping the URL.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5572#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 12 19:14:53 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 12 Jan 2021 19:14:53 -0000
Subject: [wp-meta] [Making WordPress.org] #5573: "anonymized" users should
 be blocked to prevent use
Message-ID: <051.5adb5e935c6cb9978f2b31c3260653b8@wordpress.org>

#5573: "anonymized" users should be blocked to prevent use
---------------------+--------------------
 Reporter:  Ipstenu  |      Owner:  (none)
     Type:  defect   |     Status:  new
 Priority:  normal   |  Milestone:
Component:  General  |   Keywords:
---------------------+--------------------
 Currently when a user asks to have their account pulled (ie turned
 anonymized), we blank out the email and anon them as much as possible. BUT
 we do not change the account status to blocked.

 Since they've asked us not to use/keep their data anymore, we should
 similarly block the accounts and reset passwords to prevent lingering
 cookies from allowing them to give us more data. It rather defeats the
 purpose of their request, eh? :)

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5573>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 12 21:30:56 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 12 Jan 2021 21:30:56 +0000 (UTC)
Subject: [wp-meta] [10572]
 sites/trunk/api.wordpress.org/public_html/patterns/1.0: Pattern API: Use
 `search` param instead of `/search` endpoint.
Message-ID: <20210112213056.688801B003CB@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210112/12d119a5/attachment-0001.html>

From noreply at wordpress.org  Wed Jan 13 00:27:15 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 13 Jan 2021 00:27:15 -0000
Subject: [wp-meta] [Making WordPress.org] #5573: "anonymized" users
 should be blocked to prevent use
In-Reply-To: <051.5adb5e935c6cb9978f2b31c3260653b8@wordpress.org>
References: <051.5adb5e935c6cb9978f2b31c3260653b8@wordpress.org>
Message-ID: <066.c65e66d9a38d7f65a706c31fba682765@wordpress.org>

#5573: "anonymized" users should be blocked to prevent use
---------------------+---------------------
 Reporter:  Ipstenu  |       Owner:  (none)
     Type:  defect   |      Status:  new
 Priority:  normal   |   Milestone:
Component:  General  |  Resolution:
 Keywords:           |
---------------------+---------------------

Comment (by dd32):

 - Passwords are already reset/removed out during erasure
  - Cookies become invalid once the password is removed

 The case that triggered this was an erasure which was requested moments
 after creating content, leading the the idea that perhaps the user had
 created the content after erasure.

 Blocking these accounts doesn't seem like it'll be much benefit, and it'll
 also mean that the anonymised profile activity history is no longer
 displayed to most users which could be an issue when a contributor wants
 to check other threads from the author or something..

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5573#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 13 00:33:13 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 13 Jan 2021 00:33:13 -0000
Subject: [wp-meta] [Making WordPress.org] #5571: PoC - Redirections for
 WordPress.org
In-Reply-To: <057.ddb467051c2bd2dd61c764f5942db572@wordpress.org>
References: <057.ddb467051c2bd2dd61c764f5942db572@wordpress.org>
Message-ID: <072.a5553ec5c4dcfeaa167f189f204e1338@wordpress.org>

#5571: PoC - Redirections for WordPress.org
--------------------------------------+------------------------
 Reporter:  JavierCasares             |       Owner:  (none)
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:  duplicate
 Keywords:  dev-feedback              |
--------------------------------------+------------------------
Changes (by dd32):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 I'm going to close this as a duplicate of #5519 - even though it's not the
 same functionality, it's ultimately going to be fixed by the same thing.

 I'm not going to personally deploy any plugins such as the proposed once
 onto WordPress.org, as I don't believe we should maintain something like
 that going forward, and it requires the obsolete pages to continue to
 exist.

 As per #5519, a plugin I would support, would be one which fixes
 https://core.trac.wordpress.org/ticket/4328 in a way which could be added
 to WordPress itself through the wp_old_slug_redirect() functionality.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5571#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 13 01:24:15 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 13 Jan 2021 01:24:15 +0000 (UTC)
Subject: [wp-meta] [10573] sites/trunk/wordpress.org/public_html/wp-content:
 Plugin Directory: When generating FAQ anchors,
 don't include trailing whitespace as part of the ID.
Message-ID: <20210113012415.4DC4B1B0057F@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210113/4b6ec1af/attachment.html>

From noreply at wordpress.org  Wed Jan 13 01:24:19 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 13 Jan 2021 01:24:19 -0000
Subject: [wp-meta] [Making WordPress.org] #5572: Plugin FAQ anchor links
 get broken when used in a forum post
In-Reply-To: <055.4bde25634acd359aba1c7bd54d41e16b@wordpress.org>
References: <055.4bde25634acd359aba1c7bd54d41e16b@wordpress.org>
Message-ID: <070.79b604f3ff9438c35490ee75a75a468a@wordpress.org>

#5572: Plugin FAQ anchor links get broken when used in a forum post
----------------------------+---------------------
 Reporter:  johnbillion     |       Owner:  dd32
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+---------------------
Changes (by dd32):

 * owner:  (none) => dd32
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"10573" 10573]:
 {{{
 #!CommitTicketReference repository="" revision="10573"
 Plugin Directory: When generating FAQ anchors, don't include trailing
 whitespace as part of the ID.

 This also updates the format of pre-defined ID's to match the format used
 today, as the ID's were previously being stripped out by kses, there's no
 real change here.

 The Decode/Encode and trimming works around the various different anchor
 formats used.

 Fixes #5572.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5572#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 13 01:27:34 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 13 Jan 2021 01:27:34 +0000 (UTC)
Subject: [wp-meta] [10574]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-plugins/functions.php:
 Plugin Directory: Bump JS cache after [10573].
Message-ID: <20210113012734.9D2D61B0057F@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210113/a6b33777/attachment-0001.html>

From noreply at wordpress.org  Wed Jan 13 01:27:39 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 13 Jan 2021 01:27:39 -0000
Subject: [wp-meta] [Making WordPress.org] #5572: Plugin FAQ anchor links
 get broken when used in a forum post
In-Reply-To: <055.4bde25634acd359aba1c7bd54d41e16b@wordpress.org>
References: <055.4bde25634acd359aba1c7bd54d41e16b@wordpress.org>
Message-ID: <070.977b98c74ed254ae53706270905f17d2@wordpress.org>

#5572: Plugin FAQ anchor links get broken when used in a forum post
----------------------------+---------------------
 Reporter:  johnbillion     |       Owner:  dd32
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+---------------------

Comment (by dd32):

 In [changeset:"10574" 10574]:
 {{{
 #!CommitTicketReference repository="" revision="10574"
 Plugin Directory: Bump JS cache after [10573].

 See #5572.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5572#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 13 08:24:28 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 13 Jan 2021 08:24:28 +0000 (UTC)
Subject: [wp-meta] [10575]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-gp-customizations/inc/class-plugin.php:
 Translate: Prevent suggesting a string which has already been rejected for
 that original for that user.
Message-ID: <20210113082428.E03121B00270@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210113/5e529124/attachment.html>

From noreply at wordpress.org  Wed Jan 13 19:42:17 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 13 Jan 2021 19:42:17 -0000
Subject: [wp-meta] [Making WordPress.org] #5573: "anonymized" users
 should be blocked to prevent use
In-Reply-To: <051.5adb5e935c6cb9978f2b31c3260653b8@wordpress.org>
References: <051.5adb5e935c6cb9978f2b31c3260653b8@wordpress.org>
Message-ID: <066.e2c701fa44585388b7efaf3fbb79af2f@wordpress.org>

#5573: "anonymized" users should be blocked to prevent use
---------------------+---------------------
 Reporter:  Ipstenu  |       Owner:  (none)
     Type:  defect   |      Status:  new
 Priority:  normal   |   Milestone:
Component:  General  |  Resolution:
 Keywords:           |
---------------------+---------------------

Comment (by Ipstenu):

 >    Passwords are already reset/removed out during erasure
 >    Cookies become invalid once the password is removed

 There have been other cases where the cookies aren't becoming invalid or
 this timing issue happens. Banned users have been able to, 24 hours later,
 submit plugins just for an example.

 Making another status that, similarly, can be checked as-is for an invalid
 account could make this more reliable. I've reported that a number of
 times, with no change.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5573#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 13 21:55:55 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 13 Jan 2021 21:55:55 -0000
Subject: [wp-meta] [Making WordPress.org] #5574: Banned Users are NOT being
 logged out
Message-ID: <051.967b2b7289b6f66bc9419a9757a167eb@wordpress.org>

#5574: Banned Users are NOT being logged out
---------------------+-------------------------
 Reporter:  Ipstenu  |      Owner:  (none)
     Type:  defect   |     Status:  new
 Priority:  normal   |  Milestone:
Component:  General  |   Keywords:  needs-patch
---------------------+-------------------------
 A user was banned on Jan 6th (by me)

 On Jan 13th, they were still logged in (or were able to log back in) and
 submitted a plugin.

 I'm going to make a related ticket about why on earth a banned user can
 upload anyway, but this is making it clear that the whole 'banned users
 get logged out' is not functioning properly.

 We need to revisit whatever it is we're doing on banned users to force
 logout, becuase now the only way to ensure they won't just keep on keeping
 on is to reset passwords, which alerts people that we changed their
 passwords and gets them all weird and angry (understandably).

 I can provide specifics if needed, but I don't want to name/shame in a
 ticket.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5574>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 13 22:06:57 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 13 Jan 2021 22:06:57 -0000
Subject: [wp-meta] [Making WordPress.org] #5574: Banned Users are NOT
 being logged out
In-Reply-To: <051.967b2b7289b6f66bc9419a9757a167eb@wordpress.org>
References: <051.967b2b7289b6f66bc9419a9757a167eb@wordpress.org>
Message-ID: <066.6c32a597acc677ce705fd9fd69ee3da7@wordpress.org>

#5574: Banned Users are NOT being logged out
-------------------------+---------------------
 Reporter:  Ipstenu      |       Owner:  (none)
     Type:  defect       |      Status:  new
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:  needs-patch  |
-------------------------+---------------------

Comment (by ocean90):

 > that the whole 'banned users get logged out' is not functioning properly

 I‘m wondering why you think that such functionality exists? Banning a user
 is just a role/flag which only prevents new logins and password resets.

 To force a logout you always have to change the password otherwise
 existing cookies are still valid.

 Unfortunately WordPress.org doesn’t use sessions ([WP29221]) due to Trac
 not supporting it (and maybe other systems).

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5574#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 13 22:08:41 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 13 Jan 2021 22:08:41 -0000
Subject: [wp-meta] [Making WordPress.org] #5575: Plugin Directory: Banned
 Users should not be able to upload plugins
Message-ID: <051.eac68d792b07c11a0c00b2652c9d1ee0@wordpress.org>

#5575: Plugin Directory: Banned Users should not be able to upload plugins
---------------------+--------------------
 Reporter:  Ipstenu  |      Owner:  (none)
     Type:  defect   |     Status:  new
 Priority:  normal   |  Milestone:
Component:  General  |   Keywords:
---------------------+--------------------
 Related to #5574

 In theory if that gets fixed properly this won't be AS needed, but at the
 same time, seeing as it has shown flaws, we should have a failsafe that
 checks for user permissions.

 Now we have a lot of code that looks for things like this:


 {{{
 $user = new WP_User( get_current_user_id() );

 if ( ! empty( $user->allcaps['bbp_blocked'] ) ) :
         // Do the ban message here
 endif;
 }}}

 And I thought about putting that into the upload shortcode file around
 here:
 https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html
 /wp-content/plugins/plugin-directory/shortcodes/class-upload.php#L30

 But at the same time, it strikes me that it would be better to have a
 generic function like `is_user_banned()` to be reused, since this is not
 the only time we would want to have that check, and we're crossing the DRY
 border :)

 We call bbp_blocked 11 times (attached image).

 I don't know if this should be a plugin-specific 'just add another block
 to the wall' ticket or if we should genericize this out and make it
 flexible.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5575>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 13 22:08:59 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 13 Jan 2021 22:08:59 -0000
Subject: [wp-meta] [Making WordPress.org] #5575: Plugin Directory:
 Banned Users should not be able to upload plugins
In-Reply-To: <051.eac68d792b07c11a0c00b2652c9d1ee0@wordpress.org>
References: <051.eac68d792b07c11a0c00b2652c9d1ee0@wordpress.org>
Message-ID: <066.2d03ef6799b4b416c747f024ef269cb2@wordpress.org>

#5575: Plugin Directory: Banned Users should not be able to upload plugins
---------------------+---------------------
 Reporter:  Ipstenu  |       Owner:  (none)
     Type:  defect   |      Status:  new
 Priority:  normal   |   Milestone:
Component:  General  |  Resolution:
 Keywords:           |
---------------------+---------------------
Changes (by Ipstenu):

 * Attachment "Screen Shot 2021-01-13 at 2.05.46 PM.jpg" added.

 All the uses of bbp_blocked

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5575>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 13 22:48:35 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 13 Jan 2021 22:48:35 -0000
Subject: [wp-meta] [Making WordPress.org] #5574: Banned Users are NOT
 being logged out
In-Reply-To: <051.967b2b7289b6f66bc9419a9757a167eb@wordpress.org>
References: <051.967b2b7289b6f66bc9419a9757a167eb@wordpress.org>
Message-ID: <066.a376a4f2e4dcd6d1ff2ef68c55c60cd8@wordpress.org>

#5574: Banned Users are NOT being logged out
-------------------------+---------------------
 Reporter:  Ipstenu      |       Owner:  (none)
     Type:  defect       |      Status:  new
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:  needs-patch  |
-------------------------+---------------------

Comment (by Ipstenu):

 Countless people have insisted that it does, and we were to NOT reset
 passwords when banning people. I can trawl back through Slack, but at the
 very least that's what @otto42 told me, and I believed him.

 Now if that is not happening, it needs to, because otherwise you're
 putting more work on the volunteers rather needlessly.

 > I guess a fix would be to change the password automatically when a user
 gets blocked, without sending the default notification email.

 Honest to mergatroyd, that's what I (and the Support Team) was told was
 happening!

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5574#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 00:22:44 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 00:22:44 -0000
Subject: [wp-meta] [Making WordPress.org] #5574: Banned Users are NOT
 being logged out
In-Reply-To: <051.967b2b7289b6f66bc9419a9757a167eb@wordpress.org>
References: <051.967b2b7289b6f66bc9419a9757a167eb@wordpress.org>
Message-ID: <066.83c63b6aa38b33bb0f062eb66604f80b@wordpress.org>

#5574: Banned Users are NOT being logged out
-------------------------+------------------------
 Reporter:  Ipstenu      |       Owner:  (none)
     Type:  defect       |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:  duplicate
 Keywords:  needs-patch  |
-------------------------+------------------------
Changes (by dd32):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 Replying to [comment:2 Ipstenu]:
 > Countless people have insisted that it does, and we were to NOT reset
 passwords when banning people.

 Yeah no, this is a long term known thing.. Banning users doesn't reset
 their cookies.

 #4691

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5574#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 00:23:01 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 00:23:01 -0000
Subject: [wp-meta] [Making WordPress.org] #4691: Break Password Hash
 when user is blocked
In-Reply-To: <051.3c6a5d1515ca1a3867d0371124f33402@wordpress.org>
References: <051.3c6a5d1515ca1a3867d0371124f33402@wordpress.org>
Message-ID: <066.5411e1ff3cfe814355b69803c32303a8@wordpress.org>

#4691: Break Password Hash when user is blocked
----------------------------+-----------------------
 Reporter:  Ipstenu         |       Owner:  dd32
     Type:  enhancement     |      Status:  accepted
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+-----------------------
Changes (by dd32):

 * owner:  (none) => dd32
 * status:  new => accepted


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4691#comment:20>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 00:25:18 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 00:25:18 -0000
Subject: [wp-meta] [Making WordPress.org] #4691: Break Password Hash
 when user is blocked
In-Reply-To: <051.3c6a5d1515ca1a3867d0371124f33402@wordpress.org>
References: <051.3c6a5d1515ca1a3867d0371124f33402@wordpress.org>
Message-ID: <066.6497d49982d87d1d36dc5369a684bc40@wordpress.org>

#4691: Break Password Hash when user is blocked
-----------------------------+-----------------------
 Reporter:  Ipstenu          |       Owner:  dd32
     Type:  defect           |      Status:  accepted
 Priority:  highest omg bbq  |   Milestone:
Component:  Support Forums   |  Resolution:
 Keywords:                   |
-----------------------------+-----------------------
Changes (by dd32):

 * priority:  normal => highest omg bbq
 * type:  enhancement => defect


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4691#comment:21>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 00:27:19 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 00:27:19 -0000
Subject: [wp-meta] [Making WordPress.org] #5573: "anonymized" users
 should be blocked to prevent use
In-Reply-To: <051.5adb5e935c6cb9978f2b31c3260653b8@wordpress.org>
References: <051.5adb5e935c6cb9978f2b31c3260653b8@wordpress.org>
Message-ID: <066.24d4ab0b8fa3dfc9d0e412d6299c796a@wordpress.org>

#5573: "anonymized" users should be blocked to prevent use
---------------------+---------------------
 Reporter:  Ipstenu  |       Owner:  (none)
     Type:  defect   |      Status:  new
 Priority:  normal   |   Milestone:
Component:  General  |  Resolution:
 Keywords:           |
---------------------+---------------------

Comment (by dd32):

 I'm going to close this ticket, as there's no actual bug here with
 anonymous users.

 Blocked users however, yes, there's a mess with those which I'll fix via
 #4691 today.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5573#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 00:27:52 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 00:27:52 -0000
Subject: [wp-meta] [Making WordPress.org] #5573: "anonymized" users
 should be blocked to prevent use
In-Reply-To: <051.5adb5e935c6cb9978f2b31c3260653b8@wordpress.org>
References: <051.5adb5e935c6cb9978f2b31c3260653b8@wordpress.org>
Message-ID: <066.559f08c09c537458a755c18ed37b4e05@wordpress.org>

#5573: "anonymized" users should be blocked to prevent use
---------------------+----------------------
 Reporter:  Ipstenu  |       Owner:  (none)
     Type:  defect   |      Status:  closed
 Priority:  normal   |   Milestone:
Component:  General  |  Resolution:  invalid
 Keywords:           |
---------------------+----------------------
Changes (by dd32):

 * status:  new => closed
 * resolution:   => invalid


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5573#comment:5>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 00:40:40 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 00:40:40 -0000
Subject: [wp-meta] [Making WordPress.org] #5576: Automatically reject
 previous pending translation from same user
Message-ID: <056.5b0f342343af08b3713be104576e4684@wordpress.org>

#5576: Automatically reject previous pending translation from same user
--------------------------------------+--------------------
 Reporter:  tobifjellner              |      Owner:  (none)
     Type:  enhancement               |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:
--------------------------------------+--------------------
 This problem is described in https://github.com/GlotPress/GlotPress-
 WP/issues/889 and in a perfect world, this should probably be fixed in
 GlotPress.

 But I just learnt that this probably can be solved relatively easy by
 adding a filter via an add-on to GlotPress in our own systems. So I
 suggest that this should be developed for translate.wordpress.org and then
 it can be submitted upstream for possible later inclusion.

 Currently, if a user has suggested a translation and then notices a typo
 or other error (possibly even getting a warning from GlotPress about
 missing variables, etc.) and then submits another suggestion, these both
 suggestions will both become pending in the project. (Technically, the
 user ''can'' go back and manually reject their own pending translation,
 but in reality that simply doesn't happen.)

 When a translation editor afterwards checks the pending translations,
 there's a risk that the wrong string will be approved after the correct
 one, leaving the wrong translation as the active translation. Also, if I
 as a translation editor scan a full page of translations, my view will by
 itself get stuck on various error, and only later I'll realize that the
 user already submitted a different translation for the same string.

 The solution: When a not-editor submits a translation into pending, if
 there are any previous pending translation(s) of the same string from the
 same user, then those previous strings should automatically be rejected.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5576>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 00:48:21 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 00:48:21 -0000
Subject: [wp-meta] [Making WordPress.org] #5576: Automatically reject
 previous pending translation from same user
In-Reply-To: <056.5b0f342343af08b3713be104576e4684@wordpress.org>
References: <056.5b0f342343af08b3713be104576e4684@wordpress.org>
Message-ID: <071.16d8520fbee2844c3b0b55ae98a5a6e3@wordpress.org>

#5576: Automatically reject previous pending translation from same user
--------------------------------------+-----------------------
 Reporter:  tobifjellner              |       Owner:  dd32
     Type:  enhancement               |      Status:  accepted
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+-----------------------
Changes (by dd32):

 * owner:  (none) => dd32
 * status:  new => accepted


Comment:

 Just noting that r10575 was slightly half-related:

 {{{
 Translate: Prevent suggesting a string which has already been rejected for
 that original for that user.

 This prevents a translator suggesting the same sting for an original after
 having their translation rejected once.

 See https://wordpress.slack.com/archives/C02RP50LK/p1610520419455100
 }}}

 Specifically for this ticket however, what should be the status of the
 suggested-but-replaced strings from the translator? should they be
 rejected by the translator? or is there another status I'm not aware of?

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5576#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 00:55:18 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 00:55:18 -0000
Subject: [wp-meta] [Making WordPress.org] #5576: Automatically reject
 previous pending translation from same user
In-Reply-To: <056.5b0f342343af08b3713be104576e4684@wordpress.org>
References: <056.5b0f342343af08b3713be104576e4684@wordpress.org>
Message-ID: <071.c93c833b97d59dad794191d5a4a0648d@wordpress.org>

#5576: Automatically reject previous pending translation from same user
--------------------------------------+-----------------------
 Reporter:  tobifjellner              |       Owner:  dd32
     Type:  enhancement               |      Status:  accepted
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+-----------------------

Comment (by tobifjellner):

 I'd put it as "rejected" by same user...
 When they file a new suggestion, that's their intention, after all!

 If it wouldn't be too big a resource hog, we might even consider a one-
 shot hunting for double suggestions and rejecting in the same way the
 older suggestions in the database.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5576#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 01:20:16 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 01:20:16 -0000
Subject: [wp-meta] [Making WordPress.org] #5576: Automatically reject
 previous pending translation from same user
In-Reply-To: <056.5b0f342343af08b3713be104576e4684@wordpress.org>
References: <056.5b0f342343af08b3713be104576e4684@wordpress.org>
Message-ID: <071.a5d435470413c5196dfa0e5f65252be4@wordpress.org>

#5576: Automatically reject previous pending translation from same user
--------------------------------------+-----------------------
 Reporter:  tobifjellner              |       Owner:  dd32
     Type:  enhancement               |      Status:  accepted
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+-----------------------

Comment (by dd32):

 Replying to [comment:3 tobifjellner]:
 > I'd put it as "rejected" by same user...
 > When they file a new suggestion, that's their intention, after all!

 Sounds good to me!

 > If it wouldn't be too big a resource hog, we might even consider a one-
 shot hunting for double suggestions and rejecting in the same way the
 older suggestions in the database.

 The translations table is quite massive (There's only 75 million
 translations or so), so I'm a little limited there but I'll see what I can
 do. That'll also depend upon just how many originals have multiple pending
 translations though :)

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5576#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 01:23:09 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 01:23:09 -0000
Subject: [wp-meta] [Making WordPress.org] #5576: Automatically reject
 previous pending translation from same user
In-Reply-To: <056.5b0f342343af08b3713be104576e4684@wordpress.org>
References: <056.5b0f342343af08b3713be104576e4684@wordpress.org>
Message-ID: <071.bceb2a1bb0979ea38f9081126e4b4ce9@wordpress.org>

#5576: Automatically reject previous pending translation from same user
--------------------------------------+-----------------------
 Reporter:  tobifjellner              |       Owner:  dd32
     Type:  enhancement               |      Status:  accepted
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+-----------------------

Comment (by tobifjellner):

 {{{
 ...There's only 75 million translations or so...
 }}}
 The good thing is that it can be broken down into one project at a time.
 Perhaps cron-running one locale at a time.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5576#comment:5>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 01:51:05 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 01:51:05 -0000
Subject: [wp-meta] [Making WordPress.org] #5576: Automatically reject
 previous pending translation from same user
In-Reply-To: <056.5b0f342343af08b3713be104576e4684@wordpress.org>
References: <056.5b0f342343af08b3713be104576e4684@wordpress.org>
Message-ID: <071.5dfc8674b9446a627f70d0ebf0b055fc@wordpress.org>

#5576: Automatically reject previous pending translation from same user
--------------------------------------+-----------------------
 Reporter:  tobifjellner              |       Owner:  dd32
     Type:  enhancement               |      Status:  accepted
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+-----------------------

Comment (by dd32):

 Replying to [comment:5 tobifjellner]:
 > {{{
 > ...There's only 75 million translations or so...
 > }}}
 > The good thing is that it can be broken down [...]

 There's only ~64k users with more than 1 translation suggestion (and I can
 look up all of a users translations efficiently), so it looks like it'll
 possible to go through and automatically mark the translations 🎉

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5576#comment:6>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 03:22:07 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 14 Jan 2021 03:22:07 +0000 (UTC)
Subject: [wp-meta] [10576]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-gp-customizations/inc/class-plugin.php:
 Translate: When a translator re-submits a translation suggestion,
 automatically reject their previous submitted translations for that
 original.
Message-ID: <20210114032207.546861B0041A@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210114/1acc610b/attachment.html>

From noreply at wordpress.org  Thu Jan 14 03:22:11 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 03:22:11 -0000
Subject: [wp-meta] [Making WordPress.org] #5576: Automatically reject
 previous pending translation from same user
In-Reply-To: <056.5b0f342343af08b3713be104576e4684@wordpress.org>
References: <056.5b0f342343af08b3713be104576e4684@wordpress.org>
Message-ID: <071.eb21b4102d6b41d79fb1be9e94f9f19d@wordpress.org>

#5576: Automatically reject previous pending translation from same user
--------------------------------------+---------------------
 Reporter:  tobifjellner              |       Owner:  dd32
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:  fixed
 Keywords:                            |
--------------------------------------+---------------------
Changes (by dd32):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"10576" 10576]:
 {{{
 #!CommitTicketReference repository="" revision="10576"
 Translate: When a translator re-submits a translation suggestion,
 automatically reject their previous submitted translations for that
 original.

 This will mean that those who see a Translation warning, fix it, and then
 re-submit will only have 1 waiting translation rather than 2.

 Fixes #5576.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5576#comment:7>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 03:23:25 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 03:23:25 -0000
Subject: [wp-meta] [Making WordPress.org] #5576: Automatically reject
 previous pending translation from same user
In-Reply-To: <056.5b0f342343af08b3713be104576e4684@wordpress.org>
References: <056.5b0f342343af08b3713be104576e4684@wordpress.org>
Message-ID: <071.3d9c660ca0803a5e836d8bb645e75f41@wordpress.org>

#5576: Automatically reject previous pending translation from same user
--------------------------------------+---------------------
 Reporter:  tobifjellner              |       Owner:  dd32
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:  fixed
 Keywords:                            |
--------------------------------------+---------------------
Changes (by dd32):

 * Attachment "Screen Shot 2021-01-14 at 1.22.38 pm.png" added.

 Example of a translation that's auto-rejected. Note that there's no
 "Rejected By" byline, as it was "self rejected"

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5576>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 04:49:17 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 14 Jan 2021 04:49:17 +0000 (UTC)
Subject: [wp-meta] [10577]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/support-forums/inc/class-hooks.php:
 Support: Add a forum handler for the obsolete `/profile/$slug` URI which
 should soon be hitting WordPress.
Message-ID: <20210114044917.BD4E91B0041A@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210114/73252a77/attachment-0001.html>

From noreply at wordpress.org  Thu Jan 14 04:49:22 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 04:49:22 -0000
Subject: [wp-meta] [Making WordPress.org] #5384: Remove old bb-admin
In-Reply-To: <051.72b82ef8b7b2671a6ac87a0dbaf5fbdd@wordpress.org>
References: <051.72b82ef8b7b2671a6ac87a0dbaf5fbdd@wordpress.org>
Message-ID: <066.52e79b4a68672bba0535750a59c8a34f@wordpress.org>

#5384: Remove old bb-admin
----------------------------+-----------------------
 Reporter:  Clorith         |       Owner:  dd32
     Type:  task            |      Status:  accepted
 Priority:  high            |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+-----------------------

Comment (by dd32):

 In [changeset:"10577" 10577]:
 {{{
 #!CommitTicketReference repository="" revision="10577"
 Support: Add a forum handler for the obsolete `/profile/$slug` URI which
 should soon be hitting WordPress.

 See #5384.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5384#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 05:44:38 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 14 Jan 2021 05:44:38 +0000 (UTC)
Subject: [wp-meta] [10578]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/support-forums/inc/class-hooks.php:
 Support Forums: When a user is blocked on the forums,
 break their password hash to prevent logins and terminate all current
 sessions (WordPress & Trac).
Message-ID: <20210114054438.79EB21B0041A@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210114/192112ff/attachment.html>

From noreply at wordpress.org  Thu Jan 14 05:44:42 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 05:44:42 -0000
Subject: [wp-meta] [Making WordPress.org] #4691: Break Password Hash
 when user is blocked
In-Reply-To: <051.3c6a5d1515ca1a3867d0371124f33402@wordpress.org>
References: <051.3c6a5d1515ca1a3867d0371124f33402@wordpress.org>
Message-ID: <066.09d6145d0f0fac9491fe5f3ac566a036@wordpress.org>

#4691: Break Password Hash when user is blocked
-----------------------------+-----------------------
 Reporter:  Ipstenu          |       Owner:  dd32
     Type:  defect           |      Status:  accepted
 Priority:  highest omg bbq  |   Milestone:
Component:  Support Forums   |  Resolution:
 Keywords:                   |
-----------------------------+-----------------------

Comment (by dd32):

 In [changeset:"10578" 10578]:
 {{{
 #!CommitTicketReference repository="" revision="10578"
 Support Forums: When a user is blocked on the forums, break their password
 hash to prevent logins and terminate all current sessions (WordPress &
 Trac).

 See #4691.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4691#comment:22>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 06:06:09 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 14 Jan 2021 06:06:09 +0000 (UTC)
Subject: [wp-meta] [10579]
 sites/trunk/common/includes/wporg-sso/wp-plugin.php: Authentication:
 Display the blocked user warning upon attempting to login after [10578].
Message-ID: <20210114060609.7C18F1B0041A@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210114/1e47bae3/attachment-0001.html>

From noreply at wordpress.org  Thu Jan 14 06:06:14 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 06:06:14 -0000
Subject: [wp-meta] [Making WordPress.org] #4691: Break Password Hash
 when user is blocked
In-Reply-To: <051.3c6a5d1515ca1a3867d0371124f33402@wordpress.org>
References: <051.3c6a5d1515ca1a3867d0371124f33402@wordpress.org>
Message-ID: <066.7272d21cac23ee8ba6f654393f78e8a3@wordpress.org>

#4691: Break Password Hash when user is blocked
-----------------------------+-----------------------
 Reporter:  Ipstenu          |       Owner:  dd32
     Type:  defect           |      Status:  accepted
 Priority:  highest omg bbq  |   Milestone:
Component:  Support Forums   |  Resolution:
 Keywords:                   |
-----------------------------+-----------------------

Comment (by dd32):

 In [changeset:"10579" 10579]:
 {{{
 #!CommitTicketReference repository="" revision="10579"
 Authentication: Display the blocked user warning upon attempting to login
 after [10578].

 See #4691.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4691#comment:23>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 06:30:11 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 14 Jan 2021 06:30:11 +0000 (UTC)
Subject: [wp-meta] [10580]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/support-forums/inc:
 Support Forums: Add a user log entry when a user is blocked or unblocked.
Message-ID: <20210114063011.A41391B0033C@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210114/d0d3ab41/attachment.html>

From noreply at wordpress.org  Thu Jan 14 06:30:16 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 06:30:16 -0000
Subject: [wp-meta] [Making WordPress.org] #2537: Support Forums: Audit
 Log for Mod Actions
In-Reply-To: <051.6b8fba88e37ea7da6f91c50c32d96081@wordpress.org>
References: <051.6b8fba88e37ea7da6f91c50c32d96081@wordpress.org>
Message-ID: <066.ec9d2931bd348381dfd9f011d030865e@wordpress.org>

#2537: Support Forums: Audit Log for Mod Actions
----------------------------+-----------------------
 Reporter:  Ipstenu         |       Owner:  netweb
     Type:  enhancement     |      Status:  accepted
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+-----------------------

Comment (by dd32):

 In [changeset:"10580" 10580]:
 {{{
 #!CommitTicketReference repository="" revision="10580"
 Support Forums: Add a user log entry when a user is blocked or unblocked.

 See #4691.
 See #2537.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/2537#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 06:30:16 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 06:30:16 -0000
Subject: [wp-meta] [Making WordPress.org] #4691: Break Password Hash
 when user is blocked
In-Reply-To: <051.3c6a5d1515ca1a3867d0371124f33402@wordpress.org>
References: <051.3c6a5d1515ca1a3867d0371124f33402@wordpress.org>
Message-ID: <066.a14d71f7c8a3705ca0b8feaca0cb8908@wordpress.org>

#4691: Break Password Hash when user is blocked
-----------------------------+-----------------------
 Reporter:  Ipstenu          |       Owner:  dd32
     Type:  defect           |      Status:  accepted
 Priority:  highest omg bbq  |   Milestone:
Component:  Support Forums   |  Resolution:
 Keywords:                   |
-----------------------------+-----------------------

Comment (by dd32):

 In [changeset:"10580" 10580]:
 {{{
 #!CommitTicketReference repository="" revision="10580"
 Support Forums: Add a user log entry when a user is blocked or unblocked.

 See #4691.
 See #2537.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4691#comment:24>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 06:35:19 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 06:35:19 -0000
Subject: [wp-meta] [Making WordPress.org] #4691: Break Password Hash
 when user is blocked
In-Reply-To: <051.3c6a5d1515ca1a3867d0371124f33402@wordpress.org>
References: <051.3c6a5d1515ca1a3867d0371124f33402@wordpress.org>
Message-ID: <066.921803a4fd71b8581fc355a326733c82@wordpress.org>

#4691: Break Password Hash when user is blocked
-----------------------------+-----------------------
 Reporter:  Ipstenu          |       Owner:  dd32
     Type:  defect           |      Status:  accepted
 Priority:  highest omg bbq  |   Milestone:
Component:  Support Forums   |  Resolution:
 Keywords:                   |
-----------------------------+-----------------------

Comment (by dd32):

 Okay, user sessions should no longer work when a user is blocked.

 I've also added an automated user log entry when a user is blocked, it's
 not as great as it should be, it's purely `Forum role changed to
 bbp_blocked.` See this test user
 [https://wordpress.org/support/users/dd256/ dd256].

 I'd like to enable adding a user note from the edit page, or to append
 that to a note made in the last 5 minutes, but didn't quite get there.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4691#comment:25>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 16:31:51 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 14 Jan 2021 16:31:51 +0000 (UTC)
Subject: [wp-meta] [10581]
 sites/trunk/api.wordpress.org/public_html/events/1.0/tests: Events: Port
 remaining tests to PHPUnit.
Message-ID: <20210114163151.B21251B0039F@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210114/db7a2bce/attachment-0001.html>

From noreply at wordpress.org  Thu Jan 14 16:31:58 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 14 Jan 2021 16:31:58 +0000 (UTC)
Subject: [wp-meta] [10582]
 sites/trunk/api.wordpress.org/public_html/events/1.0/tests: Events: Rename
 PHPUnit test now that it's the canonical suite.
Message-ID: <20210114163158.4FFF61B0039F@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210114/832a2a4a/attachment-0001.html>

From noreply at wordpress.org  Thu Jan 14 16:55:00 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 16:55:00 -0000
Subject: [wp-meta] [Making WordPress.org] #5577: Support Forums: Topic
 indicator hides first letter of the title on mobile devices
Message-ID: <053.eb921ffa09871815280df329423a9b3c@wordpress.org>

#5577: Support Forums: Topic indicator hides first letter of the title on mobile
devices
----------------------------+--------------------
 Reporter:  vladytimy       |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+--------------------
 On mobile devices {{{(max-width: 568px)}}} the topic header has {{{
 padding-left: 1rem;}}} instead of {{{2rem}}} as on larger screens.


 Topic indicators ''sticky, .super-sticky and .status-closed'' have an
 absolute position of {{{left: -2px;}}} that **doesn't change on mobile
 devices**.


 Because of that, on mobile devices, topic indicators will hide the first
 letter of the topic title. This caugh my attention in a plugin update
 release sticky topic where I read ''.0.6 released'' instead of ''1.0.6
 released'' - quite funny.

 Proposed solution: on devices {{{(max-width: 568px)}}} the topic
 indicators should have {{{left: -16px;}}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5577>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 16:55:24 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 16:55:24 -0000
Subject: [wp-meta] [Making WordPress.org] #5577: Support Forums: Topic
 indicator hides first letter of the title on mobile devices
In-Reply-To: <053.eb921ffa09871815280df329423a9b3c@wordpress.org>
References: <053.eb921ffa09871815280df329423a9b3c@wordpress.org>
Message-ID: <068.6fb1ac581dd5dc3bb2d279f34ac28985@wordpress.org>

#5577: Support Forums: Topic indicator hides first letter of the title on mobile
devices
----------------------------+---------------------
 Reporter:  vladytimy       |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------
Changes (by vladytimy):

 * Attachment "5577-before-and-after.jpg" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5577>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 16:56:13 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 16:56:13 -0000
Subject: [wp-meta] [Making WordPress.org] #5577: Support Forums: Topic
 indicator hides first letter of the title on mobile devices
In-Reply-To: <053.eb921ffa09871815280df329423a9b3c@wordpress.org>
References: <053.eb921ffa09871815280df329423a9b3c@wordpress.org>
Message-ID: <068.8ffec2405ab50fdb84678f039cf10983@wordpress.org>

#5577: Support Forums: Topic indicator hides first letter of the title on mobile
devices
----------------------------+---------------------
 Reporter:  vladytimy       |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------
Changes (by vladytimy):

 * Attachment "5577.patch" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5577>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 16:56:57 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 14 Jan 2021 16:56:57 -0000
Subject: [wp-meta] [Making WordPress.org] #5577: Support Forums: Topic
 indicator hides first letter of the title on mobile devices
In-Reply-To: <053.eb921ffa09871815280df329423a9b3c@wordpress.org>
References: <053.eb921ffa09871815280df329423a9b3c@wordpress.org>
Message-ID: <068.b885939c8c9bdede9b5d3531d33f9ce9@wordpress.org>

#5577: Support Forums: Topic indicator hides first letter of the title on mobile
devices
---------------------------------------------+---------------------
 Reporter:  vladytimy                        |       Owner:  (none)
     Type:  defect                           |      Status:  new
 Priority:  normal                           |   Milestone:
Component:  Support Forums                   |  Resolution:
 Keywords:  has-patch needs-design-feedback  |
---------------------------------------------+---------------------
Changes (by vladytimy):

 * keywords:   => has-patch needs-design-feedback


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5577#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 14 23:34:48 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 14 Jan 2021 23:34:48 +0000 (UTC)
Subject: [wp-meta] [10583]
 sites/trunk/browsehappy.com/public_html/functions.php: Browse Happy:
 Restore WikiQuery query clause that additionally requires the "preferred"
 software version to also explicitly have the "version type" qualifier set
 as "stable version".
Message-ID: <20210114233448.4BEDF1B0039F@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210114/8ae6dbcc/attachment.html>

From noreply at wordpress.org  Fri Jan 15 00:03:38 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 15 Jan 2021 00:03:38 -0000
Subject: [wp-meta] [Making WordPress.org] #5578: Profiles should not display
 details for banned users
Message-ID: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>

#5578: Profiles should not display details for banned users
----------------------------+--------------------
 Reporter:  Ipstenu         |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+--------------------
 When a user is banned, especially for spam, we generally do the following:

 1. Wipe the bio
 2. Delete the URL
 3. Normalize the display name

 The reason for this is that those are generally where people spam (or
 decide to be ... impolite in the brief time between a warning an a
 banning).

 It would be easier all around if the profile on the forums (i.e.
 https://wordpress.org/support/users/dd32/ ) did the following when banned:

 * Display Name (instead, just show the user ID)
 * Profile, Forum Role, Title, (show nothing)
 * Member Since, Topics Started, Replies Created, Reviews Written (maybe
 show nothing??)

 I say maybe on that last run since ... that doesn't really matter in the
 long run.

 Also I'm willing to be talked out the forum role, though right now it
 shows 'Banned' which may be objectionable to some people in a mood.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5578>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan 15 00:21:45 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 15 Jan 2021 00:21:45 -0000
Subject: [wp-meta] [Making WordPress.org] #5578: Profiles should not
 display details for banned users
In-Reply-To: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>
References: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>
Message-ID: <066.d0c0fec0a8351cf99d8537865b8013be@wordpress.org>

#5578: Profiles should not display details for banned users
----------------------------+---------------------
 Reporter:  Ipstenu         |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------

Comment (by dd32):

 > Wipe the bio
 > Delete the URL
 Hiding it seems reasonable, like profiles.w.org does for blocked users.

 > Normalize the display name
 Does this mean resetting it to the user nicename/login? That seems
 reasonable to remove any custom First/Last/Nickname added.

 > Display Name (instead, just show the user ID)
 Is the display name significant here? These pages should be noindexed, so
 I'm not sure that gains much, other than for

 > Profile, Forum Role, Title, (show nothing)
 Agreed.
 I'm not sure the Forum Role field should be shown anyway normally, it
 doesn't seem like much of a benefit other than flagging Moderators. Maybe
 we should just show it if the viewed user has Mod capabilities?

 > Member Since, Topics Started, Replies Created, Reviews Written (maybe
 show nothing??)
 I'm not sure blanking these benefits anyone much? It's not like these are
 private details or going to contain anything sensitive?

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5578#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan 15 01:13:41 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 15 Jan 2021 01:13:41 -0000
Subject: [wp-meta] [Making WordPress.org] #5578: Profiles should not
 display details for banned users
In-Reply-To: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>
References: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>
Message-ID: <066.626b1164222b371c48a9e18f7ab98cb2@wordpress.org>

#5578: Profiles should not display details for banned users
----------------------------+---------------------
 Reporter:  Ipstenu         |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------

Comment (by Ipstenu):

 I should point out... this is a 50-50 help us/help the banned person
 thing.

 So yes, making this hidden helps US mitigate people saying horrible
 things, but it also helps us SAVE those people. It's easier to help
 someone come back from a phenomenally terrible day where they go off the
 rails, if the evidence of their mistake isn't quite so glaring. And a
 number of people do realize "Oh my word, I've been a prat!" and come back
 with a sincere apology. I really want to keep the door open, rather than
 have someone go "Huh, NotOtto has been going off, I'm going to look at
 their profile ... wow. What a horrible human!" It's the same reason we
 archive their posts. It's not for us as much as them.

 > Does this mean resetting it to the user nicename/login? That seems
 reasonable to remove any custom First/Last/Nickname added.

 Yes, resetting it to the nickname to prevent someone from making their
 display name "Buy Viagra!"

 > Is the display name significant here? These pages should be noindexed,
 so I'm not sure that gains much, other than for

 That relates to the above people making their name something dumb and/or
 offensive (like "Otto Really Sux"). Not being indexable doesn't matter all
 that much if I can click on a profile link from a post. (this matters for
 users having bad days more than spammers)

 > I'm not sure blanking these benefits anyone much? It's not like these
 are private details or going to contain anything sensitive?

 It shouldn't, and like I said, really doesn't matter. But I put it there
 in case you saw something I didn't :D

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5578#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan 15 05:48:27 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 15 Jan 2021 05:48:27 +0000 (UTC)
Subject: [wp-meta] [10584]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-support/bbpress/user-profile.php:
 Support Forums: Remove some details from the support profile overview for
 blocked users.
Message-ID: <20210115054827.1423D1B004BE@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210115/2e193347/attachment.html>

From noreply at wordpress.org  Fri Jan 15 05:48:31 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 15 Jan 2021 05:48:31 -0000
Subject: [wp-meta] [Making WordPress.org] #5578: Profiles should not
 display details for banned users
In-Reply-To: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>
References: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>
Message-ID: <066.361e19452d41d893937c499eabdf1c0e@wordpress.org>

#5578: Profiles should not display details for banned users
----------------------------+---------------------
 Reporter:  Ipstenu         |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------

Comment (by dd32):

 In [changeset:"10584" 10584]:
 {{{
 #!CommitTicketReference repository="" revision="10584"
 Support Forums: Remove some details from the support profile overview for
 blocked users.

 See #5578.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5578#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan 15 05:55:04 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 15 Jan 2021 05:55:04 +0000 (UTC)
Subject: [wp-meta] [10585]
 sites/trunk/wordpress.org/public_html/wp-content/mu-plugins/pub/wporg-user-tweaks.php:
 User Tweaks: Use the user nicename for blocked users,
 rather than the contents of the display_name field which may be set to
 something not display friendly.
Message-ID: <20210115055504.444131B004BE@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210115/96e0487a/attachment-0001.html>

From noreply at wordpress.org  Fri Jan 15 05:55:08 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 15 Jan 2021 05:55:08 -0000
Subject: [wp-meta] [Making WordPress.org] #5578: Profiles should not
 display details for banned users
In-Reply-To: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>
References: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>
Message-ID: <066.b84bc5676d562389f4f10dfa5f97834a@wordpress.org>

#5578: Profiles should not display details for banned users
----------------------------+---------------------
 Reporter:  Ipstenu         |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------

Comment (by dd32):

 In [changeset:"10585" 10585]:
 {{{
 #!CommitTicketReference repository="" revision="10585"
 User Tweaks: Use the user nicename for blocked users, rather than the
 contents of the display_name field which may be set to something not
 display friendly.

 See #5578.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5578#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan 15 06:14:21 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 15 Jan 2021 06:14:21 +0000 (UTC)
Subject: [wp-meta] [10586]
 sites/trunk/wordpress.org/public_html/wp-content/mu-plugins/pub/wporg-user-tweaks.php:
 User Tweaks: Add BuddyPress support.
Message-ID: <20210115061421.C44F11B004BE@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210115/08be7fb8/attachment.html>

From noreply at wordpress.org  Fri Jan 15 06:14:26 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 15 Jan 2021 06:14:26 -0000
Subject: [wp-meta] [Making WordPress.org] #5578: Profiles should not
 display details for banned users
In-Reply-To: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>
References: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>
Message-ID: <066.f92447d7425031b58ba82e5cd24e4d6f@wordpress.org>

#5578: Profiles should not display details for banned users
----------------------------+---------------------
 Reporter:  Ipstenu         |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------

Comment (by dd32):

 In [changeset:"10586" 10586]:
 {{{
 #!CommitTicketReference repository="" revision="10586"
 User Tweaks: Add BuddyPress support.

 See #5578.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5578#comment:5>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan 15 06:19:26 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 15 Jan 2021 06:19:26 +0000 (UTC)
Subject: [wp-meta] [10587]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-gp-customizations/inc/class-plugin.php:
 Translate: Avoid PHP Notices after r10575 and r10576 when the translation
 is being added without a translator detail.
Message-ID: <20210115061926.89E381B004BE@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210115/28fd879f/attachment.html>

From noreply at wordpress.org  Fri Jan 15 06:19:31 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 15 Jan 2021 06:19:31 -0000
Subject: [wp-meta] [Making WordPress.org] #5576: Automatically reject
 previous pending translation from same user
In-Reply-To: <056.5b0f342343af08b3713be104576e4684@wordpress.org>
References: <056.5b0f342343af08b3713be104576e4684@wordpress.org>
Message-ID: <071.622236b71932256810cded9f27c1c8f8@wordpress.org>

#5576: Automatically reject previous pending translation from same user
--------------------------------------+---------------------
 Reporter:  tobifjellner              |       Owner:  dd32
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:  fixed
 Keywords:                            |
--------------------------------------+---------------------

Comment (by dd32):

 In [changeset:"10587" 10587]:
 {{{
 #!CommitTicketReference repository="" revision="10587"
 Translate: Avoid PHP Notices after r10575 and r10576 when the translation
 is being added without a translator detail.

 See #5576.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5576#comment:8>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan 15 06:26:44 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 15 Jan 2021 06:26:44 +0000 (UTC)
Subject: [wp-meta] [10588]
 sites/trunk/wordpress.org/public_html/wp-content/mu-plugins/pub/wporg-user-tweaks.php:
 User Tweaks: Fix a typo in the buddypress code in r10586.
Message-ID: <20210115062644.0A2161B00270@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210115/8d736a45/attachment.html>

From noreply at wordpress.org  Fri Jan 15 06:26:48 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 15 Jan 2021 06:26:48 -0000
Subject: [wp-meta] [Making WordPress.org] #5578: Profiles should not
 display details for banned users
In-Reply-To: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>
References: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>
Message-ID: <066.bdeb4cdce299c32c5f3b983a67b13221@wordpress.org>

#5578: Profiles should not display details for banned users
----------------------------+---------------------
 Reporter:  Ipstenu         |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------

Comment (by dd32):

 In [changeset:"10588" 10588]:
 {{{
 #!CommitTicketReference repository="" revision="10588"
 User Tweaks: Fix a typo in the buddypress code in r10586.

 See #5578.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5578#comment:6>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan 15 06:30:12 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 15 Jan 2021 06:30:12 -0000
Subject: [wp-meta] [Making WordPress.org] #5578: Profiles should not
 display details for banned users
In-Reply-To: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>
References: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>
Message-ID: <066.a6567023d2c9fb43dc7944797b606fee@wordpress.org>

#5578: Profiles should not display details for banned users
----------------------------+-----------------------
 Reporter:  Ipstenu         |       Owner:  dd32
     Type:  defect          |      Status:  accepted
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+-----------------------
Changes (by dd32):

 * owner:  (none) => dd32
 * status:  new => accepted


Comment:

 I think the raft of commits above should be enough to consider this fixed.

 Can someone go through and confirm that is the case? :)

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5578#comment:7>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan 15 10:03:02 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 15 Jan 2021 10:03:02 -0000
Subject: [wp-meta] [Making WordPress.org] #5190: Plugin
 images/screenshots should be lazy-loaded
In-Reply-To: <058.54f5a428dd5e97c2eeee2616d36c4937@wordpress.org>
References: <058.54f5a428dd5e97c2eeee2616d36c4937@wordpress.org>
Message-ID: <073.233b51f4003d88461c01dca4d338c263@wordpress.org>

#5190: Plugin images/screenshots should be lazy-loaded
------------------------------+---------------------
 Reporter:  jonoaldersonwp    |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  high              |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  seo performance   |
------------------------------+---------------------
Changes (by jonoaldersonwp):

 * priority:  normal => high


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5190#comment:5>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan 15 19:49:00 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 15 Jan 2021 19:49:00 -0000
Subject: [wp-meta] [Making WordPress.org] #5578: Profiles should not
 display details for banned users
In-Reply-To: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>
References: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>
Message-ID: <066.c4e50b65d5de5dfee8718fa9e62cea5c@wordpress.org>

#5578: Profiles should not display details for banned users
----------------------------+---------------------
 Reporter:  Ipstenu         |       Owner:  dd32
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+---------------------
Changes (by Ipstenu):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 That looks great! I do wonder if we should change the gravatar to blank
 out (Mystery Person), but ... that tends to be far less abused at the
 moment. We can close this and then if it becomes an issue, make a new one.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5578#comment:8>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sat Jan 16 13:06:53 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 16 Jan 2021 13:06:53 -0000
Subject: [wp-meta] [Making WordPress.org] #5579: TemplateNotFound: Template
 "macros.html" not found
Message-ID: <058.0f5aa72515f8f3a0ab71efd9da182340@wordpress.org>

#5579: TemplateNotFound: Template "macros.html" not found
----------------------------+--------------------
 Reporter:  Hareesh Pillai  |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  General         |   Keywords:
----------------------------+--------------------
 There's a link to [https://meta.trac.wordpress.org/rpc API] at the right
 top of the page. Clicking on the link throws Not Found error.

 ==== Details ====

 While doing a GET operation on `/rpc`, Trac issued an internal error.

 User agent: `Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7)
 AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36`

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5579>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 18 00:11:27 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 18 Jan 2021 00:11:27 -0000
Subject: [wp-meta] [Making WordPress.org] #5579: TemplateNotFound:
 Template "macros.html" not found
In-Reply-To: <058.0f5aa72515f8f3a0ab71efd9da182340@wordpress.org>
References: <058.0f5aa72515f8f3a0ab71efd9da182340@wordpress.org>
Message-ID: <073.6257419bfc8df0b59e48a1148f87170d@wordpress.org>

#5579: TemplateNotFound: Template "macros.html" not found
----------------------------+-----------------------
 Reporter:  Hareesh Pillai  |       Owner:  dd32
     Type:  defect          |      Status:  accepted
 Priority:  low             |   Milestone:
Component:  Trac            |  Resolution:
 Keywords:                  |
----------------------------+-----------------------
Changes (by dd32):

 * owner:  (none) => dd32
 * priority:  normal => low
 * status:  new => accepted
 * component:  General => Trac


Comment:

 Disabling that menu item globally seems reasonable (It's disabled on
 core.trac and build.trac).

 I'll see if I can find the macros.html template that should be there too,
 for completeness, but I suspect it's not going to be of much benefit.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5579#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 18 02:27:19 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 18 Jan 2021 02:27:19 +0000 (UTC)
Subject: [wp-meta] [10589]
 sites/trunk/wordpress.org/public_html/wp-content/mu-plugins/pub/wporg-user-tweaks.php:
 User Tweaks: Avoid some PHP Notices in the BuddyPress code,
 as the displayed user functions may be called with no displayed user.
Message-ID: <20210118022719.55FD61B0054B@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210118/3b22e637/attachment.html>

From noreply at wordpress.org  Mon Jan 18 02:27:23 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 18 Jan 2021 02:27:23 -0000
Subject: [wp-meta] [Making WordPress.org] #5578: Profiles should not
 display details for banned users
In-Reply-To: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>
References: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>
Message-ID: <066.cf6d5d3372222b522134612fa58bb6af@wordpress.org>

#5578: Profiles should not display details for banned users
----------------------------+---------------------
 Reporter:  Ipstenu         |       Owner:  dd32
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+---------------------

Comment (by dd32):

 In [changeset:"10589" 10589]:
 {{{
 #!CommitTicketReference repository="" revision="10589"
 User Tweaks: Avoid some PHP Notices in the BuddyPress code, as the
 displayed user functions may be called with no displayed user.

 See [10588], [10586].
 See #5578.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5578#comment:9>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 18 02:37:03 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 18 Jan 2021 02:37:03 -0000
Subject: [wp-meta] [Making WordPress.org] #5578: Profiles should not
 display details for banned users
In-Reply-To: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>
References: <051.1ace0bc1adf04b90b32776199810d2d8@wordpress.org>
Message-ID: <066.b8a6415e154cb1fa508f060543665f19@wordpress.org>

#5578: Profiles should not display details for banned users
----------------------------+---------------------
 Reporter:  Ipstenu         |       Owner:  dd32
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+---------------------

Comment (by dd32):

 Replying to [comment:8 Ipstenu]:
 > I do wonder if we should change the gravatar to blank out (Mystery
 Person), but ... that tends to be far less abused at the moment.

 I considered quickly adding that, until I saw the
 [https://core.trac.wordpress.org/browser/tags/5.6/src/wp-includes/link-
 template.php?marks=4202-4241#L4198 40 lines] of code to determine
 what/who/where the avatar to display is..

 If it becomes an issue, abusive/spam/obscene gravatars are probably
 against the Gravatar ToS, or at least should be marked as higher than
 G-rated, and the Gravatar support team will probably take action, or, in
 the rare case of this being a thing the email can be changed.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5578#comment:10>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 18 02:42:32 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 18 Jan 2021 02:42:32 +0000 (UTC)
Subject: [wp-meta] [10590] sites/trunk/trac.wordpress.org/conf/common.ini:
 Trac: Disable the `rpc` (API) menu item globally for all trac instances,
 rather than just on core.trac.
Message-ID: <20210118024232.150F81B0054B@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210118/ddbbf82c/attachment.html>

From noreply at wordpress.org  Mon Jan 18 02:42:36 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 18 Jan 2021 02:42:36 -0000
Subject: [wp-meta] [Making WordPress.org] #5579: TemplateNotFound:
 Template "macros.html" not found
In-Reply-To: <058.0f5aa72515f8f3a0ab71efd9da182340@wordpress.org>
References: <058.0f5aa72515f8f3a0ab71efd9da182340@wordpress.org>
Message-ID: <073.7f14c3064d83d53d4894224ac3e49e06@wordpress.org>

#5579: TemplateNotFound: Template "macros.html" not found
----------------------------+---------------------
 Reporter:  Hareesh Pillai  |       Owner:  dd32
     Type:  defect          |      Status:  closed
 Priority:  low             |   Milestone:
Component:  Trac            |  Resolution:  fixed
 Keywords:                  |
----------------------------+---------------------
Changes (by dd32):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"10590" 10590]:
 {{{
 #!CommitTicketReference repository="" revision="10590"
 Trac: Disable the `rpc` (API) menu item globally for all trac instances,
 rather than just on core.trac.

 Fixes #5579.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5579#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 18 02:47:15 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 18 Jan 2021 02:47:15 +0000 (UTC)
Subject: [wp-meta] [10591] sites/trunk/trac.wordpress.org/conf/common.ini:
 Trac: Set the `default_charset` to `urf-8`.
Message-ID: <20210118024715.EA17F1B0054B@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210118/444f6064/attachment.html>

From noreply at wordpress.org  Mon Jan 18 02:47:20 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 18 Jan 2021 02:47:20 -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.35a835eda55f2102ed3996c3b0a33f84@wordpress.org>

#1639: Themes Trac browser does not display UTF-8 text correctly
-----------------------------+-----------------------
 Reporter:  SergeyBiryukov   |       Owner:  dd32
     Type:  defect           |      Status:  accepted
 Priority:  normal           |   Milestone:  Q1
Component:  Trac             |  Resolution:
 Keywords:  pending-systems  |
-----------------------------+-----------------------

Comment (by dd32):

 In [changeset:"10591" 10591]:
 {{{
 #!CommitTicketReference repository="" revision="10591"
 Trac: Set the `default_charset` to `urf-8`.

 See https://make.wordpress.org/systems/2019/01/23/as-per-https-meta-trac-
 wordpress-org-ticket-1639-can-we/
 See #1639.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/1639#comment:13>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 18 03:34:36 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 18 Jan 2021 03:34:36 -0000
Subject: [wp-meta] [Making WordPress.org] #5579: TemplateNotFound:
 Template "macros.html" not found
In-Reply-To: <058.0f5aa72515f8f3a0ab71efd9da182340@wordpress.org>
References: <058.0f5aa72515f8f3a0ab71efd9da182340@wordpress.org>
Message-ID: <073.94851effc4b5699f11ae4c7d74754e5f@wordpress.org>

#5579: TemplateNotFound: Template "macros.html" not found
----------------------------+---------------------
 Reporter:  Hareesh Pillai  |       Owner:  dd32
     Type:  defect          |      Status:  closed
 Priority:  low             |   Milestone:
Component:  Trac            |  Resolution:  fixed
 Keywords:                  |
----------------------------+---------------------

Comment (by dd32):

 Just noting that macros.html was removed from Trac 1.2, 1.0 was the last
 version with it, I'm not sure why the templates we're using is referencing
 it, as I can't find any refs to it.

 https://trac.edgewall.org/browser/branches/1.0-stable/trac/templates/macros.html

 It's probably got something to do with us using the old Trac templating
 library, something I don't have an urgent want to touch, and I don't think
 adding `macros.html` into our custom theme is a good idea (There's
 probably others that are missing anyway).

 Removing the link is good enough for me.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5579#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 18 15:11:44 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 18 Jan 2021 15:11:44 -0000
Subject: [wp-meta] [Making WordPress.org] #5580: New meeting times for
 documentation team
Message-ID: <056.1ebb3d4e52e8dc363edf45e6d95b8c3a@wordpress.org>

#5580: New meeting times for documentation team
--------------------------------+--------------------
 Reporter:  justinahinon        |      Owner:  (none)
     Type:  defect              |     Status:  new
 Priority:  normal              |  Milestone:
Component:  WordPress.org Site  |   Keywords:
--------------------------------+--------------------
 As of January 2021, the meeting times for the documentation team have
 moved to 14:00UTC (https://make.wordpress.org/docs/2020/12/02/new-meeting-
 time-holiday-planning/)

 We'll need to alter this on the meetings page
 (https://make.wordpress.org/meetings/#docs)

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5580>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 18 23:17:38 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 18 Jan 2021 23:17:38 +0000 (UTC)
Subject: [wp-meta] [10592]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-patterns:
 WP.org Pub Themes: Add Pattern Directory theme.
Message-ID: <20210118231738.75B4C1B003C9@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210118/ab12c7c8/attachment-0001.html>

From noreply at wordpress.org  Mon Jan 18 23:50:27 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 18 Jan 2021 23:50:27 -0000
Subject: [wp-meta] [Making WordPress.org] #5580: New meeting times for
 documentation team
In-Reply-To: <056.1ebb3d4e52e8dc363edf45e6d95b8c3a@wordpress.org>
References: <056.1ebb3d4e52e8dc363edf45e6d95b8c3a@wordpress.org>
Message-ID: <071.0392363b0bcb83cebc30bc17f5dc35aa@wordpress.org>

#5580: New meeting times for documentation team
--------------------------------+---------------------
 Reporter:  justinahinon        |       Owner:  (none)
     Type:  defect              |      Status:  closed
 Priority:  normal              |   Milestone:
Component:  WordPress.org Site  |  Resolution:  fixed
 Keywords:                      |
--------------------------------+---------------------
Changes (by dd32):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Updated.

 Team reps can get access to https://make.wordpress.org/wp-
 admin/post.php?post=1686&action=edit if they want it, but pinging in the
 #meta channel to update make.wordpress.org/meetings is also acceptable.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5580#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 19 04:23:43 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 19 Jan 2021 04:23:43 +0000 (UTC)
Subject: [wp-meta] [10593]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/theme-directory/class-wporg-themes-upload.php:
 Theme Directory: Catch SVN errors when uploading a theme update.
Message-ID: <20210119042343.42B331B005EF@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210119/4493f5d8/attachment.html>

From noreply at wordpress.org  Tue Jan 19 04:38:56 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 19 Jan 2021 04:38:56 +0000 (UTC)
Subject: [wp-meta] [10594]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/support-forums/inc/class-user-notes.php:
 Support Forums: Display user notes (and allow them to be added from) the
 forum user edit screen.
Message-ID: <20210119043856.91A341B005EF@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210119/a3d55369/attachment-0001.html>

From noreply at wordpress.org  Tue Jan 19 04:39:01 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 19 Jan 2021 04:39:01 -0000
Subject: [wp-meta] [Making WordPress.org] #4192: Support Forums: Add
 User Notes to the EDIT page
In-Reply-To: <051.d7089e7e28437e65b368ede089e4c866@wordpress.org>
References: <051.d7089e7e28437e65b368ede089e4c866@wordpress.org>
Message-ID: <066.98ab1d7aaeff9855b5c8568f1b489ee9@wordpress.org>

#4192: Support Forums: Add User Notes to the EDIT page
----------------------------+---------------------
 Reporter:  Ipstenu         |       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:"10594" 10594]:
 {{{
 #!CommitTicketReference repository="" revision="10594"
 Support Forums: Display user notes (and allow them to be added from) the
 forum user edit screen.

 See #4691.
 Fixes #4192.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4192#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 19 04:39:01 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 19 Jan 2021 04:39:01 -0000
Subject: [wp-meta] [Making WordPress.org] #4691: Break Password Hash
 when user is blocked
In-Reply-To: <051.3c6a5d1515ca1a3867d0371124f33402@wordpress.org>
References: <051.3c6a5d1515ca1a3867d0371124f33402@wordpress.org>
Message-ID: <066.1ac7cd95580830477fd6cc3cdbe02398@wordpress.org>

#4691: Break Password Hash when user is blocked
-----------------------------+-----------------------
 Reporter:  Ipstenu          |       Owner:  dd32
     Type:  defect           |      Status:  accepted
 Priority:  highest omg bbq  |   Milestone:
Component:  Support Forums   |  Resolution:
 Keywords:                   |
-----------------------------+-----------------------

Comment (by dd32):

 In [changeset:"10594" 10594]:
 {{{
 #!CommitTicketReference repository="" revision="10594"
 Support Forums: Display user notes (and allow them to be added from) the
 forum user edit screen.

 See #4691.
 Fixes #4192.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4691#comment:26>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 19 04:40:47 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 19 Jan 2021 04:40:47 +0000 (UTC)
Subject: [wp-meta] [10595]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/support-forums/inc/class-hooks.php:
 Support Forums: When automatically adding a "Forum role changed to.." user
 note,
 append it to the last note added if it's from the current user in the last 5
 minutes.
Message-ID: <20210119044047.81E8D1B005EF@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210119/f9ddb89b/attachment.html>

From noreply at wordpress.org  Tue Jan 19 04:40:52 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 19 Jan 2021 04:40:52 -0000
Subject: [wp-meta] [Making WordPress.org] #4192: Support Forums: Add
 User Notes to the EDIT page
In-Reply-To: <051.d7089e7e28437e65b368ede089e4c866@wordpress.org>
References: <051.d7089e7e28437e65b368ede089e4c866@wordpress.org>
Message-ID: <066.993f1cc3650340cab70bcdac8b8535d9@wordpress.org>

#4192: Support Forums: Add User Notes to the EDIT page
----------------------------+---------------------
 Reporter:  Ipstenu         |       Owner:  dd32
     Type:  enhancement     |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:  has-patch       |
----------------------------+---------------------

Comment (by dd32):

 In [changeset:"10595" 10595]:
 {{{
 #!CommitTicketReference repository="" revision="10595"
 Support Forums: When automatically adding a "Forum role changed to.." user
 note, append it to the last note added if it's from the current user in
 the last 5 minutes.

 This allows for a note added while blocking/unblocking a user to contain
 both the moderator note and the action performed.

 See #4192.
 Fixes #4691.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4192#comment:5>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 19 04:40:52 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 19 Jan 2021 04:40:52 -0000
Subject: [wp-meta] [Making WordPress.org] #4691: Break Password Hash
 when user is blocked
In-Reply-To: <051.3c6a5d1515ca1a3867d0371124f33402@wordpress.org>
References: <051.3c6a5d1515ca1a3867d0371124f33402@wordpress.org>
Message-ID: <066.adf82bf078b38227778399dec86c760b@wordpress.org>

#4691: Break Password Hash when user is blocked
-----------------------------+---------------------
 Reporter:  Ipstenu          |       Owner:  dd32
     Type:  defect           |      Status:  closed
 Priority:  highest omg bbq  |   Milestone:
Component:  Support Forums   |  Resolution:  fixed
 Keywords:                   |
-----------------------------+---------------------
Changes (by dd32):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"10595" 10595]:
 {{{
 #!CommitTicketReference repository="" revision="10595"
 Support Forums: When automatically adding a "Forum role changed to.." user
 note, append it to the last note added if it's from the current user in
 the last 5 minutes.

 This allows for a note added while blocking/unblocking a user to contain
 both the moderator note and the action performed.

 See #4192.
 Fixes #4691.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4691#comment:27>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 19 06:13:19 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 19 Jan 2021 06:13:19 -0000
Subject: [wp-meta] [Making WordPress.org] #4135: Kill profile RSS feeds
 from bbpress 1
In-Reply-To: <055.b45f0963163f3c00a5969bbd194141b1@wordpress.org>
References: <055.b45f0963163f3c00a5969bbd194141b1@wordpress.org>
Message-ID: <070.740c5a719d39ae6f2047e390098b7f51@wordpress.org>

#4135: Kill profile RSS feeds from bbpress 1
----------------------------+---------------------
 Reporter:  joostdevalk     |       Owner:  (none)
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:  seo             |
----------------------------+---------------------
Changes (by dd32):

 * status:  new => closed
 * resolution:   => fixed


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4135#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 19 06:14:28 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 19 Jan 2021 06:14:28 -0000
Subject: [wp-meta] [Making WordPress.org] #5384: Remove old bb-admin
In-Reply-To: <051.72b82ef8b7b2671a6ac87a0dbaf5fbdd@wordpress.org>
References: <051.72b82ef8b7b2671a6ac87a0dbaf5fbdd@wordpress.org>
Message-ID: <066.e6737b820ea10fbb625fc453e2b1f402@wordpress.org>

#5384: Remove old bb-admin
----------------------------+---------------------
 Reporter:  Clorith         |       Owner:  dd32
     Type:  task            |      Status:  closed
 Priority:  high            |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+---------------------
Changes (by dd32):

 * status:  accepted => closed
 * resolution:   => fixed


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5384#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 19 06:32:12 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 19 Jan 2021 06:32:12 +0000 (UTC)
Subject: [wp-meta] =?utf-8?q?=5B10596=5D_sites/trunk/wordpress=2Eorg/publi?=
 =?utf-8?q?c=5Fhtml/wp-content/plugins/support-forums/inc=3A_Support_Forum?=
 =?utf-8?q?s=3A_Add_a_301_redirect_for_the_old_/support/topic=2Ephp=3Fid?=
 =?utf-8?q?=3D1234_URL_structure=2E?=
Message-ID: <20210119063212.5BE121B0042A@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210119/b0792394/attachment.html>

From noreply at wordpress.org  Tue Jan 19 06:32:16 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 19 Jan 2021 06:32:16 -0000
Subject: [wp-meta] [Making WordPress.org] #5274: Requesting a topic ID
 directly redirects via a 302
In-Reply-To: <058.794df6e89d018cb7a04a5f71d6b873a8@wordpress.org>
References: <058.794df6e89d018cb7a04a5f71d6b873a8@wordpress.org>
Message-ID: <073.0b7f837e264d8f201bc738d6714570fd@wordpress.org>

#5274: Requesting a topic ID directly redirects via a 302
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  dd32
     Type:  defect          |      Status:  closed
 Priority:  lowest          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:  seo             |
----------------------------+---------------------
Changes (by dd32):

 * owner:  (none) => dd32
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"10596" 10596]:
 {{{
 #!CommitTicketReference repository="" revision="10596"
 Support Forums: Add a 301 redirect for the old /support/topic.php?id=1234
 URL structure.

 Fixes #5274.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5274#comment:5>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 19 06:36:15 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 19 Jan 2021 06:36:15 -0000
Subject: [wp-meta] [Making WordPress.org] #5328: Support URLs should 301
 to lowercase (was: Theme support URLs should 301 to lowercase)
In-Reply-To: <058.4649cccac2c47d1fd3992bfba436f244@wordpress.org>
References: <058.4649cccac2c47d1fd3992bfba436f244@wordpress.org>
Message-ID: <073.fa49f1b2d962a99a1de2acd43fb72108@wordpress.org>

#5328: Support URLs should 301 to lowercase
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  seo             |
----------------------------+---------------------
Description changed by dd32:

Old description:

> URLs like https://wordpress.org/support/theme/BusinessX/ should redirect
> to the lowercase equivalent via a 301 redirect.

New description:

 URLs like https://wordpress.org/support/theme/BusinessX/ and
 https://wordpress.org/support/topic/rEmove-NO-comments/ and
 https://wordpress.org/support/view/SPAM/ should redirect to the lowercase
 equivalent via a 301 redirect.

--

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5328#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 19 06:47:07 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 19 Jan 2021 06:47:07 +0000 (UTC)
Subject: [wp-meta] [10597]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-support:
 Support Forums: Always show the topic actions when on a mobile device.
Message-ID: <20210119064707.7F0581B00448@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210119/e8cfbc4e/attachment-0001.html>

From noreply at wordpress.org  Tue Jan 19 06:47:11 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 19 Jan 2021 06:47:11 -0000
Subject: [wp-meta] [Making WordPress.org] #5516: Support forum: Make
 action links always visible
In-Reply-To: <056.6417b524ea7f3a7125b3f5134745302b@wordpress.org>
References: <056.6417b524ea7f3a7125b3f5134745302b@wordpress.org>
Message-ID: <071.7bb0d52902b0590e5b130c007e9927af@wordpress.org>

#5516: Support forum: Make action links always visible
----------------------------+---------------------
 Reporter:  tobifjellner    |       Owner:  dd32
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+---------------------
Changes (by dd32):

 * owner:  (none) => dd32
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"10597" 10597]:
 {{{
 #!CommitTicketReference repository="" revision="10597"
 Support Forums: Always show the topic actions when on a mobile device.

 Fixes #5516.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5516#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 19 06:50:00 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 19 Jan 2021 06:50:00 +0000 (UTC)
Subject: [wp-meta] [10598]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-support/functions.php:
 support Forums: Cache bump after r10597.
Message-ID: <20210119065000.E263B1B00448@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210119/26c4cc9e/attachment.html>

From noreply at wordpress.org  Tue Jan 19 06:50:05 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 19 Jan 2021 06:50:05 -0000
Subject: [wp-meta] [Making WordPress.org] #5516: Support forum: Make
 action links always visible
In-Reply-To: <056.6417b524ea7f3a7125b3f5134745302b@wordpress.org>
References: <056.6417b524ea7f3a7125b3f5134745302b@wordpress.org>
Message-ID: <071.e5446509e84ee9db3528869716fd4b08@wordpress.org>

#5516: Support forum: Make action links always visible
----------------------------+---------------------
 Reporter:  tobifjellner    |       Owner:  dd32
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+---------------------

Comment (by dd32):

 In [changeset:"10598" 10598]:
 {{{
 #!CommitTicketReference repository="" revision="10598"
 support Forums: Cache bump after r10597.

 See #5516.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5516#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 19 07:00:53 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 19 Jan 2021 07:00:53 -0000
Subject: [wp-meta] [Making WordPress.org] #5580: New meeting times for
 documentation team
In-Reply-To: <056.1ebb3d4e52e8dc363edf45e6d95b8c3a@wordpress.org>
References: <056.1ebb3d4e52e8dc363edf45e6d95b8c3a@wordpress.org>
Message-ID: <071.0b54d9a54b424ad24d6b2afc31ade40b@wordpress.org>

#5580: New meeting times for documentation team
--------------------------------+---------------------
 Reporter:  justinahinon        |       Owner:  (none)
     Type:  defect              |      Status:  closed
 Priority:  normal              |   Milestone:
Component:  WordPress.org Site  |  Resolution:  fixed
 Keywords:                      |
--------------------------------+---------------------

Comment (by justinahinon):

 Thank you @dd32 🙂.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5580#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 19 07:09:47 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 19 Jan 2021 07:09:47 +0000 (UTC)
Subject: [wp-meta] [10599]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/support-forums/inc/class-performance-optimizations.php:
 Support Forums: Limit new tag creation to moderators.
Message-ID: <20210119070947.DA7AB1B00448@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210119/ec68886e/attachment-0001.html>

From noreply at wordpress.org  Tue Jan 19 07:09:52 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 19 Jan 2021 07:09:52 -0000
Subject: [wp-meta] [Making WordPress.org] #5344: Delete stale,
 orphaned topic tags
In-Reply-To: <058.deee108539938b5d6762b863877d958d@wordpress.org>
References: <058.deee108539938b5d6762b863877d958d@wordpress.org>
Message-ID: <073.b21964bfc91aa1a2c91f6dc8b9bffd41@wordpress.org>

#5344: Delete stale, orphaned topic tags
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  low             |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  seo             |
----------------------------+---------------------

Comment (by dd32):

 In [changeset:"10599" 10599]:
 {{{
 #!CommitTicketReference repository="" revision="10599"
 Support Forums: Limit new tag creation to moderators.

 Props Clorith.
 See #5344.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5344#comment:13>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 19 07:10:28 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 19 Jan 2021 07:10:28 -0000
Subject: [wp-meta] [Making WordPress.org] #5344: Delete stale,
 orphaned topic tags
In-Reply-To: <058.deee108539938b5d6762b863877d958d@wordpress.org>
References: <058.deee108539938b5d6762b863877d958d@wordpress.org>
Message-ID: <073.1ebc90857ab5e0cb62a0f2093501d9b9@wordpress.org>

#5344: Delete stale, orphaned topic tags
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  low             |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  seo             |
----------------------------+---------------------

Comment (by dd32):

 Just noting that I cleaned up [attachment:"5344-limit-topic-
 creation.2.patch"] a little bit, and moved it to Performance
 Optimizations, so that this only affects the english support forums, and
 not all the localised support forums.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5344#comment:14>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 19 07:18:28 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 19 Jan 2021 07:18:28 +0000 (UTC)
Subject: [wp-meta] [10600]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-support:
 Support Forums: Don't overlap the sticky/locked/etc icon over the title on
 mobile devices.
Message-ID: <20210119071828.131C91B00448@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210119/50fda6e7/attachment-0001.html>

From noreply at wordpress.org  Tue Jan 19 07:18:32 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 19 Jan 2021 07:18:32 -0000
Subject: [wp-meta] [Making WordPress.org] #5577: Support Forums: Topic
 indicator hides first letter of the title on mobile devices
In-Reply-To: <053.eb921ffa09871815280df329423a9b3c@wordpress.org>
References: <053.eb921ffa09871815280df329423a9b3c@wordpress.org>
Message-ID: <068.e51ba617f4cca4273aab2cdc7b08c749@wordpress.org>

#5577: Support Forums: Topic indicator hides first letter of the title on mobile
devices
---------------------------------------------+---------------------
 Reporter:  vladytimy                        |       Owner:  dd32
     Type:  defect                           |      Status:  closed
 Priority:  normal                           |   Milestone:
Component:  Support Forums                   |  Resolution:  fixed
 Keywords:  has-patch needs-design-feedback  |
---------------------------------------------+---------------------
Changes (by dd32):

 * owner:  (none) => dd32
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"10600" 10600]:
 {{{
 #!CommitTicketReference repository="" revision="10600"
 Support Forums: Don't overlap the sticky/locked/etc icon over the title on
 mobile devices.

 Props vladytimy.
 Fixes #5577.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5577#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 19 07:20:56 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 19 Jan 2021 07:20:56 +0000 (UTC)
Subject: [wp-meta] [10601]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-support/functions.php:
 Support Forums: cache bump after [10600].
Message-ID: <20210119072056.3D66C1B00448@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210119/98401a93/attachment.html>

From noreply at wordpress.org  Tue Jan 19 07:21:00 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 19 Jan 2021 07:21:00 -0000
Subject: [wp-meta] [Making WordPress.org] #5577: Support Forums: Topic
 indicator hides first letter of the title on mobile devices
In-Reply-To: <053.eb921ffa09871815280df329423a9b3c@wordpress.org>
References: <053.eb921ffa09871815280df329423a9b3c@wordpress.org>
Message-ID: <068.6ce017ea2c5e4ba00f8010c3889ca29d@wordpress.org>

#5577: Support Forums: Topic indicator hides first letter of the title on mobile
devices
---------------------------------------------+---------------------
 Reporter:  vladytimy                        |       Owner:  dd32
     Type:  defect                           |      Status:  closed
 Priority:  normal                           |   Milestone:
Component:  Support Forums                   |  Resolution:  fixed
 Keywords:  has-patch needs-design-feedback  |
---------------------------------------------+---------------------

Comment (by dd32):

 In [changeset:"10601" 10601]:
 {{{
 #!CommitTicketReference repository="" revision="10601"
 Support Forums: cache bump after [10600].

 See #5577.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5577#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 19 07:26:38 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 19 Jan 2021 07:26:38 -0000
Subject: [wp-meta] [Making WordPress.org] #5338: "Topic tag" templates
 should be noindexed
In-Reply-To: <058.6cb9ddf95421db051a0d8cf4d79a511f@wordpress.org>
References: <058.6cb9ddf95421db051a0d8cf4d79a511f@wordpress.org>
Message-ID: <073.aa2d8958f37a61d116cd129c1c8646d7@wordpress.org>

#5338: "Topic tag" templates should be noindexed
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  seo             |
----------------------------+---------------------

Comment (by dd32):

 Does this replace #4324, #4338?

 Keep in mind, there's also #5344 which will result in many fewer tags, and
 more focused ones.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5338#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 19 09:05:43 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 19 Jan 2021 09:05:43 -0000
Subject: [wp-meta] [Making WordPress.org] #5338: "Topic tag" templates
 should be noindexed
In-Reply-To: <058.6cb9ddf95421db051a0d8cf4d79a511f@wordpress.org>
References: <058.6cb9ddf95421db051a0d8cf4d79a511f@wordpress.org>
Message-ID: <073.00ff66cd5c1f13942775c520f6f76f24@wordpress.org>

#5338: "Topic tag" templates should be noindexed
----------------------------+-------------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  maybelater
 Keywords:  seo             |
----------------------------+-------------------------
Changes (by jonoaldersonwp):

 * status:  new => closed
 * resolution:   => maybelater


Comment:

 Good shout; closing pending a re-review in a world of fewer tags!

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5338#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 19 09:06:27 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 19 Jan 2021 09:06:27 -0000
Subject: [wp-meta] [Making WordPress.org] #5344: Delete stale,
 orphaned topic tags
In-Reply-To: <058.deee108539938b5d6762b863877d958d@wordpress.org>
References: <058.deee108539938b5d6762b863877d958d@wordpress.org>
Message-ID: <073.7f69146182d0879e7f05d087fcc10d52@wordpress.org>

#5344: Delete stale, orphaned topic tags
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  low             |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  seo             |
----------------------------+---------------------

Comment (by jonoaldersonwp):

 Replying to [comment:14 dd32]:
 > Just noting that I cleaned up [attachment:"5344-limit-topic-
 creation.2.patch"] a little bit, and moved it to Performance
 Optimizations, so that this only affects the english support forums, and
 not all the localised support forums.

 Nice one!

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5344#comment:15>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 19 23:07:16 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 19 Jan 2021 23:07:16 +0000 (UTC)
Subject: [wp-meta] [10602]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/support-forums/inc/class-performance-optimizations.php:
 Support: Fix a PHP warning caused when only one tag is added to a thread.
Message-ID: <20210119230716.AB4561B0042E@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210119/4c8c035d/attachment.html>

From noreply at wordpress.org  Tue Jan 19 23:07:20 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 19 Jan 2021 23:07:20 -0000
Subject: [wp-meta] [Making WordPress.org] #5344: Delete stale,
 orphaned topic tags
In-Reply-To: <058.deee108539938b5d6762b863877d958d@wordpress.org>
References: <058.deee108539938b5d6762b863877d958d@wordpress.org>
Message-ID: <073.c5f26b9d75aab4fb5edc2bb5da5d6f77@wordpress.org>

#5344: Delete stale, orphaned topic tags
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  low             |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  seo             |
----------------------------+---------------------

Comment (by dd32):

 In [changeset:"10602" 10602]:
 {{{
 #!CommitTicketReference repository="" revision="10602"
 Support: Fix a PHP warning caused when only one tag is added to a thread.

 Amends [10599].
 See #5344.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5344#comment:16>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 19 23:09:41 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 19 Jan 2021 23:09:41 +0000 (UTC)
Subject: [wp-meta] [10603]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/support-forums/inc/class-performance-optimizations.php:
 Support: Handle `one, two` being passed not just `one, two`.
Message-ID: <20210119230941.CE19C1B0042E@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210119/b98bffe8/attachment.html>

From noreply at wordpress.org  Tue Jan 19 23:09:46 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 19 Jan 2021 23:09:46 -0000
Subject: [wp-meta] [Making WordPress.org] #5344: Delete stale,
 orphaned topic tags
In-Reply-To: <058.deee108539938b5d6762b863877d958d@wordpress.org>
References: <058.deee108539938b5d6762b863877d958d@wordpress.org>
Message-ID: <073.55bb250fca9eee5824ea4aaef5c59f9c@wordpress.org>

#5344: Delete stale, orphaned topic tags
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  low             |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  seo             |
----------------------------+---------------------

Comment (by dd32):

 In [changeset:"10603" 10603]:
 {{{
 #!CommitTicketReference repository="" revision="10603"
 Support: Handle `one,two` being passed not just `one, two`. This shouldn't
 be needed, but better to be forwards compatible.

 Amends [10602].
 See #5344.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5344#comment:17>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 20 05:31:04 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 20 Jan 2021 05:31:04 +0000 (UTC)
Subject: [wp-meta] [10604] sites/trunk/wordpress.org/public_html/wp-content:
 Support: Add a 'All Replies' moderator view to see an overview all of
 current forum activity.
Message-ID: <20210120053104.B96B21B00728@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210120/8eb70963/attachment-0001.html>

From noreply at wordpress.org  Wed Jan 20 16:37:47 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 20 Jan 2021 16:37:47 +0000 (UTC)
Subject: [wp-meta] [10605]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-plugins:
 Plugin Directory: Remove unused React code.
Message-ID: <20210120163747.98DBB1B00221@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210120/8ec15bf0/attachment-0001.html>

From noreply at wordpress.org  Wed Jan 20 16:37:51 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 20 Jan 2021 16:37:51 -0000
Subject: [wp-meta] [Making WordPress.org] #5431: Plugin Directory:
 Remove unused React code
In-Reply-To: <050.cabb2a40277b7c6f7646cbc59a4fe5a2@wordpress.org>
References: <050.cabb2a40277b7c6f7646cbc59a4fe5a2@wordpress.org>
Message-ID: <065.11d7b3cb1829aa9bd9df246280e749f5@wordpress.org>

#5431: Plugin Directory: Remove unused React code
------------------------------+---------------------
 Reporter:  ryelle            |       Owner:  ryelle
     Type:  task              |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:  has-patch         |
------------------------------+---------------------
Changes (by ryelle):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"10605" 10605]:
 {{{
 #!CommitTicketReference repository="" revision="10605"
 Plugin Directory: Remove unused React code.

 As part of the Plugin Directory refresh #1719, the UI was rewritten into a
 React app, but currently only the screenshot slider uses React. This
 removes all the React JS except for the screenshots, and flattens the Sass
 into less complex files. Additionally it updates the packages and JS build
 process to use @wordpress/scripts.

 Fixes #5431.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5431#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 20 17:51:34 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 20 Jan 2021 17:51:34 +0000 (UTC)
Subject: [wp-meta] [10606]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-plugins/js/section-faq.js:
 Plugin Directory: Stop adding a `#` when generating FAQ IDs in JavaScript.
Message-ID: <20210120175134.868431B00221@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210120/0aaebe50/attachment.html>

From noreply at wordpress.org  Wed Jan 20 17:51:39 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 20 Jan 2021 17:51:39 -0000
Subject: [wp-meta] [Making WordPress.org] #5572: Plugin FAQ anchor links
 get broken when used in a forum post
In-Reply-To: <055.4bde25634acd359aba1c7bd54d41e16b@wordpress.org>
References: <055.4bde25634acd359aba1c7bd54d41e16b@wordpress.org>
Message-ID: <070.27d225a7c15746e74c7dc40b4e828ab9@wordpress.org>

#5572: Plugin FAQ anchor links get broken when used in a forum post
----------------------------+---------------------
 Reporter:  johnbillion     |       Owner:  dd32
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+---------------------

Comment (by ryelle):

 In [changeset:"10606" 10606]:
 {{{
 #!CommitTicketReference repository="" revision="10606"
 Plugin Directory: Stop adding a `#` when generating FAQ IDs in JavaScript.

 This keeps the behavior consistent between PHP and JS.

 See #5572.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5572#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 20 17:53:49 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 20 Jan 2021 17:53:49 +0000 (UTC)
Subject: [wp-meta] [10607]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-plugins/functions.php:
 Plugin Directory: Bump JS cache after [10606].
Message-ID: <20210120175349.0F3DB1B00221@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210120/db9d4d02/attachment.html>

From noreply at wordpress.org  Wed Jan 20 17:53:53 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 20 Jan 2021 17:53:53 -0000
Subject: [wp-meta] [Making WordPress.org] #5572: Plugin FAQ anchor links
 get broken when used in a forum post
In-Reply-To: <055.4bde25634acd359aba1c7bd54d41e16b@wordpress.org>
References: <055.4bde25634acd359aba1c7bd54d41e16b@wordpress.org>
Message-ID: <070.e2aa959be4a63a03062a1dab1ee99095@wordpress.org>

#5572: Plugin FAQ anchor links get broken when used in a forum post
----------------------------+---------------------
 Reporter:  johnbillion     |       Owner:  dd32
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+---------------------

Comment (by ryelle):

 In [changeset:"10607" 10607]:
 {{{
 #!CommitTicketReference repository="" revision="10607"
 Plugin Directory: Bump JS cache after [10606].

 See #5572.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5572#comment:5>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 20 19:38:57 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 20 Jan 2021 19:38:57 -0000
Subject: [wp-meta] [Making WordPress.org] #5581: Consolidating setup of
 local Dev environment documentation and testing instructions.
Message-ID: <055.c21c2a31ed9157aea19cbb810b655e9c@wordpress.org>

#5581: Consolidating setup of local Dev environment documentation and testing
instructions.
-------------------------+--------------------
 Reporter:  paaljoachim  |      Owner:  (none)
     Type:  task         |     Status:  new
 Priority:  normal       |  Milestone:
Component:  General      |   Keywords:
-------------------------+--------------------
 There are several places that have the same kind of documentation for
 setting up a local dev environment. These exist in various degrees of
 completeness and quality. There is also a crossover of docs in regards to
 testing/contributing. It would be great to see if we can combine these
 efforts and create one central place for documentation for setting up a
 local dev environment + testing instructions.

 Here is an example from the Block Editor Handbook:
 https://developer.wordpress.org/block-editor/tutorials/devenv/#quick-start
 +
 Issue in relation to testing pull requests:
 https://github.com/WordPress/gutenberg/issues/25202

 Here is an example from a post on P2:
 https://make.wordpress.org/core/2021/01/15/test-scrub-for-wordpress-5-7/

 Core Handbook Getting Started
 https://make.wordpress.org/core/handbook/tutorials/getting-started
 /#setting-up-a-local-server

 https://github.com/WordPress/wordpress-develop


 -------


 Documentation we can easily update showing methods for WordPress core and
 Gutenberg. A document for setting up a local dev environment, and a
 document for testing trac tickets as well as Gutenberg Github pull
 requests.

 Having an easy to follow step by step hand holding method with some short
 explanations and some troubleshooting tips would be a huge help to people
 at various skill levels. Making it easy for developers and non developers
 to follow.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5581>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 20 22:02:09 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 20 Jan 2021 22:02:09 +0000 (UTC)
Subject: [wp-meta] [10608]
 sites/trunk/api.wordpress.org/public_html/patterns/1.0/index.php: Pattern
 API: Sort alphabetically so that browsing is intuitive.
Message-ID: <20210120220209.542551B00221@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210120/a1c87cdf/attachment.html>

From noreply at wordpress.org  Wed Jan 20 22:02:15 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 20 Jan 2021 22:02:15 +0000 (UTC)
Subject: [wp-meta] [10609]
 sites/trunk/api.wordpress.org/public_html/patterns/1.0: Pattern API: Remove
 unnecessary fields and embedding for terms.
Message-ID: <20210120220215.6DC871B00221@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210120/4f863142/attachment.html>

From noreply at wordpress.org  Wed Jan 20 23:50:44 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 20 Jan 2021 23:50:44 +0000 (UTC)
Subject: [wp-meta] [10610]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/support-forums/inc/class-moderators.php:
 Support: Bump the replies on the new `All Replies` view to 50.
Message-ID: <20210120235044.0F06B1B00221@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210120/ea117c01/attachment-0001.html>

From noreply at wordpress.org  Thu Jan 21 00:38:10 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 21 Jan 2021 00:38:10 +0000 (UTC)
Subject: [wp-meta] [10611]
 sites/trunk/common/includes/slack/announce/config.php: Slack: Adjust
 `/here` permissions for meta and meta-learn
Message-ID: <20210121003810.682FD1B0042E@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210121/200f499d/attachment.html>

From noreply at wordpress.org  Thu Jan 21 00:44:18 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 21 Jan 2021 00:44:18 +0000 (UTC)
Subject: [wp-meta] [10612]
 sites/trunk/common/includes/slack/announce/config.php: Slack: Grant myself
 announce rights for #meta.
Message-ID: <20210121004418.B9B541B0042E@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210121/da28fa47/attachment.html>

From noreply at wordpress.org  Thu Jan 21 00:50:18 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 21 Jan 2021 00:50:18 +0000 (UTC)
Subject: [wp-meta] [10613] sites/trunk/common/includes/slack/announce:
 Slack: Announce: Inherit whitelisting from parent channels for
 sub-channels.
Message-ID: <20210121005018.A978C1B0042E@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210121/a2bd670f/attachment-0001.html>

From noreply at wordpress.org  Thu Jan 21 01:01:08 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 21 Jan 2021 01:01:08 +0000 (UTC)
Subject: [wp-meta] [10614]
 sites/trunk/common/includes/slack/announce/lib.php: Slack: Announce: Add
 some context to `get_whitelisted_channels_for_user()` to ensure that it
 will properly state the user has access to an "unknown" current channel if
 it has no whitelisted users,
 but the user is granted access via the inherited grants.
Message-ID: <20210121010108.E76581B0042E@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210121/28c17d26/attachment.html>

From noreply at wordpress.org  Thu Jan 21 03:21:06 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 21 Jan 2021 03:21:06 +0000 (UTC)
Subject: [wp-meta] [10615]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/support-forums/inc/class-user-notes.php:
 Support: Remove undefined variable reference that's not needed.
Message-ID: <20210121032106.3ABA01B0042E@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210121/5e2dae98/attachment.html>

From noreply at wordpress.org  Thu Jan 21 20:07:07 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 21 Jan 2021 20:07:07 +0000 (UTC)
Subject: [wp-meta] [10616]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/front-page.php:
 wporg-main: rm rolling stones from notable list, see dotorg:15522
Message-ID: <20210121200707.07FDF1B003C6@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210121/abead156/attachment.html>

From noreply at wordpress.org  Thu Jan 21 22:36:06 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 21 Jan 2021 22:36:06 +0000 (UTC)
Subject: [wp-meta] [10617]
 sites/trunk/api.wordpress.org/public_html/patterns/1.0/tests/test-index.php:
 Patterns API: Send e2e tests to loopback address to avoid redirects.
Message-ID: <20210121223606.8BA771B003C6@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210121/da3ffb3b/attachment.html>

From noreply at wordpress.org  Fri Jan 22 00:50:23 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 22 Jan 2021 00:50:23 +0000 (UTC)
Subject: [wp-meta] [10618]
 sites/trunk/jobs.wordpress.net/public_html/wp-content/themes/jobswp/functions.php:
 Jobs theme: Add a body class based on page slug.
Message-ID: <20210122005023.889691B00728@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210122/02559503/attachment.html>

From noreply at wordpress.org  Fri Jan 22 00:52:06 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 22 Jan 2021 00:52:06 +0000 (UTC)
Subject: [wp-meta] [10619]
 sites/trunk/jobs.wordpress.net/public_html/wp-content/themes/jobswp/style.css:
 Jobs theme: Rename selectors pertaining to FAQ-specific styles to use
 slug-based body class instead of ID-based.
Message-ID: <20210122005206.24A251B00728@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210122/c97042e9/attachment-0001.html>

From noreply at wordpress.org  Fri Jan 22 00:52:30 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 22 Jan 2021 00:52:30 +0000 (UTC)
Subject: [wp-meta] [10620]
 sites/trunk/jobs.wordpress.net/public_html/wp-content/themes/jobswp/style.css:
 Jobs theme: Add styling for additional markup used in FAQ.
Message-ID: <20210122005230.036221B00728@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210122/996b82dc/attachment.html>

From noreply at wordpress.org  Fri Jan 22 00:53:12 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 22 Jan 2021 00:53:12 +0000 (UTC)
Subject: [wp-meta] [10621]
 sites/trunk/jobs.wordpress.net/public_html/wp-content/themes/jobswp/wporg-footer.php:
 Jobs theme: Sync with wporg footer by adding "Learn" link.
Message-ID: <20210122005312.BC4331B00728@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210122/97c867e9/attachment.html>

From noreply at wordpress.org  Fri Jan 22 01:06:14 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 22 Jan 2021 01:06:14 +0000 (UTC)
Subject: [wp-meta] [10622]
 sites/trunk/jobs.wordpress.net/public_html/wp-content/themes/jobswp/style.css:
 Jobs theme: Fix alignment of search input form and search submit button
 relative to one another.
Message-ID: <20210122010614.49A031B00728@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210122/26cf7607/attachment.html>

From noreply at wordpress.org  Fri Jan 22 03:31:22 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 22 Jan 2021 03:31:22 -0000
Subject: [wp-meta] [Making WordPress.org] #5344: Delete stale,
 orphaned topic tags
In-Reply-To: <058.deee108539938b5d6762b863877d958d@wordpress.org>
References: <058.deee108539938b5d6762b863877d958d@wordpress.org>
Message-ID: <073.a09a5bd07b931923671ee1163f1dc7d0@wordpress.org>

#5344: Delete stale, orphaned topic tags
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  low             |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  seo             |
----------------------------+---------------------

Comment (by Clorith):

 Replying to [comment:14 dd32]:
 > Just noting that I cleaned up [attachment:"5344-limit-topic-
 creation.2.patch"] a little bit, and moved it to Performance
 Optimizations, so that this only affects the english support forums, and
 not all the localised support forums.

 Sounds reasonable for now (I seem to recall rosetta also wanting this at
 some point, but I think it makes sense to revisit that once the full on
 tag-upgrade-process is in place, since the curated tags are only really
 valuable once we've also implemented a way to more sanely choose tags,
 what I like to call phase 3 of this).

 For the next phase, I'm thinking removing all "undesirables" from the tag
 list makes sense as a first step. Doing so will reduce the total dataset
 we have to work with, and make it much easier to determine the overarching
 tag hierarchy needed to group the remaining tags.

 I'm thinking something initially manageable like removing tags that:
 - Have a numeric only slug (these are purely HTML entity tags from a quick
 check, and even if the tag was fully numeric any way, numbers alone give
 no context and as such hold no value)
 - Have fewer than 5 uses
 - Are literally the term `WordPress`, or `wp` (since it's fairly redundant
 to tag a topic as being about WordPress, on a WordPress support forum)

 I'll lean a bit on @jonoaldersonwp to sanity check that these sound like
 sensible criteria for a first set of removable tags.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5344#comment:18>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan 22 04:02:45 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 22 Jan 2021 04:02:45 -0000
Subject: [wp-meta] [Making WordPress.org] #5344: Delete stale,
 orphaned topic tags
In-Reply-To: <058.deee108539938b5d6762b863877d958d@wordpress.org>
References: <058.deee108539938b5d6762b863877d958d@wordpress.org>
Message-ID: <073.ccc001d2e51a56861d8aeddc48e421e5@wordpress.org>

#5344: Delete stale, orphaned topic tags
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  low             |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  seo             |
----------------------------+---------------------

Comment (by dd32):

 Those sound reasonable to me as a first set to remove.

 Replying to [comment:18 Clorith]:
 > I'm thinking something initially manageable like removing tags that:
 > - Have a numeric only slug (these are purely HTML entity tags from a
 quick check, and even if the tag was fully numeric any way, numbers alone
 give no context and as such hold no value)
 > - Have fewer than 5 uses
 Looking at the current list of tags, here's the counts:
 {{{
 Topics. Tags w/ that many topics.
 0        36,724
 1       492,877
 2        53,658
 3        19,359
 4        10,231
 5         6,288
 6         4,271
 7         3,233
 8         2,484
 9         1,945
 >10      22,257
 }}}

 Combining removing tags with less than 5 uses, and those whose slugs are
 just numeric, we'd be removing 613k tags leaving 40k tags behind.

 > - Are literally the term `WordPress`, or `wp` (since it's fairly
 redundant to tag a topic as being about WordPress, on a WordPress support
 forum)
 There's quite a few which match that too, but I suspect that list is going
 to be harder to come up with, although, looking at the most used tags,
 there's a number of obvious ones.
 Eg, top 20 topic-tags in use:
 {{{
 name            count
 woocommerce     43,541
 plugin          38,768
 wordpress       37,200
 error           36,563
 css             29,316
 theme           25,310
 menu            21,195
 php             18,578
 image           18,525
 header          18,308
 images          18,149
 post            16,522
 posts           16,094
 categories      15,393
 sidebar         15,298
 widget          14,654
 category        14,577
 Comments        13,920
 login           13,784
 multisite       13,680
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5344#comment:19>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan 22 08:41:09 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 22 Jan 2021 08:41:09 -0000
Subject: [wp-meta] [Making WordPress.org] #5344: Delete stale,
 orphaned topic tags
In-Reply-To: <058.deee108539938b5d6762b863877d958d@wordpress.org>
References: <058.deee108539938b5d6762b863877d958d@wordpress.org>
Message-ID: <073.58e66d9233b75bb562e4fa06dde9f1ad@wordpress.org>

#5344: Delete stale, orphaned topic tags
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  low             |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  seo             |
----------------------------+---------------------

Comment (by jonoaldersonwp):

 Oh, wow. That jump down to 40k would be ''amazing''.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5344#comment:20>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan 22 19:23:19 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 22 Jan 2021 19:23:19 +0000 (UTC)
Subject: [wp-meta] [10623] sites/trunk/wordpress.org/public_html/style:
 Style: Remove extra spacing under home showcase thumbnails.
Message-ID: <20210122192319.E99C51B00308@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210122/8d74666d/attachment.html>

From noreply at wordpress.org  Fri Jan 22 19:26:44 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 22 Jan 2021 19:26:44 +0000 (UTC)
Subject: [wp-meta] [10624]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub: wporg-main:
 Sync with static homepage.
Message-ID: <20210122192644.82ED01B00308@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210122/9d2ed4b7/attachment-0001.html>

From noreply at wordpress.org  Fri Jan 22 20:18:36 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 22 Jan 2021 20:18:36 +0000 (UTC)
Subject: [wp-meta] [10625]
 sites/trunk/api.wordpress.org/public_html/events/1.0/tests/test-index.php:
 Events: Add e2e test.
Message-ID: <20210122201836.A09631B00308@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210122/6db0e6b6/attachment.html>

From noreply at wordpress.org  Fri Jan 22 20:18:55 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 22 Jan 2021 20:18:55 +0000 (UTC)
Subject: [wp-meta] [10626]
 sites/trunk/api.wordpress.org/public_html/patterns/1.0/tests/test-index.php:
 Patterns API: Move `send_request()` to `phpunit-bootstrap.php`
Message-ID: <20210122201855.200D81B00308@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210122/85717ac7/attachment.html>

From noreply at wordpress.org  Fri Jan 22 23:00:58 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 22 Jan 2021 23:00:58 +0000 (UTC)
Subject: [wp-meta] [10627]
 sites/trunk/api.wordpress.org/public_html/patterns/1.0: Pattern API: Update
 slugs to match latest.
Message-ID: <20210122230058.2B38C1B00308@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210122/5c519781/attachment-0001.html>

From noreply at wordpress.org  Sat Jan 23 11:57:02 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 23 Jan 2021 11:57:02 -0000
Subject: [wp-meta] [Making WordPress.org] #5344: Delete stale,
 orphaned topic tags
In-Reply-To: <058.deee108539938b5d6762b863877d958d@wordpress.org>
References: <058.deee108539938b5d6762b863877d958d@wordpress.org>
Message-ID: <073.a284504d057639a5ac508c65743a37d9@wordpress.org>

#5344: Delete stale, orphaned topic tags
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  low             |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  seo             |
----------------------------+---------------------

Comment (by Clorith):

 That sounds great, I think we'll hold off on removing any of the other
 top-20 tag uses (with the exception of `wordpress` and `wp`), as some of
 them are plugin slugs.

 The reasoning is simple, some plugin authors follow their slugs to catch
 topics, and depending on how they do this following, they might get odd
 errors on their end, so I would like to announce the removal of these
 properly first, to ensure a good transition for those who may be using
 them.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5344#comment:21>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sun Jan 24 14:30:29 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sun, 24 Jan 2021 14:30:29 +0000 (UTC)
Subject: [wp-meta] [10628]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/wp-i18n-teams: WP
 I18N Teams: Split main plugin class out into separate include files.
Message-ID: <20210124143029.589E81B0056D@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210124/2c1b23bb/attachment-0001.html>

From noreply at wordpress.org  Sun Jan 24 14:30:33 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 24 Jan 2021 14:30:33 -0000
Subject: [wp-meta] [Making WordPress.org] #3423: Add new functionality
 for editor/locale requests
In-Reply-To: <052.2e4f3425f0456305278278f1c347b62e@wordpress.org>
References: <052.2e4f3425f0456305278278f1c347b62e@wordpress.org>
Message-ID: <067.7494d35fe235c460074b66fa1c9b6b90@wordpress.org>

#3423: Add new functionality for editor/locale requests
--------------------------------------+---------------------
 Reporter:  danieltj                  |       Owner:  (none)
     Type:  task                      |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  2nd-opinion               |
--------------------------------------+---------------------

Comment (by ocean90):

 In [changeset:"10628" 10628]:
 {{{
 #!CommitTicketReference repository="" revision="10628"
 WP I18N Teams: Split main plugin class out into separate include files.

 See #3423.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/3423#comment:22>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 25 04:50:48 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 25 Jan 2021 04:50:48 -0000
Subject: [wp-meta] [Making WordPress.org] #5582: Facilitate embedded videos
 in readme.md for plugin directory page
Message-ID: <055.af19bf2a78f6997330d14423f904f054@wordpress.org>

#5582: Facilitate embedded videos in readme.md for plugin directory page
------------------------------+--------------------
 Reporter:  westonruter       |      Owner:  (none)
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
------------------------------+--------------------
 I [https://johnblackbourn.com/readme-md-plugin-on-wordpress-org/
 discovered] recently that WordPress.org supports `readme.md` in addition
 to `readme.txt`. This is great since for a long time I've been using a
 [https://github.com/xwp/wp-dev-lib/blob/master/scripts/generate-markdown-
 readme script] to convert the `readme.txt` into a `readme.md` for the sake
 of GitHub, but then excluding it from WordPress.org.

 Now I can avoid doing this and just have the one `readme.md`.

 Nevertheless, there is one thing that doesn't port over so well, and that
 is video.  A plugin's readme may
 [https://make.wordpress.org/core/2010/02/20/plugins-can-now-include-
 videos-in-their-readme-txt-files/ include a video] via a bare oEmbed URL
 or shortcode and this is shown on the directory as a video embed. In the
 script I used, I'd take such a bare URL (for a YouTube video) in the
 `readme.txt` to have the poster image linked to the video. This would then
 have something acceptable for the markdown version on GitHub (which
 doesn't support video embeds) while also having the actual video embed on
 the plugin directory page.

 What I did in the script is take any instance of the following in the
 `readme.txt`:

 {{{
 [youtube https://www.youtube.com/watch?v=s52JNMT59s8]
 }}}

 And [https://github.com/xwp/wp-dev-
 lib/blob/a62ccca94f9995f294e12d500c45856adff81e34/scripts/class-wordpress-
 readme-parser.php#L96-L100 convert it] into the following in the
 `readme.md`:

 {{{
 [![Play video on
 YouTube](https://i1.ytimg.com/vi/s52JNMT59s8/hqdefault.jpg)](https://www.youtube.com/watch?v=s52JNMT59s8)
 }}}

 But now that I can use the `readme.md` as the source of truth, I'd like
 the opposite to be supported.

 My proposal: Extend
 `WordPressdotorg\Plugin_Directory\Markdown::transform()` to support
 matching any instance of linked poster images (to YouTube) and
 automatically transform them to bare URLs for oEmbed to kick in.

 So given a `readme.md` that contained:

 {{{
 [![Play video on
 YouTube](https://i1.ytimg.com/vi/s52JNMT59s8/hqdefault.jpg)](https://www.youtube.com/watch?v=s52JNMT59s8)
 }}}

 This would get transformed into:

 {{{
 https://www.youtube.com/watch?v=s52JNMT59s8
 }}}

 The same would go for other oEmbed providers in addition to YouTube.

 The benefit here is that the `readme.md` on GitHub would not need to have
 an unsightly bare URL and could instead have a linked video poster image.
 See the AMP plugin's `README.md` on GitHub for example:
 https://github.com/ampproject/amp-wp/blob/develop/README.md#description

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5582>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 25 08:47:28 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 25 Jan 2021 08:47:28 -0000
Subject: [wp-meta] [Making WordPress.org] #5582: Facilitate embedded
 videos in readme.md for plugin directory page
In-Reply-To: <055.af19bf2a78f6997330d14423f904f054@wordpress.org>
References: <055.af19bf2a78f6997330d14423f904f054@wordpress.org>
Message-ID: <070.8f3117701d5d5f94a0948ba9ed9ace5c@wordpress.org>

#5582: Facilitate embedded videos in readme.md for plugin directory page
------------------------------+---------------------
 Reporter:  westonruter       |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------

Comment (by Otto42):

 No, readme.md is supported instead of readme.txt, but the formatting for
 the two remains identical.

 You should still use a readme.txt for wordpress.org, and readme.md for
 GitHub, because of the differences in the formatting specifications.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5582#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 25 12:50:21 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 25 Jan 2021 12:50:21 -0000
Subject: [wp-meta] [Making WordPress.org] #4965: Nav menu icon size
 problem on mobiles device
In-Reply-To: <054.e16bbd2fb3e9227181fbaea36dec96a9@wordpress.org>
References: <054.e16bbd2fb3e9227181fbaea36dec96a9@wordpress.org>
Message-ID: <069.00b9596faaafe11a69209515eedcee4b@wordpress.org>

#4965: Nav menu icon size problem on mobiles device
---------------------------------------+---------------------
 Reporter:  fayazgabol                 |       Owner:  (none)
     Type:  defect                     |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Trac                       |  Resolution:
 Keywords:  has-screenshots has-patch  |
---------------------------------------+---------------------
Changes (by akabarikalpesh):

 * Attachment "4965.patch" added.

 menu icon css added. please check and let me know if any changes.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4965>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 25 12:50:50 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 25 Jan 2021 12:50:50 -0000
Subject: [wp-meta] [Making WordPress.org] #4965: Nav menu icon size
 problem on mobiles device
In-Reply-To: <054.e16bbd2fb3e9227181fbaea36dec96a9@wordpress.org>
References: <054.e16bbd2fb3e9227181fbaea36dec96a9@wordpress.org>
Message-ID: <069.b81d2d255e7b52d25f498e00e6458bee@wordpress.org>

#4965: Nav menu icon size problem on mobiles device
-----------------------------------------------------+---------------------
 Reporter:  fayazgabol                               |       Owner:  (none)
     Type:  defect                                   |      Status:  new
 Priority:  normal                                   |   Milestone:
Component:  Trac                                     |  Resolution:
 Keywords:  has-screenshots has-patch needs-testing  |
-----------------------------------------------------+---------------------
Changes (by akabarikalpesh):

 * keywords:  has-screenshots has-patch => has-screenshots has-patch needs-
     testing


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4965#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 25 17:29:37 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 25 Jan 2021 17:29:37 -0000
Subject: [wp-meta] [Making WordPress.org] #5583: Convert incorrect usage of
 "email" i Czech translations
Message-ID: <056.23671131b8fe50842f9f81b68024e588@wordpress.org>

#5583: Convert incorrect usage of "email" i Czech translations
--------------------------------------+--------------------
 Reporter:  tobifjellner              |      Owner:  (none)
     Type:  task                      |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:
--------------------------------------+--------------------
 The Meta team can help the #cs_CZ team to streamline the fixing of all
 strings that use the incorrect term "email" and replace is with "e-mail"
 (with hyphen).

 So this is the request more specifically:

 For all **CURRENT** strings where the translation to **cs_CZ** contains
 the sub-string "email" or "Email", generate a parallel, pending
 translation string where the matched sub-string is replaced with "e-mail"
 or "E-mail", respectively.

 After this, the locale team will manually check and approve/fix these
 strings.

 Any clarifications needed will be given by @kalich5 GTE for cs_CZ

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5583>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 25 17:30:55 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 25 Jan 2021 17:30:55 -0000
Subject: [wp-meta] [Making WordPress.org] #5583: Convert incorrect usage
 of "email" i Czech translations
In-Reply-To: <056.23671131b8fe50842f9f81b68024e588@wordpress.org>
References: <056.23671131b8fe50842f9f81b68024e588@wordpress.org>
Message-ID: <071.782bc3aae3253ff030cab56cbd5d83e5@wordpress.org>

#5583: Convert incorrect usage of "email" i Czech translations
--------------------------------------+---------------------
 Reporter:  tobifjellner              |       Owner:  (none)
     Type:  task                      |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------

Comment (by tobifjellner):

 If feasible, then the pending string could be generated as "translated by"
 the same user that is marked as translator for the current string.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5583#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 25 23:00:08 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 25 Jan 2021 23:00:08 -0000
Subject: [wp-meta] [Making WordPress.org] #5584: slack block users from Iran
Message-ID: <054.4ef1b5d000069f4d7e2257a208651fae@wordpress.org>

#5584: slack block users from Iran
-------------------------+--------------------
 Reporter:  alihendavi   |      Owner:  (none)
     Type:  defect       |     Status:  new
 Priority:  high         |  Milestone:
Component:  Slack & IRC  |   Keywords:
-------------------------+--------------------
 hello
 I'm from Iran and slack blocks users from our country. when I'm going to
 wordpress.slack.com  this site don't allow to me go to the WordPress
 space, and then send me this email
 **"Hi ali,
 You recently tried to sign in to Making WordPress, but it looks like your
 account for that workspace is deactivated. We're sorry about that!
 If you think this was a mistake, please contact a Workspace Administrator
 to reactivate the account.
 Cheers,
 The team at Slack"**

 please solve this problem

 with best regards

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5584>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jan 25 23:11:36 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 25 Jan 2021 23:11:36 +0000 (UTC)
Subject: [wp-meta] [10629]
 sites/trunk/api.wordpress.org/public_html/patterns/1.0/tests/test-index.php:
 Patterns API: Use latest `pattern-categories` endpoint name.
Message-ID: <20210125231136.800601B004D7@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210125/5fab1af4/attachment.html>

From noreply at wordpress.org  Tue Jan 26 00:02:30 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 26 Jan 2021 00:02:30 -0000
Subject: [wp-meta] [Making WordPress.org] #5584: slack block users from
 Iran
In-Reply-To: <054.4ef1b5d000069f4d7e2257a208651fae@wordpress.org>
References: <054.4ef1b5d000069f4d7e2257a208651fae@wordpress.org>
Message-ID: <069.11a8efbc117a2de0078fe413a2df0a57@wordpress.org>

#5584: slack block users from Iran
-------------------------+----------------------
 Reporter:  alihendavi   |       Owner:  (none)
     Type:  defect       |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Slack & IRC  |  Resolution:  wontfix
 Keywords:               |
-------------------------+----------------------
Changes (by Otto42):

 * priority:  high => normal
 * status:  new => closed
 * resolution:   => wontfix


Comment:

 Unfortunately, as long as we use Slack, there is nothing we can do about
 that.

 Nevertheless, this is an ongoing concern, but not one that can be solved
 here.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5584#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 26 00:14:15 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 26 Jan 2021 00:14:15 +0000 (UTC)
Subject: [wp-meta] [10630]
 sites/trunk/api.wordpress.org/public_html/patterns/1.0: Patterns API:
 Return all categories when passed `?categories`.
Message-ID: <20210126001415.D0AC11B0054B@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210126/d6f57f3b/attachment.html>

From noreply at wordpress.org  Tue Jan 26 04:48:12 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 26 Jan 2021 04:48:12 -0000
Subject: [wp-meta] [Making WordPress.org] #5582: Facilitate embedded
 videos in readme.md for plugin directory page
In-Reply-To: <055.af19bf2a78f6997330d14423f904f054@wordpress.org>
References: <055.af19bf2a78f6997330d14423f904f054@wordpress.org>
Message-ID: <070.36c0387bdd47aeec58e214a7e69ea661@wordpress.org>

#5582: Facilitate embedded videos in readme.md for plugin directory page
------------------------------+----------------------
 Reporter:  westonruter       |       Owner:  (none)
     Type:  enhancement       |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  wontfix
 Keywords:                    |
------------------------------+----------------------
Changes (by westonruter):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 OK, I've opted to generate the `readme.txt` from the `README.md` at build
 time, doing various transformations as needed for formatting.

 https://github.com/GoogleChromeLabs/pwa-wp/pull/400
 https://github.com/ampproject/amp-wp/pull/5815

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5582#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 26 06:40:26 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 26 Jan 2021 06:40:26 -0000
Subject: [wp-meta] [Making WordPress.org] #5585: The block editor handbook
 title links to developer.wordpress.org
Message-ID: <056.e3b729d887d9c0f5294310ac836551c1@wordpress.org>

#5585: The block editor handbook title links to developer.wordpress.org
--------------------------+--------------------
 Reporter:  justinahinon  |      Owner:  (none)
     Type:  defect        |     Status:  new
 Priority:  normal        |  Milestone:
Component:  Handbooks     |   Keywords:
--------------------------+--------------------
 When you are on this page https://developer.wordpress.org/block-editor, or
 on any of its sub-pages, a click on the page title "Block Editor Handbook"
 sends to developer.wordpress.org instead of developer.wordpress.org/block-
 editor.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5585>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 26 06:51:31 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 26 Jan 2021 06:51:31 +0000 (UTC)
Subject: [wp-meta] [10631]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/wp-i18n-teams/inc/locales.php:
 WP I18N Teams: Avoid a fatal error if subdomain or latest release of a
 locale is not yet available.
Message-ID: <20210126065131.B1F9B1B00210@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210126/e58dd4b5/attachment-0001.html>

From noreply at wordpress.org  Tue Jan 26 08:59:53 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 26 Jan 2021 08:59:53 -0000
Subject: [wp-meta] [Making WordPress.org] #5585: The block editor
 handbook title links to developer.wordpress.org
In-Reply-To: <056.e3b729d887d9c0f5294310ac836551c1@wordpress.org>
References: <056.e3b729d887d9c0f5294310ac836551c1@wordpress.org>
Message-ID: <071.69c327b1c33bb8ebc6de1b084cb7d6ba@wordpress.org>

#5585: The block editor handbook title links to developer.wordpress.org
---------------------------+---------------------
 Reporter:  justinahinon   |       Owner:  (none)
     Type:  defect         |      Status:  new
 Priority:  normal         |   Milestone:
Component:  Developer Hub  |  Resolution:
 Keywords:                 |
---------------------------+---------------------
Changes (by coffee2code):

 * component:  Handbooks => Developer Hub


Comment:

 Actually, I contend that the link in question ("Block Editor Handbook" in
 the blue site title bar) should be re-titled as "Developer Resources".

 That location on any other WordPress.org property is reserved for the
 site's name linked to the root of the site. The link for !DevHub handbooks
 already goes to the root of the site, but the text is changed to reflect
 the name of the current handbook. This is inconsistent with the rest of
 wordpress.org (the text should be the site's name) and is locally
 confusing (if it's the handbook name, one would expect the link to take
 you to the front page of the handbook).

 What I propose instead is that the handbooks on !DevHub adopt a handbook
 linking approach as used on a multi-handbook site such as Make/Community.
 As an example, see [https://make.wordpress.org/community/handbook
 /community-deputy/meetup-tracker/ this handbook page] in the
 Make/Community's Community Deputy Handbook. At the top of each handbook
 page, you'll see the handbook name with a link to the handbook's homepage.

 (Note that there are already 2 existing links to the handbook front page:
 the first link in the sidebar and the handbook's name in the breadcrumb
 navigation.)

 This change would need to apply to all sections of !DevHub and not just
 handbooks. (Currently the non-handbook sections '''''do''''' change the
 link to go to the root of their section instead of linking to the !DevHub
 homepage.)

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5585#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 26 15:51:30 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 26 Jan 2021 15:51:30 -0000
Subject: [wp-meta] [Making WordPress.org] #5582: Facilitate embedded
 videos in readme.md for plugin directory page
In-Reply-To: <055.af19bf2a78f6997330d14423f904f054@wordpress.org>
References: <055.af19bf2a78f6997330d14423f904f054@wordpress.org>
Message-ID: <070.662782771014678d1ac36a47577bb99f@wordpress.org>

#5582: Facilitate embedded videos in readme.md for plugin directory page
------------------------------+----------------------
 Reporter:  westonruter       |       Owner:  (none)
     Type:  enhancement       |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  wontfix
 Keywords:                    |
------------------------------+----------------------

Comment (by Otto42):

 Yeah, right now, limited markdown is supported (in either txt or md), but
 it's not quite the same as GitHub's markdown all the time. If at some
 point we decide to separate the two and use different types of markups for
 them, then this would make more sense then. But that's a bit more of a
 comprehensive thing to do.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5582#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 26 22:10:28 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 26 Jan 2021 22:10:28 -0000
Subject: [wp-meta] [Making WordPress.org] #5586: You attempted to access the
 "WordPress.org Profiles" dashboard,
 but you do not currently have privileges on this site. If you believe you
 should be able to access the "WordPress.org Profiles" dashboard,
 please contact your network administrator
Message-ID: <049.da7f57361a5af32b52a5cee399226119@wordpress.org>

#5586: You attempted to access the "WordPress.org Profiles" dashboard, but you do
not currently have privileges on this site. If you believe you should be
able to access the "WordPress.org Profiles" dashboard, please contact your
network administrator
----------------------+-----------------------------
 Reporter:  bebe7     |      Owner:  (none)
     Type:  defect    |     Status:  new
 Priority:  normal    |  Milestone:  Improved Search
Component:  Profiles  |   Keywords:
----------------------+-----------------------------
 i am unable to access my dashboared admin site as you can see, it is
 informing me that i do not currently have the privileges to do somaking it
 default to access everything in the website, i have tried everything to
 try and fix it but no luck.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5586>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 26 22:20:06 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 26 Jan 2021 22:20:06 -0000
Subject: [wp-meta] [Making WordPress.org] #5586: You attempted to access
 the "WordPress.org Profiles" dashboard,
 but you do not currently have privileges on this site. If you believe you
 should be able to access the "WordPress.org Profiles" dashboard,
 please contact your network administrator
In-Reply-To: <049.da7f57361a5af32b52a5cee399226119@wordpress.org>
References: <049.da7f57361a5af32b52a5cee399226119@wordpress.org>
Message-ID: <064.6229544419b31299b86f03441c78c0c3@wordpress.org>

#5586: You attempted to access the "WordPress.org Profiles" dashboard, but you do
not currently have privileges on this site. If you believe you should be
able to access the "WordPress.org Profiles" dashboard, please contact your
network administrator
----------------------+----------------------
 Reporter:  bebe7     |       Owner:  (none)
     Type:  defect    |      Status:  closed
 Priority:  normal    |   Milestone:
Component:  Profiles  |  Resolution:  invalid
 Keywords:            |
----------------------+----------------------
Changes (by Otto42):

 * status:  new => closed
 * resolution:   => invalid
 * milestone:  Improved Search =>


Comment:

 The "WordPress.org Profiles" site is our site at profiles.wordpress.org.
 You're getting that message because you do not have access to it. Nobody
 but the administrators of WordPress.org have that access.

 If you're looking to edit your profile on WordPress.org, you can go here:
 https://profiles.wordpress.org/bebe7/ and edit the profile directly.

 If you are trying to access your own site, you need to go to your site's
 /wp-admin page, not to ours. WordPress sites are not connected like that,
 we're not like Facebook. We don't host sites for other people, WordPress
 is free software that anybody can use to build their own site with. We
 only host our own sites here. So, you cannot access your site through
 WordPress.org, nor will we have the same username and passwords here.

 If you have any questions about this, you can also ask on the support
 forums at https://wordpress.org/support/forums/.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5586#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jan 26 23:48:43 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 26 Jan 2021 23:48:43 -0000
Subject: [wp-meta] [Making WordPress.org] #5581: Consolidating setup of
 local Dev environment documentation and testing instructions.
In-Reply-To: <055.c21c2a31ed9157aea19cbb810b655e9c@wordpress.org>
References: <055.c21c2a31ed9157aea19cbb810b655e9c@wordpress.org>
Message-ID: <070.929a865b10ac4dcfaad81ffd9f4b497f@wordpress.org>

#5581: Consolidating setup of local Dev environment documentation and testing
instructions.
-------------------------+---------------------
 Reporter:  paaljoachim  |       Owner:  (none)
     Type:  task         |      Status:  new
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by paaljoachim):

 To begin the road to consolidating a setup for core and Gutenberg I need
 to know how both are done. The following are instructions for core. I will
 below that add instructions for Gutenberg.

 I have with help from @hellofromtonya updated the testing instructions for
 setting up a local WP dev environment + testing trac tickets.

 Setting up a local Development Environment for WordPress core.

 1- Open Terminal.

 2- Install homebrew by pasting

 {{{
 /bin/bash -c "$(curl -fsSL
 https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"
 }}}

 You might be asked if you want to install the Xcode Command Line Tools.
 Confirm yes.

 3- Install Git by typing: brew install git

 4- Install Docker by downloading the app here:
 https://www.docker.com/products/docker-desktop
 Or in terminal install Docker by typing:
 {{{
 brew cask install docker
 }}}

 If that does not work type:
 {{{
 brew install cask docker
 }}}


 5- In terminal. Install Node by typing:
 {{{
 brew install node
 }}}


 6- Open the Docker app on your computer and ignore the welcome screen that
 tells you to create a container.

 7- Clone the Github repository. Go to https://github.com/WordPress
 /wordpress-develop
 Click the green button (Code) at the top of the repository.   Copy the
 HTTPS URL. https://github.com/WordPress/wordpress-develop.git
 In terminal type:
 {{{
 git clone https://github.com/WordPress/wordpress-develop.git
 }}}


 8- Go to the directory where you cloned the repo.
 Type: cd wordpress-develop to locate it.

 9- Now type these 4 commands.
  -A.
 {{{
 npm install
 }}}

  -B.
 {{{
 npm run build:dev
 }}}

  -C.
 {{{
 npm run env:start
 }}}

  -D.
 {{{
 npm run env:install
 }}}


 10. You should now be able to access the development version of WordPress
 at http://localhost:8889/.
 Login with using
 username: **admin**
 password: **password**

 Testing a trac ticket.

 An example trac ticket:
 https://core.trac.wordpress.org/ticket/43890

 Open terminal. Type:
 {{{
 npm run grunt patch:43890
 }}}

 The trac ticket number to be tested.
 After inserting the command an option will show up to where one can select
 which patch to test. With the up and down arrows on your keyboard select
 the newest patch.

 Login to your local WordPress site: http://localhost:8889/ with
 username: admin
 password: password

 Check the results of the patch.

 Uninstall

 1.Uninstall Homebrew.
 In terminal type:

 {{{
 /bin/bash -c "$(curl -fsSL
 https://raw.githubusercontent.com/Homebrew/install/master/uninstall.sh)"
 }}}

 Type y to confirm.
 Type your password.

 2.A
 Uninstall Docker.
 Open Docker and go to the Dashboard.
 Click the bug icon button seen in the top blue bar.
 Click the Uninstall button.
 Then drag the Docker app to your trash can.

 2.B
 Skip uninstalling Docker.
 (If you do not want to remove Docker. Then follow these steps.)
 Uninstall WordPress developer environment
 In terminal type:
 {{{
 npm run env:reset
 }}}

 This will uninstall the Docker image and all the virtual discs it creates.

 3.Delete wordpress-develop
 Open the user folder in the root the wordpress-develop folder is located.
 Select it and drag it to the trash can.

 One resource I used:
 https://github.com/Homebrew/install

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5581#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 27 01:15:50 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 27 Jan 2021 01:15:50 -0000
Subject: [wp-meta] [Making WordPress.org] #5587: Skip sanitization of code
 snippets in forum replies email notifications
Message-ID: <056.593124af908197f39202c53d67d75210@wordpress.org>

#5587: Skip sanitization of code snippets in forum replies email notifications
----------------------------+--------------------
 Reporter:  YordanSoares    |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+--------------------
 I replied to [https://wordpress.org/support/topic/contact-form-7-data-not-
 showing-data/#post-13884276/ this user] in the support forum, but she used
 the code that received in her inbox.

 I have noticed that when we use {{{<code>}}} tags to display raw code, the
 message arrive to inbox with the {{{<}}} and {{{<}}} characters converted
 into HTML entities.

 [[Image(https://i.imgur.com/yAs3GrB.png)]]
 ''Example of a code snippet in a forum reply...''

 The problem I see here is that if the user uses this code from the email
 instead the one in the forum reply, it will not work. As you can see in
 the below replies, she entered the forum through a video I recorded and
 realized that the code was different from what she received in the email
 notification.

 [[Image(https://i.imgur.com/5pO6Ev4.png)]]
 ''...code delivered to the user inbox''

 My proposal is to add an exception to the parsing performed to the
 messages before sending the mail so that it skip the sanitization in the
 code enclosed in {{{<code>}}} tags including, of course, the {{{<code>}}}
 tags in order to display as a code snippet in the mail message.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5587>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 27 01:40:31 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 27 Jan 2021 01:40:31 -0000
Subject: [wp-meta] [Making WordPress.org] #5583: Convert incorrect usage
 of "email" i Czech translations
In-Reply-To: <056.23671131b8fe50842f9f81b68024e588@wordpress.org>
References: <056.23671131b8fe50842f9f81b68024e588@wordpress.org>
Message-ID: <071.f09bfbf602031c143e43dc3ad68a4558@wordpress.org>

#5583: Convert incorrect usage of "email" i Czech translations
--------------------------------------+-----------------------
 Reporter:  tobifjellner              |       Owner:  dd32
     Type:  task                      |      Status:  accepted
 Priority:  low                       |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+-----------------------
Changes (by dd32):

 * owner:  (none) => dd32
 * priority:  normal => low
 * status:  new => accepted


Comment:

 This seems like a reasonable request, and I'll take a stab at it once I
 know what the actual level of work involved is.

 A quick overview would be to...
  - Find all currently active strings that contain `email` in `cs_CZ`
 locale in all projects (core, meta, plugins, themes)
  - Filter out translations which have a suggested variant that does NOT
 contain `email`
  - Suggest a new translation with case-matching `str_replace( email,
 e-mail ) & str_replace( Email, E-mail )` authored by the source
 translation string.


 Marking as low priority, but I'll probably get to this over the next week
 or so, tasks permitting, do ping me if by end of next week you've not
 heard back from me @tobifjellner

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5583#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 27 06:54:14 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 27 Jan 2021 06:54:14 -0000
Subject: [wp-meta] [Making WordPress.org] #5584: slack block users from
 Iran
In-Reply-To: <054.4ef1b5d000069f4d7e2257a208651fae@wordpress.org>
References: <054.4ef1b5d000069f4d7e2257a208651fae@wordpress.org>
Message-ID: <069.e1a67c21772542c616ccf775660d80dd@wordpress.org>

#5584: slack block users from Iran
-------------------------+----------------------
 Reporter:  alihendavi   |       Owner:  (none)
     Type:  defect       |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Slack & IRC  |  Resolution:  wontfix
 Keywords:               |
-------------------------+----------------------

Comment (by alihendavi):

 last year GitHub ban Iranian users from private repositories and now as
 you can see in this link, GitHub solves Iranian users Limitations.

  wordpress.slack.com's admin can request to solve this problem for Iranian
 users.
 WordPress is free and opens source all people around the world can use it
 freely.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5584#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 27 07:06:16 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 27 Jan 2021 07:06:16 -0000
Subject: [wp-meta] [Making WordPress.org] #5584: slack block users from
 Iran
In-Reply-To: <054.4ef1b5d000069f4d7e2257a208651fae@wordpress.org>
References: <054.4ef1b5d000069f4d7e2257a208651fae@wordpress.org>
Message-ID: <069.01a31118a7bbca2cc27010fc0acd8919@wordpress.org>

#5584: slack block users from Iran
-------------------------+----------------------
 Reporter:  alihendavi   |       Owner:  (none)
     Type:  defect       |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Slack & IRC  |  Resolution:  wontfix
 Keywords:               |
-------------------------+----------------------

Comment (by dd32):

 Hi @alihendavi,

 Replying to [comment:2 alihendavi]:
 > wordpress.slack.com's admin can request to solve this problem for
 Iranian users.

 Unfortunately, WordPress cannot influence Slacks commercial decisions and
 their legal obligations under their respective laws.

 As I'm sure you're aware, the US trade embargo's affect the ability for
 companies to export certain content and as a result Iranian IP addresses
 are blocked from the service. That, combined with Iranian laws also
 restricts the usage of VPNs to work around those IP limitations.

 As how GitHub [https://github.blog/2021-01-05-advancing-developer-freedom-
 github-is-fully-available-in-iran/ has secured a license] to maintain
 compliance with US law, Slack can opt to do the same, but WordPress cannot
 influence that decision. [https://slack.com/intl/en-au/help/requests/new
 You can reach out to Slack] to let them know about your want to use their
 software and encourage them to follow GitHubs lead to secure a license of
 their own.

 > WordPress is free and opens source all people around the world can use
 it freely.

 WordPress, as an open-source project, will remain to be available to all
 freely. Unfortunately due to our usage of Slack, you will be limited from
 being able to access our real-time communication platform at this point in
 time. This may change at a future date depending on Slacks decisions
 (Which are their own and not ours), trade embargo's, or if we were to move
 to another open platform entirely.

 Thank you for wanting to contribute to WordPress, I encourage you to
 continue to be involved through Trac and any other means accessible to
 you. I'm sorry our communication platform can't be included at this time.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5584#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 27 09:39:10 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 27 Jan 2021 09:39:10 -0000
Subject: [wp-meta] [Making WordPress.org] #5583: Convert incorrect usage
 of "email" i Czech translations
In-Reply-To: <056.23671131b8fe50842f9f81b68024e588@wordpress.org>
References: <056.23671131b8fe50842f9f81b68024e588@wordpress.org>
Message-ID: <071.602a07ed9ac64cee1616d670100ce021@wordpress.org>

#5583: Convert incorrect usage of "email" i Czech translations
--------------------------------------+-----------------------
 Reporter:  tobifjellner              |       Owner:  dd32
     Type:  task                      |      Status:  accepted
 Priority:  low                       |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+-----------------------

Comment (by kalich5):

 This is a translation ...

 emails -> e-maily
 Emails -> E-maily

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5583#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 27 10:55:07 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 27 Jan 2021 10:55:07 -0000
Subject: [wp-meta] [Making WordPress.org] #5588: Duplicate heading links on
 https://developer.wordpress.org/block-editor
Message-ID: <056.bc43d9efe6a3e709c98e500fba559e14@wordpress.org>

#5588: Duplicate heading links on https://developer.wordpress.org/block-editor
---------------------------+-----------------------------
 Reporter:  justinahinon   |      Owner:  (none)
     Type:  defect         |     Status:  new
 Priority:  normal         |  Milestone:
Component:  Developer Hub  |   Keywords:  has-screenshots
---------------------------+-----------------------------
 I've recently merged a PR
 (https://github.com/WordPress/gutenberg/pull/28142) to update the homepage
 of the block editor handbook https://developer.wordpress.org/block-editor.

 After that, some heading links on the page are duplicated (see
 screenshot).

 According to @sergeybiryukov, "It looks like the latter part is supposed
 to be a screen reader text, however the {{{.screen-reader-text}}} class is
 not loaded in the CSS.".

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5588>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 27 10:55:57 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 27 Jan 2021 10:55:57 -0000
Subject: [wp-meta] [Making WordPress.org] #5588: Duplicate heading links
 on https://developer.wordpress.org/block-editor
In-Reply-To: <056.bc43d9efe6a3e709c98e500fba559e14@wordpress.org>
References: <056.bc43d9efe6a3e709c98e500fba559e14@wordpress.org>
Message-ID: <071.85c21cf3788af63f0f11fcfc4bfa726c@wordpress.org>

#5588: Duplicate heading links on https://developer.wordpress.org/block-editor
-----------------------------+---------------------
 Reporter:  justinahinon     |       Owner:  (none)
     Type:  defect           |      Status:  new
 Priority:  normal           |   Milestone:
Component:  Developer Hub    |  Resolution:
 Keywords:  has-screenshots  |
-----------------------------+---------------------
Changes (by justinahinon):

 * Attachment "Screenshot_2021-01-27 Getting started Block Editor Handbook
 WordPress Developer Resources.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5588>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 27 11:50:39 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 27 Jan 2021 11:50:39 -0000
Subject: [wp-meta] [Making WordPress.org] #5589: Category archives pages :
 accessibility improvement (HTML)
Message-ID: <053.fe263a5235bccec7d49c445d0e75cab7@wordpress.org>

#5589: Category archives pages : accessibility improvement (HTML)
-------------------------+-----------------------
 Reporter:  Chaton666    |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:
Component:  HelpHub      |   Keywords:  has-patch
-------------------------+-----------------------
 This ticket is about **category archives pages** in helphub/support sites,
 for example : https://wordpress.org/support/category/getting-started/

 Accessibility of theses pages can be improved by moving links around
 `article` inside `h2` tag (title).

 Actual markup :

 {{{
 <a href="https://wordpress.org/support/article/users-your-profile-screen/"
 class="archive-block">
         <article id="post-10778661" class="post-10778661 helphub_article
 type-helphub_article status-publish hentry category-basic-usage category-
 getting-started category-how-to helphub_persona-maintainers
 helphub_experience-beginner">
                 <h2>Users Your Profile Screen</h2>
                 <p>Users → Your Profile The Your Profile Screen is
 accessible from both the main navigation menu under Users and by clicking
 on your name link […]</p>
         </article>
 </a>
 }}}


 New markup :

 {{{
 <div class="archive-block">
         <article id="post-10778661" class="post-10778661 helphub_article
 type-helphub_article status-publish hentry category-basic-usage category-
 getting-started category-how-to helphub_persona-maintainers
 helphub_experience-beginner">
                 <h2><a href="https://wordpress.org/support/article/users-
 your-profile-screen/" class="archive-block">Users Your Profile
 Screen</a></h2>
                 <p>Users → Your Profile The Your Profile Screen is
 accessible from both the main navigation menu under Users and by clicking
 on your name link […]</p>
         </article>
 </div>
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5589>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 27 11:51:39 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 27 Jan 2021 11:51:39 -0000
Subject: [wp-meta] [Making WordPress.org] #5589: Category archives pages
 : accessibility improvement (HTML)
In-Reply-To: <053.fe263a5235bccec7d49c445d0e75cab7@wordpress.org>
References: <053.fe263a5235bccec7d49c445d0e75cab7@wordpress.org>
Message-ID: <068.0b7e9ffb98a7a170507b2a9c85012e16@wordpress.org>

#5589: Category archives pages : accessibility improvement (HTML)
-------------------------+---------------------
 Reporter:  Chaton666    |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  HelpHub      |  Resolution:
 Keywords:  has-patch    |
-------------------------+---------------------
Changes (by Chaton666):

 * Attachment "5589.diff" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5589>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 27 16:16:36 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 27 Jan 2021 16:16:36 -0000
Subject: [wp-meta] [Making WordPress.org] #5586: You attempted to access
 the "WordPress.org Profiles" dashboard,
 but you do not currently have privileges on this site. If you believe you
 should be able to access the "WordPress.org Profiles" dashboard,
 please contact your network administrator
In-Reply-To: <049.da7f57361a5af32b52a5cee399226119@wordpress.org>
References: <049.da7f57361a5af32b52a5cee399226119@wordpress.org>
Message-ID: <064.5cb6effcdd5a7acd0dc6ed7f5a4cdaea@wordpress.org>

#5586: You attempted to access the "WordPress.org Profiles" dashboard, but you do
not currently have privileges on this site. If you believe you should be
able to access the "WordPress.org Profiles" dashboard, please contact your
network administrator
----------------------+----------------------
 Reporter:  bebe7     |       Owner:  (none)
     Type:  defect    |      Status:  closed
 Priority:  normal    |   Milestone:
Component:  Profiles  |  Resolution:  invalid
 Keywords:            |
----------------------+----------------------

Comment (by bebe7):

 hello thanks alot for the reply. so basically i can not use this site to
 connect to facebook page domain as a register? Replying to [comment:1
 Otto42]:
 > The "WordPress.org Profiles" site is our site at profiles.wordpress.org.
 You're getting that message because you do not have access to it. Nobody
 but the administrators of WordPress.org have that access.
 >
 > If you're looking to edit your profile on WordPress.org, you can go
 here: https://profiles.wordpress.org/bebe7/ and edit the profile directly.
 >
 > If you are trying to access your own site, you need to go to your site's
 /wp-admin page, not to ours. WordPress sites are not connected like that,
 we're not like Facebook. We don't host sites for other people, WordPress
 is free software that anybody can use to build their own site with. We
 only host our own sites here. So, you cannot access your site through
 WordPress.org, nor will we have the same username and passwords here.
 >
 > If you have any questions about this, you can also ask on the support
 forums at https://wordpress.org/support/forums/.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5586#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 27 16:19:04 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 27 Jan 2021 16:19:04 -0000
Subject: [wp-meta] [Making WordPress.org] #5586: You attempted to access
 the "WordPress.org Profiles" dashboard,
 but you do not currently have privileges on this site. If you believe you
 should be able to access the "WordPress.org Profiles" dashboard,
 please contact your network administrator
In-Reply-To: <049.da7f57361a5af32b52a5cee399226119@wordpress.org>
References: <049.da7f57361a5af32b52a5cee399226119@wordpress.org>
Message-ID: <064.51a13a44c691e472b3e64301837f1e34@wordpress.org>

#5586: You attempted to access the "WordPress.org Profiles" dashboard, but you do
not currently have privileges on this site. If you believe you should be
able to access the "WordPress.org Profiles" dashboard, please contact your
network administrator
----------------------+----------------------
 Reporter:  bebe7     |       Owner:  (none)
     Type:  defect    |      Status:  closed
 Priority:  normal    |   Milestone:
Component:  Profiles  |  Resolution:  invalid
 Keywords:            |
----------------------+----------------------

Comment (by bebe7):

 thank you lots for the reply.
 what i am trying to actually do is link
 wordpress to facebook page creator studio
 is that something thats not possible, that i need
 to recreate my own WordPresss?

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5586#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jan 27 17:30:41 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 27 Jan 2021 17:30:41 +0000 (UTC)
Subject: [wp-meta] [10632]
 sites/trunk/common/includes/slack/announce/config.php: Slack: Add chaion07
 and hedgefield to #design, rm mapk, michaelarestad, and noahshrader.
Message-ID: <20210127173041.592161B00297@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210127/e1e41744/attachment.html>

From noreply at wordpress.org  Wed Jan 27 21:38:44 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 27 Jan 2021 21:38:44 -0000
Subject: [wp-meta] [Making WordPress.org] #5581: Consolidating setup of
 local Dev environment documentation and testing instructions.
In-Reply-To: <055.c21c2a31ed9157aea19cbb810b655e9c@wordpress.org>
References: <055.c21c2a31ed9157aea19cbb810b655e9c@wordpress.org>
Message-ID: <070.55963e21cd8b09cf779259f6d053046f@wordpress.org>

#5581: Consolidating setup of local Dev environment documentation and testing
instructions.
-------------------------+---------------------
 Reporter:  paaljoachim  |       Owner:  (none)
     Type:  task         |      Status:  new
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by Clorith):

 In the case of a Windows install, you would replace steps 1 through 6 with
 the following:

 1: Install Git from https://git-scm.com/download/win
 2: Download Docker Desktop from https://www.docker.com/get-started
 3: Download and install Node.js and NPM from https://nodejs.org/en/ (they
 are bundled together in one installer)

 4: Restart your computer after completing step 3 to ensure system settings
 are correctly applied.

 Docker automatically starts with your machine once installed on Windows
 unless you configure it to do otherwise.

 Removing them afterwards should be a familiar experience to Windows users,
 as you would visit your computers "uninstall programs" screen and just
 select them there and they will be gone.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5581#comment:8>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 28 00:41:42 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 28 Jan 2021 00:41:42 -0000
Subject: [wp-meta] [Making WordPress.org] #5348: Redirect legacy mobile
 subdomain forums into new support forums
In-Reply-To: <058.5db0e012502346a93e707ea7b900e310@wordpress.org>
References: <058.5db0e012502346a93e707ea7b900e310@wordpress.org>
Message-ID: <073.8c803e50265af773730a3c9e4dad0421@wordpress.org>

#5348: Redirect legacy mobile subdomain forums into new support forums
----------------------------+-----------------------
 Reporter:  jonoaldersonwp  |       Owner:  dd32
     Type:  defect          |      Status:  accepted
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+-----------------------
Changes (by dd32):

 * owner:  (none) => dd32
 * status:  new => accepted


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5348#comment:8>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 28 00:42:09 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 28 Jan 2021 00:42:09 -0000
Subject: [wp-meta] [Making WordPress.org] #4398: 'Forums' subdomains
 should have friendly error templates
In-Reply-To: <058.8ed6a63a63e360f98343036d57874c1a@wordpress.org>
References: <058.8ed6a63a63e360f98343036d57874c1a@wordpress.org>
Message-ID: <073.66531099f5913e59db679ae6db9460d9@wordpress.org>

#4398: 'Forums' subdomains should have friendly error templates
----------------------------------+---------------------
 Reporter:  jonoaldersonwp        |       Owner:  (none)
     Type:  defect                |      Status:  new
 Priority:  lowest                |   Milestone:
Component:  International Forums  |  Resolution:
 Keywords:  seo analytics         |
----------------------------------+---------------------

Comment (by dd32):

 This ticket will be superseded by #5348. Leaving this ticket open for
 tracking purposes of this issue until that's done.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4398#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 28 00:42:13 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 28 Jan 2021 00:42:13 -0000
Subject: [wp-meta] [Making WordPress.org] #4397: 'Forums' subdomains
 should include Google Tag Manager
In-Reply-To: <058.0efa3fc1d21d81ecb87e31f2a585be3d@wordpress.org>
References: <058.0efa3fc1d21d81ecb87e31f2a585be3d@wordpress.org>
Message-ID: <073.153eeb8e4f0f0eebcb2bb11fd9c822a4@wordpress.org>

#4397: 'Forums' subdomains should include Google Tag Manager
----------------------------------+---------------------
 Reporter:  jonoaldersonwp        |       Owner:  (none)
     Type:  defect                |      Status:  new
 Priority:  lowest                |   Milestone:
Component:  International Forums  |  Resolution:
 Keywords:  analytics             |
----------------------------------+---------------------

Comment (by dd32):

 This ticket will be superseded by #5348. Leaving this ticket open for
 tracking purposes of this issue until that's done.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4397#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 28 21:44:01 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 28 Jan 2021 21:44:01 -0000
Subject: [wp-meta] [Making WordPress.org] #5590: Improve messaging on
 login.wordpress.org
Message-ID: <050.efc0212856e07934c51c89df856251a5@wordpress.org>

#5590: Improve messaging on login.wordpress.org
------------------------------------+--------------------
 Reporter:  Otto42                  |      Owner:  (none)
     Type:  task                    |     Status:  new
 Priority:  normal                  |  Milestone:
Component:  Login & Authentication  |   Keywords:
------------------------------------+--------------------
 We've been getting a lot of very specific kinds of emails to the forum-
 password-resets email lately. Not sure why the uptick in these
 specifically, but after asking people how they got to us, we are
 reasonably sure how they got there.

 Case:
 - User goes to their wp-admin on their own site.
 - Some error happens (various causes), causing the error message:
 "There has been a critical error on this website. Please check your site
 admin email inbox for instructions.
 Learn more about debugging in WordPress."
 - The learn more line is linked to https://wordpress.org/support/article
 /debugging-in-wordpress/
 - Now, this is a user, so they get there, and there's no info there that
 really helps them out (the content there can be debated elsewhere), but
 there are Login links in the admin bar.
 - That takes them to https://login.wordpress.org/
 - They try to login using admin/whatever or some other username. The admin
 name has been a bit common in these cases.

 Result: "ERROR: Your account has been disabled. Please contact forum-
 password-resets at wordpress.org for more details."

 Which leads them to emailing us. We then have to explain the difference
 between their site and w.org, why their username won't work, how to
 register, how to get to the support forums to ask their question, etc.
 Basically, they're confused as heck and we're getting the email about it.

 So, there's a few ideas, but one of them is to improve the messaging on
 the login page.

 1. On the login page, we have the WordPress.org logo instead of the normal
 one, but no messaging indicating where they are. Idea: Add in some text
 right there, before they login.

 "Log in to your WordPress.org account to contribute to WordPress, get help
 in the support forum, or rate and review themes and plugins." or something
 like that. Tell them where they are and what they are currently doing.

 2. On the error message: detect common username cases like "admin" and
 provide better info. Yes, the "admin" account is blocked on org and will
 be forever, so nobody will ever use it legitimately, so they are obviously
 in the wrong place and should be told so and where to properly go to most
 likely help them.

 3. Similar for username does not exist cases. Different messaging perhaps,
 tell them to try their email address instead or something.

 The goal being to try to prevent confused people emailing us and even
 including their admin passwords. Which yes, happens a lot. If we can
 recognize what they're doing wrong, then provide them with better info
 instead of just the password reset email address.

 While we're at it, improve the existing messages as well. This may need
 some design work for how to best display this information on the page,
 since the current space is too small, really. Mobile is tricky as well.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5590>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jan 28 21:47:55 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 28 Jan 2021 21:47:55 -0000
Subject: [wp-meta] [Making WordPress.org] #5590: Improve messaging on
 login.wordpress.org
In-Reply-To: <050.efc0212856e07934c51c89df856251a5@wordpress.org>
References: <050.efc0212856e07934c51c89df856251a5@wordpress.org>
Message-ID: <065.ed7da2bc21809ea1549778a6765b798d@wordpress.org>

#5590: Improve messaging on login.wordpress.org
------------------------------------+---------------------
 Reporter:  Otto42                  |       Owner:  (none)
     Type:  task                    |      Status:  new
 Priority:  normal                  |   Milestone:
Component:  Login & Authentication  |  Resolution:
 Keywords:                          |
------------------------------------+---------------------

Comment (by Otto42):

 Related: https://core.trac.wordpress.org/ticket/52392

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5590#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan 29 00:16:05 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 29 Jan 2021 00:16:05 -0000
Subject: [wp-meta] [Making WordPress.org] #5591: Plugin Directory: Clarified
 some trademark issues and adding more things
Message-ID: <051.f44dd0fdfb6a3bc408e281cde1ebc6a3@wordpress.org>

#5591: Plugin Directory: Clarified some trademark issues and adding more things
------------------------------+-----------------------
 Reporter:  Ipstenu           |      Owner:  Ipstenu
     Type:  defect            |     Status:  assigned
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:  has-patch
------------------------------+-----------------------
 Talked to a couple trademark owners about things they'd like to see
 prevented going forward.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5591>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan 29 00:16:58 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 29 Jan 2021 00:16:58 -0000
Subject: [wp-meta] [Making WordPress.org] #5591: Plugin Directory:
 Clarified some trademark issues and adding more things
In-Reply-To: <051.f44dd0fdfb6a3bc408e281cde1ebc6a3@wordpress.org>
References: <051.f44dd0fdfb6a3bc408e281cde1ebc6a3@wordpress.org>
Message-ID: <066.c1a58e7f56a215c2e32e419cc3ed4d9d@wordpress.org>

#5591: Plugin Directory: Clarified some trademark issues and adding more things
------------------------------+-----------------------
 Reporter:  Ipstenu           |       Owner:  Ipstenu
     Type:  defect            |      Status:  assigned
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  has-patch         |
------------------------------+-----------------------
Changes (by Ipstenu):

 * Attachment "5591.diff" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5591>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jan 29 00:19:19 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 29 Jan 2021 00:19:19 +0000 (UTC)
Subject: [wp-meta] [10633]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/shortcodes/class-upload-handler.php:
 Plugin Directory: Trademarks
Message-ID: <20210129001919.D79861B004B7@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210129/6a49c22d/attachment.html>

From noreply at wordpress.org  Fri Jan 29 00:19:24 2021
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 29 Jan 2021 00:19:24 -0000
Subject: [wp-meta] [Making WordPress.org] #5591: Plugin Directory:
 Clarified some trademark issues and adding more things
In-Reply-To: <051.f44dd0fdfb6a3bc408e281cde1ebc6a3@wordpress.org>
References: <051.f44dd0fdfb6a3bc408e281cde1ebc6a3@wordpress.org>
Message-ID: <066.6667e154b3a08da4be2d2705fef4bed3@wordpress.org>

#5591: Plugin Directory: Clarified some trademark issues and adding more things
------------------------------+----------------------
 Reporter:  Ipstenu           |       Owner:  Ipstenu
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:  has-patch         |
------------------------------+----------------------
Changes (by Ipstenu):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"10633" 10633]:
 {{{
 #!CommitTicketReference repository="" revision="10633"
 Plugin Directory: Trademarks

 Adding in some more things to block based on use and trademarks.

 Don't want to break large plugins, or small ones, if we can.

 Fixes #5591
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5591#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sat Jan 30 02:19:04 2021
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat, 30 Jan 2021 02:19:04 +0000 (UTC)
Subject: [wp-meta] [10634]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-learn-2020/js/filters.js:
 WordPress.org Learn: Sync with GitHub
Message-ID: <20210130021904.D23721B004D7@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20210130/fb8beb8f/attachment.html>