tags on translate.wordpress.org In-Reply-To: <049.f852fdb0ce284a9d405c46451e66a27e@wordpress.org> References: <049.f852fdb0ce284a9d405c46451e66a27e@wordpress.org> Message-ID: <064.4edee0969df53e0894b638143a95afa5@wordpress.org> #1280: <title> tags on translate.wordpress.org --------------------------------------+---------------------- Reporter: ramiy | Owner: Type: defect | Status: closed Priority: lowest | Milestone: Component: Translate Site & Plugins | Resolution: wontfix Keywords: has-patch | --------------------------------------+---------------------- Changes (by ocean90): * status: new => closed * resolution: => wontfix Comment: This needs to be improved in GlotPress directly, closing as wontfix. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1280#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sun May 14 17:12:54 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sun, 14 May 2017 17:12:54 -0000 Subject: [wp-meta] [Making WordPress.org] #2826: Download failed, not found error when plugin update out of sync Message-ID: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> #2826: Download failed, not found error when plugin update out of sync ------------------------------+----------------- Reporter: brianhogg | Owner: Type: defect | Status: new Priority: high | Milestone: Component: Plugin Directory | Keywords: ------------------------------+----------------- After 27 hours the wordpress.org listing still doesn't show the latest update. This is fine and can happen when the servers are overloaded. However, WordPress sites with the plugin are showing that an update is available. The new update details do not appear when "view version details" is clicked, and trying to update results in "Update Failed: Download failed. Not Found" If the update cannot be downloaded, it should not be shown in WordPress sites. 'Update available' should be the last thing to be updated after the zip has been generated. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2826> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sun May 14 19:11:09 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sun, 14 May 2017 19:11:09 -0000 Subject: [wp-meta] [Making WordPress.org] #2826: Download failed, not found error when plugin update out of sync In-Reply-To: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> References: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> Message-ID: <068.1293e7d2084396855887c215dbe8a461@wordpress.org> #2826: Download failed, not found error when plugin update out of sync ------------------------------+------------------ Reporter: brianhogg | Owner: Type: defect | Status: new Priority: high | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------ Comment (by pigeonhut): Same happening for me across 2 plugins updated yesterday and today, have also had clients opening support tickets for it -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2826#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sun May 14 19:53:38 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sun, 14 May 2017 19:53:38 -0000 Subject: [wp-meta] [Making WordPress.org] #2826: Plugin Directory: Data not syncing/updating properly from SVN commits (was: Download failed, not found error when plugin update out of sync) In-Reply-To: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> References: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> Message-ID: <068.48569ce6f2338ac85c4847021f0657b4@wordpress.org> #2826: Plugin Directory: Data not syncing/updating properly from SVN commits ------------------------------+------------------ Reporter: brianhogg | Owner: Type: defect | Status: new Priority: highest omg bbq | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------ Changes (by Ipstenu): * priority: high => highest omg bbq Comment: We're doing a mass import to try and catch everyone, but this is going to take a while. I'm leaving this open so people can report more issues here, as it's basically ALL related to the sync jobs that run after you commit code to SVN. They're not behaving. Server team is looking, but it's Sunday :/ Issues you MAY be experiencing: * Version numbers not updating * Versions updating, but downloads failing * Downloads failing for SOME people In all cases, PLEASE DO NOT SUBMIT MULTIPLE UPDATES. You probably didn't do anything wrong, so just give it a while :/ It will work out but it's going to be slow until we figure out what broke. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2826#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sun May 14 21:23:41 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Sun, 14 May 2017 21:23:41 +0000 (UTC) Subject: [wp-meta] [5488] sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory: Plugin Directory: Replace `shell_exec()`/`system() ` calls with `exec()`. Message-ID: <20170514212341.D00A110803A7@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170514/5d36132b/attachment-0001.html> From noreply at wordpress.org Mon May 15 12:25:46 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 15 May 2017 12:25:46 -0000 Subject: [wp-meta] [Making WordPress.org] #2699: Add a new role to the forums: plugin/theme support In-Reply-To: <053.e04c8d0168f06e230413f4c13e10a319@wordpress.org> References: <053.e04c8d0168f06e230413f4c13e10a319@wordpress.org> Message-ID: <068.e5b69c72aa59472b96f54d5d0427b600@wordpress.org> #2699: Add a new role to the forums: plugin/theme support ----------------------------+------------------ Reporter: TacoVerdo | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Comment (by wfasa): I wanted to pitch in here and argue for the exact same thing but for a different reason. While I agree with all of the above, I think adding a support role could also increase security. If an account with commit privileges was compromised it could cause a lot of trouble for the plugin authors, plugin users and potentially also for wordpress.org staff (helping authors clean up the mess). Users who only work the forums providing support do not need commit privileges. So for security reasons, it makes sense to limit commit privileges to only those who actually need it. I'm therefore very much in favor of a separate support role that 1. Allows thread resolve but not code commit 2. Is not subject to spam filtering/rate limiting 3. Shows up with a "support" tag in the forums Thanks to @ocean90 for showing me this thread. And re:@kraftbj comment above, in Wordfence 6.3.5 we made a slight modification so readme.txt files will now only be flagged in scan if "High sensitivity" scan option is enabled. You may still see those warnings, but it shouldn't be as often. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2699#comment:26> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Mon May 15 17:25:29 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 15 May 2017 17:25:29 -0000 Subject: [wp-meta] [Making WordPress.org] #2818: WordCamp: Add the new theme In-Reply-To: <051.55c628fc3ed7cd8bb5cf3c923f6e7f30@wordpress.org> References: <051.55c628fc3ed7cd8bb5cf3c923f6e7f30@wordpress.org> Message-ID: <066.d1697e2daaa67543e4980377c342e22c@wordpress.org> #2818: WordCamp: Add the new theme -------------------------------------+----------------------- Reporter: Kau-Boy | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: has-patch | -------------------------------------+----------------------- Changes (by iandunn): * owner: => iandunn * status: new => accepted -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2818#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Mon May 15 18:49:26 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 15 May 2017 18:49:26 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.b35d0dd720d42e6a66b174a255b3437d@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): Replying to [comment:12 barry]: > 1) The ip2location data on WP.org is very very old. > 2) WP.org doesn't have a subscription/license to use the data > 3) I don't think there is any legitimate use case to pass an ip in the query string > 4) The query performance is very poor and probably won't scale to the volume that we need > 5) We need a way to keep the information always current if we are going to use it !#1, !#2, and !#5 are all easy to solve. == !#3 (EULA) == On a technical level, it's easy to switch the client to request the data directly from api.w.org instead of proxying through their WP site. For anyone who's concerned about privacy with that architecture, we can release a plugin that will disable the Events section of the Dashboard widget entirely. We could replace it with a simple link to [https://make.wordpress.org/community/events/ the Events page on make/Community]. Does anyone think that would not be enough to mitigate privacy concerns? == !#4 (performance) == I'm going to start digging into this and looking for ways to optimize. If you can say which queries you're concerned the most about, that would be helpful. Almost all of the queries are there to support extra functionality and edge cases. Worst case scenario, the queries in the following functions can all be disabled without preventing the majority of users from successfully retrieving events: `guess_location_from_ip()`, `guess_location_from_geonames_fallback()`, `get_valid_country_codes()`, `get_country_from_name()`, and `get_city_from_coordinates()` That can be done at-will on the API side without breaking the client in Core. We could even do it automatically during traffic spikes if we have some kind of signal from monitoring agents to check. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:15> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Mon May 15 20:51:22 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 15 May 2017 20:51:22 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.9fa913a0ede069c534d107582ab56b22@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by barry): I have been thinking about the EULA a bit, I think if we remove the actual passed IP geolocation data from the response and just return the events data it will be fine. We would then use the client IP geolocation internally, in "business logic" to figure out the closest events and return them. We still need to work on the other issues, but they are technical and thus easier to fix. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:16> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Mon May 15 22:03:37 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 15 May 2017 22:03:37 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.342e18f97feb29af0714cd331fc70958@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): That sounds like a good idea to me. I think the detailed steps look like this: 1. The initial request. The client doesn't have a location saved at this point. 1. Client requests events near `{ip address}` 1. API returns the `events` object like it does today, but no `location` object 1. Client parses the city name from first event (e.g. "Seattle"), and saves that as the location 1. The second request. The client has a city name saved at this point. 1. The client requests events near `{city name}`, just like it does today when a user manually types in a location 1. The API matches the city name to lat/long coordinates using the Creative Commons data from geonames.org 1. The API returns the `events` object, and a `location` object, just like it does today. 1. The client saves the full `location` object as its location 1. All future requests. The client has a saved `lat` and `long` at this time 1. These would be exactly the same as they are today. So, the client would have to make 2 requests instead of 1, but it would eventually get the same behavior as we have today. The client could do step !#2 asynchronously after the events received in step !#1 have been displayed, in order to make things a little smoother. All of the above only applies if the user hasn't manually entered a location. If they enter a location manually, then we skip step !#1, and go straight to !#2. @barry, does that sound right to you? If so, I'll get started on the necessary changes. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:17> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Mon May 15 22:13:18 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 15 May 2017 22:13:18 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.b5951399aa67463bd1e17167a91cd065@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): To clarify, are you thinking we'd remove the IP from the client's request and just use `REMOTE_ADDR` on the API side, or would the client still be able to specify an arbitrary IP? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:18> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Mon May 15 22:28:42 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 15 May 2017 22:28:42 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.f21551f0046d02d477f8306293439e26@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by barry): Replying to [comment:18 iandunn]: > To clarify, are you thinking we'd remove the IP from the client's request and just use `REMOTE_ADDR` on the API side, or would the client still be able to specify an arbitrary IP? Clients can specify an arbitrary IP. I was initially concerned about the privacy implications of the clients connecting directly to the .org API which would provide their full IP and not the truncated version that the current proxy approach uses. I thought this would be the only place that a .org site sends the client IP to WordPress.org (as opposed to the server IP which is sent in many places). However, I then remembered that we use the W.org CDN for serving emoji in core, so I am not sure if it's a huge problem. I'm ok with any approach that satisfies the "business requirements" of this widget and doesn't violate the EULA for the data source(s) we use. The rest of the stuff like performance and scaling we can figure out pretty easily. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:19> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Mon May 15 22:30:43 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 15 May 2017 22:30:43 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.5e4167968d527760754f3c17c2302766@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by barry): Oh, and I forgot, if we send arbitrary IPs we might need IPv6 support which I haven't looked at yet. If the privacy concerns aren't an issue, having the client connect directly to the API endpoint might be the cleaner implementation. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:20> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 02:52:55 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 02:52:55 -0000 Subject: [wp-meta] [Making WordPress.org] #2642: Better boosting for phrase matches (or add support for the user to specify a phrase) In-Reply-To: <051.6ac0b0ad0bb1fc49ee7e4ab29ad2ae98@wordpress.org> References: <051.6ac0b0ad0bb1fc49ee7e4ab29ad2ae98@wordpress.org> Message-ID: <066.1ca11310d63d1ec95b24747c90245fdc@wordpress.org> #2642: Better boosting for phrase matches (or add support for the user to specify a phrase) ------------------------------+------------------------------------------- Reporter: gibrown | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by gsexton): I'm seeing cases where search relevancy is overwhelmed by large numbers of downloads. For example, if you search for the single word "calendar", JetPack is listed in the results of page 1. I looked at the readme.txt file and found that it contains that keyword exactly one time. Evidently, it's massive installed base overwhelms many plugins that from a straight textual analysis are vastly more relevant. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2642#comment:27> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 13:21:30 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 13:21:30 -0000 Subject: [wp-meta] [Making WordPress.org] #2827: Change size font Message-ID: <055.fc679e415e8f94ab91cfe1260c56176e@wordpress.org> #2827: Change size font ---------------------------+----------------------------- Reporter: jommartinez | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Developer Hub | Keywords: has-screenshots ---------------------------+----------------------------- I think you could reduce the text size a bit so it would fit into a single line. In some low resolutions only the symbol of the arrow and it looks bad ...: S url : https://developer.wordpress.org/ [[Image(http://i65.tinypic.com/kda2bd.png)]] -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2827> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 13:22:35 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 13:22:35 -0000 Subject: [wp-meta] [Making WordPress.org] #2827: Change size font In-Reply-To: <055.fc679e415e8f94ab91cfe1260c56176e@wordpress.org> References: <055.fc679e415e8f94ab91cfe1260c56176e@wordpress.org> Message-ID: <070.c235bb9cb283a13b20e5cd20a087b610@wordpress.org> #2827: Change size font ---------------------------+------------------ Reporter: jommartinez | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Developer Hub | Resolution: Keywords: | ---------------------------+------------------ Changes (by jommartinez): * keywords: has-screenshots => -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2827#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 13:28:54 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 13:28:54 -0000 Subject: [wp-meta] [Making WordPress.org] #2826: Plugin Directory: Data not syncing/updating properly from SVN commits In-Reply-To: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> References: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> Message-ID: <068.8f09ce366e6938bdc026d0ef4345f005@wordpress.org> #2826: Plugin Directory: Data not syncing/updating properly from SVN commits ------------------------------+--------------------- Reporter: brianhogg | Owner: Type: defect | Status: closed Priority: highest omg bbq | Milestone: Component: Plugin Directory | Resolution: fixed Keywords: | ------------------------------+--------------------- Changes (by Otto42): * status: new => closed * resolution: => fixed Comment: The problems with our scheduler appear to have been fixed now, and the queue length has returned to normal levels. The issue was not specific to plugin updates, but plugin updates were the most obvious side-effect. We will continue to monitor the situation, and we have setup automatic alerts in case things go wrong again. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2826#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 13:47:57 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 13:47:57 -0000 Subject: [wp-meta] [Making WordPress.org] #2642: Better boosting for phrase matches (or add support for the user to specify a phrase) In-Reply-To: <051.6ac0b0ad0bb1fc49ee7e4ab29ad2ae98@wordpress.org> References: <051.6ac0b0ad0bb1fc49ee7e4ab29ad2ae98@wordpress.org> Message-ID: <066.604ba18e75f2cc07ce8073ef0f4f4a31@wordpress.org> #2642: Better boosting for phrase matches (or add support for the user to specify a phrase) ------------------------------+------------------------------------------- Reporter: gibrown | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by quantumcloud): 100% agreed. The search results are quite polluted with false positives from big names. I reported the issue multiple times but nothing has been done on it so far. The highest priority seems to be that the big names show up for the most popular searches on 1st page. All other searches and the search result quality are largely ignored at this point. Not to mention how next to impossible it has become for new plugin developers to gain any momentum as they start with 0 active installs. New WordPress plugin developers can pretty much forget about their plugins ever getting downloaded from the repository through organic searches. Truly hope that the situation is rectified asap. Replying to [comment:27 gsexton]: > I'm seeing cases where search relevancy is overwhelmed by large numbers of downloads. For example, if you search for the single word "calendar", JetPack is listed in the results of page 1. I looked at the readme.txt file and found that it contains that keyword exactly one time. Evidently, it's massive installed base overwhelms many plugins that from a straight textual analysis are vastly more relevant. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2642#comment:28> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 16:50:51 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 16:50:51 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.a90f160e43c5eaaf5676b9fdd6c5630b@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): @dd32 has a really good idea to modify the process a bit. I think will make things simpler on the client side, while still staying within the EULA. When the client makes a request for events and provides the IP, we geolocate that IP from `ip2location`, and fetch the events that are close to it. We do not return the location data provided by `ip2location` to the client. At this point, the `response` object being built looks like this: {{{ { 'location: {}, 'events: { { 'id' => 1234, 'date' => 194323423, 'type' => 'wordcamp', 'title' => 'WordCamp Seattle', 'location' => 'Seattle, WA, USA' }, // more events here } } }}} The `response.location` is empty. The `response.events[0].location` field above is pulled from `wporg_events`, and originally comes from the WordCamp.org API. The next step is to take that `response.events[0].location` field, and search our `geonames` table for it. `geonames` is Creative Commons licensed, and provides `latitude` and `longitude`. So now, we can populate the `location` field in the response with the data we've pulled from `geonames`. Now the `response` object looks like this: {{{ { 'location: { 'name' => 'Seattle', 'latitude' => '47.200324', 'longitude' => '-121.32523', 'country' => 'US', }, 'events: { { 'id' => 1234, 'date' => 194323423, 'type' => 'wordcamp', 'title' => 'WordCamp Seattle', 'location' => 'Seattle, WA, USA' }, // more events here } } }}} This way, we can still return a location to the client in the initial request, but we're not directly exposing the location details from `ip2location` at all. The previous approach was essentially the same thing, but the `response.location` lookup was being done in a subsequent request (see comment:17), rather than all at once. @barry, do you see any problems with that? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:21> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 18:57:33 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 16 May 2017 18:57:33 +0000 (UTC) Subject: [wp-meta] [5489] sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-cli/ inc/class-markdown-import.php: make/cli: Handbook manifest is at a new location Message-ID: <20170516185733.BCA5D10803B4@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170516/0473b5c1/attachment.html> From noreply at wordpress.org Tue May 16 21:08:27 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 21:08:27 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.5ed5e83e2734d691a8501824e3217aac@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): In [changeset:"5491"]: {{{ #!CommitTicketReference repository="" revision="5491" Events: Replace IP geolocated data with venue location data See #2823 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:23> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 21:08:22 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 16 May 2017 21:08:22 +0000 (UTC) Subject: [wp-meta] [5490] sites/trunk/api.wordpress.org/public_html/events/1.0/tests/ test-index.php: Events: Update IP test cases with current data Message-ID: <20170516210822.CB00310803B4@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170516/d613df36/attachment.html> From noreply at wordpress.org Tue May 16 21:08:23 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 21:08:23 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.5d9360c6b8bebff4032fcc342350ce2d@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): In [changeset:"5490"]: {{{ #!CommitTicketReference repository="" revision="5490" Events: Update IP test cases with current data The IP geolocation database was updated, and a few locations shifted as a result. See #2823 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:22> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 21:08:27 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 16 May 2017 21:08:27 +0000 (UTC) Subject: [wp-meta] [5491] sites/trunk/api.wordpress.org/public_html/events/1.0: Events: Replace IP geolocated data with venue location data Message-ID: <20170516210827.195C810803B4@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170516/6012e717/attachment-0001.html> From noreply at wordpress.org Tue May 16 21:16:57 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 21:16:57 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.f4a923e9346b97353f1ce57ad096c2a7@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): In [changeset:"5492"]: {{{ #!CommitTicketReference repository="" revision="5492" Events: Restore `location['description']` r5491 accidentally changed this, which caused the Core client to have an empty location description. See #2823 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:24> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 21:16:56 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 16 May 2017 21:16:56 +0000 (UTC) Subject: [wp-meta] [5492] sites/trunk/api.wordpress.org/public_html/events/1.0/index.php: Events: Restore `location['description']` Message-ID: <20170516211656.B15B510803B4@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170516/b133b548/attachment.html> From noreply at wordpress.org Tue May 16 21:22:49 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 21:22:49 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.02346be87c4bcaed23df39cb0217f660@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): It turned out to be even simpler than comment:21, since we already have the venue's location data in the events table. r5491 fixed !#3 from comment:15. Barry updated the geolocation data from ip2location.com, which fixed !#1 and !#2. That just leaves !#4 (performance), which Dion is working on, and !#5 (automatic updates), which I'll look into once higher priority tasks are done. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:25> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 22:39:37 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 16 May 2017 22:39:37 +0000 (UTC) Subject: [wp-meta] [5493] sites/trunk/api.wordpress.org/public_html/events/1.0/index.php: Events: Restore `no_location_available` behavior Message-ID: <20170516223937.E3E0110803B4@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170516/665c5cbf/attachment.html> From noreply at wordpress.org Tue May 16 22:39:38 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 22:39:38 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.713d285c75e38e50b6786a407e411c56@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): In [changeset:"5493"]: {{{ #!CommitTicketReference repository="" revision="5493" Events: Restore `no_location_available` behavior r5491 introduced a new condition where the client might receive an unsuccesful `location` lookup, but it wasn't consistent with prior behavior. This commit applies the prior behavior to the new case, so that clients can expect a consistent `no_location_available` error if the location wasn't found. See #2823 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:26> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 23:30:48 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 16 May 2017 23:30:48 +0000 (UTC) Subject: [wp-meta] [5494] sites/trunk/common/includes/slack/announce/lib.php: Slack: Add a `/ deputies` command for the Commnunity team Message-ID: <20170516233048.7CC4D10803B4@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170516/fa25ca7e/attachment.html> From noreply at wordpress.org Wed May 17 01:27:43 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 01:27:43 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.2db1eb7fbcdfbba37ebc1b0fd77e6284@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by coreymckrill): Added the above patch to address Problem 2, IPv6 support. It will need to get updated once we know the name of the table with the IPv6 location data. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:27> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 03:25:01 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 03:25:01 -0000 Subject: [wp-meta] [Making WordPress.org] #2018: Add functionality to flag topics and replies NSFW In-Reply-To: <050.378a5271e359deb473eab0557a2f7cd7@wordpress.org> References: <050.378a5271e359deb473eab0557a2f7cd7@wordpress.org> Message-ID: <065.9d018b75faf870e1a6245cb6b5f209ea@wordpress.org> #2018: Add functionality to flag topics and replies NSFW ----------------------------+------------------ Reporter: netweb | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: needs-patch | ----------------------------+------------------ Comment (by netweb): Related: we should investigate doing similar for "Not a support question" at the same time -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2018#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 10:28:35 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 10:28:35 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.6aed0f0b5d0810d9d781e1a01af206b8@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by dd32): [attachment:2823.diff] takes a pretty harsh attack on some of the code in order to attempt to get the performance better for location searches. * `get_city_from_coordinates()` is gone - It's just not performant enough and I couldn't find an easy way to achieve decent performance for such an edgecase * `get_valid_country_codes()` wasn't actually being used (though was querying) * `guess_location_from_geonames_fallback()` and as a result `get_ideographic_counties()` is gone - this at first seems like a step backwards, however, I think what it's attempting to achieve was going about things the wrong way. * `REPLACE( alternatenames, CONCAT( asciiname, ' - ' ), '' ) LIKE` wasn't performant and there wasn't much of a chance of it being so * using a `alternatenames LIKE '%,Blah,%'` was working, but wasn't really fast In order to speed things up, I created a new table based off the `geoname` data, `geoname_summary` which expands the `(name, asciiname, alternatenames)` out into a single `name` column, and also adds variants (for example the city name without dashes). One major change in this is that if you type in, for example, `The Big Apple` the location returned will now be `The Big Apple` instead of `New York City`, similarly, if you search for `Wien` you'll get just that `Wien` not `Vienna`. Unfortunately typo's will stay as typo's (for example, `New Yorke` or `Lunden`). This might also make it easier to return multiple results in the future (`Springfield, MO` vs `Springfield, MA` for example, or allowing an en_AU locale to pull up `Wellington, NZ` instead of `Wellington, AU`). All the test cases that passed are still passing albeit with the new return data, but instead of the ~100 queries taking 4-6 seconds, it now takes 0.04s for a slightly fewer number of queries. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:28> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 11:31:57 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 11:31:57 -0000 Subject: [wp-meta] [Making WordPress.org] #2828: Minor change on extending-the-rest-api Message-ID: <053.a4a00602b615710ef29b2c778ee6495d@wordpress.org> #2828: Minor change on extending-the-rest-api ---------------------------+-------------------------- Reporter: rafasashi | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Developer Hub | Keywords: dev-feedback ---------------------------+-------------------------- In [https://developer.wordpress.org/rest-api/extending-the-rest-api /adding-custom-endpoints/] The given example works only replacing {{{ $data['id'] }}} by {{{ $data['URL']['id'] }}} ------------------------------------------------------------------------------ {{{ /** * Grab latest post title by an author! * * @param array $data Options for the function. * @return string|null Post title for the latest, * or null if none. */ function my_awesome_func( $data ) { $posts = get_posts( array( 'author' => $data['URL']['id'], ) ); if ( empty( $posts ) ) { return new WP_Error( 'awesome_no_author', 'Invalid author', array( 'status' => 404 ) ); } return $posts[0]->post_title; } }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2828> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 11:42:33 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 11:42:33 -0000 Subject: [wp-meta] [Making WordPress.org] #2828: Minor change on extending-the-rest-api In-Reply-To: <053.a4a00602b615710ef29b2c778ee6495d@wordpress.org> References: <053.a4a00602b615710ef29b2c778ee6495d@wordpress.org> Message-ID: <068.a73c9c0d6d09b17be3b26163ca70f184@wordpress.org> #2828: Minor change on extending-the-rest-api ---------------------------+---------------------- Reporter: rafasashi | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Developer Hub | Resolution: invalid Keywords: dev-feedback | ---------------------------+---------------------- Changes (by rafasashi): * status: new => closed * resolution: => invalid -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2828#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 17:08:13 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 17:08:13 -0000 Subject: [wp-meta] [Making WordPress.org] #2829: Enhancement Request - Clear the page parameter when filter changes the current view Message-ID: <059.efee59752d3a7d6fb09dc919a6704f8f@wordpress.org> #2829: Enhancement Request - Clear the page parameter when filter changes the current view -----------------------------+----------------- Reporter: garrett-eclipse | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: General | Keywords: -----------------------------+----------------- I originally posted this to GlotPress-WP but this is a WP issue and it's not part of the default GP install. Full Details - https://github.com/GlotPress/GlotPress- WP/issues/718#event-1085632935 -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2829> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 17:10:33 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 17:10:33 -0000 Subject: [wp-meta] [Making WordPress.org] #2829: Clear the page parameter when filter changes the current view (was: Enhancement Request - Clear the page parameter when filter changes the current view) In-Reply-To: <059.efee59752d3a7d6fb09dc919a6704f8f@wordpress.org> References: <059.efee59752d3a7d6fb09dc919a6704f8f@wordpress.org> Message-ID: <074.6eb61600f1c717212613f98b62326649@wordpress.org> #2829: Clear the page parameter when filter changes the current view --------------------------------------+------------------ Reporter: garrett-eclipse | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Translate Site & Plugins | Resolution: Keywords: | --------------------------------------+------------------ Changes (by ocean90): * component: General => Translate Site & Plugins Old description: > I originally posted this to GlotPress-WP but this is a WP issue and it's > not part of the default GP install. > > Full Details - https://github.com/GlotPress/GlotPress- > WP/issues/718#event-1085632935 New description: I originally posted this to GlotPress-WP but this is a WP.org issue and it's not part of the default GP install. Full Details - https://github.com/GlotPress/GlotPress- WP/issues/718#event-1085632935 -- -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2829#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 17:17:16 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 17:17:16 -0000 Subject: [wp-meta] [Making WordPress.org] #2829: Clear the page parameter when filter changes the current view In-Reply-To: <059.efee59752d3a7d6fb09dc919a6704f8f@wordpress.org> References: <059.efee59752d3a7d6fb09dc919a6704f8f@wordpress.org> Message-ID: <074.0d972bdd3305a364033cc67b381fe0d3@wordpress.org> #2829: Clear the page parameter when filter changes the current view --------------------------------------+------------------ Reporter: garrett-eclipse | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Translate Site & Plugins | Resolution: Keywords: | --------------------------------------+------------------ Comment (by garrett-eclipse): Thanks for the tweak @ocean90 -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2829#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 18:21:50 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 17 May 2017 18:21:50 +0000 (UTC) Subject: [wp-meta] [5495] sites/trunk/api.wordpress.org/public_html/events/1.0/index.php: Events: Prefer meetups over WordCamps to improve location accuracy Message-ID: <20170517182150.0BBEA108033F@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170517/3adc941c/attachment.html> From noreply at wordpress.org Wed May 17 18:21:50 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 18:21:50 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.1c554cc79545836c4828c41fb9f6de2b@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): In [changeset:"5495"]: {{{ #!CommitTicketReference repository="" revision="5495" Events: Prefer meetups over WordCamps to improve location accuracy See #2823 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:29> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 19:23:19 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 17 May 2017 19:23:19 +0000 (UTC) Subject: [wp-meta] [5496] sites/trunk/api.wordpress.org/public_html/events/1.0/tests/ test-index.php: Events: Track query execution time to aid optimization Message-ID: <20170517192319.74A73108033F@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170517/1f80e5fe/attachment-0001.html> From noreply at wordpress.org Wed May 17 19:23:19 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 19:23:19 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.26ebc9a4bc375974f8afe540a6845447@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): In [changeset:"5496"]: {{{ #!CommitTicketReference repository="" revision="5496" Events: Track query execution time to aid optimization The test suite isn't representative of real-world usage, because by nature it's weighted heavily towards edge cases. Establishing a performance baseline is still useful when optimizing, though. See #2823 Props dd32 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:30> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 20:30:29 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 17 May 2017 20:30:29 +0000 (UTC) Subject: [wp-meta] [5497] sites/trunk/api.wordpress.org/public_html/events/1.0: Events: Remove `get_city_from_coordinates()` to improve performance Message-ID: <20170517203029.77501108033F@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170517/a0b3239e/attachment.html> From noreply at wordpress.org Wed May 17 20:30:29 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 20:30:29 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.9f6f0d0b7a4df3fc29abd74ce7b0fe4f@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): In [changeset:"5497"]: {{{ #!CommitTicketReference repository="" revision="5497" Events: Remove `get_city_from_coordinates()` to improve performance The function was not performant, and it's not easy to make it that way. It's only needed for a few edge cases, and we can get the location from the events themselves (similar to r5491). So, removing this is a good trade-off. Because we are able to rebuild the location, no changes are needed in Core, and a new version of this endpoint is not needed. See #2823 Props dd32 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:32> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 21:06:36 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 21:06:36 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.7288bc361b9806a2cf3dcf650f527931@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by karmatosed): Its worth adding the oddity I experience here: [[Image(https://cldup.com/U3LohVCeQu.png)]] Firstly, I am nowhere near Romford (that's a pretty far away from where I am). Secondly, as someone from UK, showing US City in the box is a weird experience. Also, why only cities? In UK for example towns have meetups and a lot of people don't live in cities.. this I am sure happens in US :) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:34> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 21:21:15 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 21:21:15 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.73a94a9d13f537742af6ae92aae202bc@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): Replying to [comment:34 karmatosed]: > Secondly, as someone from UK, showing US City in the box is a weird experience. That string is internationalized, so you'll see a local city as soon as it's translated. > Also, why only cities? The database we have is primarily city-centric. It has some region information, but it's not detailed or comprehensive enough to fully support. The API does try to match inputs other than cities, but we only explicitly mention cities in the instructions because that's the only thing we can guarantee will work. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:35> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 22:12:03 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 22:12:03 -0000 Subject: [wp-meta] [Making WordPress.org] #1724: Readme parsing bugs In-Reply-To: <048.f0a4034ffeb07046bc76b987bdf394f2@wordpress.org> References: <048.f0a4034ffeb07046bc76b987bdf394f2@wordpress.org> Message-ID: <063.8828e938d862d956dcbf22ee72cd8e05@wordpress.org> #1724: Readme parsing bugs ------------------------------+------------------ Reporter: dd32 | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: close | ------------------------------+------------------ Changes (by Ipstenu): * keywords: => close Comment: I think we can close this and open up new ones as needed. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1724#comment:19> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 22:24:13 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 22:24:13 -0000 Subject: [wp-meta] [Making WordPress.org] #2594: Plugin Directory: List pending plugins on 'add' page In-Reply-To: <051.8682691f18de896a37086227c227a3cc@wordpress.org> References: <051.8682691f18de896a37086227c227a3cc@wordpress.org> Message-ID: <066.0209a346ebcd959a5ca37a0653c0f24e@wordpress.org> #2594: Plugin Directory: List pending plugins on 'add' page ----------------------------------------------+---------------------------- Reporter: Ipstenu | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Component: Plugin Directory | Directory v3.0 Keywords: has-patch commit has-screenshots | Resolution: ----------------------------------------------+---------------------------- Changes (by tellyworth): * milestone: Plugin Directory v3 - Future => Plugin Directory v3.0 -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2594#comment:8> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 23:22:37 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 23:22:37 -0000 Subject: [wp-meta] [Making WordPress.org] #2653: 404 on Browse url In-Reply-To: <054.96045bfc56395581132ce69301c6bac7@wordpress.org> References: <054.96045bfc56395581132ce69301c6bac7@wordpress.org> Message-ID: <069.69469ecabf6379084fe56d7d196e93ae@wordpress.org> #2653: 404 on Browse url ------------------------------+------------------------------------------- Reporter: tellyworth | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by joyously): > A redirect to https://wordpress.org/plugins/browse/featured/ slipped into r5248 This is bad UX since it takes an inclusive URL and turns it into a dead end. I think the intent of a URL like `https://wordpress.org/plugins/browse/` is to show everything that there is. I always thought it should show the main taxonomy of the plugin directory, with counts, and no actual plugins. If that idea isn't popular, my fallback would be to have it show plugins ordered by plugin name, with an alphabet of links to jump to the sections for each letter. It definitely should not be the same as `https://wordpress.org/plugins/browse/new/`, although the Browse page could have links to other ways to browse like New or Popular. I think Updated can be very useful, but not promoted with a link. It should work, though, if you know the URL. By the way, looking at the Featured page, why do they never change? Who determines what goes here? And why the confusing language of having "feature plugins" under "Beta Testing" and a few big plugins under "Featured"? I think the plugins that could go into core would get more interest and feedback if they were shown by default (featured), instead of always showing the same 6 everyone knows about. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2653#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 23:32:35 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 23:32:35 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.ddcb2a72606a4a3fdf49724cf3ebb833@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by dd32): Replying to [comment:35 iandunn]: > Replying to [comment:34 karmatosed]: > > Also, why only cities? > > The database we have is primarily city-centric. It has some region information, but it's not detailed or comprehensive enough to fully support. The API does try to match inputs other than cities, but we only explicitly mention cities in the instructions because that's the only thing we can guarantee will work. Worth noting that the database we've been using says "city" but in this context, city means town. We've used a data source which includes town with a population of >1k (or an administrative area of 1k, so town X of 500 and 500 in the surrounding area, where X is the common point would be included). For `countrycode = GB` there were 3.6k 'towns' with 14k different spellings and alternate names. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:36> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 01:26:49 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 18 May 2017 01:26:49 +0000 (UTC) Subject: [wp-meta] [5498] sites/trunk/api.wordpress.org/public_html/dotorg/github-sync/ feature-plugins.sh: Feature Plugins Github Sync: Don't performa a commit/ version bump if nothing has changed. Message-ID: <20170518012649.13A0310805FB@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170518/3d259309/attachment.html> From noreply at wordpress.org Thu May 18 05:54:12 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 18 May 2017 05:54:12 +0000 (UTC) Subject: [wp-meta] [5499] sites/trunk/api.wordpress.org/public_html/events/1.0/index.php: Events: Stop using fuzzy locations for 4.8-beta2 Message-ID: <20170518055412.2E23E10805FB@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170518/917cfbfe/attachment-0001.html> From noreply at wordpress.org Thu May 18 05:54:12 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 05:54:12 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.2bcc76be157293419cb3da7c3aaed582@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): In [changeset:"5499"]: {{{ #!CommitTicketReference repository="" revision="5499" Events: Stop using fuzzy locations for 4.8-beta2 See #2823 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:37> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 07:07:40 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 18 May 2017 07:07:40 +0000 (UTC) Subject: [wp-meta] [5500] sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory/class-plugin-directory.php: Plugin directory: properly fix duplicate plugin slug issue. Message-ID: <20170518070740.853D01080394@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170518/b4384025/attachment.html> From noreply at wordpress.org Thu May 18 07:07:41 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 07:07:41 -0000 Subject: [wp-meta] [Making WordPress.org] #2787: Plugin Directory: Reject plugin on duplicate slugs In-Reply-To: <051.2ac2a1bb741f1b18b5c20f5005ec290b@wordpress.org> References: <051.2ac2a1bb741f1b18b5c20f5005ec290b@wordpress.org> Message-ID: <066.644d8b0b3345743f8b31c2c82a03f86d@wordpress.org> #2787: Plugin Directory: Reject plugin on duplicate slugs ------------------------------+------------------------- Reporter: Ipstenu | Owner: tellyworth Type: defect | Status: closed Priority: normal | Milestone: Component: Plugin Directory | Resolution: fixed Keywords: has-patch | ------------------------------+------------------------- Changes (by tellyworth): * status: reopened => closed * resolution: => fixed Comment: In [changeset:"5500"]: {{{ #!CommitTicketReference repository="" revision="5500" Plugin directory: properly fix duplicate plugin slug issue. Props @SergeyBiryukov Refines earlier fix in [5416] Fixes #2787 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2787#comment:10> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 09:29:58 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 09:29:58 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.6b706717eed8163de85d58bdc87af796@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by ocean90): Searching for "K?ln" gives me a "We couldn?t locate K?ln." error but a search for "Cologne" or "Koeln" returns the proper "K?ln". "M?nster" is working fine so I'm not sure if it's an issue with umlauts. Another oddity: "D?sseldorf" returns "D?sseldorf-Pempelfort" which is kinda unexpected because "Pempelfort" is just a city part of "D?sseldorf". -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:38> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 14:37:27 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 14:37:27 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.e1726318731cb072c7acf69fe4c49423@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by pbiron): As I mentioned in the devchat yesterday, searching for "Gardner, CO" gives events in Kansas City, MO...which is almost 700 miles away. Looking into the `community-events-location` meta_key, I see that the lat/lng stored is for KC, MO, which explains why it showing event for KC, MO. However, if [[https://meta.trac.wordpress.org/ticket/2823#comment:1|Otto's comment]] is correct that place name searches are using `geonames.org` data then that is odd, because http://www.geonames.org/search.html?q=gardner%2C+co&country= correctly finds Gardner, CO (with the correct lat/lng) as the 1st result. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:39> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 15:07:07 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 15:07:07 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.1bd9daa9db127321c26f1dc5d1014217@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): Replying to [comment:38 ocean90]: > Searching for "K?ln" gives me a "We couldn?t locate K?ln." error but a search for "Cologne" or "Koeln" returns the proper "K?ln". "M?nster" is working fine so I'm not sure if it's an issue with umlauts. > > Another oddity: "D?sseldorf" returns "D?sseldorf-Pempelfort" which is kinda unexpected because "Pempelfort" is just a city part of "D?sseldorf". I think most of the charset issues have been worked out, but there's still at least one that I know about (see the unit tests). @dd32 is working on upgrading our geocoding from geonames.org to Google's Geocoding API, which should fix all of that. See [attachment:2823.2.diff]. Replying to [comment:39 pbiron]: > As I mentioned in the devchat yesterday, searching for "Gardner, CO" gives events in Kansas City, MO...which is almost 700 miles away. Looking into the community-events-location meta_key, I see that the lat/lng stored is for KC, MO, which explains why it showing event for KC, MO. I think that's an edge case just because there's not enough information to distinguish between the two Kansas Citys, since they're so close to each other geographically. [wp40774] might be able to help there, though, since we could use the IP geolocation as a signal. We'd also like to have the API start returning a list of alternate locations, and have Core display those in a dropdown for the user to choose. That'll probably have to be 4.8.1, though. > However, if Otto's comment is correct that place name searches are using geonames.org data then that is odd, because http://www.geonames.org/search.html?q=gardner%2C+co&country= correctly finds Gardner, CO (with the correct lat/lng) as the 1st result. Otto's definitely correct, but the code does a lot of gymnastics to try and parse the query and look it up in a lot of ways. There could be a bug in there, or just some conflicting edge cases, etc. Dion's work to switch to Google's API should help there too. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:40> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 15:12:28 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 15:12:28 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.3fc74bb2144d19334fd2e82c72d51502@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by pbiron): Replying to [comment:36 dd32]: > Worth noting that the database we've been using says "city" but in this context, city means town. We've used a data source which includes town with a population of >1k (or an administrative area of 1k, so town X of 500 and 500 in the surrounding area, where X is the common point would be included). That probably explains the behavior I'm seeing...as Gardner, CO has a population of only **70**. If the surrounding farms are included, what I call "Greater Metropolitan Gardner", the pop balloons to a whopping **400**. Yes, I live in the sticks :-). -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:41> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 15:21:52 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 15:21:52 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.9457d08c834f2fbce8bc3bfd98d7408f@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by pbiron): Replying to [comment:40 iandunn]: > Replying to [comment:39 pbiron]: > > As I mentioned in the devchat yesterday, searching for "Gardner, CO" gives events in Kansas City, MO...which is almost 700 miles away. Looking into the community-events-location meta_key, I see that the lat/lng stored is for KC, MO, which explains why it showing event for KC, MO. > > I think that's an edge case just because there's not enough information to distinguish between the two Kansas Citys, since they're so close to each other geographically. Sorry, "KC, MO" was just my abbreviation for "Kansas City, MO"...I should have been more clear. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:43> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 15:20:14 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 15:20:14 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.976d1067d255e4a4b676715249c913cf@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): Replying to [comment:41 pbiron]: > Replying to [comment:36 dd32]: > > Worth noting that the database we've been using says "city" but in this context, city means town. We've used a data source which includes town with a population of >1k (or an administrative area of 1k, so town X of 500 and 500 in the surrounding area, where X is the common point would be included). > > That probably explains the behavior I'm seeing...as Gardner, CO has a population of only **70**. If the surrounding farms are included, what I call "Greater Metropolitan Gardner", the pop balloons to a whopping **400**. Yes, I live in the sticks :-). No shame in that :) I think the only reason we limited it to towns with > 1k population is just because, for an endpoint that will see as much traffic as this one, we don't have the server resources to do the database queries on larger data sets. Once we switch to Google's API, though, that should solve that problem. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:42> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 17:27:08 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 17:27:08 -0000 Subject: [wp-meta] [Making WordPress.org] #2753: Plugin directory search sorting and filtering In-Reply-To: <054.ea0beff6952873fe3a66bcfa513e7b6b@wordpress.org> References: <054.ea0beff6952873fe3a66bcfa513e7b6b@wordpress.org> Message-ID: <069.e5ffe04e38ed8e13796c8d13c82d383a@wordpress.org> #2753: Plugin directory search sorting and filtering -------------------------------------+------------------------------------- Reporter: tellyworth | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Component: Plugin Directory | Future Keywords: ui-feedback needs- | Resolution: screenshots | -------------------------------------+------------------------------------- Comment (by joyously): @gibrown, I put the filters that made sense to me into a mockup image (see attachments). I am of two minds on how the filters should behave. One is that each choice is a link (parameterized search) so the page reloads on each. The other is that it is a form that you set all the parameters and then submit once. When I have used these types of filters, my preference is one submit, but people with fast connections probably prefer each click to change the page. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2753#comment:5> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 18:02:55 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 18:02:55 -0000 Subject: [wp-meta] [Making WordPress.org] #2753: Plugin directory search sorting and filtering In-Reply-To: <054.ea0beff6952873fe3a66bcfa513e7b6b@wordpress.org> References: <054.ea0beff6952873fe3a66bcfa513e7b6b@wordpress.org> Message-ID: <069.2b6d36cf2ac0512c8ff5bb9345047bab@wordpress.org> #2753: Plugin directory search sorting and filtering -------------------------------------+------------------------------------- Reporter: tellyworth | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Component: Plugin Directory | Future Keywords: ui-feedback needs- | Resolution: screenshots | -------------------------------------+------------------------------------- Comment (by joyously): One thing that is unclear is whether it is different code that populates the plugin search results in the admin versus the page that looks the same on wordpress.org. Does this ticket cover both contexts? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2753#comment:6> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 20:28:08 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 20:28:08 -0000 Subject: [wp-meta] [Making WordPress.org] #2245: Migrate pending plugins In-Reply-To: <054.f162bbe9076a6f343bde09022707488c@wordpress.org> References: <054.f162bbe9076a6f343bde09022707488c@wordpress.org> Message-ID: <069.278d72244e9f3ea060046d2c00a9288b@wordpress.org> #2245: Migrate pending plugins ------------------------------+------------------------------------ Reporter: tellyworth | Owner: dd32 Type: task | Status: assigned Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------ Comment (by Ipstenu): @dd32 - Did we migrate the rejected plugins? I'd like to be able to close this out :) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2245#comment:8> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 20:31:26 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 20:31:26 -0000 Subject: [wp-meta] [Making WordPress.org] #2665: Plugin Directory Admins: Contact Plugin Author should open in new window In-Reply-To: <051.88b69e0e89d215bc69777301a3f89077@wordpress.org> References: <051.88b69e0e89d215bc69777301a3f89077@wordpress.org> Message-ID: <066.e55704f893a5312870b7e0b49f8b603b@wordpress.org> #2665: Plugin Directory Admins: Contact Plugin Author should open in new window ------------------------------+---------------------- Reporter: Ipstenu | Owner: Otto42 Type: enhancement | Status: closed Priority: normal | Milestone: Component: Plugin Directory | Resolution: wontfix Keywords: has-patch commit | ------------------------------+---------------------- Changes (by Ipstenu): * status: assigned => closed * resolution: => wontfix Comment: On review and having used the directory for a month now, I classify this as won't fix. We don't actually need it. I was wrong :) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2665#comment:7> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 20:39:06 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 20:39:06 -0000 Subject: [wp-meta] [Making WordPress.org] #2830: Plugin Directory: Include slug in submission emails Message-ID: <051.980ca4c7bb6bb49acc9857d3105e0019@wordpress.org> #2830: Plugin Directory: Include slug in submission emails ------------------------------+----------------------- Reporter: Ipstenu | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Keywords: has-patch ------------------------------+----------------------- To mitigate the accidents of "Oh no! I didn't want THAT slug!" we should let people know what the slug's going to be when the plugin is submitted. This patch tells them in two places: 1) The in-page notice of "Submission in!" 2) The email of "We got it!" Both detail what the slug is and remind developers not to resubmit and just email us if there's a problem. This MAY result in a lot of weird emails about "WooCommerce! We need woo!" but that's better than after- approval complaints about bad slugs. I think. If I'm wrong, we'll try again. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2830> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 20:47:15 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 20:47:15 -0000 Subject: [wp-meta] [Making WordPress.org] #2677: Plugin Directory: Admin email subjects to plugin author (s) improvements (was: Plugin Directory: Admin email to plugin author (s) improvements) In-Reply-To: <051.76e30163c28c8e10b716b6642fdc91d1@wordpress.org> References: <051.76e30163c28c8e10b716b6642fdc91d1@wordpress.org> Message-ID: <066.0b0030985e40ea6e31edb21cf4a75035@wordpress.org> #2677: Plugin Directory: Admin email subjects to plugin author (s) improvements ------------------------------+------------------------- Reporter: Ipstenu | Owner: tellyworth Type: enhancement | Status: reopened Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch commit | ------------------------------+------------------------- Comment (by Ipstenu): Agree with Sergey! Attached patch that also adds in a subject for rejected plugins so it's more clear there too. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2677#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 21:43:51 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 21:43:51 -0000 Subject: [wp-meta] [Making WordPress.org] #2831: On the Advanced view of a plugin the list of committers is imporperly formatted. Message-ID: <050.a1902e359d66d525b6d3ac015ea54721@wordpress.org> #2831: On the Advanced view of a plugin the list of committers is imporperly formatted. ------------------------------+------------------------------------------ Reporter: aguseo | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Keywords: has-screenshots ui-feedback ------------------------------+------------------------------------------ On the Advanced view of a plugin the list of committers is cascading vs being under each other. Screenshot here: https://cloudup.com/c_eWP58vjh5 It could be fixed with a bit of css like this: {{{ .committer-list li { clear: both; margin-bottom: 0.5rem; } }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2831> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 21:55:34 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 21:55:34 -0000 Subject: [wp-meta] [Making WordPress.org] #2831: On the Advanced view of a plugin the list of committers is imporperly formatted. In-Reply-To: <050.a1902e359d66d525b6d3ac015ea54721@wordpress.org> References: <050.a1902e359d66d525b6d3ac015ea54721@wordpress.org> Message-ID: <065.0644df10955787fa1554274f31e8fe23@wordpress.org> #2831: On the Advanced view of a plugin the list of committers is imporperly formatted. -------------------------------------+------------------------------------- Reporter: aguseo | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Component: Plugin Directory | Future Keywords: has-screenshots ui- | Resolution: feedback reporter-feedback | -------------------------------------+------------------------------------- Changes (by Ipstenu): * keywords: has-screenshots ui-feedback => has-screenshots ui-feedback reporter-feedback Comment: @aguseo - what plugin is that on? And what browser/OS are you on. I can't reproduce that view. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2831#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 19 02:37:09 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 19 May 2017 02:37:09 -0000 Subject: [wp-meta] [Making WordPress.org] #2245: Migrate pending plugins In-Reply-To: <054.f162bbe9076a6f343bde09022707488c@wordpress.org> References: <054.f162bbe9076a6f343bde09022707488c@wordpress.org> Message-ID: <069.090fcd373b2cfbc8d0c4274745972b16@wordpress.org> #2245: Migrate pending plugins ------------------------------+------------------------------------ Reporter: tellyworth | Owner: dd32 Type: task | Status: assigned Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------ Comment (by dd32): Nope, never got to migrating them over. Sorry. I'll try to get to it in the next couple of weeks, hopefully after 4.8 ships. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2245#comment:9> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 19 08:35:39 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 19 May 2017 08:35:39 -0000 Subject: [wp-meta] [Making WordPress.org] #2832: Search result not working properly Message-ID: <057.58ee2aeb07cce0d41b56ca0079fe0edf@wordpress.org> #2832: Search result not working properly ------------------------------+--------------------------------------- Reporter: karan.gadhavi | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Keywords: 2nd-opinion needs-testing ------------------------------+--------------------------------------- Hi I searched for "Facebook Events" in plug-in directory and found surprising result. "EME Sync Facebook Events" Plug-in second and "Facebook Events Importer" & " Import Facebook Events" below it event both has many points better then EME Sync Facebook Events plig-in Here is comparison Search in Title Name Active Ins Search Term in Tag rating EME Sync Facebook Events 500 not exact 5 Facebook Events Importer 2000 exact 3 Import Facebook Events 1000+ exact 5 Import Facebook Events plug-in should came first i believe -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2832> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 19 08:55:14 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 19 May 2017 08:55:14 -0000 Subject: [wp-meta] [Making WordPress.org] #2831: On the Advanced view of a plugin the list of committers is imporperly formatted. In-Reply-To: <050.a1902e359d66d525b6d3ac015ea54721@wordpress.org> References: <050.a1902e359d66d525b6d3ac015ea54721@wordpress.org> Message-ID: <065.08b799fe1b3f378b235c8be4aec1ef14@wordpress.org> #2831: On the Advanced view of a plugin the list of committers is imporperly formatted. -------------------------------------+------------------------------------- Reporter: aguseo | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Component: Plugin Directory | Future Keywords: has-screenshots ui- | Resolution: feedback reporter-feedback | -------------------------------------+------------------------------------- Comment (by aguseo): Replying to [comment:1 Ipstenu]: > @aguseo - what plugin is that on? And what browser/OS are you on. > > I can't reproduce that view. Hi @Ipstenu, Sorry, I should have shared the link upfront. I found it on these urls so far: https://wordpress.org/plugins/gigpress/advanced/ https://wordpress.org/plugins/event-tickets/advanced/ https://wordpress.org/plugins/image-widget/advanced/ https://wordpress.org/plugins/advanced-post-manager/advanced/ I'm contributor to these plugins. It only seems to be like that when I'm logged in. That is when I see the committers list where this glitch happens. When I'm logged out I don't see committers. I'm using Windows 7 / 10 and Firefox 52 / 53, chrome 58.0.3029.110 (64-bit), IE11. I hope this helps, let me know if you need more info. Cheers -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2831#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 19 12:47:03 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 19 May 2017 12:47:03 -0000 Subject: [wp-meta] [Making WordPress.org] #2631: Plugin Directory: No way to view Recently Updated plugins In-Reply-To: <052.eb4400b9e45b87852011048965021979@wordpress.org> References: <052.eb4400b9e45b87852011048965021979@wordpress.org> Message-ID: <067.86909614abf4dc96771f153d402f2c26@wordpress.org> #2631: Plugin Directory: No way to view Recently Updated plugins ------------------------------+------------------------------------------- Reporter: infokurs | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: needs-patch | ------------------------------+------------------------------------------- Comment (by djr): Fortunately there's absolutely no spamming now in the Plugin directory... /sarcasm. https://wordpress.org/plugins/popup-master/ -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2631#comment:5> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 19 14:16:56 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 19 May 2017 14:16:56 -0000 Subject: [wp-meta] [Making WordPress.org] #2119: Profiles: Notifications should have an option to match whole words only In-Reply-To: <058.0e5ddec94026ef8887b7fb79e9528bc5@wordpress.org> References: <058.0e5ddec94026ef8887b7fb79e9528bc5@wordpress.org> Message-ID: <073.d922f0636c7a85988a8769bfda747147@wordpress.org> #2119: Profiles: Notifications should have an option to match whole words only ----------------------------+------------------ Reporter: SergeyBiryukov | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Profiles | Resolution: Keywords: | ----------------------------+------------------ Comment (by denisco): Is there a chance that this will be corrected in the near future? Or will the source code of notifications be opened? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2119#comment:6> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 19 14:22:19 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 19 May 2017 14:22:19 -0000 Subject: [wp-meta] [Making WordPress.org] #2832: Search result not working properly In-Reply-To: <057.58ee2aeb07cce0d41b56ca0079fe0edf@wordpress.org> References: <057.58ee2aeb07cce0d41b56ca0079fe0edf@wordpress.org> Message-ID: <072.fad0f93841a37d1ca836704204b40095@wordpress.org> #2832: Search result not working properly ---------------------------------------+----------------------------------- Reporter: karan.gadhavi | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory Component: Plugin Directory | v3.0 Keywords: 2nd-opinion needs-testing | Resolution: ---------------------------------------+----------------------------------- Description changed by SergeyBiryukov: Old description: > Hi > > I searched for "Facebook Events" in plug-in directory and found > surprising result. > > "EME Sync Facebook Events" Plug-in second and "Facebook Events Importer" > & " > Import Facebook Events" below it event both has many points better then > EME Sync Facebook Events plig-in > > Here is comparison > Search in Title Name Active Ins Search Term in Tag rating > EME Sync Facebook Events 500 not exact 5 > Facebook Events Importer 2000 exact 3 > Import Facebook Events 1000+ exact 5 > > Import Facebook Events plug-in should came first i believe New description: Hi I searched for "Facebook Events" in plug-in directory and found surprising result. "EME Sync Facebook Events" Plug-in second and "Facebook Events Importer" & " Import Facebook Events" below it event both has many points better then EME Sync Facebook Events plig-in Here is comparison ||Search in Title Name ||Active Ins ||Search Term in Tag ||rating || ||EME Sync Facebook Events ||500 ||not exact ||5 || ||Facebook Events Importer ||2000 ||exact ||3 || ||Import Facebook Events ||1000+ ||exact ||5 || Import Facebook Events plug-in should came first i believe -- -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2832#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 19 15:18:25 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 19 May 2017 15:18:25 -0000 Subject: [wp-meta] [Making WordPress.org] #2119: Profiles: Notifications should have an option to match whole words only In-Reply-To: <058.0e5ddec94026ef8887b7fb79e9528bc5@wordpress.org> References: <058.0e5ddec94026ef8887b7fb79e9528bc5@wordpress.org> Message-ID: <073.f353e497095ea6b4d6904b0400427a96@wordpress.org> #2119: Profiles: Notifications should have an option to match whole words only ----------------------------+------------------ Reporter: SergeyBiryukov | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Profiles | Resolution: Keywords: | ----------------------------+------------------ Comment (by fierevere): I'm getting 2/3 false notifications for "Yui", not just JqueryUi but random strings and even other usernames like {{{ Hi @tzyyyuin }}} matching should be done versus exact string, otherwise such notifications are close to useless -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2119#comment:7> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 19 17:40:40 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 19 May 2017 17:40:40 -0000 Subject: [wp-meta] [Making WordPress.org] #2831: On the Advanced view of a plugin the list of committers is imporperly formatted. In-Reply-To: <050.a1902e359d66d525b6d3ac015ea54721@wordpress.org> References: <050.a1902e359d66d525b6d3ac015ea54721@wordpress.org> Message-ID: <065.20f20bc2321cbacf12545aab3809c0fa@wordpress.org> #2831: On the Advanced view of a plugin the list of committers is imporperly formatted. -------------------------------------+------------------------------------- Reporter: aguseo | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Component: Plugin Directory | Future Keywords: has-screenshots ui- | Resolution: feedback reporter-feedback | -------------------------------------+------------------------------------- Comment (by Ipstenu): Oooh. So mine won't look like that when logged in because I'm an admin, and I have an extra line below it (for the email addresses). Interesting... I'm torn between "You shouldn't see committers at all if you're not a committer of that plugin" and "We should fix that!" -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2831#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 19 18:41:58 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 19 May 2017 18:41:58 -0000 Subject: [wp-meta] [Making WordPress.org] #2686: Plugin Search: Search should also take into account the number of ratings In-Reply-To: <051.6a8a8298224b7d93c0ff73de59c8a80c@wordpress.org> References: <051.6a8a8298224b7d93c0ff73de59c8a80c@wordpress.org> Message-ID: <066.ecc56d9dc66016b9019453b5533d789b@wordpress.org> #2686: Plugin Search: Search should also take into account the number of ratings ------------------------------+------------------------------------------- Reporter: bfintal | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by gibrown): Ah ha! Wilson score confidence interval for a Bernoulli parameter from http://www.evanmiller.org/how-not-to-sort-by-average-rating.html I think I will try putting something like this into the index. I need to figure how to make it work on a 5 star scale, but this addresses a lot of my concerns with hard coding any limits. Noting here mostly as a reminder. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2686#comment:11> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 19 18:53:30 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Fri, 19 May 2017 18:53:30 +0000 (UTC) Subject: [wp-meta] [5501] sites/trunk/api.wordpress.org/public_html/events/1.0: Events: Support IPv6 address geolocation. Message-ID: <20170519185330.0F4A51080374@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170519/d50927c7/attachment-0001.html> From noreply at wordpress.org Fri May 19 18:53:30 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 19 May 2017 18:53:30 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.081773489b6a19a5b6d3d80085dad3fc@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): In [changeset:"5501"]: {{{ #!CommitTicketReference repository="" revision="5501" Events: Support IPv6 address geolocation. See #2823 Props coreymckrill }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:44> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 14:08:29 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 14:08:29 -0000 Subject: [wp-meta] =?utf-8?q?=5BMaking_WordPress=2Eorg=5D_=232833=3A_A_lin?= =?utf-8?q?k_to_=E2=80=9CUnresolved_topics_for_this_plugin=E2=80=9D_displa?= =?utf-8?q?yed_to_plugin_contributors=2E?= Message-ID: <050.6143ae76b38ea6ef0c123b092eb36926@wordpress.org> #2833: A link to ?Unresolved topics for this plugin? displayed to plugin contributors. ------------------------------+----------------- Reporter: lapzor | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Keywords: ------------------------------+----------------- Show a link to ?Unresolved topics for this plugin? displayed to plugin contributors on their plugins support forum. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2833> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 14:09:46 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 14:09:46 -0000 Subject: [wp-meta] [Making WordPress.org] #2834: Give plugin contributors the right to lock a topic, or... Message-ID: <050.e7617ae4910ad984e73d420dab714c0d@wordpress.org> #2834: Give plugin contributors the right to lock a topic, or... -------------------------+----------------- Reporter: lapzor | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Keywords: -------------------------+----------------- Give plugin contributors the right to lock a topic in their plugins support forum, or automatically lock topics that are marked as resolved (no more replies allowed), or by default mark them as unresolved again when anyone replies. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2834> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 14:12:06 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 14:12:06 -0000 Subject: [wp-meta] [Making WordPress.org] #2835: Assign topic to specific plugin contributor Message-ID: <050.44e1cb2a6a38c93fdbc4e979b7a1f158@wordpress.org> #2835: Assign topic to specific plugin contributor -------------------------+----------------- Reporter: lapzor | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Keywords: -------------------------+----------------- Let plugin contributors assign a topic in their plugins support forum to a(nother) plugin contributor, that will receive a notification and maybe even highlight the thread for this user and/or show them under "Topics assigned to me" -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2835> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 14:14:13 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 14:14:13 -0000 Subject: [wp-meta] [Making WordPress.org] #2834: Give plugin contributors the right to lock a topic, or... In-Reply-To: <050.e7617ae4910ad984e73d420dab714c0d@wordpress.org> References: <050.e7617ae4910ad984e73d420dab714c0d@wordpress.org> Message-ID: <065.d17f590b280be30b62b902573606ba46@wordpress.org> #2834: Give plugin contributors the right to lock a topic, or... ----------------------------+------------------ Reporter: lapzor | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Changes (by lapzor): * component: General => Support Forums -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2834#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 14:13:42 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 14:13:42 -0000 Subject: [wp-meta] =?utf-8?q?=5BMaking_WordPress=2Eorg=5D_=232833=3A_A_lin?= =?utf-8?q?k_to_=E2=80=9CUnresolved_topics_for_this_plugin=E2=80=9D_displa?= =?utf-8?q?yed_to_plugin_contributors=2E?= In-Reply-To: <050.6143ae76b38ea6ef0c123b092eb36926@wordpress.org> References: <050.6143ae76b38ea6ef0c123b092eb36926@wordpress.org> Message-ID: <065.72ea9ede1e45ad37e311bb08e8d062b0@wordpress.org> #2833: A link to ?Unresolved topics for this plugin? displayed to plugin contributors. ----------------------------+------------------ Reporter: lapzor | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Changes (by lapzor): * component: Plugin Directory => Support Forums -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2833#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 14:14:33 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 14:14:33 -0000 Subject: [wp-meta] [Making WordPress.org] #2835: Assign topic to specific plugin contributor In-Reply-To: <050.44e1cb2a6a38c93fdbc4e979b7a1f158@wordpress.org> References: <050.44e1cb2a6a38c93fdbc4e979b7a1f158@wordpress.org> Message-ID: <065.86d4335a864bc832fb3e216578a3a6d4@wordpress.org> #2835: Assign topic to specific plugin contributor ----------------------------+------------------ Reporter: lapzor | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Changes (by lapzor): * component: General => Support Forums -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2835#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 14:50:20 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 14:50:20 -0000 Subject: [wp-meta] [Making WordPress.org] #2835: Assign topic to specific plugin contributor In-Reply-To: <050.44e1cb2a6a38c93fdbc4e979b7a1f158@wordpress.org> References: <050.44e1cb2a6a38c93fdbc4e979b7a1f158@wordpress.org> Message-ID: <065.482beb54788fa19f0ff0355a01e982dc@wordpress.org> #2835: Assign topic to specific plugin contributor ----------------------------+------------------ Reporter: lapzor | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Comment (by SergeyBiryukov): Hi @lapzor, welcome to WordPress Meta Trac! Thanks for the ticket. It's already possible to ping a plugin contributor (or any other WordPress.org user) by a username and ask them to take a look at the topic. Currently anyone can reply to any topic, what's the benefit of limiting that to a single person? That sounds more like a ticket system, forums generally don't work that way :) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2835#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 14:56:26 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 14:56:26 -0000 Subject: [wp-meta] [Making WordPress.org] #2834: Give plugin contributors the right to lock a topic, or... In-Reply-To: <050.e7617ae4910ad984e73d420dab714c0d@wordpress.org> References: <050.e7617ae4910ad984e73d420dab714c0d@wordpress.org> Message-ID: <065.d7194176732296a3fa50cd2201ce8d2d@wordpress.org> #2834: Give plugin contributors the right to lock a topic, or... ----------------------------+------------------------ Reporter: lapzor | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: Support Forums | Resolution: duplicate Keywords: | ----------------------------+------------------------ Changes (by SergeyBiryukov): * status: new => closed * resolution: => duplicate Comment: Hi @lapzor, welcome to WordPress Meta Trac! Thanks for the ticket. > Give plugin contributors the right to lock a topic in their plugins support forum We're already tracking this enhancement in #2598. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2834#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 15:02:21 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 15:02:21 -0000 Subject: [wp-meta] =?utf-8?q?=5BMaking_WordPress=2Eorg=5D_=232833=3A_A_lin?= =?utf-8?q?k_to_=E2=80=9CUnresolved_topics_for_this_plugin=E2=80=9D_displa?= =?utf-8?q?yed_to_plugin_contributors=2E?= In-Reply-To: <050.6143ae76b38ea6ef0c123b092eb36926@wordpress.org> References: <050.6143ae76b38ea6ef0c123b092eb36926@wordpress.org> Message-ID: <065.08446e3141efba2573c8b49bbd260a89@wordpress.org> #2833: A link to ?Unresolved topics for this plugin? displayed to plugin contributors. ----------------------------+------------------ Reporter: lapzor | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Comment (by SergeyBiryukov): Hi @lapzor, welcome to WordPress Meta Trac! Thanks for the ticket. I'm not sure I understand the suggestion, could you clarify a bit more? Where should the link be added? There's already an Unresolved Topics view for any plugin: https://wordpress.org/support/plugin/jetpack/unresolved/ -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2833#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 15:41:41 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 15:41:41 -0000 Subject: [wp-meta] =?utf-8?q?=5BMaking_WordPress=2Eorg=5D_=232833=3A_A_lin?= =?utf-8?q?k_to_=E2=80=9CUnresolved_topics_for_this_plugin=E2=80=9D_displa?= =?utf-8?q?yed_to_plugin_contributors=2E?= In-Reply-To: <050.6143ae76b38ea6ef0c123b092eb36926@wordpress.org> References: <050.6143ae76b38ea6ef0c123b092eb36926@wordpress.org> Message-ID: <065.c7d9ff471965ead6cd52c8fd2a079974@wordpress.org> #2833: A link to ?Unresolved topics for this plugin? displayed to plugin contributors. ----------------------------+------------------ Reporter: lapzor | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Comment (by jcastaneda): Both theme and plugins have those views by default as well. [[Image(plugin-views.png)]] [[Image(theme-views.png)]] Both are images of when a user is not signed on. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2833#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 15:52:52 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 15:52:52 -0000 Subject: [wp-meta] [Making WordPress.org] #2835: Assign topic to specific plugin contributor In-Reply-To: <050.44e1cb2a6a38c93fdbc4e979b7a1f158@wordpress.org> References: <050.44e1cb2a6a38c93fdbc4e979b7a1f158@wordpress.org> Message-ID: <065.3530c8c60245aeacda6843970c4a6094@wordpress.org> #2835: Assign topic to specific plugin contributor ----------------------------+------------------------- Reporter: lapzor | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: Support Forums | Resolution: worksforme Keywords: | ----------------------------+------------------------- Changes (by lapzor): * status: new => closed * resolution: => worksforme Comment: Replying to [comment:2 SergeyBiryukov]: > Hi @lapzor, welcome to WordPress Meta Trac! Thanks for the ticket. > > It's already possible to ping a plugin contributor (or any other WordPress.org user) by a username and ask them to take a look at the topic. Thanks, That will work :) > Currently anyone can reply to any topic, what's the benefit of limiting that to a single person? That sounds more like a ticket system, forums generally don't work that way :) Yes of course. I did not mean that others shouldn't be able to reply. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2835#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 15:53:40 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 15:53:40 -0000 Subject: [wp-meta] [Making WordPress.org] #2834: Give plugin contributors the right to lock a topic, or... In-Reply-To: <050.e7617ae4910ad984e73d420dab714c0d@wordpress.org> References: <050.e7617ae4910ad984e73d420dab714c0d@wordpress.org> Message-ID: <065.7252fdb45f60ce2b46bd35a35b739470@wordpress.org> #2834: Give plugin contributors the right to lock a topic, or... ----------------------------+------------------------ Reporter: lapzor | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: Support Forums | Resolution: duplicate Keywords: | ----------------------------+------------------------ Comment (by lapzor): thanks. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2834#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 15:55:07 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 15:55:07 -0000 Subject: [wp-meta] =?utf-8?q?=5BMaking_WordPress=2Eorg=5D_=232833=3A_A_lin?= =?utf-8?q?k_to_=E2=80=9CUnresolved_topics_for_this_plugin=E2=80=9D_displa?= =?utf-8?q?yed_to_plugin_contributors=2E?= In-Reply-To: <050.6143ae76b38ea6ef0c123b092eb36926@wordpress.org> References: <050.6143ae76b38ea6ef0c123b092eb36926@wordpress.org> Message-ID: <065.02f9359de581a795af01649c21bc2ada@wordpress.org> #2833: A link to ?Unresolved topics for this plugin? displayed to plugin contributors. ----------------------------+------------------------- Reporter: lapzor | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: Support Forums | Resolution: worksforme Keywords: | ----------------------------+------------------------- Changes (by lapzor): * status: new => closed * resolution: => worksforme Comment: Ah, I now see that i've been clicking on the wrong link, showing me all unresolved topics on the whole forum. Thanks :) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2833#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 21:23:56 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 21:23:56 -0000 Subject: [wp-meta] [Making WordPress.org] #2383: Add a meta field in the Sponsor CPT for Twitter handle In-Reply-To: <059.52fb31ba9390e59e798830d188b97820@wordpress.org> References: <059.52fb31ba9390e59e798830d188b97820@wordpress.org> Message-ID: <074.a2d84c7cb267748f98b169a5d29e0d2b@wordpress.org> #2383: Add a meta field in the Sponsor CPT for Twitter handle --------------------------------------+----------------------- Reporter: andreamiddleton | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: good-first-bug has-patch | --------------------------------------+----------------------- Changes (by chandrapatel): * keywords: good-first-bug needs-patch => good-first-bug has-patch Comment: HI @iandunn I've added `Twitter Handle:` meta field in Sponsor CPT. I've attached a patch. [https://meta.trac.wordpress.org/attachment/ticket/2383/2383.diff 2383.diff] Please check and let me know if it's fine. Thanks, -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2383#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sun May 21 13:51:02 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Sun, 21 May 2017 13:51:02 +0000 (UTC) Subject: [wp-meta] [5502] sites/trunk/wordpress.org/public_html/wp-content/plugins: Translate : Avoid PHP notices if a translation set doesn't exist. Message-ID: <20170521135102.3948B1080374@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170521/532d40bf/attachment-0001.html> From noreply at wordpress.org Sun May 21 14:20:50 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Sun, 21 May 2017 14:20:50 +0000 (UTC) Subject: [wp-meta] [5503] sites/trunk/wordpress.org/public_html/wp-content/plugins/ wporg-gp-routes/inc/routes/class-locale.php: Translate: Replace query for translation set slugs with a hardcoded list to fix performance issue. Message-ID: <20170521142050.9520B1080374@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170521/b70c0eb3/attachment.html> From noreply at wordpress.org Mon May 22 16:53:38 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 22 May 2017 16:53:38 +0000 (UTC) Subject: [wp-meta] [5504] sites/trunk: Trac: Link to the WordPress HackerOne program. Message-ID: <20170522165338.3395B1080409@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170522/7c5b2719/attachment.html> From noreply at wordpress.org Mon May 22 16:58:16 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 22 May 2017 16:58:16 +0000 (UTC) Subject: [wp-meta] [5505] sites/trunk/trac.wordpress.org/templates/site.html: Trac: Replace one more instance of the security@ email with a link to the WordPress HackerOne program. Message-ID: <20170522165816.E1E241080409@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170522/a28abaa2/attachment.html> From noreply at wordpress.org Mon May 22 20:18:11 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 22 May 2017 20:18:11 -0000 Subject: [wp-meta] [Making WordPress.org] #2383: Add a meta field in the Sponsor CPT for Twitter handle In-Reply-To: <059.52fb31ba9390e59e798830d188b97820@wordpress.org> References: <059.52fb31ba9390e59e798830d188b97820@wordpress.org> Message-ID: <074.10802341b7d1815b11562b8de6c7c380@wordpress.org> #2383: Add a meta field in the Sponsor CPT for Twitter handle --------------------------------------+----------------------- Reporter: andreamiddleton | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: good-first-bug has-patch | --------------------------------------+----------------------- Comment (by iandunn): That looks good, thanks! Eventually we'll also want to add a corresponding field to the `multi- event-sponsors` plugin, and copy the value from those global sponsors to the `wcpt` sponsor posts when new sites get created. [attachment:2383.diff] can be committed without that, though. We've got a backlog of patches to review and commit, but I've added this one to the list. Hoping to find some time soonish. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2383#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Mon May 22 21:09:14 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 22 May 2017 21:09:14 -0000 Subject: [wp-meta] [Making WordPress.org] #2820: Add Japanese meetups to event API In-Reply-To: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> References: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> Message-ID: <068.b93c1bbe4d0664f50a4ba7b65e50f99a@wordpress.org> #2820: Add Japanese meetups to event API -------------------------------------+----------------------- Reporter: mayukojpn | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: has-patch | -------------------------------------+----------------------- Comment (by coreymckrill): @mayukojpn I haven't been able to retrieve any events from the Doorkeeper API using either the URL format in the patch or the one in their [https://www.doorkeeperhq.com/developer/api API docs]. Example: https://api.doorkeeper.jp/events?group_id=2504&time=0,3m or https://api.doorkeeper.jp/groups/2504/events In the docs it says "API requests without authentication will fail", so I'm wondering if maybe you were able to get events because you were currently logged in with a Doorkeeper account, and I'm not? We may need to set up a WordPress.org Community Team account on Doorkeeper and get an API token to get this to work... cc @iandunn -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2820#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 04:50:28 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 04:50:28 -0000 Subject: [wp-meta] [Making WordPress.org] #2686: Plugin Search: Search should also take into account the number of ratings In-Reply-To: <051.6a8a8298224b7d93c0ff73de59c8a80c@wordpress.org> References: <051.6a8a8298224b7d93c0ff73de59c8a80c@wordpress.org> Message-ID: <066.3989118072a3003dbc9053ea35d2dd3b@wordpress.org> #2686: Plugin Search: Search should also take into account the number of ratings ------------------------------+------------------------------------------- Reporter: bfintal | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by bfintal): @gibrown Looks promising! -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2686#comment:12> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 07:41:08 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 07:41:08 -0000 Subject: [wp-meta] [Making WordPress.org] #2836: Plugin favorites no longer showing on main Plugin Direcotry page Message-ID: <051.43f189427900e3e173e246f713f14763@wordpress.org> #2836: Plugin favorites no longer showing on main Plugin Direcotry page ------------------------------+----------------- Reporter: ahortin | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Keywords: ------------------------------+----------------- Up until recently there was a link to your saved plugin favorites at the bottom of the main plugin directory page on WordPress.org. This link used to appear after the list of Featured & Popular plugins, but it no longer exists. This means that you can no longer get to your plugin favorites (when logged in), from the main plugin page. The only way to get to your favourites is by viewing your profile page, or by using one of the Featured/Popular links and then selecting the Favorites link. Can you please fix the plugin directory page so that this link is available as it was previously. Thanks. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2836> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 08:40:47 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 08:40:47 -0000 Subject: [wp-meta] [Making WordPress.org] #2836: Plugin favorites no longer showing on main Plugin Directory page (was: Plugin favorites no longer showing on main Plugin Direcotry page) In-Reply-To: <051.43f189427900e3e173e246f713f14763@wordpress.org> References: <051.43f189427900e3e173e246f713f14763@wordpress.org> Message-ID: <066.892d4ee61a1e904920f5dbda53dd81ca@wordpress.org> #2836: Plugin favorites no longer showing on main Plugin Directory page ------------------------------+------------------ Reporter: ahortin | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------ -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2836#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 08:49:14 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 08:49:14 -0000 Subject: [wp-meta] [Making WordPress.org] #2836: Plugin favorites no longer showing on main Plugin Directory page In-Reply-To: <051.43f189427900e3e173e246f713f14763@wordpress.org> References: <051.43f189427900e3e173e246f713f14763@wordpress.org> Message-ID: <066.4972f7d0b6e38d67b6b4901ced64a6c1@wordpress.org> #2836: Plugin favorites no longer showing on main Plugin Directory page ------------------------------+------------------------------------ Reporter: ahortin | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: needs-patch | ------------------------------+------------------------------------ Changes (by ocean90): * keywords: => needs-patch * milestone: => Plugin Directory v3.0 Comment: Broken since [5500]. The query on the front page isn't the main query so the custom query vars don't get applied. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2836#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 16:16:37 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 16:16:37 -0000 Subject: [wp-meta] [Making WordPress.org] #2837: Change the name of the forum "Plugins & Hacks" to "Plugins" Message-ID: <051.c114815ad2125dae8baef24415f3a6b7@wordpress.org> #2837: Change the name of the forum "Plugins & Hacks" to "Plugins" ---------------------+----------------- Reporter: Shelob9 | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: General | Keywords: ---------------------+----------------- Since most users probably think "hacks" relates to sites being hacked, not the precursor to plugins that was deprecated 10+ years ago and is removed from WordPress about 2 years ago, I propose that a better name for the forum for support with plugins and hacks would be better named "Plugins." I'm sure those users on WordPress 1.4 or earlier will figure it out. Related: https://core.trac.wordpress.org/changeset/34291 -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2837> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 16:21:26 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 16:21:26 -0000 Subject: [wp-meta] [Making WordPress.org] #2838: In WordPress.org notification matchers, show forum name. Message-ID: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> #2838: In WordPress.org notification matchers, show forum name. ---------------------+----------------- Reporter: Shelob9 | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: General | Keywords: ---------------------+----------------- When I get an email from WordPress.org matcher, it shows the top level forum, not the child forum. For example, this is an email I got because of the use of the word "caldera" but it's not from the Caldera Forms plugin support forum. I had to click on that to know it. [[Image(http://i.imgur.com/JtDUYKz.png)]] In my opinion, the fact that it is in one of the ~50k child forums of the Plugins and Hack forum is less useful then which child forum it is in. On WordPress.org, the breadcrumbs show `Support ? Plugin: Hustle - Pop-Ups, Slide-ins and Email Opt-ins ? Conflicts with Caldera forms` which would be a way more useful bit of information to put in the email. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2838> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 16:29:14 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 16:29:14 -0000 Subject: [wp-meta] [Making WordPress.org] #2837: Change the name of the forum "Plugins & Hacks" to "Plugins" In-Reply-To: <051.c114815ad2125dae8baef24415f3a6b7@wordpress.org> References: <051.c114815ad2125dae8baef24415f3a6b7@wordpress.org> Message-ID: <066.cc1fbab3948b6923b01cce9ec6e85cd7@wordpress.org> #2837: Change the name of the forum "Plugins & Hacks" to "Plugins" -------------------------+------------------ Reporter: Shelob9 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: | -------------------------+------------------ Changes (by Otto42): * type: defect => enhancement -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2837#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 16:29:24 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 16:29:24 -0000 Subject: [wp-meta] [Making WordPress.org] #2838: In WordPress.org notification matchers, show forum name. In-Reply-To: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> References: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> Message-ID: <066.e21b675a88d4cd2b13e8ba8c8e5a2996@wordpress.org> #2838: In WordPress.org notification matchers, show forum name. -------------------------+------------------ Reporter: Shelob9 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: | -------------------------+------------------ Changes (by Otto42): * type: defect => enhancement -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2838#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 18:01:28 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 18:01:28 -0000 Subject: [wp-meta] [Making WordPress.org] #596: Create plugin icons for all plugins In-Reply-To: <051.6d2fbeb076c9d5730e02db5deb4c01ec@wordpress.org> References: <051.6d2fbeb076c9d5730e02db5deb4c01ec@wordpress.org> Message-ID: <066.5303191a87a632973722640bf749fa77@wordpress.org> #596: Create plugin icons for all plugins -------------------------------------------------+------------------------- Reporter: iandunn | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: General | Resolution: Keywords: good-first-bug needs-ui dev- | feedback has-patch | -------------------------------------------------+------------------------- Comment (by karmatosed): @danieltj how is it going with this ticket? @alwaysbrightblue that would be ace to have you involved. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/596#comment:24> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 18:01:41 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 18:01:41 -0000 Subject: [wp-meta] [Making WordPress.org] #2815: Teams: Create Hosting Badge & Color In-Reply-To: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> References: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> Message-ID: <063.31f2157ab8fae45b2489ad0fc01e8eff@wordpress.org> #2815: Teams: Create Hosting Badge & Color -------------------------------------+--------------------- Reporter: mapk | Owner: Type: task | Status: closed Priority: high | Milestone: Component: Profiles | Resolution: fixed Keywords: 2nd-opinion ui-feedback | -------------------------------------+--------------------- Changes (by coreymckrill): * status: new => closed * resolution: => fixed Comment: Fixed with [dotorg13169] -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2815#comment:13> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 18:00:43 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 18:00:43 -0000 Subject: [wp-meta] [Making WordPress.org] #2813: Profiles: Add WP-CLI Badge In-Reply-To: <054.8af312384d284740d2f9848107f1b4bc@wordpress.org> References: <054.8af312384d284740d2f9848107f1b4bc@wordpress.org> Message-ID: <069.5a41099e247a12d5a9cab19718269342@wordpress.org> #2813: Profiles: Add WP-CLI Badge ------------------------+--------------------- Reporter: schlessera | Owner: Type: defect | Status: closed Priority: high | Milestone: Component: Profiles | Resolution: fixed Keywords: | ------------------------+--------------------- Changes (by coreymckrill): * status: new => closed * resolution: => fixed Comment: Fixed with [dotorg13168] -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2813#comment:8> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 18:04:28 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 18:04:28 -0000 Subject: [wp-meta] [Making WordPress.org] #1340: Update screenshot on wordpress.org front page In-Reply-To: <049.68b7cf5a29938f40626acc7e037f5c2a@wordpress.org> References: <049.68b7cf5a29938f40626acc7e037f5c2a@wordpress.org> Message-ID: <064.2d13720e87aaf13ffb4893fd030a5a5c@wordpress.org> #1340: Update screenshot on wordpress.org front page ----------------------+---------------------- Reporter: GaryJ | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: General | Resolution: invalid Keywords: needs-ui | ----------------------+---------------------- Changes (by karmatosed): * status: new => closed * resolution: => invalid Comment: Closing as the design has now changed. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1340#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 18:20:02 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 18:20:02 -0000 Subject: [wp-meta] [Making WordPress.org] #718: Increase Support Visibility with Orange In-Reply-To: <051.61a401c8ed63f81d912010103afb6165@wordpress.org> References: <051.61a401c8ed63f81d912010103afb6165@wordpress.org> Message-ID: <066.2e779aae7ce952af4bdbdca978c0284c@wordpress.org> #718: Increase Support Visibility with Orange ----------------------------------+------------------ Reporter: macmanx | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: needs-ui ui-feedback | ----------------------------------+------------------ Comment (by karmatosed): If there is data that we are causing people to get lost then +1 for making this more obvious. If thats not the case the I think not doing anything works well. @macmanx are you still finding this issue with the site changes? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/718#comment:15> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 18:32:03 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 18:32:03 -0000 Subject: [wp-meta] [Making WordPress.org] #718: Increase Support Visibility with Orange In-Reply-To: <051.61a401c8ed63f81d912010103afb6165@wordpress.org> References: <051.61a401c8ed63f81d912010103afb6165@wordpress.org> Message-ID: <066.697cf0e50d7db6dae74f1665f71fe343@wordpress.org> #718: Increase Support Visibility with Orange ----------------------------------+------------------ Reporter: macmanx | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: needs-ui ui-feedback | ----------------------------------+------------------ Comment (by macmanx): It's hard to say on that front @karmatosed As you noted, we don't really have any data. Anecdotally, the prior observation was made based on the amount of folks reaching out on IRC and even WordPress.com forums because they couldn't find the WordPress.org forums, as well as a number of "WordPress has no Support" blog posts and such that were going around. Since the re-design, incoming support topics seem to have decreased some, but the misdirection and statements of no support appear to have stopped. There's no data, so it's really impossible to say if that's related in any way. Leaving it as-is would probably be fine at this point. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/718#comment:16> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 20:10:38 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 20:10:38 -0000 Subject: [wp-meta] [Making WordPress.org] #718: Increase Support Visibility with Orange In-Reply-To: <051.61a401c8ed63f81d912010103afb6165@wordpress.org> References: <051.61a401c8ed63f81d912010103afb6165@wordpress.org> Message-ID: <066.50e59e899f926fc7250617257d183a23@wordpress.org> #718: Increase Support Visibility with Orange ----------------------------------+------------------------- Reporter: macmanx | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: General | Resolution: maybelater Keywords: needs-ui ui-feedback | ----------------------------------+------------------------- Changes (by karmatosed): * status: new => closed * resolution: => maybelater Comment: @macmanx ok, lets close this then. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/718#comment:17> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 20:36:07 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 20:36:07 -0000 Subject: [wp-meta] [Making WordPress.org] #2837: Change the name of the forum "Plugins & Hacks" to "Plugins" In-Reply-To: <051.c114815ad2125dae8baef24415f3a6b7@wordpress.org> References: <051.c114815ad2125dae8baef24415f3a6b7@wordpress.org> Message-ID: <066.ad187aa1e4266f0b81ec3e22b760ec78@wordpress.org> #2837: Change the name of the forum "Plugins & Hacks" to "Plugins" -------------------------+------------------ Reporter: Shelob9 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: | -------------------------+------------------ Comment (by Clorith): Where are you seeing any relation to this forum? We made it hidden last year with the forum upgrade (we can't actually outright remove it from existence, as it's the base location for all plugin support forums, but this shouldn't matter as no user will see it). -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2837#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 20:49:37 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 23 May 2017 20:49:37 +0000 (UTC) Subject: [wp-meta] [5506] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-plugins/page-developers.php: Plugin Directory: Update path for the example `readme.txt`. Message-ID: <20170523204937.32CC11080287@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170523/9e269712/attachment.html> From noreply at wordpress.org Tue May 23 20:52:58 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 20:52:58 -0000 Subject: [wp-meta] [Making WordPress.org] #2838: In WordPress.org notification matchers, show forum name. In-Reply-To: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> References: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> Message-ID: <066.d01d0467fbfa9d04a98acaa5b4ed1657@wordpress.org> #2838: In WordPress.org notification matchers, show forum name. -------------------------+------------------ Reporter: Shelob9 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: | -------------------------+------------------ Comment (by Otto42): > the fact that it is in one of the ~50k child forums of the Yeah... that's kind of a trick. We don't actually have 50k "child forums". They're all threads in one single forum. We're just showing you a "view" of that forum which only includes the relevant threads for the plugin in question. Not to say that the email could not be improved, but it's not as simple as that. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2838#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 22:21:02 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 22:21:02 -0000 Subject: [wp-meta] [Making WordPress.org] #2820: Add Japanese meetups to event API In-Reply-To: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> References: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> Message-ID: <068.07bbb2f4c9889625d62b08a61400adcc@wordpress.org> #2820: Add Japanese meetups to event API -------------------------------------+----------------------- Reporter: mayukojpn | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: has-patch | -------------------------------------+----------------------- Comment (by iandunn): Replying to [comment:3 coreymckrill]: > We may need to set up a WordPress.org Community Team account on Doorkeeper and get an API token to get this to work... That makes sense. Do you see any obstacles to doing that? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2820#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 22:21:53 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 22:21:53 -0000 Subject: [wp-meta] [Making WordPress.org] #2820: Add Japanese meetups to event API In-Reply-To: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> References: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> Message-ID: <068.08cd27547c3c118238285b27e88eb0ee@wordpress.org> #2820: Add Japanese meetups to event API -------------------------------------+----------------------- Reporter: mayukojpn | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: has-patch | -------------------------------------+----------------------- Comment (by coreymckrill): Update: I figured out how to get some events from the API. I signed up for a Doorkeeper account and got an API key, which allowed me to make authenticated requests. Anonymous requests are actually allowed also, but the request limit is very low, so if anyone else is making anonymous requests at the same time you might get locked out. I also discovered that of all the group IDs listed in the array, only '''Tokyo WordPress Mokumoku Club''' has any events. Is that the one that's part of the chapter program? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2820#comment:5> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 22:30:52 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 22:30:52 -0000 Subject: [wp-meta] [Making WordPress.org] #2820: Add Japanese meetups to event API In-Reply-To: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> References: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> Message-ID: <068.6ca66774ca997d888b114ac098f7b192@wordpress.org> #2820: Add Japanese meetups to event API -------------------------------------+----------------------- Reporter: mayukojpn | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: has-patch | -------------------------------------+----------------------- Comment (by coreymckrill): > Do you see any obstacles to doing that? We can probably just change the name/email address for the account I already created when the time comes. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2820#comment:6> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 23:00:52 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 23 May 2017 23:00:52 +0000 (UTC) Subject: [wp-meta] [5507] sites/trunk/api.wordpress.org/public_html/dotorg/github-sync/ feature-plugins.sh: Feature Plugins Github Sync: Bump the property later so that the no-files-changed check will correctly abort the update. Message-ID: <20170523230052.9A9CA1080287@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170523/c227b7df/attachment.html> From noreply at wordpress.org Wed May 24 00:30:40 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 00:30:40 -0000 Subject: [wp-meta] [Making WordPress.org] #2016: Subscription themes/plugins emails should include the theme/plugin name in the title In-Reply-To: <050.021524746837b0ca69dccfe332a72de6@wordpress.org> References: <050.021524746837b0ca69dccfe332a72de6@wordpress.org> Message-ID: <065.f2ec54e72cf18af8556125d405815a68@wordpress.org> #2016: Subscription themes/plugins emails should include the theme/plugin name in the title ----------------------------+------------------ Reporter: netweb | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: needs-patch | ----------------------------+------------------ Comment (by netweb): Related: #2838 -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2016#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 00:30:45 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 00:30:45 -0000 Subject: [wp-meta] [Making WordPress.org] #2838: In WordPress.org notification matchers, show forum name. In-Reply-To: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> References: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> Message-ID: <066.718a43be37fd65ffefff87e4d9b2372b@wordpress.org> #2838: In WordPress.org notification matchers, show forum name. -------------------------+------------------ Reporter: Shelob9 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: | -------------------------+------------------ Comment (by netweb): Related: #2016 -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2838#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 07:02:49 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 07:02:49 -0000 Subject: [wp-meta] [Making WordPress.org] #2837: Change the name of the forum "Plugins & Hacks" to "Plugins" In-Reply-To: <051.c114815ad2125dae8baef24415f3a6b7@wordpress.org> References: <051.c114815ad2125dae8baef24415f3a6b7@wordpress.org> Message-ID: <066.f22252a176a5cea68f8c11455ac59334@wordpress.org> #2837: Change the name of the forum "Plugins & Hacks" to "Plugins" ----------------------------+------------------ Reporter: Shelob9 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Changes (by SergeyBiryukov): * component: General => Support Forums -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2837#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 07:04:04 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 07:04:04 -0000 Subject: [wp-meta] [Making WordPress.org] #2838: In WordPress.org notification matchers, show forum name. In-Reply-To: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> References: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> Message-ID: <066.fe3aa94a2dc3c654371f9e2d22146c75@wordpress.org> #2838: In WordPress.org notification matchers, show forum name. ----------------------------+------------------ Reporter: Shelob9 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Changes (by SergeyBiryukov): * component: General => Support Forums -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2838#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 07:04:27 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 07:04:27 -0000 Subject: [wp-meta] [Making WordPress.org] #2838: In WordPress.org notification matchers, show forum name. In-Reply-To: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> References: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> Message-ID: <066.11c4c517d017f021d39b975165837450@wordpress.org> #2838: In WordPress.org notification matchers, show forum name. -------------------------+------------------ Reporter: Shelob9 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Profiles | Resolution: Keywords: | -------------------------+------------------ Changes (by SergeyBiryukov): * component: Support Forums => Profiles -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2838#comment:5> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 07:05:39 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 07:05:39 -0000 Subject: [wp-meta] [Making WordPress.org] #2837: Change the name of the forum "Plugins & Hacks" to "Plugins" In-Reply-To: <051.c114815ad2125dae8baef24415f3a6b7@wordpress.org> References: <051.c114815ad2125dae8baef24415f3a6b7@wordpress.org> Message-ID: <066.c8625fed667dc49171bdf6c54aa683c5@wordpress.org> #2837: Change the name of the forum "Plugins & Hacks" to "Plugins" ----------------------------+------------------ Reporter: Shelob9 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Comment (by SergeyBiryukov): Replying to [comment:2 Clorith]: > Where are you seeing any relation to this forum? It's still visible in notification emails, see #2838. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2837#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 11:28:02 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 11:28:02 -0000 Subject: [wp-meta] [Making WordPress.org] #200: "Download WordPress" button in header feels like a submit button for the search bar In-Reply-To: <053.e2aa5c22e12dc6e33fcf254e331ed8f5@wordpress.org> References: <053.e2aa5c22e12dc6e33fcf254e331ed8f5@wordpress.org> Message-ID: <068.eaccf3b06e8d28799521aba6ccf4644a@wordpress.org> #200: "Download WordPress" button in header feels like a submit button for the search bar -------------------------+------------------ Reporter: melchoyce | Owner: Type: enhancement | Status: new Priority: low | Milestone: Component: General | Resolution: Keywords: ui-feedback | -------------------------+------------------ Comment (by karmatosed): How about we get some ideas for what this could be? With the new design does anyone have some suggestions? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/200#comment:17> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 11:33:04 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 11:33:04 -0000 Subject: [wp-meta] [Making WordPress.org] #1173: 'Showcase' Not Responsive In-Reply-To: <054.880cf034fd82ff428c7b28a381084582@wordpress.org> References: <054.880cf034fd82ff428c7b28a381084582@wordpress.org> Message-ID: <069.0baa0e109b9cd622152565b4b0199a56@wordpress.org> #1173: 'Showcase' Not Responsive ----------------------------------------------+------------------ Reporter: atomicjack | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: ui-feedback needs-patch needs-ui | ----------------------------------------------+------------------ Comment (by karmatosed): @danetroup are you still interested in working on this? I would love to see if we can at least get this responsive. We do not need to change the design I feel at this point, just make what we have responsive. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1173#comment:8> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 11:35:43 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 11:35:43 -0000 Subject: [wp-meta] [Making WordPress.org] #2137: Full Reviews no longer show when looking at ratings. In-Reply-To: <051.fa4d463ecf1a348962cd4cbdefff3124@wordpress.org> References: <051.fa4d463ecf1a348962cd4cbdefff3124@wordpress.org> Message-ID: <066.b2de551c4cedb08d502a4000931c89ec@wordpress.org> #2137: Full Reviews no longer show when looking at ratings. -------------------------------------+------------------ Reporter: jdailey | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: ui-feedback ux-feedback | -------------------------------------+------------------ Changes (by karmatosed): * component: General => Plugin Directory Comment: I assume you are talking about the plugin directory here? Going to change the component to reflect this, let me know if not the case. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2137#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 11:36:45 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 11:36:45 -0000 Subject: [wp-meta] [Making WordPress.org] #1887: Site title should be a visible link In-Reply-To: <051.838a7d28e811bc68c9d8e0018f8f9f19@wordpress.org> References: <051.838a7d28e811bc68c9d8e0018f8f9f19@wordpress.org> Message-ID: <066.27782f6953abad568ac357cf42f2a262@wordpress.org> #1887: Site title should be a visible link -------------------------+---------------------- Reporter: La Geek | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: General | Resolution: wontfix Keywords: ux-feedback | -------------------------+---------------------- Changes (by karmatosed): * status: new => closed * resolution: => wontfix Comment: I think we are ok saying this is a design decision at this point, so closing. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1887#comment:10> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 14:57:12 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 14:57:12 -0000 Subject: [wp-meta] [Making WordPress.org] #2389: Move TOC to allow more space for the content In-Reply-To: <058.d3990b3f32e882e3f0da18968ec49800@wordpress.org> References: <058.d3990b3f32e882e3f0da18968ec49800@wordpress.org> Message-ID: <073.1abfacf7326af5f397632880aa38bdaa@wordpress.org> #2389: Move TOC to allow more space for the content -------------------------------------+------------------ Reporter: grapplerulrich | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Handbooks | Resolution: Keywords: ui-feedback ux-feedback | -------------------------------------+------------------ Comment (by karmatosed): @mapk what is the current state on this? Is it being rolled out, complete and ok to close? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2389#comment:13> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 17:20:42 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 24 May 2017 17:20:42 +0000 (UTC) Subject: [wp-meta] [5508] sites/trunk/common/includes/slack/announce/config.php: Slack Announce: Add users to whitelist Message-ID: <20170524172042.625621080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170524/714b2305/attachment.html> From noreply at wordpress.org Wed May 24 18:25:21 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 18:25:21 -0000 Subject: [wp-meta] [Making WordPress.org] #2383: Add a meta field in the Sponsor CPT for Twitter handle In-Reply-To: <059.52fb31ba9390e59e798830d188b97820@wordpress.org> References: <059.52fb31ba9390e59e798830d188b97820@wordpress.org> Message-ID: <074.0dedfa6465bec5b31e8bae3074d69cc7@wordpress.org> #2383: Add a meta field in the Sponsor CPT for Twitter handle --------------------------------------+----------------------- Reporter: andreamiddleton | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: good-first-bug has-patch | --------------------------------------+----------------------- Comment (by coreymckrill): In [changeset:"5509"]: {{{ #!CommitTicketReference repository="" revision="5509" WordCamp: Add Twitter Handle field to Sponsor CPT This commit adds the field to the Sponsor CPT on individual WC sites. A corresponding field in the `multi-event-sponsors` plugin still needs to be added. Refs #2383 Props chandrapatel }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2383#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 18:28:52 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 18:28:52 -0000 Subject: [wp-meta] [Making WordPress.org] #2383: Add a meta field in the Sponsor CPT for Twitter handle In-Reply-To: <059.52fb31ba9390e59e798830d188b97820@wordpress.org> References: <059.52fb31ba9390e59e798830d188b97820@wordpress.org> Message-ID: <074.09959f2300091139df6ce88227e89d56@wordpress.org> #2383: Add a meta field in the Sponsor CPT for Twitter handle ----------------------------------------+----------------------- Reporter: andreamiddleton | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: good-first-bug needs-patch | ----------------------------------------+----------------------- Changes (by coreymckrill): * keywords: good-first-bug has-patch => good-first-bug needs-patch Old description: > It would be a nice convenience for organizers if we had a field for a > sponsor's twitter handle, so it?s easier to tweet a thank you. This would > be particularly helpful in the case of global sponsors, but I could see a > use case for local sponsors as well. It would not need to be a required > field. New description: It would be a nice convenience for organizers if we had a field for a sponsor's twitter handle, so it?s easier to tweet a thank you. This would be particularly helpful in the case of global sponsors, but I could see a use case for local sponsors as well. It would not need to be a required field. '''Update:''' the Twitter Handle field has been added for the Sponsor CPT. A similar field still needs to be added to the `multi-event-sponsor` plugin, though. See [#3]. -- -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2383#comment:5> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 18:25:21 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 24 May 2017 18:25:21 +0000 (UTC) Subject: [wp-meta] [5509] sites/trunk/wordcamp.org/public_html/wp-content/plugins/ wc-post-types: WordCamp: Add Twitter Handle field to Sponsor CPT Message-ID: <20170524182521.438DA1080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170524/44ae38f0/attachment-0001.html> From noreply at wordpress.org Wed May 24 18:45:38 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 24 May 2017 18:45:38 +0000 (UTC) Subject: [wp-meta] [5510] sites/trunk/wordcamp.org/public_html/wp-content/plugins/wcpt/ wcpt-wordcamp/wordcamp-new-site.php: WordCamp: Update sponsorship link in Sponsors page content stub Message-ID: <20170524184538.3C2901080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170524/6560f63a/attachment.html> From noreply at wordpress.org Wed May 24 18:45:38 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 18:45:38 -0000 Subject: [wp-meta] [Making WordPress.org] #2579: Broken Multi Event Sponsorship Packages In-Reply-To: <052.808c278eee725572fc95dd92da28818a@wordpress.org> References: <052.808c278eee725572fc95dd92da28818a@wordpress.org> Message-ID: <067.16595ef2b9f72d7ce96605ce09465613@wordpress.org> #2579: Broken Multi Event Sponsorship Packages -------------------------------------+---------------------- Reporter: edpittol | Owner: iandunn Type: defect | Status: closed Priority: low | Milestone: Component: WordCamp Site & Plugins | Resolution: fixed Keywords: has-patch | -------------------------------------+---------------------- Changes (by coreymckrill): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"5510"]: {{{ #!CommitTicketReference repository="" revision="5510" WordCamp: Update sponsorship link in Sponsors page content stub This change also removes the link from the `gettext` string and inserts it via `sprintf` instead. Fixes #2579 Props edpittol, SergeyBiryukov }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2579#comment:5> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 19:44:21 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 19:44:21 -0000 Subject: [wp-meta] [Making WordPress.org] #2389: Move TOC to allow more space for the content In-Reply-To: <058.d3990b3f32e882e3f0da18968ec49800@wordpress.org> References: <058.d3990b3f32e882e3f0da18968ec49800@wordpress.org> Message-ID: <073.9f5bca5e3a97dad190ef99d1241bfc28@wordpress.org> #2389: Move TOC to allow more space for the content -------------------------------------+------------------ Reporter: grapplerulrich | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Handbooks | Resolution: Keywords: ui-feedback ux-feedback | -------------------------------------+------------------ Comment (by mapk): @karmatosed I think we're good to go, but it hasn't been implemented across the board. For example, the use case in the ticket subscription hasn't adopted the new design. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2389#comment:14> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 20:49:03 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 20:49:03 -0000 Subject: [wp-meta] [Making WordPress.org] #2826: Plugin Directory: Data not syncing/updating properly from SVN commits In-Reply-To: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> References: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> Message-ID: <068.eb367e4d20aff4b908688b13dac13c49@wordpress.org> #2826: Plugin Directory: Data not syncing/updating properly from SVN commits ------------------------------+--------------------- Reporter: brianhogg | Owner: Type: defect | Status: closed Priority: highest omg bbq | Milestone: Component: Plugin Directory | Resolution: fixed Keywords: | ------------------------------+--------------------- Comment (by brianhogg): @Otto42 After pushing an update today to The Events Calendar Shortcode, sites were showing the update as available but when trying to update you get a "Update Failed: Plugin update failed." message. After about 15 minutes it cleared up and the updates went through. Is this a related issue or should I open a new ticket? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2826#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 20:51:40 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 20:51:40 -0000 Subject: [wp-meta] [Making WordPress.org] #2826: Plugin Directory: Data not syncing/updating properly from SVN commits In-Reply-To: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> References: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> Message-ID: <068.4ebc5504dc64e2dcca787ee831ecc51d@wordpress.org> #2826: Plugin Directory: Data not syncing/updating properly from SVN commits ------------------------------+--------------------- Reporter: brianhogg | Owner: Type: defect | Status: closed Priority: highest omg bbq | Milestone: Component: Plugin Directory | Resolution: fixed Keywords: | ------------------------------+--------------------- Comment (by Otto42): @brianhogg It is a related issue, and we know the cause. It will be fixed soon, but in the meantime, that window you noticed tends to be much shorter, on the scale of 2-3 minutes or so. The window will disappear entirely when the underlying problem is corrected. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2826#comment:5> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 22:15:53 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 22:15:53 -0000 Subject: [wp-meta] [Making WordPress.org] #2832: Search result not working properly In-Reply-To: <057.58ee2aeb07cce0d41b56ca0079fe0edf@wordpress.org> References: <057.58ee2aeb07cce0d41b56ca0079fe0edf@wordpress.org> Message-ID: <072.1c9c3f23e1296c14fe0dd684399dcbfd@wordpress.org> #2832: Search result not working properly ---------------------------------------+------------------------ Reporter: karan.gadhavi | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Plugin Directory | Resolution: duplicate Keywords: 2nd-opinion needs-testing | ---------------------------------------+------------------------ Changes (by gibrown): * status: new => closed * resolution: => duplicate * milestone: Plugin Directory v3.0 => Comment: This is another good example where the ranking can be adjusted a little bit for #2642 Link to the full results: https://wordpress.org/plugins/search/Facebook+Events/ I'm going to mark this as a duplicate since that other ticket is tracking the same thing. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2832#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 22:41:12 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 24 May 2017 22:41:12 +0000 (UTC) Subject: [wp-meta] [5511] sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory/shortcodes/class-upload.php: Plugin directory: list author's pending plugins on Add page, to reduce duplicate uploads. Message-ID: <20170524224112.1E3DA1080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170524/8fee1ddc/attachment-0001.html> From noreply at wordpress.org Wed May 24 22:41:12 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 22:41:12 -0000 Subject: [wp-meta] [Making WordPress.org] #2594: Plugin Directory: List pending plugins on 'add' page In-Reply-To: <051.8682691f18de896a37086227c227a3cc@wordpress.org> References: <051.8682691f18de896a37086227c227a3cc@wordpress.org> Message-ID: <066.cba99dbc3e2d7261a7fcbe7770c832e1@wordpress.org> #2594: Plugin Directory: List pending plugins on 'add' page ----------------------------------------------+---------------------------- Reporter: Ipstenu | Owner: tellyworth Type: enhancement | Status: closed Priority: normal | Milestone: Plugin Component: Plugin Directory | Directory v3.0 Keywords: has-patch commit has-screenshots | Resolution: fixed ----------------------------------------------+---------------------------- Changes (by tellyworth): * owner: => tellyworth * status: new => closed * resolution: => fixed Comment: In [changeset:"5511"]: {{{ #!CommitTicketReference repository="" revision="5511" Plugin directory: list author's pending plugins on Add page, to reduce duplicate uploads. Fixes #2594 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2594#comment:10> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 22:50:47 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 24 May 2017 22:50:47 +0000 (UTC) Subject: [wp-meta] [5512] sites/trunk/wordcamp.org/public_html/wp-content/plugins: WordCamp: Add organizer reminder trigger for pre-planning status Message-ID: <20170524225047.CA14B1080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170524/cb5903da/attachment.html> From noreply at wordpress.org Wed May 24 22:50:48 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 22:50:48 -0000 Subject: [wp-meta] [Making WordPress.org] #2346: WordCamp pre-planning status trigger In-Reply-To: <048.4c1f8a874991d1961b287cb2cbd1b048@wordpress.org> References: <048.4c1f8a874991d1961b287cb2cbd1b048@wordpress.org> Message-ID: <063.298b23732119b9445c6530362e223d1b@wordpress.org> #2346: WordCamp pre-planning status trigger -------------------------------------+---------------------- Reporter: nvwd | Owner: iandunn Type: enhancement | Status: closed Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: fixed Keywords: has-patch | -------------------------------------+---------------------- Changes (by coreymckrill): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"5512"]: {{{ #!CommitTicketReference repository="" revision="5512" WordCamp: Add organizer reminder trigger for pre-planning status Fixes #2346 Props nvwd }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2346#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 23:38:13 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 23:38:13 -0000 Subject: [wp-meta] [Making WordPress.org] #2839: Update Twemoji on CDN to 2.3.0 Message-ID: <057.ebf0d9b54fb832c6e642f24d69981158@wordpress.org> #2839: Update Twemoji on CDN to 2.3.0 ---------------------------+----------------- Reporter: peterwilsoncc | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: General | Keywords: ---------------------------+----------------- Twemoji 2.3.0 was released overnight to support Emoji 5 Diff https://github.com/twitter/twemoji/compare/v2.2.5...v2.3.0 This includes modifications to existing emoji so will require a new directory on the CDN. Related core ticket https://core.trac.wordpress.org/ticket/40858 -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2839> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 23:42:00 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 24 May 2017 23:42:00 +0000 (UTC) Subject: [wp-meta] [5513] sites/trunk/wordcamp.org/public_html/wp-content/plugins: WordCamp: Remove non-functional organizer reminder trigger Message-ID: <20170524234200.BCEB21080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170524/0c660512/attachment-0001.html> From noreply at wordpress.org Thu May 25 00:23:54 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 25 May 2017 00:23:54 +0000 (UTC) Subject: [wp-meta] [5514] sites/trunk/common/includes/slack/announce/config.php: Slack: Give WCEU Happiness Bar Wranglers announce in their channel. Message-ID: <20170525002354.940A010805A0@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170525/92628ac7/attachment.html> From noreply at wordpress.org Thu May 25 01:11:00 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 25 May 2017 01:11:00 +0000 (UTC) Subject: [wp-meta] [5515] sites/trunk/trac.wordpress.org/templates/core/site-specific.html: Trac: Add the focus leads as committers, and tidy up some old titles. Message-ID: <20170525011100.7EDDD10805A0@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170525/1e7d24f2/attachment.html> From noreply at wordpress.org Thu May 25 01:28:33 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 01:28:33 -0000 Subject: [wp-meta] [Making WordPress.org] #2839: Update Twemoji on CDN to 2.3.0 In-Reply-To: <057.ebf0d9b54fb832c6e642f24d69981158@wordpress.org> References: <057.ebf0d9b54fb832c6e642f24d69981158@wordpress.org> Message-ID: <072.d19b81ebd308ecb89f366ee0ce005150@wordpress.org> #2839: Update Twemoji on CDN to 2.3.0 ---------------------------+--------------------- Reporter: peterwilsoncc | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: General | Resolution: Keywords: | ---------------------------+--------------------- Changes (by Otto42): * status: new => closed * type: defect => enhancement Comment: We don't really need a separate meta ticket for this, I feel. The existing core ticket to track the changes is fine, since it needs to be synced with core there anyway. One problem, one ticket. Marking as duplicate. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2839#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 02:27:07 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 25 May 2017 02:27:07 +0000 (UTC) Subject: [wp-meta] [5516] sites/trunk/common/includes/slack/announce/config.php: Slack: Revert [5514], because private channels don't need to be whitelisted. Message-ID: <20170525022708.06DF310805A0@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170525/3994772f/attachment-0001.html> From noreply at wordpress.org Thu May 25 11:10:02 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 11:10:02 -0000 Subject: [wp-meta] [Making WordPress.org] #2788: Plugin Directory: Clarify language for submission errors (was: Plugin Direction: Clarify language for submission errors) In-Reply-To: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> References: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> Message-ID: <066.e598dfe55d3f974e69bbec4a8d785420@wordpress.org> #2788: Plugin Directory: Clarify language for submission errors ------------------------------+------------------------- Reporter: Ipstenu | Owner: tellyworth Type: enhancement | Status: reopened Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: needs-patch | ------------------------------+------------------------- -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2788#comment:5> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 11:50:24 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 11:50:24 -0000 Subject: [wp-meta] [Making WordPress.org] #2137: Full Reviews no longer show when looking at ratings. In-Reply-To: <051.fa4d463ecf1a348962cd4cbdefff3124@wordpress.org> References: <051.fa4d463ecf1a348962cd4cbdefff3124@wordpress.org> Message-ID: <066.787dffb3161c76928a3f9ce0300ddc14@wordpress.org> #2137: Full Reviews no longer show when looking at ratings. -------------------------------------+------------------ Reporter: jdailey | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: ui-feedback ux-feedback | -------------------------------------+------------------ Changes (by SergeyBiryukov): * component: Plugin Directory => Support Forums Comment: It's about the Support Forums theme. The old one used to show review text in general list: [attachment:2137.PNG], the new one doesn't: [attachment:2137.2.PNG]. That said, the new plugin directory currently displays the latest reviews on the plugin page: [attachment:2137.3.PNG], although that might be changed in #2632. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2137#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 12:04:41 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 12:04:41 -0000 Subject: [wp-meta] [Making WordPress.org] #2677: Plugin Directory: Admin email subjects to plugin author (s) improvements In-Reply-To: <051.76e30163c28c8e10b716b6642fdc91d1@wordpress.org> References: <051.76e30163c28c8e10b716b6642fdc91d1@wordpress.org> Message-ID: <066.05595a7bda691e4dea630fc3d0694fef@wordpress.org> #2677: Plugin Directory: Admin email subjects to plugin author (s) improvements ------------------------------+------------------------------------ Reporter: Ipstenu | Owner: tellyworth Type: enhancement | Status: reopened Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch commit | ------------------------------+------------------------------------ Changes (by SergeyBiryukov): * milestone: => Plugin Directory v3.0 Comment: [attachment:2677.4.diff] switches to Yoda conditions, as per WP coding standards and for consistency with the check a few lines above. Moving to v3.0, as the ticket already has a commit that just needs a follow-up. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2677#comment:5> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 12:19:55 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 12:19:55 -0000 Subject: [wp-meta] [Making WordPress.org] #2788: Plugin Directory: Clarify language for submission errors In-Reply-To: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> References: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> Message-ID: <066.c410a2e10be321fa0bc288a1436e177b@wordpress.org> #2788: Plugin Directory: Clarify language for submission errors ------------------------------+------------------------------------ Reporter: Ipstenu | Owner: tellyworth Type: enhancement | Status: reopened Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------ Changes (by SergeyBiryukov): * keywords: needs-patch => has-patch * milestone: => Plugin Directory v3.0 Comment: [attachment:2788.4.diff] switches the email address to a placeholder and updates translator comments, as per comment:2. Moving to v3.0, as the ticket already has a commit that just needs a follow-up. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2788#comment:6> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 12:55:52 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 12:55:52 -0000 Subject: [wp-meta] [Making WordPress.org] #2830: Plugin Directory: Include slug in submission emails In-Reply-To: <051.980ca4c7bb6bb49acc9857d3105e0019@wordpress.org> References: <051.980ca4c7bb6bb49acc9857d3105e0019@wordpress.org> Message-ID: <066.66deb491ce281193e1337cd1a3f04c25@wordpress.org> #2830: Plugin Directory: Include slug in submission emails ------------------------------+------------------ Reporter: Ipstenu | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------ Comment (by SergeyBiryukov): [attachment:2830.2.diff] updates translator comments. [attachment:2830.3.diff] is a combined patch with the changes from #2788, as they have some overlap. Whichever one gets committed first, should fix the other one as well :) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2830#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 12:56:10 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 12:56:10 -0000 Subject: [wp-meta] [Making WordPress.org] #2788: Plugin Directory: Clarify language for submission errors In-Reply-To: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> References: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> Message-ID: <066.b0aa0f03c93dff2f0177a7c4d6e2b166@wordpress.org> #2788: Plugin Directory: Clarify language for submission errors ------------------------------+------------------------------------ Reporter: Ipstenu | Owner: tellyworth Type: enhancement | Status: reopened Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------ Comment (by SergeyBiryukov): [attachment:2788.5.diff] is a combined patch with the changes from #2830, as they have some overlap. Whichever one gets committed first, should fix the other one as well :) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2788#comment:7> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 13:14:58 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 13:14:58 -0000 Subject: [wp-meta] [Making WordPress.org] #2618: Plugin Directory: Translation needed banner omits language In-Reply-To: <051.eed73691dd5ba0b981c0645fe16da796@wordpress.org> References: <051.eed73691dd5ba0b981c0645fe16da796@wordpress.org> Message-ID: <066.60ebc2d6ce860cf1f0cf7232876f8775@wordpress.org> #2618: Plugin Directory: Translation needed banner omits language ------------------------------+------------------------------------------- Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------------- Comment (by SergeyBiryukov): @ocean90: Anything I can do to help move [attachment:2618.2.patch] forward? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2618#comment:8> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 13:15:31 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 13:15:31 -0000 Subject: [wp-meta] [Making WordPress.org] #2781: Plugin Directory: Add translator comments for placeholders in Stats Report tool In-Reply-To: <058.03697759c32f7f3c720db10da4f5a581@wordpress.org> References: <058.03697759c32f7f3c720db10da4f5a581@wordpress.org> Message-ID: <073.c936f0c22d13e1f8bd0e5d8b1bcb56d6@wordpress.org> #2781: Plugin Directory: Add translator comments for placeholders in Stats Report tool ------------------------------+------------------ Reporter: SergeyBiryukov | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------ Comment (by SergeyBiryukov): @ocean90: Anything I can do to help move [attachment:2781.patch] forward? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2781#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 13:23:01 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 13:23:01 -0000 Subject: [wp-meta] [Making WordPress.org] #2590: Enhance compatibility with per forum moderators In-Reply-To: <051.ef2c0624040c63d1e71b94d15700a274@wordpress.org> References: <051.ef2c0624040c63d1e71b94d15700a274@wordpress.org> Message-ID: <066.fe965a7b0d994e071b4de1e18bf0771a@wordpress.org> #2590: Enhance compatibility with per forum moderators ------------------------------+------------------ Reporter: ocean90 | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: has-patch commit | ------------------------------+------------------ Comment (by SergeyBiryukov): @ocean90: Anything I can do to help move [attachment:2590.3.diff] forward? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2590#comment:8> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 16:32:09 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 16:32:09 -0000 Subject: [wp-meta] [Making WordPress.org] #2840: Abuse of popular list due to active installs count Message-ID: <057.09bf642953cbca24bb8745640714e0dc@wordpress.org> #2840: Abuse of popular list due to active installs count -----------------------------+----------------- Reporter: thinkupthemes | Owner: Type: defect | Status: new Priority: low | Milestone: Component: Theme Directory | Keywords: -----------------------------+----------------- There is possible abuse of the popular list by theme authors due to how active installs are counted. The popular theme list takes account of the active installs count based on the number of active installs over the past 2 weeks (I believe). Authors are able to abuse this submitting themes which have the same name as themes distributed elsewhere. It appears this issue is not best managed by the theme review team on a case by case basis due to the subjective nature of the issue. Having a check in place to ensure that the theme being counted when ranking is that which was distributed from .org, as opposed to some 3rd party platform will help combat this issue. A previous ticket was raised for this similar issue, however was subsequently closed: https://meta.trac.wordpress.org/ticket/2114 Thanks. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2840> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 16:43:53 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 16:43:53 -0000 Subject: [wp-meta] [Making WordPress.org] #2840: Abuse of popular list due to active installs count In-Reply-To: <057.09bf642953cbca24bb8745640714e0dc@wordpress.org> References: <057.09bf642953cbca24bb8745640714e0dc@wordpress.org> Message-ID: <072.360acc040dd464f314b3a0db4f6b8678@wordpress.org> #2840: Abuse of popular list due to active installs count -----------------------------+------------------------ Reporter: thinkupthemes | Owner: Type: defect | Status: closed Priority: low | Milestone: Component: Theme Directory | Resolution: duplicate Keywords: | -----------------------------+------------------------ Changes (by ocean90): * status: new => closed * resolution: => duplicate Comment: #2114 is still open. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2840#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 17:05:22 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 17:05:22 -0000 Subject: [wp-meta] [Making WordPress.org] #2114: Possible abuse on popular themes list based on active installs In-Reply-To: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org> References: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org> Message-ID: <066.2a3220a18da616afd53730334f84a4c6@wordpress.org> #2114: Possible abuse on popular themes list based on active installs -----------------------------+------------------ Reporter: acosmin | Owner: Type: defect | Status: new Priority: low | Milestone: Component: Theme Directory | Resolution: Keywords: close | -----------------------------+------------------ Comment (by MH Themes): Regarding the popular list issue like pointed out by @thinkupthemes in ticket #2840, wouldn't it already help if the time parameter in the algorithm would be adjusted? At the moment new themes will appear on the popular list after 2 weeks. You could for example adjust this to 3 months, that way it would be much harder to game the system because while it's quite easy to get 2-3k active installs, it's much harder to get 10-20k. Usually after 3 months most of the new themes with only 2-3k active installs rank already much lower because they fail to attract more users. So if you adjust the algorithm from 2 weeks to 3 months, that would possibly prevent new themes with only 2-3k active installs to appear in the top spots on the popular list right after release. If these themes really become popular and achieve 10-20k active installs or more, then they will rank accordingly anyway. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2114#comment:14> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 17:45:35 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 17:45:35 -0000 Subject: [wp-meta] [Making WordPress.org] #2389: Move TOC to allow more space for the content In-Reply-To: <058.d3990b3f32e882e3f0da18968ec49800@wordpress.org> References: <058.d3990b3f32e882e3f0da18968ec49800@wordpress.org> Message-ID: <073.c7fc523a9c5367118a718ab79ce594a1@wordpress.org> #2389: Move TOC to allow more space for the content -------------------------------------+------------------ Reporter: grapplerulrich | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Handbooks | Resolution: Keywords: ui-feedback ux-feedback | -------------------------------------+------------------ Comment (by karmatosed): @mapk cool...so how should we go about doing that? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2389#comment:15> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 17:58:32 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 17:58:32 -0000 Subject: [wp-meta] [Making WordPress.org] #2389: Move TOC to allow more space for the content In-Reply-To: <058.d3990b3f32e882e3f0da18968ec49800@wordpress.org> References: <058.d3990b3f32e882e3f0da18968ec49800@wordpress.org> Message-ID: <073.81073c05648061dd8d928632cdcb9474@wordpress.org> #2389: Move TOC to allow more space for the content -------------------------------------+------------------ Reporter: grapplerulrich | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Handbooks | Resolution: Keywords: ui-feedback ux-feedback | -------------------------------------+------------------ Comment (by mapk): Replying to [comment:15 karmatosed]: > @mapk cool...so how should we go about doing that? I'm really not sure. Either @samuelsidler helped with that, or the team contributors did. Maybe @pento or @coffee2code might have an idea? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2389#comment:16> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 18:05:11 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 25 May 2017 18:05:11 +0000 (UTC) Subject: [wp-meta] [5517] sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/ security.php: Security: Send `X-Frame-Origins` on the front end to mitigate clickjacking Message-ID: <20170525180511.F41501080287@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170525/8abd5de5/attachment.html> From noreply at wordpress.org Thu May 25 19:36:19 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 25 May 2017 19:36:19 +0000 (UTC) Subject: [wp-meta] [5518] sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/ wcorg-misc.php: WordCamp: Load `wordcamporg` text domain based on user locale Message-ID: <20170525193619.2DB511080287@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170525/e45978ff/attachment.html> From noreply at wordpress.org Thu May 25 20:39:45 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 20:39:45 -0000 Subject: [wp-meta] [Making WordPress.org] #2389: Move TOC to allow more space for the content In-Reply-To: <058.d3990b3f32e882e3f0da18968ec49800@wordpress.org> References: <058.d3990b3f32e882e3f0da18968ec49800@wordpress.org> Message-ID: <073.991bf0d65bcd33768c3a74c4197ed34b@wordpress.org> #2389: Move TOC to allow more space for the content -------------------------------------+------------------ Reporter: grapplerulrich | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Handbooks | Resolution: Keywords: ui-feedback ux-feedback | -------------------------------------+------------------ Comment (by samuelsidler): Looks like we need a patch for devhub. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2389#comment:17> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 22:08:07 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 22:08:07 -0000 Subject: [wp-meta] [Making WordPress.org] #2836: Plugin favorites no longer showing on main Plugin Directory page In-Reply-To: <051.43f189427900e3e173e246f713f14763@wordpress.org> References: <051.43f189427900e3e173e246f713f14763@wordpress.org> Message-ID: <066.8d41ac3025b98bb68f5324fb9175c908@wordpress.org> #2836: Plugin favorites no longer showing on main Plugin Directory page ------------------------------+------------------------------------ Reporter: ahortin | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------ Changes (by SergeyBiryukov): * keywords: needs-patch => has-patch Comment: [attachment:2836.patch] replaces [5500] with a more targeted fix. Double-checked to make sure it doesn't introduces any regressions in #2594 or #2787. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2836#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 23:24:16 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 23:24:16 -0000 Subject: [wp-meta] [Making WordPress.org] #2788: Plugin Directory: Clarify language for submission errors In-Reply-To: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> References: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> Message-ID: <066.d1c24e770bc7f73c273af63c1a004ba6@wordpress.org> #2788: Plugin Directory: Clarify language for submission errors ------------------------------+------------------------------------ Reporter: Ipstenu | Owner: tellyworth Type: enhancement | Status: reopened Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------ Comment (by SergeyBiryukov): [attachment:2788.6.diff] is the same as [attachment:2788.5.diff], but with raw email address converted to a `mailto:` link for better UX. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2788#comment:8> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 23:25:36 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 23:25:36 -0000 Subject: [wp-meta] [Making WordPress.org] #2830: Plugin Directory: Include slug in submission emails In-Reply-To: <051.980ca4c7bb6bb49acc9857d3105e0019@wordpress.org> References: <051.980ca4c7bb6bb49acc9857d3105e0019@wordpress.org> Message-ID: <066.0eac630f669726e9b6d4390c997263af@wordpress.org> #2830: Plugin Directory: Include slug in submission emails ------------------------------+------------------ Reporter: Ipstenu | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------ Comment (by SergeyBiryukov): [attachment:2830.4.diff] is the same as [attachment:2830.3.diff], but with raw email address converted to a `mailto:` link for better UX. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2830#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 23:51:22 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 23:51:22 -0000 Subject: [wp-meta] [Making WordPress.org] #2830: Plugin Directory: Include slug in submission emails In-Reply-To: <051.980ca4c7bb6bb49acc9857d3105e0019@wordpress.org> References: <051.980ca4c7bb6bb49acc9857d3105e0019@wordpress.org> Message-ID: <066.24703561bcac40a67312f59163c6a0aa@wordpress.org> #2830: Plugin Directory: Include slug in submission emails ------------------------------+------------------ Reporter: Ipstenu | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------ Comment (by SergeyBiryukov): The new message looks like a wall of text: [attachment:2830.PNG]. [attachment:2830.5.diff] splits it into several paragraphs to make it more readable: [attachment:2830.paragraphs.PNG]. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2830#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 00:28:32 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 00:28:32 -0000 Subject: [wp-meta] [Making WordPress.org] #2821: Plugin Directory: Plugin slug should be Latin Characters Only In-Reply-To: <051.25e027265662218e64083f79ba18e777@wordpress.org> References: <051.25e027265662218e64083f79ba18e777@wordpress.org> Message-ID: <066.7934863b69a1d9c0f6b828cc6feaeec4@wordpress.org> #2821: Plugin Directory: Plugin slug should be Latin Characters Only ------------------------------+------------------ Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------ Changes (by SergeyBiryukov): * keywords: needs-patch => has-patch Comment: [attachment:2821.patch] replaces `sanitize_title_with_dashes()` with `sanitize_title()`, which includes `remove_accents()`. This doesn't cover Cyrillic/Arabic/Hebrew/Japanese characters ? do we need to block those as well, or removing accents would be good enough for now? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2821#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 00:37:03 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Fri, 26 May 2017 00:37:03 +0000 (UTC) Subject: [wp-meta] [5519] sites/trunk/trac.wordpress.org/templates/core/site-specific.html: Trac: Add aaroncampbell's long overdue Core Committer badge. Message-ID: <20170526003703.68C4F108053D@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170526/99760c0c/attachment.html> From noreply at wordpress.org Fri May 26 01:03:55 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 01:03:55 -0000 Subject: [wp-meta] [Making WordPress.org] #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ In-Reply-To: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> References: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> Message-ID: <065.0a1bcdfe6a8f2ada8419e6bc66511b1e@wordpress.org> #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ ----------------------------------------+----------------------- Reporter: netweb | Owner: iandunn Type: enhancement | Status: reopened Priority: low | Milestone: Component: General | Resolution: Keywords: needs-patch good-first-bug | ----------------------------------------+----------------------- Comment (by coreymckrill): > change the SVN URLs to be wrapped in code blocks so they are also easily cut & pastable How about something like the above? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1103#comment:21> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 01:16:22 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 01:16:22 -0000 Subject: [wp-meta] [Making WordPress.org] #2800: Plugin Directory: Ask for confirmation before removing someone as a committer In-Reply-To: <054.334261ed8da287672092be0c6c8fe2d4@wordpress.org> References: <054.334261ed8da287672092be0c6c8fe2d4@wordpress.org> Message-ID: <069.29a1740a4f563b5840c89cfc5b71ee7d@wordpress.org> #2800: Plugin Directory: Ask for confirmation before removing someone as a committer ------------------------------+------------------ Reporter: Nikschavan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------ Comment (by SergeyBiryukov): [attachment:2800.2.diff] uses an existing string from [source:sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin- directory/admin/class-customizations.php?rev=5335&marks=114#L105 Customizations::enqueue_assets()], which already has this confirmation when removing a committer on Edit Plugin page in the admin. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2800#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 10:04:05 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 10:04:05 -0000 Subject: [wp-meta] [Making WordPress.org] #2114: Possible abuse on popular themes list based on active installs In-Reply-To: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org> References: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org> Message-ID: <066.4bd9256fb58ca2afa26d223bf691210f@wordpress.org> #2114: Possible abuse on popular themes list based on active installs -----------------------------+------------------ Reporter: acosmin | Owner: Type: defect | Status: new Priority: low | Milestone: Component: Theme Directory | Resolution: Keywords: close | -----------------------------+------------------ Comment (by ThemeZee): Adding new themes to the popular list not until after three months is a disadvantage for all new themes, not just the ones with naming conflicts and gaming the system. Right now it is only a great advantage for new themes if they already have active installs before going live. It does not matter if these come from a different theme with the same name or from an existing user base. I would therefore measure the growth of active installs, not the total amount, as @ionutn said: - Save the initial active install count when theme gets live - Calculate active installs from day two with the difference of initial and current active installs -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2114#comment:15> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 10:12:15 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 10:12:15 -0000 Subject: [wp-meta] [Making WordPress.org] #2114: Possible abuse on popular themes list based on active installs In-Reply-To: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org> References: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org> Message-ID: <066.c1c0378e5487da943667a6a517857452@wordpress.org> #2114: Possible abuse on popular themes list based on active installs -----------------------------+------------------ Reporter: acosmin | Owner: Type: defect | Status: new Priority: low | Milestone: Component: Theme Directory | Resolution: Keywords: close | -----------------------------+------------------ Comment (by MH Themes): In general I think it's inappropriate to rank brand-new themes with a bunch of active installs (2-3k) in the ''Top 10-20'' on the popular list. These are not popular themes, they are trending, if at all. But users who don't know about these issues may think these themes are the best what .org has to offer and start using these themes even more which will keep these new themes high in the popular list based on a flaw in the algorithm. It's a self-fulfilling prophecy. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2114#comment:16> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 13:43:32 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 13:43:32 -0000 Subject: [wp-meta] [Making WordPress.org] #2700: Plugin Directory: Improve quality of automated emails and messages for submissions In-Reply-To: <051.597732bb57c7e553445129eb5c2ae020@wordpress.org> References: <051.597732bb57c7e553445129eb5c2ae020@wordpress.org> Message-ID: <066.f760cefc5b5c8aed140f62f800c3727b@wordpress.org> #2700: Plugin Directory: Improve quality of automated emails and messages for submissions -------------------------------------+------------------------------------ Reporter: Ipstenu | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch needs-refresh | -------------------------------------+------------------------------------ Changes (by SergeyBiryukov): * keywords: has-patch commit => has-patch needs-refresh Comment: Needs a refresh after [5471], but there's also some overlap with #2788 and #2830, so I guess I'd wait for those tickets to be committed rather than refresh several times. Seeing simple text changes like this taking weeks to commit is not exactly encouraging, luckily there's plenty of other tickets to work on in the meantime :) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2700#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 14:52:30 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 14:52:30 -0000 Subject: [wp-meta] [Making WordPress.org] #2796: Plugin Directory Admin: Limit State Switching for Plugin Statuses In-Reply-To: <051.ad8639951baef0ece119c495143919d3@wordpress.org> References: <051.ad8639951baef0ece119c495143919d3@wordpress.org> Message-ID: <066.d4abdaad39f792e7406828fb799f9aa4@wordpress.org> #2796: Plugin Directory Admin: Limit State Switching for Plugin Statuses ------------------------------+------------------ Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------ Changes (by SergeyBiryukov): * keywords: => has-patch Comment: [attachment:2796.patch] implements the described flow, including Rejected ? Pending. This first pass only works on Edit Plugin page, and doesn't cover the Status dropdown in Quick Edit (haven't found a non-hacky way to replace it yet). Maybe Quick Edit should be disabled for plugins altogether? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2796#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 15:37:59 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 15:37:59 -0000 Subject: [wp-meta] [Making WordPress.org] #2821: Plugin Directory: Plugin slug should be Latin Characters Only In-Reply-To: <051.25e027265662218e64083f79ba18e777@wordpress.org> References: <051.25e027265662218e64083f79ba18e777@wordpress.org> Message-ID: <066.2c2512f8761701931ffcf577e88d4039@wordpress.org> #2821: Plugin Directory: Plugin slug should be Latin Characters Only ------------------------------+------------------ Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------ Comment (by Ipstenu): We need to block those too :( It does weird things if we use non ... boring English (I'm sleepy and I can't remember the right word for non- accented English characters) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2821#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 15:39:15 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 15:39:15 -0000 Subject: [wp-meta] [Making WordPress.org] #2796: Plugin Directory Admin: Limit State Switching for Plugin Statuses In-Reply-To: <051.ad8639951baef0ece119c495143919d3@wordpress.org> References: <051.ad8639951baef0ece119c495143919d3@wordpress.org> Message-ID: <066.9afa18d09f40296233530018642b3c67@wordpress.org> #2796: Plugin Directory Admin: Limit State Switching for Plugin Statuses ------------------------------+------------------ Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------ Comment (by Ipstenu): > Maybe Quick Edit should be disabled for plugins altogether? That's fine. We don't use it and while I wish we could sometimes, since we've managed to mitigate the whole double-submission dance, it's not a requirement at all. tl;dr We can totally disable quick-edit for plugins. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2796#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 15:54:21 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 15:54:21 -0000 Subject: [wp-meta] [Making WordPress.org] #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ In-Reply-To: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> References: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> Message-ID: <065.ee9e40b7a0a46ccbcc869bda975f9850@wordpress.org> #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ ----------------------------------------+----------------------- Reporter: netweb | Owner: iandunn Type: enhancement | Status: reopened Priority: low | Milestone: Component: General | Resolution: Keywords: needs-patch good-first-bug | ----------------------------------------+----------------------- Comment (by iandunn): That looks pretty good to me. What does the `dashicons-external` link to? Does it open in new tab? We might want to consider adding the checkout/clone commands, like: > * Subversion: `svn checkout https://core.svn.wordpress.org/trunk` > * Git: `git clone git://core.git.wordpress.org/` That might make it easier for users who aren't familiar with SVN/Git at all, but it could also confuse people who use GUI clients, since they'd need to parse out the URL. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1103#comment:22> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 16:30:42 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 16:30:42 -0000 Subject: [wp-meta] [Making WordPress.org] #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ In-Reply-To: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> References: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> Message-ID: <065.32fd8939b790f7913f20ec6f8d2607d7@wordpress.org> #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ ----------------------------------------+----------------------- Reporter: netweb | Owner: iandunn Type: enhancement | Status: reopened Priority: low | Milestone: Component: General | Resolution: Keywords: needs-patch good-first-bug | ----------------------------------------+----------------------- Comment (by coreymckrill): > What does the `dashicons-external` link to? Does it open in new tab? It links to the SVN repo, not in a new tab. I included it because in the previous iteration the SVN URL was a link instead of copiable text. I would be fine removing it, but I do think it's useful to show people that they can look through the repo on their browser rather than having to do a checkout. > We might want to consider adding the checkout/clone commands In this case, I would probably prefer to leave them as just the URLs for simplicity. People who want to know what the repo URLs are need to have a basic level of understanding about SVN/Git in order to do anything with them anyway, so they should know which commands to use. For the same reason, my preference would be to leave off `/trunk`. Branches and tags are useful for some people, and checking out the whole repo doesn't take ''that'' long (unlike the Plugins repo). -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1103#comment:23> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 19:20:14 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 19:20:14 -0000 Subject: [wp-meta] [Making WordPress.org] #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ In-Reply-To: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> References: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> Message-ID: <065.55cb8d4a38dc2f32fa45ef8357554c46@wordpress.org> #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ ----------------------------------------+----------------------- Reporter: netweb | Owner: iandunn Type: enhancement | Status: reopened Priority: low | Milestone: Component: General | Resolution: Keywords: needs-patch good-first-bug | ----------------------------------------+----------------------- Comment (by iandunn): Replying to [comment:23 coreymckrill]: > It links to the SVN repo, not in a new tab. I included it because in the previous iteration the SVN URL was a link instead of copiable text. I would be fine removing it, but I do think it's useful to show people that they can look through the repo on their browser rather than having to do a checkout. I agree that's a useful feature. I think Trac offers a better online- browsing experience, though (syntax highlighting, AJAX folder expanding, etc). Just linking to Trac could confuse some people, though, since the distinction between `core.svn` and `core.trac` needs explaining. I wonder if something like this would be good? > The built WordPress source [...] can be [https://core.trac.wordpress.org/browser/trunk/src/ browsed online], or checked out locally: > > Subversion: `https://core.svn.wordpress.org/` > Git mirror: `git://core.git.wordpress.org/` ---- > In this case, I would probably prefer to leave them as just the URLs for simplicity. People who want to know what the repo URLs are need to have a basic level of understanding about SVN/Git in order to do anything with them anyway, so they should know which commands to use. Works for me. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1103#comment:24> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 20:14:40 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 20:14:40 -0000 Subject: [wp-meta] [Making WordPress.org] #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ In-Reply-To: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> References: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> Message-ID: <065.fd6c3485a8fd0d3e5d4507700ca63f68@wordpress.org> #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ ----------------------------------------+----------------------- Reporter: netweb | Owner: iandunn Type: enhancement | Status: reopened Priority: low | Milestone: Component: General | Resolution: Keywords: needs-patch good-first-bug | ----------------------------------------+----------------------- Comment (by coreymckrill): > The built WordPress source [...] can be browsed online, or checked out locally: Love it. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1103#comment:25> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 20:23:33 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 20:23:33 -0000 Subject: [wp-meta] [Making WordPress.org] #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ In-Reply-To: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> References: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> Message-ID: <065.ebfb5aeeead6ba7d2addc2d062f05e9b@wordpress.org> #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ ----------------------------------------+----------------------- Reporter: netweb | Owner: iandunn Type: enhancement | Status: reopened Priority: low | Milestone: Component: General | Resolution: Keywords: needs-patch good-first-bug | ----------------------------------------+----------------------- Comment (by coreymckrill): Hmm, is there a way to link to the Trac browser for the built version? https://core.trac.wordpress.org/browser goes to the development version... -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1103#comment:26> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 21:03:33 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Fri, 26 May 2017 21:03:33 +0000 (UTC) Subject: [wp-meta] [5520] sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/ wcorg-misc.php: WordCamp: Don't load `wordcamporg` text domain for en_US Message-ID: <20170526210333.8DC941080143@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170526/c13d32e0/attachment.html> From noreply at wordpress.org Fri May 26 21:17:45 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 21:17:45 -0000 Subject: [wp-meta] [Making WordPress.org] #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ In-Reply-To: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> References: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> Message-ID: <065.80cfd4d9c48fe06a9a877df455cb3a26@wordpress.org> #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ ----------------------------------------+----------------------- Reporter: netweb | Owner: iandunn Type: enhancement | Status: reopened Priority: low | Milestone: Component: General | Resolution: Keywords: needs-patch good-first-bug | ----------------------------------------+----------------------- Comment (by iandunn): Replying to [comment:26 coreymckrill]: > Hmm, is there a way to link to the Trac browser for the built version? Hmm, I don't think there is. For the use case of someone casually browsing the code, though, is that distinction important? If we link to `/browser/trunk/src/`, then the user lands in a familiar spot (wp-admin, wp-includes, etc). If they're aware of the unit tests, etc and want to see them, they can just browse up a few directories. It seems like just having the 1 link might be easier to describe in the paragraph too, rather than having to explain what each is. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1103#comment:27> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 22:10:14 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 22:10:14 -0000 Subject: [wp-meta] [Making WordPress.org] #2821: Plugin Directory: Plugin slug should be Latin Characters Only In-Reply-To: <051.25e027265662218e64083f79ba18e777@wordpress.org> References: <051.25e027265662218e64083f79ba18e777@wordpress.org> Message-ID: <066.926f23da3357fe39cb7b747a72e84e98@wordpress.org> #2821: Plugin Directory: Plugin slug should be Latin Characters Only ---------------------------------------+------------------ Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch has-screenshots | ---------------------------------------+------------------ Changes (by SergeyBiryukov): * keywords: has-patch => has-patch has-screenshots Comment: In [attachment:2821.2.patch]: * Runs the plugin name through `remove_accents()`. * Strip any non-ASCII characters. * Run the rest through `sanitize_title_with_dashes()`. If the slug turns out to be empty, an error message is displayed: > The plugin has an unsupported name. Plugin names can only contain latin letters (A-z), numbers, spaces, and hyphens. Please change the `Plugin Name:` line in your main plugin file and upload it again. Suggestions for better text welcome :) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2821#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 23:30:19 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Fri, 26 May 2017 23:30:19 +0000 (UTC) Subject: [wp-meta] [5521] sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/ wcorg-misc.php: WordCamp: Change timing of text domain load to allow usage of user locale Message-ID: <20170526233019.978EC1080143@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170526/5177a24b/attachment-0001.html> From noreply at wordpress.org Sat May 27 00:46:30 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 27 May 2017 00:46:30 -0000 Subject: [wp-meta] [Making WordPress.org] #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ In-Reply-To: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> References: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> Message-ID: <065.3998369d67e4efa3b3ff9a80a5d4964b@wordpress.org> #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ ----------------------------------------+----------------------- Reporter: netweb | Owner: iandunn Type: enhancement | Status: reopened Priority: low | Milestone: Component: General | Resolution: Keywords: needs-patch good-first-bug | ----------------------------------------+----------------------- Comment (by netweb): Replying to [comment:27 iandunn]: > Replying to [comment:26 coreymckrill]: > > Hmm, is there a way to link to the Trac browser for the built version? > > Hmm, I don't think there is. Yes, here it is https://build.trac.wordpress.org/browser > For the use case of someone casually browsing the code, though, is that distinction important? I don't think so, if someone wants to view the "built" source code they can view the contents locally via wordpress.zip -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1103#comment:28> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 27 01:12:44 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 27 May 2017 01:12:44 -0000 Subject: [wp-meta] [Making WordPress.org] #2821: Plugin Directory: Plugin slug should be Latin Characters Only In-Reply-To: <051.25e027265662218e64083f79ba18e777@wordpress.org> References: <051.25e027265662218e64083f79ba18e777@wordpress.org> Message-ID: <066.4a378a04f4392acbe0ebe9a300ca7936@wordpress.org> #2821: Plugin Directory: Plugin slug should be Latin Characters Only ---------------------------------------+------------------ Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch has-screenshots | ---------------------------------------+------------------ Comment (by Ipstenu): I think that's good to start with. My +1 for you, sir! -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2821#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 27 19:12:08 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 27 May 2017 19:12:08 -0000 Subject: [wp-meta] [Making WordPress.org] #2841: Theme Directory - Feature filter has a min-height Message-ID: <052.dbd7c1412cbe4187cbab2e45a4e36536@wordpress.org> #2841: Theme Directory - Feature filter has a min-height -----------------------------+----------------- Reporter: joyously | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Theme Directory | Keywords: -----------------------------+----------------- When using the Feature Filter of the theme directory, there are 3 sections. Each section lists the filters and then has a big white space. Is there some aspect of the filters that isn't developed yet that is supposed to go in the white space? Looking at the CSS, there is a class `filter-group` with a calculated width and `min-height: 710px`. Then another rule that overrides with `width:100%` and `height: auto`. Can the `min-height` be removed, please? (Actually, all four could be removed, but the min-height is the worst one.) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2841> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sun May 28 03:12:39 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sun, 28 May 2017 03:12:39 -0000 Subject: [wp-meta] [Making WordPress.org] #2842: REST API handbook contains incorrect links to Requests class Message-ID: <050.7d84eaea24beca2592bba48d6913fa20@wordpress.org> #2842: REST API handbook contains incorrect links to Requests class ---------------------------+----------------- Reporter: rmccue | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Developer Hub | Keywords: ---------------------------+----------------- Not sure where the code is that auto-links classes used in text, but for the REST API handbook, when `Requests` is used in the text (case- sensitively), it's linked to the Requests class. This is most visible in the [https://developer.wordpress.org/rest- api/#requests broken Requests section header] on the handbook's homepage. This code is in the [https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html /wp-content/themes/pub/wporg-developer/inc/formatting.php#L289 DevHub_Formatting::autolink_references] code, but is explicitly included there, so this seems intentional. Since "requests" is both the name of the class and a common English word, IMO this should err on the most common case, which is as an English word. References to the class itself can be manually linked by the page author. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2842> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 02:37:12 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 02:37:12 -0000 Subject: [wp-meta] [Making WordPress.org] #2753: Plugin directory search sorting and filtering In-Reply-To: <054.ea0beff6952873fe3a66bcfa513e7b6b@wordpress.org> References: <054.ea0beff6952873fe3a66bcfa513e7b6b@wordpress.org> Message-ID: <069.978c3cb5b1ced32b917155fd79bfe20f@wordpress.org> #2753: Plugin directory search sorting and filtering -------------------------------------+------------------------------------- Reporter: tellyworth | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Component: Plugin Directory | Future Keywords: ui-feedback needs- | Resolution: screenshots | -------------------------------------+------------------------------------- Comment (by gibrown): Replying to [comment:6 joyously]: > One thing that is unclear is whether it is different code that populates the plugin search results in the admin versus the page that looks the same on wordpress.org. > Does this ticket cover both contexts? It is different code. The core plugin search is separate, but it uses the same backend algorithm. I think we should focus on iterating on the design here before looking to improve the UI in core. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2753#comment:8> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 02:35:01 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 02:35:01 -0000 Subject: [wp-meta] [Making WordPress.org] #2753: Plugin directory search sorting and filtering In-Reply-To: <054.ea0beff6952873fe3a66bcfa513e7b6b@wordpress.org> References: <054.ea0beff6952873fe3a66bcfa513e7b6b@wordpress.org> Message-ID: <069.0e9f29a606b3b5805b016e249a71c170@wordpress.org> #2753: Plugin directory search sorting and filtering -------------------------------------+------------------------------------- Reporter: tellyworth | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Component: Plugin Directory | Future Keywords: ui-feedback needs- | Resolution: screenshots | -------------------------------------+------------------------------------- Comment (by gibrown): Thanks for adding some mockups. Helps to think through some of the complexities. For sorting: - I'm going back and forth a bit on the word "popularity" and wondering if we should just say "relevance" which is at least open to interpretation - I'm not sure what sorting by plugin name would be? Alphabetical? What use cases does that solve for us? Also, we won't always be able to page through all of the results, so I think it would be a broken experience Looking at the original design some more, I don't really like that the search box is in the upper right of the current design. Makes it hard to find and therefore hard to adjust. Feels to me that it should be in the center of the page, and much bigger than the text that says: "Showing results for:" We also need someplace to display any filters that have already been added to the search. Maybe just below a more prominent search box with a set of filters using something like https://select2.github.io/examples.html#tags (though maybe something better than that). For faceting, I think we should have the facets on screen at all times on large screens. That may mean reworking how the current results are displayed, but should make the search more browsable and interactive. I guess on small screens the faceting will have to slide in, or not exist at all. I'd also love to just skip straight to doing a React UI for the search interface to make interacting much faster, but that would make the project a fair bit bigger I think (or at least it would make it harder for me to implement). I was looking at these for instance: https://react.rocks/tag/Faceted_Search -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2753#comment:7> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 10:27:09 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 10:27:09 -0000 Subject: [wp-meta] [Making WordPress.org] #957: Create a community Code of Conduct In-Reply-To: <053.003b95e85f7c7cb56c4aa3750a9b223d@wordpress.org> References: <053.003b95e85f7c7cb56c4aa3750a9b223d@wordpress.org> Message-ID: <068.71cd81f2af9fa60c5241ad6f998a5ec2@wordpress.org> #957: Create a community Code of Conduct -------------------------+------------------ Reporter: melchoyce | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: | -------------------------+------------------ Comment (by mor10): Good news everyone! It took a lot longer than expected, but here's the proposal for the Community Code of Conduct Project: https://make.wordpress.org/updates/2017/05/19/proposal-wordpress- community-conduct-project/ Please sign up and let's get started! -- Ticket URL: <https://meta.trac.wordpress.org/ticket/957#comment:31> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 18:12:29 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 30 May 2017 18:12:29 +0000 (UTC) Subject: [wp-meta] [5522] sites/trunk/wordcamp.org/public_html/wp-content/plugins/ wc-post-types/wc-post-types.php: WordCamp Post Types: Show sponsors post type in the v2 REST API Message-ID: <20170530181229.7CE601080339@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170530/1ff5ae6c/attachment.html> From noreply at wordpress.org Tue May 30 18:31:31 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 18:31:31 -0000 Subject: [wp-meta] [Making WordPress.org] #2802: Credit to initial translator when validator uploads po-file In-Reply-To: <056.93036d4247cdee75d8b7445ebe57538d@wordpress.org> References: <056.93036d4247cdee75d8b7445ebe57538d@wordpress.org> Message-ID: <071.ba600497897702ed5c740e1dd8862dc1@wordpress.org> #2802: Credit to initial translator when validator uploads po-file --------------------------------------+---------------------- Reporter: tobifjellner | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: Translate Site & Plugins | Resolution: invalid Keywords: | --------------------------------------+---------------------- Changes (by ocean90): * status: new => closed * resolution: => invalid Comment: The GlotPress issue is the correct one in this case. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2802#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 20:30:07 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 20:30:07 -0000 Subject: [wp-meta] [Making WordPress.org] #148: Restyle/redesign the registration page In-Reply-To: <051.ab1c08ab370895eaf5a087029eef46c5@wordpress.org> References: <051.ab1c08ab370895eaf5a087029eef46c5@wordpress.org> Message-ID: <066.de0ece24a888a9edd99a9efd602d79ac@wordpress.org> #148: Restyle/redesign the registration page ------------------------------------+----------------------- Reporter: j.conti | Owner: dd32 Type: task | Status: assigned Priority: high | Milestone: Component: Login & Authentication | Resolution: Keywords: has-ui-feedback | ------------------------------------+----------------------- Changes (by karmatosed): * keywords: ui-feedback => has-ui-feedback -- Ticket URL: <https://meta.trac.wordpress.org/ticket/148#comment:49> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 20:30:53 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 20:30:53 -0000 Subject: [wp-meta] [Making WordPress.org] #148: Restyle/redesign the registration page In-Reply-To: <051.ab1c08ab370895eaf5a087029eef46c5@wordpress.org> References: <051.ab1c08ab370895eaf5a087029eef46c5@wordpress.org> Message-ID: <066.f83b460da177b0d2a341378a27126984@wordpress.org> #148: Restyle/redesign the registration page ------------------------------------+----------------------- Reporter: j.conti | Owner: dd32 Type: task | Status: assigned Priority: high | Milestone: Component: Login & Authentication | Resolution: Keywords: | ------------------------------------+----------------------- Changes (by karmatosed): * keywords: has-ui-feedback => -- Ticket URL: <https://meta.trac.wordpress.org/ticket/148#comment:50> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 20:32:06 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 20:32:06 -0000 Subject: [wp-meta] [Making WordPress.org] #148: Restyle/redesign the registration page In-Reply-To: <051.ab1c08ab370895eaf5a087029eef46c5@wordpress.org> References: <051.ab1c08ab370895eaf5a087029eef46c5@wordpress.org> Message-ID: <066.a37d427cda81d1751877c732bb2823f4@wordpress.org> #148: Restyle/redesign the registration page ------------------------------------+--------------------- Reporter: j.conti | Owner: dd32 Type: task | Status: closed Priority: high | Milestone: Component: Login & Authentication | Resolution: fixed Keywords: | ------------------------------------+--------------------- Changes (by ocean90): * status: assigned => closed * resolution: => fixed -- Ticket URL: <https://meta.trac.wordpress.org/ticket/148#comment:51> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 20:36:52 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 30 May 2017 20:36:52 +0000 (UTC) Subject: [wp-meta] [5523] sites/trunk/wordpress.org/public_html/wp-content/plugins: Support Forums: Pass post IDs to `moderate` capability checks. Message-ID: <20170530203652.3918C1080339@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170530/c98f51fe/attachment-0001.html> From noreply at wordpress.org Tue May 30 20:36:52 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 20:36:52 -0000 Subject: [wp-meta] [Making WordPress.org] #2590: Enhance compatibility with per forum moderators In-Reply-To: <051.ef2c0624040c63d1e71b94d15700a274@wordpress.org> References: <051.ef2c0624040c63d1e71b94d15700a274@wordpress.org> Message-ID: <066.e35b24b28a2443a942a5e25311d351b2@wordpress.org> #2590: Enhance compatibility with per forum moderators ------------------------------+---------------------- Reporter: ocean90 | Owner: ocean90 Type: defect | Status: closed Priority: normal | Milestone: Component: Support Forums | Resolution: fixed Keywords: has-patch commit | ------------------------------+---------------------- Changes (by ocean90): * owner: => ocean90 * status: new => closed * resolution: => fixed Comment: In [changeset:"5523"]: {{{ #!CommitTicketReference repository="" revision="5523" Support Forums: Pass post IDs to `moderate` capability checks. Props SergeyBiryukov. Fixes #2590. }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2590#comment:9> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 20:39:55 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 20:39:55 -0000 Subject: [wp-meta] [Making WordPress.org] #2618: Plugin Directory: Translation needed banner omits language In-Reply-To: <051.eed73691dd5ba0b981c0645fe16da796@wordpress.org> References: <051.eed73691dd5ba0b981c0645fe16da796@wordpress.org> Message-ID: <066.3bde2961fcfc73f9acb1868408f2b4cf@wordpress.org> #2618: Plugin Directory: Translation needed banner omits language ------------------------------+------------------------------------------- Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Changes (by ocean90): * keywords: has-patch => Comment: Yeah, we're not going to use the name of a site for the banner. See https://meta.trac.wordpress.org/ticket/2517#comment:2 -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2618#comment:9> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 20:47:56 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 30 May 2017 20:47:56 +0000 (UTC) Subject: [wp-meta] [5524] sites/trunk/wordpress.org/public_html/wp-content/plugins/ wporg-gp-customizations/templates: Translate: Move the right parenthesis of `esc_url()` to the correct position. Message-ID: <20170530204756.5A1421080339@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170530/d9877b12/attachment.html> From noreply at wordpress.org Tue May 30 20:50:43 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 30 May 2017 20:50:43 +0000 (UTC) Subject: [wp-meta] [5525] sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-cli: make/cli: Add `cli-repo-list` shortcode Message-ID: <20170530205043.0B98D1080339@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170530/dd86b296/attachment-0001.html> From noreply at wordpress.org Tue May 30 21:17:19 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 21:17:19 -0000 Subject: [wp-meta] [Making WordPress.org] #2756: Improve search form styling and correct meeting time in 404 template on make/core P2 In-Reply-To: <051.492fbf3beaa5974f52535dcec2edb17b@wordpress.org> References: <051.492fbf3beaa5974f52535dcec2edb17b@wordpress.org> Message-ID: <066.10da8a0bbf939f9416d2bc00cb149c98@wordpress.org> #2756: Improve search form styling and correct meeting time in 404 template on make/core P2 --------------------------------------+---------------------- Reporter: alkesh7 | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Make (Get Involved) / P2 | Resolution: invalid Keywords: ui-feedback | --------------------------------------+---------------------- Changes (by karmatosed): * status: new => closed * resolution: => invalid Comment: I just tested this and seems that it with the new design is fixed, or at least not such an issue: [[Image(https://cldup.com/0Zc_sYImQc.png)]] As this has been fairly recent, going to mark as closed for now. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2756#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 21:22:25 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 21:22:25 -0000 Subject: [wp-meta] [Making WordPress.org] #2779: Single Plugin: Remove URL to Current Page from Plugin Title In-Reply-To: <053.d2026e74568a0d11713bdcfd28a44421@wordpress.org> References: <053.d2026e74568a0d11713bdcfd28a44421@wordpress.org> Message-ID: <068.be2efc2b42a7b301e6d316453fe45ef4@wordpress.org> #2779: Single Plugin: Remove URL to Current Page from Plugin Title ------------------------------+------------------------------------ Reporter: bmoredrew | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------ Changes (by karmatosed): * keywords: has-patch ux-feedback ui-feedback => has-patch -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2779#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 21:23:07 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 21:23:07 -0000 Subject: [wp-meta] [Making WordPress.org] #2756: Improve search form styling and correct meeting time in 404 template on make/core P2 In-Reply-To: <051.492fbf3beaa5974f52535dcec2edb17b@wordpress.org> References: <051.492fbf3beaa5974f52535dcec2edb17b@wordpress.org> Message-ID: <066.25431286c489fc2521061a8b430d81b3@wordpress.org> #2756: Improve search form styling and correct meeting time in 404 template on make/core P2 --------------------------------------+----------------------- Reporter: alkesh7 | Owner: Type: defect | Status: reopened Priority: normal | Milestone: Component: Make (Get Involved) / P2 | Resolution: Keywords: ui-feedback | --------------------------------------+----------------------- Changes (by SergeyBiryukov): * status: closed => reopened * resolution: invalid => Comment: https://make.wordpress.org/core/non-existing-url still displays both issues, exactly as on the screenshot. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2756#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 21:27:46 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 21:27:46 -0000 Subject: [wp-meta] [Making WordPress.org] #2831: On the Advanced view of a plugin the list of committers is imporperly formatted. In-Reply-To: <050.a1902e359d66d525b6d3ac015ea54721@wordpress.org> References: <050.a1902e359d66d525b6d3ac015ea54721@wordpress.org> Message-ID: <065.b80e72c0fd7c36afa2cb3a81ba430d73@wordpress.org> #2831: On the Advanced view of a plugin the list of committers is imporperly formatted. -------------------------------------+------------------------------------- Reporter: aguseo | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Component: Plugin Directory | Future Keywords: has-screenshots ui- | Resolution: feedback reporter-feedback | -------------------------------------+------------------------------------- Comment (by karmatosed): I also wonder how useful this information is if you are just a user/viewer. Don't we need to fix though then for someone who is? It seems a less optimal visual experience otherwise. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2831#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 22:47:04 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 30 May 2017 22:47:04 +0000 (UTC) Subject: [wp-meta] [5526] sites/trunk/wordpress.org/public_html/wp-content/plugins: make/cli: Create a shortcode for listing issues Message-ID: <20170530224704.618F61080339@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170530/f2fa11a8/attachment-0001.html> From noreply at wordpress.org Tue May 30 23:26:06 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 30 May 2017 23:26:06 +0000 (UTC) Subject: [wp-meta] [5527] sites/trunk/wordpress.org/public_html/wp-content/plugins/ p2-new-post-categories/: P2 New Post Categories: Remove from repository because no longer used Message-ID: <20170530232606.6777A1080339@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170530/0f6c391d/attachment.html> From noreply at wordpress.org Wed May 31 02:53:19 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 02:53:19 -0000 Subject: [wp-meta] [Making WordPress.org] #2790: Blockquote styles enhancement In-Reply-To: <058.1519385a51fb59753db7156e002686b1@wordpress.org> References: <058.1519385a51fb59753db7156e002686b1@wordpress.org> Message-ID: <073.7578d6429a04fdc6718d91203cd6fdbf@wordpress.org> #2790: Blockquote styles enhancement ------------------------------+------------------------------------ Reporter: webdevmattcrom | Owner: mapk Type: enhancement | Status: reviewing Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------ Comment (by joyously): I don't think `blockquote` should be italic. Blockquote can have nested HTML, including `<em>`, which would be indistinguishable. I favor an indent, but not a background color change. After all, `blockquote` is for quoting an external source, not making something stand out. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2790#comment:8> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 12:28:18 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 31 May 2017 12:28:18 +0000 (UTC) Subject: [wp-meta] [5528] sites/trunk/common/includes/slack/announce/config.php: Slack: Give adamsilverstein announce in #core. Message-ID: <20170531122818.7590A108041E@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170531/9bf08184/attachment.html> From noreply at wordpress.org Wed May 31 15:58:48 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 15:58:48 -0000 Subject: [wp-meta] [Making WordPress.org] #2843: Slack: Add ?support Slackbot auto-response Message-ID: <053.567febe8b56a96cc1b1db44fb4ca23af@wordpress.org> #2843: Slack: Add ?support Slackbot auto-response -------------------------+----------------- Reporter: melchoyce | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Slack & IRC | Keywords: -------------------------+----------------- We get a lot of people on Slack asking for support. I think it would be helpful to create a `?support` Slack auto-response with a friendly reply directing people to the support forums. Maybe: > Welcome to the Making WordPress slack! This Slack is for discussion related to the creation of WordPress itself. For general support or questions, please check out the WordPress.org support forums https://wordpress.org/support/ or IRC https://make.wordpress.org/support /irc-support-channel/. (Need some smoothing) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2843> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 17:06:01 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 31 May 2017 17:06:01 +0000 (UTC) Subject: [wp-meta] [5529] sites/trunk/wordcamp.org/public_html/wp-content/plugins/ wc-post-types/wc-post-types.php: WordCamp Post Types: Show track and level taxonomies in REST API Message-ID: <20170531170601.6AE39108041E@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170531/4614026b/attachment.html> From noreply at wordpress.org Wed May 31 19:16:21 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 19:16:21 -0000 Subject: [wp-meta] [Making WordPress.org] #2821: Plugin Directory: Plugin slug should be Latin Characters Only In-Reply-To: <051.25e027265662218e64083f79ba18e777@wordpress.org> References: <051.25e027265662218e64083f79ba18e777@wordpress.org> Message-ID: <066.2dd72cca59ec0cca017c64b22d208ff8@wordpress.org> #2821: Plugin Directory: Plugin slug should be Latin Characters Only ---------------------------------------+----------------------------------- Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory Component: Plugin Directory | v3.0 Keywords: has-patch has-screenshots | Resolution: ---------------------------------------+----------------------------------- Changes (by SergeyBiryukov): * milestone: => Plugin Directory v3.0 -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2821#comment:5> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 19:16:35 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 19:16:35 -0000 Subject: [wp-meta] [Making WordPress.org] #2721: Plugin Directory: Use a consistent font size for Committers and Contributors widgets In-Reply-To: <058.681e5903d68600d88138ab13d1c4f78d@wordpress.org> References: <058.681e5903d68600d88138ab13d1c4f78d@wordpress.org> Message-ID: <073.37412e92fba201997bf06387901653d0@wordpress.org> #2721: Plugin Directory: Use a consistent font size for Committers and Contributors widgets -------------------------------------+------------------------------------- Reporter: SergeyBiryukov | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Component: Plugin Directory | Future Keywords: has-patch commit has- | Resolution: screenshots | -------------------------------------+------------------------------------- Changes (by SergeyBiryukov): * milestone: => Plugin Directory v3 - Future -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2721#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 19:16:33 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 19:16:33 -0000 Subject: [wp-meta] [Making WordPress.org] #2830: Plugin Directory: Include slug in submission emails In-Reply-To: <051.980ca4c7bb6bb49acc9857d3105e0019@wordpress.org> References: <051.980ca4c7bb6bb49acc9857d3105e0019@wordpress.org> Message-ID: <066.2dca7d24903499943ca3cca5fd5a9c47@wordpress.org> #2830: Plugin Directory: Include slug in submission emails ------------------------------+------------------------------------ Reporter: Ipstenu | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------ Changes (by SergeyBiryukov): * milestone: => Plugin Directory v3.0 -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2830#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 19:16:37 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 19:16:37 -0000 Subject: [wp-meta] [Making WordPress.org] #2781: Plugin Directory: Add translator comments for placeholders in Stats Report tool In-Reply-To: <058.03697759c32f7f3c720db10da4f5a581@wordpress.org> References: <058.03697759c32f7f3c720db10da4f5a581@wordpress.org> Message-ID: <073.ad31ff40ea13943ee58a05d3eb5bd2f1@wordpress.org> #2781: Plugin Directory: Add translator comments for placeholders in Stats Report tool ------------------------------+------------------------------------------- Reporter: SergeyBiryukov | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------------- Changes (by SergeyBiryukov): * milestone: => Plugin Directory v3 - Future -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2781#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 19:16:40 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 19:16:40 -0000 Subject: [wp-meta] [Making WordPress.org] #2782: Plugin Directory: Use consistent punctuation in meta descriptions In-Reply-To: <058.2b0bc6e3e877dd01c767b417b2dfa077@wordpress.org> References: <058.2b0bc6e3e877dd01c767b417b2dfa077@wordpress.org> Message-ID: <073.ea68029d7ee177b353c914e9cdcca324@wordpress.org> #2782: Plugin Directory: Use consistent punctuation in meta descriptions ------------------------------+------------------------------------------- Reporter: SergeyBiryukov | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------------- Changes (by SergeyBiryukov): * milestone: => Plugin Directory v3 - Future -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2782#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 19:17:31 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 19:17:31 -0000 Subject: [wp-meta] [Making WordPress.org] #2843: Slack: Add ?support Slackbot auto-response In-Reply-To: <053.567febe8b56a96cc1b1db44fb4ca23af@wordpress.org> References: <053.567febe8b56a96cc1b1db44fb4ca23af@wordpress.org> Message-ID: <068.fcd9e983cd01f0573ff7dd7d5b1ba76a@wordpress.org> #2843: Slack: Add ?support Slackbot auto-response -------------------------+------------------ Reporter: melchoyce | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Slack & IRC | Resolution: Keywords: | -------------------------+------------------ Comment (by casiepa): You could also help them getting to their locals slacks. Something like : ''Or find a local slack (https://make.wordpress.org/polyglots/handbook/about/teams/local-slacks/) and ask your question there if it's related to something local.'' Another frequent question is about jobs. My standard response: ''Hi there, for job postings, please use one of the resources such as jobs.wordpress.net or jetpack.pro. Or find a local slack (https://make.wordpress.org/polyglots/handbook/about/teams/local-slacks/) and look for a job channel.'' So that could be a ?jobs or something -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2843#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 19:17:48 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 19:17:48 -0000 Subject: [wp-meta] [Making WordPress.org] #2800: Plugin Directory: Ask for confirmation before removing someone as a committer In-Reply-To: <054.334261ed8da287672092be0c6c8fe2d4@wordpress.org> References: <054.334261ed8da287672092be0c6c8fe2d4@wordpress.org> Message-ID: <069.59b6c46309a905609e77bcf04942b4c6@wordpress.org> #2800: Plugin Directory: Ask for confirmation before removing someone as a committer ------------------------------+------------------------------------------- Reporter: Nikschavan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------------- Changes (by SergeyBiryukov): * milestone: => Plugin Directory v3 - Future -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2800#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 19:24:52 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 19:24:52 -0000 Subject: [wp-meta] [Making WordPress.org] #2796: Plugin Directory Admin: Limit State Switching for Plugin Statuses In-Reply-To: <051.ad8639951baef0ece119c495143919d3@wordpress.org> References: <051.ad8639951baef0ece119c495143919d3@wordpress.org> Message-ID: <066.d5cd534690774782d0340343ddc87280@wordpress.org> #2796: Plugin Directory Admin: Limit State Switching for Plugin Statuses ------------------------------+------------------------------------ Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------ Changes (by SergeyBiryukov): * milestone: => Plugin Directory v3.0 Comment: Just realized the patch doesn't allow for plugins to be moved to Trash :) Is that something admins should be able to do (e.g. for spam submissions), or Rejected status would be sufficient? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2796#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 21:48:25 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 21:48:25 -0000 Subject: [wp-meta] [Making WordPress.org] #2843: Slack: Add ?support Slackbot auto-response In-Reply-To: <053.567febe8b56a96cc1b1db44fb4ca23af@wordpress.org> References: <053.567febe8b56a96cc1b1db44fb4ca23af@wordpress.org> Message-ID: <068.51721a0060bd17a1555c2db050ab4fc4@wordpress.org> #2843: Slack: Add ?support Slackbot auto-response -------------------------+------------------ Reporter: melchoyce | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Slack & IRC | Resolution: Keywords: | -------------------------+------------------ Comment (by netweb): This has been brought up multiple times and the general consensus is to not add a Slack bot for this https://wordpress.slack.com/archives/C02RQBWTW/p1484646847005814 * [[Image(https://cldup.com/oyJKG1d11k.png)]] There's a few more instances through my search foo was unable to find them :( -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2843#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 22:10:56 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 22:10:56 -0000 Subject: [wp-meta] [Making WordPress.org] #2843: Slack: Add ?support Slackbot auto-response In-Reply-To: <053.567febe8b56a96cc1b1db44fb4ca23af@wordpress.org> References: <053.567febe8b56a96cc1b1db44fb4ca23af@wordpress.org> Message-ID: <068.23dec3d7d47cdeae80d779bf1c96a293@wordpress.org> #2843: Slack: Add ?support Slackbot auto-response -------------------------+------------------ Reporter: melchoyce | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Slack & IRC | Resolution: Keywords: | -------------------------+------------------ Comment (by melchoyce): I don't think we need a bot, just a manually-triggered Slack auto- response. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2843#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 22:18:31 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 31 May 2017 22:18:31 +0000 (UTC) Subject: [wp-meta] [5530] sites/trunk/wordcamp.org/public_html/wp-content/themes/ wordcamp-central-2012: WordCamp Central: Add year to camp dates on the schedule Message-ID: <20170531221831.5526B108041E@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170531/7be1c464/attachment-0001.html> From noreply at wordpress.org Wed May 31 22:18:31 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 22:18:31 -0000 Subject: [wp-meta] [Making WordPress.org] #2065: Add year to dates on http://central.wordcamp.org/schedule/ In-Reply-To: <059.ac3962f242437219871b68a88feac608@wordpress.org> References: <059.ac3962f242437219871b68a88feac608@wordpress.org> Message-ID: <074.fcbb50f10aa4b1dc074e54e2f8309c98@wordpress.org> #2065: Add year to dates on http://central.wordcamp.org/schedule/ --------------------------------------+---------------------- Reporter: andreamiddleton | Owner: iandunn Type: enhancement | Status: closed Priority: low | Milestone: Component: WordCamp Site & Plugins | Resolution: fixed Keywords: good-first-bug has-patch | --------------------------------------+---------------------- Changes (by coreymckrill): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"5530"]: {{{ #!CommitTicketReference repository="" revision="5530" WordCamp Central: Add year to camp dates on the schedule Changes the Schedule page template to emulate the organization on the Past Camps page template, by grouping camps under a year header and including the year in each camp's date. This also adds a param to `WordCamp_Central_Theme::the_wordcamp_date` to include the year in the camp date output. The default is to not include it, for backcompat. Props frq Fixes #2065 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2065#comment:6> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org

From noreply at wordpress.org Mon May 1 11:00:53 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 1 May 2017 11:00:53 +0000 (UTC) Subject: [wp-meta] [5453] sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory/jobs: Plugin Directory: Update a scheduled job if another i18n import is triggered during the 15 minutes timeframe. Message-ID: <20170501110053.5116610803BA@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon May 1 11:50:37 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 01 May 2017 11:50:37 -0000 Subject: [wp-meta] [Making WordPress.org] #2661: Plugin Theme: Reviews schema is missing on plugin pages, resulting in missing star ratings in Google In-Reply-To: <053.554abb8b9fdf2d86d25e44164d924031@wordpress.org> References: <053.554abb8b9fdf2d86d25e44164d924031@wordpress.org> Message-ID: <068.90d03591e9317e4f2f9f0940c001957a@wordpress.org> #2661: Plugin Theme: Reviews schema is missing on plugin pages, resulting in missing star ratings in Google ------------------------------+------------------------------------------- Reporter: Dharm1025 | Owner: Otto42 Type: defect | Status: accepted Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by ocean90): @joostdevalk What do you think about this markup? {{{ }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 1 12:28:24 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 01 May 2017 12:28:24 -0000 Subject: [wp-meta] [Making WordPress.org] #2661: Plugin Theme: Reviews schema is missing on plugin pages, resulting in missing star ratings in Google In-Reply-To: <053.554abb8b9fdf2d86d25e44164d924031@wordpress.org> References: <053.554abb8b9fdf2d86d25e44164d924031@wordpress.org> Message-ID: <068.423ff527d5c4f9fb4f49eac624416888@wordpress.org> #2661: Plugin Theme: Reviews schema is missing on plugin pages, resulting in missing star ratings in Google ------------------------------+------------------------------------------- Reporter: Dharm1025 | Owner: Otto42 Type: defect | Status: accepted Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by joostdevalk): I don't think I'd do softwareApplication, to be honest @ocean90, product is simpler and more likely to get picked up right. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 1 12:30:38 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 01 May 2017 12:30:38 -0000 Subject: [wp-meta] [Making WordPress.org] #2661: Plugin Theme: Reviews schema is missing on plugin pages, resulting in missing star ratings in Google In-Reply-To: <053.554abb8b9fdf2d86d25e44164d924031@wordpress.org> References: <053.554abb8b9fdf2d86d25e44164d924031@wordpress.org> Message-ID: <068.8c49c0a449529bb6bdbc6fa6d65e0ca6@wordpress.org> #2661: Plugin Theme: Reviews schema is missing on plugin pages, resulting in missing star ratings in Google ------------------------------+------------------------------------------- Reporter: Dharm1025 | Owner: Otto42 Type: defect | Status: accepted Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by ocean90): For the records: softwareApplication is what we had used in the old plugin directory. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 1 13:04:02 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 01 May 2017 13:04:02 -0000 Subject: [wp-meta] [Making WordPress.org] #2661: Plugin Theme: Reviews schema is missing on plugin pages, resulting in missing star ratings in Google In-Reply-To: <053.554abb8b9fdf2d86d25e44164d924031@wordpress.org> References: <053.554abb8b9fdf2d86d25e44164d924031@wordpress.org> Message-ID: <068.99e3fbe3eed6a776fb3023d3cc6d53e4@wordpress.org> #2661: Plugin Theme: Reviews schema is missing on plugin pages, resulting in missing star ratings in Google ------------------------------+------------------------------------------- Reporter: Dharm1025 | Owner: Otto42 Type: defect | Status: accepted Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by joostdevalk): Oh ok, then ehm, go? :-) -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 1 13:08:56 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 01 May 2017 13:08:56 -0000 Subject: [wp-meta] [Making WordPress.org] #2661: Plugin Theme: Reviews schema is missing on plugin pages, resulting in missing star ratings in Google In-Reply-To: <053.554abb8b9fdf2d86d25e44164d924031@wordpress.org> References: <053.554abb8b9fdf2d86d25e44164d924031@wordpress.org> Message-ID: <068.a9cbde962887dae56f0ee778aa610722@wordpress.org> #2661: Plugin Theme: Reviews schema is missing on plugin pages, resulting in missing star ratings in Google ------------------------------+------------------------------------------- Reporter: Dharm1025 | Owner: Otto42 Type: defect | Status: accepted Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by ocean90): Heh, okay. Following an example for Product: {{{ }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 1 16:59:43 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 1 May 2017 16:59:43 +0000 (UTC) Subject: [wp-meta] [5454] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-plugins: Plugin Directory: Replace the `#screenshot` container when inserting the screenshot slider. Message-ID: <20170501165943.9179110803BA@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon May 1 16:59:44 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 01 May 2017 16:59:44 -0000 Subject: [wp-meta] [Making WordPress.org] #2680: Plugin Directory: Same id is used twice In-Reply-To: <050.3887cfc622d3b83de733d5f70a617e8c@wordpress.org> References: <050.3887cfc622d3b83de733d5f70a617e8c@wordpress.org> Message-ID: <065.881aa9e06e821da0f63f9bbaf0f6da4d@wordpress.org> #2680: Plugin Directory: Same id is used twice ------------------------------+------------------------------------ Reporter: nico23 | Owner: ocean90 Type: defect | Status: closed Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: fixed Keywords: needs-patch | ------------------------------+------------------------------------ Changes (by ocean90): * owner: => ocean90 * status: new => closed * resolution: => fixed Comment: In [changeset:"5454"]: {{{ #!CommitTicketReference repository="" revision="5454" Plugin Directory: Replace the `#screenshot` container when inserting the screenshot slider. Fixes #2680. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 1 17:06:10 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 1 May 2017 17:06:10 +0000 (UTC) Subject: [wp-meta] [5455] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-plugins/functions.php: Plugin Directory: Bump script version for cache bust. Message-ID: <20170501170610.2700B10803BA@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon May 1 17:31:45 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 01 May 2017 17:31:45 -0000 Subject: [wp-meta] [Making WordPress.org] #2661: Plugin Theme: Reviews schema is missing on plugin pages, resulting in missing star ratings in Google In-Reply-To: <053.554abb8b9fdf2d86d25e44164d924031@wordpress.org> References: <053.554abb8b9fdf2d86d25e44164d924031@wordpress.org> Message-ID: <068.0a15dece2a6b1e6d470c0073a8647fce@wordpress.org> #2661: Plugin Theme: Reviews schema is missing on plugin pages, resulting in missing star ratings in Google ------------------------------+------------------------------------------- Reporter: Dharm1025 | Owner: ocean90 Type: defect | Status: accepted Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Changes (by ocean90): * owner: Otto42 => ocean90 -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 1 18:57:45 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 1 May 2017 18:57:45 +0000 (UTC) Subject: [wp-meta] [5456] sites/trunk/wordcamp.org/public_html/wp-content/plugins/ wordcamp-site-cloner/wordcamp-site-cloner.php: WordCamp: Update URL for the mshots API in the Site Cloner Message-ID: <20170501185745.ECFD110803BA@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon May 1 19:19:00 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 01 May 2017 19:19:00 -0000 Subject: [wp-meta] [Making WordPress.org] #2642: Better boosting for phrase matches (or add support for the user to specify a phrase) In-Reply-To: <051.6ac0b0ad0bb1fc49ee7e4ab29ad2ae98@wordpress.org> References: <051.6ac0b0ad0bb1fc49ee7e4ab29ad2ae98@wordpress.org> Message-ID: <066.7296512ee25dbb8b82fa330b3be0f5e2@wordpress.org> #2642: Better boosting for phrase matches (or add support for the user to specify a phrase) ------------------------------+------------------------------------------- Reporter: gibrown | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by yani.iliev): Changing of plugin tags and plugin display name does not have any implications and is almost instantly indexed. This allows for adjusting the tags and the display name, tests search rankings, and repeat until desired result is reached. The search should look at how long a plugin has been using a certain name and also how old the tags are. A new plugin that added the tag "automate" should not be put ahead of a plugin that had the tag "automate" for the last 1 year. The same should apply to the name, any recent change needs to reset the weight of the display name. Active Installs needs to have lower weight compared to Reviews. Reviews provides instant feedback of how satisfied users are with a plugin - active installs tells that a plugin is active but it does not tells if users are satisfied and that this plugin should be ahead in the results. Plugins that are used once and then wiped suffer a lot from this - one example is migration plugins that do not need to stay activated after a transfer. Thinking more about it, reviews and forum posts tell the plugin story from user perspective - they define the most what the plugin does and what it is good at. They should be indexed and added to the rankings. Stemming is not very good - migration and migrator match very different plugins -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 1 20:43:12 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 01 May 2017 20:43:12 -0000 Subject: [wp-meta] [Making WordPress.org] #2803: Tags and action links appended to [info] blocks in P2 post content Message-ID: <055.47fe1f405b4e46c7341091c8cacab14d@wordpress.org> #2803: Tags and action links appended to [info] blocks in P2 post content --------------------------------------+------------------------- Reporter: johnbillion | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Make (Get Involved) / P2 | Keywords: needs-patch --------------------------------------+------------------------- Example post: https://make.wordpress.org/core/2017/04/23/recent-updates- to-the-unit-testing-infrastructure/ Note that the tags and the `Reply` and `Follow` buttons are being appended to the `[info]` message near the beginning of the post. This is in addition to their display at the end of the post. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 1 21:23:29 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 01 May 2017 21:23:29 -0000 Subject: [wp-meta] [Making WordPress.org] #2661: Plugin Theme: Reviews schema is missing on plugin pages, resulting in missing star ratings in Google In-Reply-To: <053.554abb8b9fdf2d86d25e44164d924031@wordpress.org> References: <053.554abb8b9fdf2d86d25e44164d924031@wordpress.org> Message-ID: <068.9914a4c143669ead3b3f7350b077f699@wordpress.org> #2661: Plugin Theme: Reviews schema is missing on plugin pages, resulting in missing star ratings in Google ------------------------------+------------------------------------------- Reporter: Dharm1025 | Owner: ocean90 Type: defect | Status: accepted Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by ocean90): In [changeset:"5457"]: {{{ #!CommitTicketReference repository="" revision="5457" Plugin Directory: Add markup information (JSON+LD) for front page and plugin pages. See #2661. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 1 21:23:28 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 1 May 2017 21:23:28 +0000 (UTC) Subject: [wp-meta] [5457] sites/trunk/wordpress.org/public_html/wp-content: Plugin Directory: Add markup information (JSON+LD) for front page and plugin pages. Message-ID: <20170501212328.DB06D10803BA@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon May 1 21:32:25 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 01 May 2017 21:32:25 -0000 Subject: [wp-meta] [Making WordPress.org] #2776: Plugin Directory: Improve responsive design of tabs In-Reply-To: <057.4652b685e582b5b4d950db30360f520e@wordpress.org> References: <057.4652b685e582b5b4d950db30360f520e@wordpress.org> Message-ID: <072.208f49f42dda80f2577bef7e601f16fb@wordpress.org> #2776: Plugin Directory: Improve responsive design of tabs -----------------------------------------------------+------------------ Reporter: kevinwhoffman | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: ui-feedback ux-feedback has-screenshots | -----------------------------------------------------+------------------ Comment (by mapk): I've got it just about dialed in with really bad JS. :) The responsiveness of the tabs works pretty well. Try it out here: http://codepen.io/mapk/full/BRWGWQ/ If anyone has any suggestions or feedback, please speak up. We'll be looking to get this implemented as soon as the JS gets worked out better. Thanks! [[Image(https://cldup.com/F6ONY3YLsM.gif)]] -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 1 22:10:30 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 1 May 2017 22:10:30 +0000 (UTC) Subject: [wp-meta] [5458] sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory/jobs/class-plugin-i18n-import.php: Plugin Directory: Call `array_unique()` after merging touched tags (and revisions) to avoid duplicate imports. Message-ID: <20170501221030.5CF0110803BA@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon May 1 23:05:43 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 01 May 2017 23:05:43 -0000 Subject: [wp-meta] [Making WordPress.org] #2804: Plugin Directory: Plugin names are being grabbed from the wrong file Message-ID: <051.af15c041d0aaa46226e9fa210b2e7a99@wordpress.org> #2804: Plugin Directory: Plugin names are being grabbed from the wrong file ------------------------------+----------------- Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Keywords: ------------------------------+----------------- When you submit a plugin, it is SUPPOSED to scan the main plugin file for headers, and use that to generate the plugin slug and display name. That scan should limit itself to the first folder, as otherwise it grabs the wrong data. Like if you've included a sub-plugin with headers it may grab those instead of yours. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 2 05:49:59 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 02 May 2017 05:49:59 -0000 Subject: [wp-meta] [Making WordPress.org] #2606: Inaccurate plugin rating counts In-Reply-To: <051.0bf781f8f7524fa1b946e2cf4dbff5bb@wordpress.org> References: <051.0bf781f8f7524fa1b946e2cf4dbff5bb@wordpress.org> Message-ID: <066.f253d9da912891d6e89e3eb37d522431@wordpress.org> #2606: Inaccurate plugin rating counts ------------------------------+------------------------------------ Reporter: svenl77 | Owner: Otto42 Type: defect | Status: assigned Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: needs-patch | ------------------------------+------------------------------------ Comment (by keraweb): What is the status for this issue? I have the same thing with one of my plugins. The WP.org API returns the archived/spammed reviews as well. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 2 07:49:34 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 2 May 2017 07:49:34 +0000 (UTC) Subject: [wp-meta] [5459] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-plugins/functions.php: Plugin Directory: Make tagline for the document title translatable. Message-ID: <20170502074934.923A4108034D@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Tue May 2 16:27:49 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 02 May 2017 16:27:49 -0000 Subject: [wp-meta] [Making WordPress.org] #2737: Plugin Directory: Rejected Plugins slugs need to be changed In-Reply-To: <051.7cf3a17926c50ef2f393dc4062bc0f4e@wordpress.org> References: <051.7cf3a17926c50ef2f393dc4062bc0f4e@wordpress.org> Message-ID: <066.93b4971cd45e7c6c8bf226f40924bde4@wordpress.org> #2737: Plugin Directory: Rejected Plugins slugs need to be changed ------------------------------+--------------------- Reporter: Ipstenu | Owner: Otto42 Type: defect | Status: closed Priority: normal | Milestone: Component: Plugin Directory | Resolution: fixed Keywords: has-patch commit | ------------------------------+--------------------- Changes (by Otto42): * owner: => Otto42 * status: new => closed * resolution: => fixed Comment: In [changeset:"5460"]: {{{ #!CommitTicketReference repository="" revision="5460" Plugin Directory: Add 'rejected' to slugs of rejected plugins. Fixes #2737. Props @SergeyBiryukov }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 2 16:27:48 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 2 May 2017 16:27:48 +0000 (UTC) Subject: [wp-meta] [5460] sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory/admin/class-status-transitions.php: Plugin Directory: Add 'rejected' to slugs of rejected plugins. Message-ID: <20170502162748.9A16A108034D@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Tue May 2 16:28:51 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 02 May 2017 16:28:51 -0000 Subject: [wp-meta] [Making WordPress.org] #2642: Better boosting for phrase matches (or add support for the user to specify a phrase) In-Reply-To: <051.6ac0b0ad0bb1fc49ee7e4ab29ad2ae98@wordpress.org> References: <051.6ac0b0ad0bb1fc49ee7e4ab29ad2ae98@wordpress.org> Message-ID: <066.69a6cd0e2897f0538e9333bc29d116a2@wordpress.org> #2642: Better boosting for phrase matches (or add support for the user to specify a phrase) ------------------------------+------------------------------------------- Reporter: gibrown | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by gibrown): Hi @yani.iliev thanks for the feedback very helpful, will look into these. On > Stemming is not very good We are intentionally using minimal stemming so for English we are only removing plurals. Very aggressive stemming like you suggest tends to reduce search relevancy based on most of the papers I have read. A good one looking at stemming in various languages is https://www.ercim.eu/publication/ws-proceedings/CLEF2/savoy.pdf Off the top of my head, a good example where more aggressive stemming would hurt us is "stored", "store", and "storing". This change would likely boost some popular plugins that are storing data into the results for building an e-commerce "store". It may be interesting to try more aggressive stemming as a boost, but I think the impact would be marginal at best and we don't really have the A/B testing infrastructure in place to evaluate such a change. (I wish we did because I'd really like to know what impact this would have). -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 2 16:37:49 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 02 May 2017 16:37:49 -0000 Subject: [wp-meta] [Making WordPress.org] #2755: 404s for Plugins should return search results In-Reply-To: <051.b826d8fb7fc192a9ab6231e674975963@wordpress.org> References: <051.b826d8fb7fc192a9ab6231e674975963@wordpress.org> Message-ID: <066.3b04cd9d580437b655012e5b815af943@wordpress.org> #2755: 404s for Plugins should return search results -------------------------------+------------------------------------------- Reporter: gibrown | Owner: Otto42 Type: enhancement | Status: closed Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: fixed Keywords: has-patch dev- | feedback | -------------------------------+------------------------------------------- Changes (by Otto42): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"5461"]: {{{ #!CommitTicketReference repository="" revision="5461" Plugin Directory: Redirect 404s to plugin search using the slug as the search term. Fixes #2755. Props @gibrown }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 2 16:36:54 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 02 May 2017 16:36:54 -0000 Subject: [wp-meta] [Making WordPress.org] #2755: 404s for Plugins should return search results In-Reply-To: <051.b826d8fb7fc192a9ab6231e674975963@wordpress.org> References: <051.b826d8fb7fc192a9ab6231e674975963@wordpress.org> Message-ID: <066.e840debdc7a936b2f94997b1b328e898@wordpress.org> #2755: 404s for Plugins should return search results -------------------------------+------------------------------------------- Reporter: gibrown | Owner: Otto42 Type: enhancement | Status: accepted Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: has-patch dev- | feedback | -------------------------------+------------------------------------------- Changes (by Otto42): * owner: => Otto42 * status: new => accepted Comment: Seems to work correctly for both admin and non-admin users. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 2 16:37:48 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 2 May 2017 16:37:48 +0000 (UTC) Subject: [wp-meta] [5461] sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory/class-plugin-directory.php: Plugin Directory: Redirect 404s to plugin search using the slug as the search term. Message-ID: <20170502163748.CE081108034D@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Tue May 2 17:51:45 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 02 May 2017 17:51:45 -0000 Subject: [wp-meta] [Making WordPress.org] #2655: Code blocks escaped with backticks are not parsed in FAQ? In-Reply-To: <050.550f9180f4374492d522eed5f479fcd8@wordpress.org> References: <050.550f9180f4374492d522eed5f479fcd8@wordpress.org> Message-ID: <065.d17239e030920b8b87104439ee15a8a8@wordpress.org> #2655: Code blocks escaped with backticks are not parsed in FAQ? ------------------------------+------------------ Reporter: GamerZ | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------ Comment (by Otto42): @GamerZ Can't hurt to try the original form. I have seen authors using more or less unaltered markdown, including such things as # headers. Seems to work fine in the new directory. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 2 17:54:12 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 02 May 2017 17:54:12 -0000 Subject: [wp-meta] [Making WordPress.org] #2644: Last updated should update when trunk is stable_tag & trunk files altered In-Reply-To: <048.adc8ee0e51654d9cb5f132bb38161fb2@wordpress.org> References: <048.adc8ee0e51654d9cb5f132bb38161fb2@wordpress.org> Message-ID: <063.0ee0737750ee626effca2d81bebf9714@wordpress.org> #2644: Last updated should update when trunk is stable_tag & trunk files altered ------------------------------+------------------------------------------- Reporter: dd32 | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by Otto42): Could we not simply use "svn info" to get the last changed date of the directory where "Stable" is and consider that to be the last updated date? Seems like this would solve both problems. It also is what one previous incarnation of the directory did, though that has changed a few times. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 2 18:05:36 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 02 May 2017 18:05:36 -0000 Subject: [wp-meta] [Making WordPress.org] #2647: search in plugin repository by contributors name does not find their plugins In-Reply-To: <055.b5a37bbbae65b8498fd0ad3ab35615a2@wordpress.org> References: <055.b5a37bbbae65b8498fd0ad3ab35615a2@wordpress.org> Message-ID: <070.80b5f8804300667ce6a8975f23d30176@wordpress.org> #2647: search in plugin repository by contributors name does not find their plugins ------------------------------+---------------------- Reporter: progmastery | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Plugin Directory | Resolution: wontfix Keywords: needs-patch | ------------------------------+---------------------- Changes (by Otto42): * status: new => closed * resolution: => wontfix * milestone: Plugin Directory v3.0 => Comment: [5204] did not introduce the problem, that simply fixed it for the API case. Note that searching from a WordPress installation has a dropdown next to the search for Keyword, Tag, and Author searching. These appear to work correctly in my testing, and searching for an author with the Author selected will indeed return the correct results. That's what [5204] fixed. However, the Plugin directory search displayed on the website is essentially only returning the search results as if you're doing a "Keyword" search. Since author name is not in the index as part of the plugin description or changelog or what have you, then it won't be found by such a search on the website itself. I believe this is working as intended in this case, as the "author" fields are being specifically saved as such for those Author searches in the WordPress backend. If you wish to present a place for people to find your plugins, then the profiles page is best for that, as you have control over what plugins are displayed there. If you want to direct people how to find your plugins in the WordPress backend admin pages, for installation, then the Author search is available, as is the Tags search, which you have a fine grain of control over as well. Alternatively, simply putting author information into your description will work for that case as well, although given the profiles listing, the Author dropdown, and even Tags, this seems unnecessary. For these reasons, I'm closing this as wontfix for now. If at some point it makes sense to include that author information in the index as a searchable keyword, then this may be re-opened. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 2 21:33:55 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 2 May 2017 21:33:55 +0000 (UTC) Subject: [wp-meta] [5462] sites/trunk/api.wordpress.org/public_html/events/1.0: Events: Attempts all name-based lookups before resorting to IP lookup Message-ID: <20170502213355.42A21108034D@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed May 3 02:01:10 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 3 May 2017 02:01:10 +0000 (UTC) Subject: [wp-meta] [5463] sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory/shortcodes/class-developers.php: Plugin Directory: Fix errorin translation ordering. Message-ID: <20170503020110.B4EAA1080595@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed May 3 03:18:58 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 03 May 2017 03:18:58 -0000 Subject: [wp-meta] [Making WordPress.org] #2805: Sort Beta browser by last updated Message-ID: <048.e38f940947a526718063d2d428bbcb2b@wordpress.org> #2805: Sort Beta browser by last updated ------------------------------+------------------------------------------ Reporter: dd32 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Keywords: ux-feedback ------------------------------+------------------------------------------ It'd probably be useful to people to sort https://wordpress.org/plugins/browse/beta/ by their updated dates rather than by active installs. My reasoning is that people are more interested in testing newly developed features rather than some of the 1+ year old plugins which exist as feature projects. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 3 07:46:44 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 03 May 2017 07:46:44 -0000 Subject: [wp-meta] [Making WordPress.org] #2655: Code blocks escaped with backticks are not parsed in FAQ? In-Reply-To: <050.550f9180f4374492d522eed5f479fcd8@wordpress.org> References: <050.550f9180f4374492d522eed5f479fcd8@wordpress.org> Message-ID: <065.d93da6ffd652dd634b67c62181c87528@wordpress.org> #2655: Code blocks escaped with backticks are not parsed in FAQ? ------------------------------+------------------ Reporter: GamerZ | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------ Comment (by GamerZ): Replying to [comment:5 Otto42]: > @GamerZ Can't hurt to try the original form. I have seen authors using more or less unaltered markdown, including such things as # headers. Seems to work fine in the new directory. Thanks. I tested, it works fine. But the bug still persists despite using GH Markdown. Can't have code in a bullet point -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 3 09:13:36 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 03 May 2017 09:13:36 -0000 Subject: [wp-meta] [Making WordPress.org] #2699: Add a new role to the forums: plugin/theme support In-Reply-To: <053.e04c8d0168f06e230413f4c13e10a319@wordpress.org> References: <053.e04c8d0168f06e230413f4c13e10a319@wordpress.org> Message-ID: <068.5a3049f0988b90671fbb6d2268a75a05@wordpress.org> #2699: Add a new role to the forums: plugin/theme support ----------------------------+------------------ Reporter: TacoVerdo | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Comment (by Luminus): +1 I'd love to see this shipped. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 3 09:19:46 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 03 May 2017 09:19:46 -0000 Subject: [wp-meta] [Making WordPress.org] #2699: Add a new role to the forums: plugin/theme support In-Reply-To: <053.e04c8d0168f06e230413f4c13e10a319@wordpress.org> References: <053.e04c8d0168f06e230413f4c13e10a319@wordpress.org> Message-ID: <068.081a8f3e22f40e44b2e6286a48e40755@wordpress.org> #2699: Add a new role to the forums: plugin/theme support ----------------------------+------------------ Reporter: TacoVerdo | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Comment (by davor.altman): +1 definitely! -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 3 09:30:50 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 03 May 2017 09:30:50 -0000 Subject: [wp-meta] [Making WordPress.org] #2642: Better boosting for phrase matches (or add support for the user to specify a phrase) In-Reply-To: <051.6ac0b0ad0bb1fc49ee7e4ab29ad2ae98@wordpress.org> References: <051.6ac0b0ad0bb1fc49ee7e4ab29ad2ae98@wordpress.org> Message-ID: <066.b7b136175882cc2581f991346d003633@wordpress.org> #2642: Better boosting for phrase matches (or add support for the user to specify a phrase) ------------------------------+------------------------------------------- Reporter: gibrown | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by yani.iliev): Replying to [comment:24 gibrown]: Hi @gibrown, Could you provide some details on the stemming algorithm currently in use and I might be able to provide some suggestions how to make it slightly more aggressive? I think there is a case of understemming in English and I'd like to see a slightly more aggressive stemming but not to cause overstemming. Every language different - what works in English will likely not work in Bulgarian - I'd optimize per language. You mentioned that there is no A/B testing infrastructure. In the search data that you have - is there a link between a search term and the plugins that were installed after the search? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 3 12:45:41 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 3 May 2017 12:45:41 +0000 (UTC) Subject: [wp-meta] [5464] sites/trunk/common/includes/slack/announce/config.php: Slack Announce: Add @schlessera to #cli. Message-ID: <20170503124541.A3AE810803BA@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed May 3 13:13:08 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 03 May 2017 13:13:08 -0000 Subject: [wp-meta] [Making WordPress.org] #2642: Better boosting for phrase matches (or add support for the user to specify a phrase) In-Reply-To: <051.6ac0b0ad0bb1fc49ee7e4ab29ad2ae98@wordpress.org> References: <051.6ac0b0ad0bb1fc49ee7e4ab29ad2ae98@wordpress.org> Message-ID: <066.db5dc34c606a5fca531283bde4e2966d@wordpress.org> #2642: Better boosting for phrase matches (or add support for the user to specify a phrase) ------------------------------+------------------------------------------- Reporter: gibrown | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by gibrown): Hi @yani.iliev Most of my thinking on stemming is still applicable from this post: https://greg.blog/2013/05/01/three-principles-for-multilingal-indexing-in- elasticsearch/ The analyzers we are using are here: https://github.com/Automattic/wpes- lib/blob/master/src/common/class.wpes-analyzer-builder.php > is there a link between a search term and the plugins that were installed after the search? No unfortunately. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 3 13:56:19 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 03 May 2017 13:56:19 -0000 Subject: [wp-meta] [Making WordPress.org] #2805: Sort Beta browser by last updated In-Reply-To: <048.e38f940947a526718063d2d428bbcb2b@wordpress.org> References: <048.e38f940947a526718063d2d428bbcb2b@wordpress.org> Message-ID: <063.b5983978eecc67644628f9207da439f7@wordpress.org> #2805: Sort Beta browser by last updated ------------------------------+------------------------------------------- Reporter: dd32 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: ux-feedback | ------------------------------+------------------------------------------- Comment (by gibrown): That makes sense. I think this should be a part of #2753 Make a UI for search that is also more browsable. "beta" is just a special tag/category right? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 3 16:38:12 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 03 May 2017 16:38:12 -0000 Subject: [wp-meta] [Making WordPress.org] #2806: Feature Request - Introduce Name onto User Profiles Message-ID: <059.7afbd222a2d5cc83ce21b57be0338ac2@wordpress.org> #2806: Feature Request - Introduce Name onto User Profiles -----------------------------+----------------- Reporter: garrett-eclipse | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Profiles | Keywords: -----------------------------+----------------- Hello, Clicking through a user @tag to their profile I realized that although their name is in the forums it's not listed on their profile. Figured it should be there. http://i.imgur.com/z6rJBlf.png Cheers -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 3 17:32:15 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 3 May 2017 17:32:15 +0000 (UTC) Subject: [wp-meta] [5465] sites/trunk/wordpress.org/public_html/wp-content/plugins/handbook/ inc/callout-boxes.php: Handbook plugin: Disable o2 processing for callout box content. Message-ID: <20170503173215.29E2710803BA@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed May 3 17:36:10 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 3 May 2017 17:36:10 +0000 (UTC) Subject: [wp-meta] [5467] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-breathe/style.css: Breathe: Change styling for "Top" links so as not to overlap with in-page table of contents. Message-ID: <20170503173610.F409610803BA@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed May 3 17:36:11 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 03 May 2017 17:36:11 -0000 Subject: [wp-meta] [Making WordPress.org] #2777: Issue on the recently created FAQ page In-Reply-To: <048.c4f0c001e6ea4b1da6c162535f7ccd2b@wordpress.org> References: <048.c4f0c001e6ea4b1da6c162535f7ccd2b@wordpress.org> Message-ID: <063.0a409ab34ab75e74c866e7e962951ea9@wordpress.org> #2777: Issue on the recently created FAQ page --------------------------+-------------------------- Reporter: bplv | Owner: coffee2code Type: defect | Status: closed Priority: normal | Milestone: Component: Theme Review | Resolution: fixed Keywords: | --------------------------+-------------------------- Changes (by coffee2code): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"5467"]: {{{ #!CommitTicketReference repository="" revision="5467" Breathe: Change styling for "Top" links so as not to overlap with in-page table of contents. Fixes #2777. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 3 17:32:15 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 03 May 2017 17:32:15 -0000 Subject: [wp-meta] [Making WordPress.org] #2803: Tags and action links appended to [info] blocks in P2 post content In-Reply-To: <055.47fe1f405b4e46c7341091c8cacab14d@wordpress.org> References: <055.47fe1f405b4e46c7341091c8cacab14d@wordpress.org> Message-ID: <070.0476725eb8de4ef11f2e9d0082b055de@wordpress.org> #2803: Tags and action links appended to [info] blocks in P2 post content --------------------------------------+-------------------------- Reporter: johnbillion | Owner: coffee2code Type: defect | Status: closed Priority: normal | Milestone: Component: Make (Get Involved) / P2 | Resolution: fixed Keywords: needs-patch | --------------------------------------+-------------------------- Changes (by coffee2code): * owner: => coffee2code * status: new => closed * resolution: => fixed Comment: In [changeset:"5465"]: {{{ #!CommitTicketReference repository="" revision="5465" Handbook plugin: Disable o2 processing for callout box content. Fixes #2803. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 3 17:34:20 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 3 May 2017 17:34:20 +0000 (UTC) Subject: [wp-meta] [5466] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-breathe/style.css: Breathe: Decrease bottom padding within callout boxes. Message-ID: <20170503173420.73F7010803BA@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed May 3 17:43:24 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 3 May 2017 17:43:24 +0000 (UTC) Subject: [wp-meta] [5468] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-breathe/style.css: Breathe: Add spacing between adjacent `h3` and `h4` tags. Message-ID: <20170503174324.9C1A810803BA@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed May 3 17:46:32 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 03 May 2017 17:46:32 -0000 Subject: [wp-meta] [Making WordPress.org] #1944: Plugin Commit Check: Verify License Declarations In-Reply-To: <051.3a4adfaaa14b2a9b7bc406f22046d4d6@wordpress.org> References: <051.3a4adfaaa14b2a9b7bc406f22046d4d6@wordpress.org> Message-ID: <066.eeeed5dd7dcbb82e9ddcba358cca2e3d@wordpress.org> #1944: Plugin Commit Check: Verify License Declarations ------------------------------+------------------ Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------ Comment (by Ipstenu): Use https://spdx.org/licenses/ to validate license format. If we could somehow automate checking "These are GPLv2+ compatible" that would be brilliant. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 3 17:54:09 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 03 May 2017 17:54:09 -0000 Subject: [wp-meta] [Making WordPress.org] #2465: Create new WPorg home for wp-cli.org/commands and wp-cli.org/docs/internal-api In-Reply-To: <059.b4f59d4a8621ef6ac581d70037e4aba9@wordpress.org> References: <059.b4f59d4a8621ef6ac581d70037e4aba9@wordpress.org> Message-ID: <074.816e9d8264442860ab098cc5cfde4aa5@wordpress.org> #2465: Create new WPorg home for wp-cli.org/commands and wp-cli.org/docs/internal- api -----------------------------+-------------------------- Reporter: danielbachhuber | Owner: coffee2code Type: task | Status: closed Priority: normal | Milestone: Component: Developer Hub | Resolution: fixed Keywords: wp-cli | -----------------------------+-------------------------- Changes (by coffee2code): * owner: => coffee2code * status: new => closed * resolution: => fixed Comment: In [changeset:"5469"]: {{{ #!CommitTicketReference repository="" revision="5469" developer.wordpress.org: Register `command` post type and cron jobs for importing command documentation. For wp-cli command documentation. Props danielbachhuber. Fixes #2465. }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 3 17:54:08 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 3 May 2017 17:54:08 +0000 (UTC) Subject: [wp-meta] [5469] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-developer: developer.wordpress.org: Register `command` post type and cron jobs for importing command documentation. Message-ID: <20170503175408.C0B1610803BA@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed May 3 18:06:38 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 3 May 2017 18:06:38 +0000 (UTC) Subject: [wp-meta] [5470] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-breathe/functions.php: Breathe: Bump CSS version for cache bust. Message-ID: <20170503180638.D68D410803BA@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed May 3 20:07:08 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 03 May 2017 20:07:08 -0000 Subject: [wp-meta] [Making WordPress.org] #2807: Plugin Directory - Remove "Installation Instructions" from FAQ Message-ID: <048.41c54c3e8d8de7f1e5dfe791761aa1ad@wordpress.org> #2807: Plugin Directory - Remove "Installation Instructions" from FAQ ------------------------------+------------------------- Reporter: mapk | Owner: Type: task | Status: new Priority: normal | Milestone: Component: Plugin Directory | Keywords: 2nd-opinion ------------------------------+------------------------- Now that "Installation" has its own tab, we could probably remove it from the first item in the FAQs. [[Image(https://cldup.com/RGRSVQ3ORM.png)]] -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 3 21:52:49 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 03 May 2017 21:52:49 -0000 Subject: [wp-meta] [Making WordPress.org] #2787: Plugin Directory: Reject plugin on duplicate slugs In-Reply-To: <051.2ac2a1bb741f1b18b5c20f5005ec290b@wordpress.org> References: <051.2ac2a1bb741f1b18b5c20f5005ec290b@wordpress.org> Message-ID: <066.34f349ddbe5fa98036d17fb11cd9c55c@wordpress.org> #2787: Plugin Directory: Reject plugin on duplicate slugs ------------------------------+------------------------- Reporter: Ipstenu | Owner: tellyworth Type: defect | Status: reopened Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------- Comment (by SergeyBiryukov): Replying to [comment:5 Ipstenu]: > Someone decided to keep resubmitting when the name was 'wrong' (I need to change THAT error message too...) and we got the same plugin with a -2 appending. Just tested on a local install, and [5416] appears to work as expected. Could it be that it was not deployed yet at the time when that happened? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 3 22:00:20 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 03 May 2017 22:00:20 -0000 Subject: [wp-meta] [Making WordPress.org] #2776: Plugin Directory: Improve responsive design of tabs In-Reply-To: <057.4652b685e582b5b4d950db30360f520e@wordpress.org> References: <057.4652b685e582b5b4d950db30360f520e@wordpress.org> Message-ID: <072.a5b05ef44baaf0627e61280da5684a78@wordpress.org> #2776: Plugin Directory: Improve responsive design of tabs -----------------------------------------------------+------------------ Reporter: kevinwhoffman | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: ui-feedback ux-feedback has-screenshots | -----------------------------------------------------+------------------ Comment (by kevinwhoffman): @mapk This looks really good to me. Keep in mind there is also an `Installation` tab on the live Plugin Directory, but the way you are calculating widths means the number of tabs should not matter. Good stuff. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 3 22:26:11 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 03 May 2017 22:26:11 -0000 Subject: [wp-meta] [Making WordPress.org] #2788: Plugin Direction: Clarify language for submission errors In-Reply-To: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> References: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> Message-ID: <066.08fa2598c333da569037769341cda79c@wordpress.org> #2788: Plugin Direction: Clarify language for submission errors -------------------------------------+------------------ Reporter: Ipstenu | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch needs-refresh | -------------------------------------+------------------ Changes (by ocean90): * keywords: has-patch => has-patch needs-refresh Comment: The email should be a placeholder in the strings so it doesn't get translated. Don't forget to update the translator comments. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 3 22:38:30 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 3 May 2017 22:38:30 +0000 (UTC) Subject: [wp-meta] [5471] sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory/shortcodes/class-upload-handler.php: Plugin directory: clarify error messages during submission process. Message-ID: <20170503223830.9734E10803BA@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed May 3 22:38:31 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 03 May 2017 22:38:31 -0000 Subject: [wp-meta] [Making WordPress.org] #2788: Plugin Direction: Clarify language for submission errors In-Reply-To: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> References: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> Message-ID: <066.310111db98b29b718c309a61f9aa55cc@wordpress.org> #2788: Plugin Direction: Clarify language for submission errors -------------------------------------+------------------------- Reporter: Ipstenu | Owner: tellyworth Type: enhancement | Status: closed Priority: normal | Milestone: Component: Plugin Directory | Resolution: fixed Keywords: has-patch needs-refresh | -------------------------------------+------------------------- Changes (by tellyworth): * owner: => tellyworth * status: new => closed * resolution: => fixed Comment: In [changeset:"5471"]: {{{ #!CommitTicketReference repository="" revision="5471" Plugin directory: clarify error messages during submission process. Props @ipstenu. Fixes #2788 }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 3 22:35:18 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 03 May 2017 22:35:18 -0000 Subject: [wp-meta] [Making WordPress.org] #2787: Plugin Directory: Reject plugin on duplicate slugs In-Reply-To: <051.2ac2a1bb741f1b18b5c20f5005ec290b@wordpress.org> References: <051.2ac2a1bb741f1b18b5c20f5005ec290b@wordpress.org> Message-ID: <066.df837951e442e2beb9d157fc57ec3471@wordpress.org> #2787: Plugin Directory: Reject plugin on duplicate slugs ------------------------------+------------------------- Reporter: Ipstenu | Owner: tellyworth Type: defect | Status: reopened Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------- Comment (by SergeyBiryukov): Nevermind, reproduced with a newly submitted plugin (previously tried with a published one). It's the same issue that was mentioned in comment:4:ticket:2594. [source:sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin- directory/class-plugin-directory.php?rev=5463&marks=1164#L1160 Plugin_Directory::get_plugin_post()] includes a list of 7 plugin statuses to query: `'publish', 'pending', 'disabled', 'closed', 'new', 'draft', 'approved'`, but [source:sites/trunk/wordpress.org/public_html/wp- content/plugins/plugin-directory/class-plugin- directory.php?rev=5463&marks=758#L755 Plugin_Directory::pre_get_posts()] overrides that list and limits the query to 4 statuses `'approved', 'publish', 'closed', 'disabled'` (note that lack of `'new'`). Adding `! $wp_query->is_main_query()` to `Plugin_Directory::pre_get_posts()`, as in attachment:2594.3.patch:ticket:2594, fixes the issue. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 3 22:46:48 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 3 May 2017 22:46:48 +0000 (UTC) Subject: [wp-meta] [5472] sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/ wcorg-network-plugin-control.php: WordCamp: Remove the EU Cookie Law plugin from the network control list Message-ID: <20170503224648.093C110803BA@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Wed May 3 23:23:57 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 03 May 2017 23:23:57 -0000 Subject: [wp-meta] [Making WordPress.org] #2808: WordCamp 'organizers' shortcode does not accept an order attribute Message-ID: <056.ad656282860d62eeb839324b60abc753@wordpress.org> #2808: WordCamp 'organizers' shortcode does not accept an order attribute ----------------------------------+---------------------------------------- Reporter: coreymckrill | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: WordCamp Site & | Keywords: needs-patch good-first-bug Plugins | ----------------------------------+---------------------------------------- Unlike some of its sibling shortcodes like `speakers` and `sessions`, the `organizers` shortcode has no way to sort the items it outputs in ascending order. It accepts an `orderby` attribute, but not `order`, so the resulting post query defaults to descending order. Slack discussion here: https://wordpress.slack.com/archives/C08M59V3P/p1493841000894509 -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 3 23:59:50 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 03 May 2017 23:59:50 -0000 Subject: [wp-meta] [Making WordPress.org] #2806: Feature Request - Introduce Name onto User Profiles In-Reply-To: <059.7afbd222a2d5cc83ce21b57be0338ac2@wordpress.org> References: <059.7afbd222a2d5cc83ce21b57be0338ac2@wordpress.org> Message-ID: <074.cfd2e1fce92a15ad688f43009c9c09f1@wordpress.org> #2806: Feature Request - Introduce Name onto User Profiles -----------------------------+------------------ Reporter: garrett-eclipse | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | -----------------------------+------------------ Changes (by netweb): * component: Profiles => Support Forums Comment: A thumbs up from me, maybe in the same location above the gravatar as it is for profiles.w.org: * [[Image(https://cldup.com/GQAc3qDHpX.png)]] -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 00:12:18 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 00:12:18 -0000 Subject: [wp-meta] [Making WordPress.org] #2806: Feature Request - Introduce Name onto User Profiles In-Reply-To: <059.7afbd222a2d5cc83ce21b57be0338ac2@wordpress.org> References: <059.7afbd222a2d5cc83ce21b57be0338ac2@wordpress.org> Message-ID: <074.80a4c11a0f92d26e94f1a9fb7d9996ed@wordpress.org> #2806: Feature Request - Introduce Name onto User Profiles -----------------------------+------------------ Reporter: garrett-eclipse | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | -----------------------------+------------------ Comment (by garrett-eclipse): Thanks @netweb Seeing those side by side I'd almost say merge them or somehow have their templates match and be consistent with the icons and what information is available. Cheers -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 00:13:58 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 00:13:58 -0000 Subject: [wp-meta] [Making WordPress.org] #2806: Feature Request - Introduce Name onto User Profiles In-Reply-To: <059.7afbd222a2d5cc83ce21b57be0338ac2@wordpress.org> References: <059.7afbd222a2d5cc83ce21b57be0338ac2@wordpress.org> Message-ID: <074.c597eff143698830fa868aa1e0fc2f33@wordpress.org> #2806: Feature Request - Introduce Name onto User Profiles -----------------------------+------------------ Reporter: garrett-eclipse | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | -----------------------------+------------------ Comment (by netweb): Replying to [comment:2 garrett-eclipse]: > Thanks @netweb > Seeing those side by side I'd almost say merge them or somehow have their templates match and be consistent with the icons and what information is available. > Cheers That'd be #518 -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 00:24:43 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 00:24:43 -0000 Subject: [wp-meta] [Making WordPress.org] #2806: Feature Request - Introduce Name onto User Profiles In-Reply-To: <059.7afbd222a2d5cc83ce21b57be0338ac2@wordpress.org> References: <059.7afbd222a2d5cc83ce21b57be0338ac2@wordpress.org> Message-ID: <074.870eff109d6fe60d9edbcec9315fe087@wordpress.org> #2806: Feature Request - Introduce Name onto User Profiles -----------------------------+------------------ Reporter: garrett-eclipse | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | -----------------------------+------------------ Comment (by garrett-eclipse): Replying to [comment:3 netweb]: > Replying to [comment:2 garrett-eclipse]: > > Thanks @netweb > > Seeing those side by side I'd almost say merge them or somehow have their templates match and be consistent with the icons and what information is available. > > Cheers > That'd be #518 THANKS @netweb -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 02:17:18 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 02:17:18 -0000 Subject: [wp-meta] [Making WordPress.org] #2809: Support posts with HTML can break page display In-Reply-To: <052.56371cd89be700c27d3808dc3e92c6e6@wordpress.org> References: <052.56371cd89be700c27d3808dc3e92c6e6@wordpress.org> Message-ID: <067.7d8d0e75d840e56d4dd36c1b7e5f2455@wordpress.org> #2809: Support posts with HTML can break page display ------------------------------+------------------ Reporter: webaware | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------ Changes (by webaware): * component: General => Plugin Directory -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 02:15:35 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 02:15:35 -0000 Subject: [wp-meta] [Making WordPress.org] #2809: Support posts with HTML can break page display Message-ID: <052.56371cd89be700c27d3808dc3e92c6e6@wordpress.org> #2809: Support posts with HTML can break page display ----------------------+----------------- Reporter: webaware | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: General | Keywords: ----------------------+----------------- When support posts contain broken HTML, the whole page layout can be broken. This can happen when someone posts an HTML example without wrapping in code tags. Yes, they should do that, but they often know that they should do that. e.g. https://wordpress.org/support/topic/upgrade-killed-page-edit- ability/#post-9091322 -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 02:25:48 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 02:25:48 -0000 Subject: [wp-meta] [Making WordPress.org] #2809: Support posts with HTML can break page display In-Reply-To: <052.56371cd89be700c27d3808dc3e92c6e6@wordpress.org> References: <052.56371cd89be700c27d3808dc3e92c6e6@wordpress.org> Message-ID: <067.7940be9a5f161ec36d4682d89e20f9f8@wordpress.org> #2809: Support posts with HTML can break page display ----------------------------+------------------------ Reporter: webaware | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Support Forums | Resolution: duplicate Keywords: | ----------------------------+------------------------ Changes (by netweb): * status: new => closed * resolution: => duplicate * component: Plugin Directory => Support Forums Comment: Thanks, closing as a duplicate of #20 -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 03:00:35 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 03:00:35 -0000 Subject: [wp-meta] [Making WordPress.org] #2810: plugin_information API Missing Screenshot Captions Message-ID: <053.c90ec661559858e6da93b648bd6657e6@wordpress.org> #2810: plugin_information API Missing Screenshot Captions -----------------------+----------------- Reporter: blobfolio | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: General | Keywords: -----------------------+----------------- I'm not sure when exactly this started, but I noticed tonight that the plugin_information API is no longer providing screenshot captions; there's a key for them, but the values are empty strings. {{{ // Example call from within WordPress. $response = plugins_api('plugin_information', array('slug'=>'apocalypse- meow')); print_r($response); /* ... [screenshots] => Array ( [1] => Array ( [src] => https://ps.w.org/apocalypse- meow/assets/screenshot-1.png?rev=1421211 [caption] => ) ... */ }}} The problem doesn't appear to be within the Core's `plugins_api()` wrapper function; the raw responses (both serialized and JSON) are also missing captions. The WordPress.org plugin landing pages, however, are still correctly showing screenshot captions. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 03:14:23 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 4 May 2017 03:14:23 +0000 (UTC) Subject: [wp-meta] [5473] sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory/api/routes/class-plugin.php: Plugin Directory: API: Fix a typo preventing the screenshot captions being returned. Message-ID: <20170504031423.C065510805B2@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Thu May 4 03:14:24 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 03:14:24 -0000 Subject: [wp-meta] [Making WordPress.org] #2810: plugin_information API Missing Screenshot Captions In-Reply-To: <053.c90ec661559858e6da93b648bd6657e6@wordpress.org> References: <053.c90ec661559858e6da93b648bd6657e6@wordpress.org> Message-ID: <068.26408ceb3f37e144ee1bb3b84100a2af@wordpress.org> #2810: plugin_information API Missing Screenshot Captions -----------------------+--------------------- Reporter: blobfolio | Owner: dd32 Type: defect | Status: closed Priority: normal | Milestone: Component: General | Resolution: fixed Keywords: | -----------------------+--------------------- Changes (by dd32): * owner: => dd32 * status: new => closed * resolution: => fixed Comment: In [changeset:"5473"]: {{{ #!CommitTicketReference repository="" revision="5473" Plugin Directory: API: Fix a typo preventing the screenshot captions being returned. Fixes #2810 }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 03:15:34 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 03:15:34 -0000 Subject: [wp-meta] [Making WordPress.org] #2810: plugin_information API Missing Screenshot Captions In-Reply-To: <053.c90ec661559858e6da93b648bd6657e6@wordpress.org> References: <053.c90ec661559858e6da93b648bd6657e6@wordpress.org> Message-ID: <068.dcf92147ef974e6cc0deb82f2061c678@wordpress.org> #2810: plugin_information API Missing Screenshot Captions ------------------------------+--------------------- Reporter: blobfolio | Owner: dd32 Type: defect | Status: closed Priority: normal | Milestone: Component: Plugin Directory | Resolution: fixed Keywords: | ------------------------------+--------------------- Changes (by dd32): * component: General => Plugin Directory Comment: It'll take a little while for api caches to clear (I'd give it a day) but committing a change to your plugin (whitespace even) *should* be enough to trigger a cache clear. Thanks for reporting it! -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 03:18:56 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 03:18:56 -0000 Subject: [wp-meta] [Making WordPress.org] #2810: plugin_information API Missing Screenshot Captions In-Reply-To: <053.c90ec661559858e6da93b648bd6657e6@wordpress.org> References: <053.c90ec661559858e6da93b648bd6657e6@wordpress.org> Message-ID: <068.7af99121d008e3f8bd48a2806e4a01c8@wordpress.org> #2810: plugin_information API Missing Screenshot Captions ------------------------------+--------------------- Reporter: blobfolio | Owner: dd32 Type: defect | Status: closed Priority: normal | Milestone: Component: Plugin Directory | Resolution: fixed Keywords: | ------------------------------+--------------------- Comment (by blobfolio): So fast! Thank you! -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 03:27:20 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 03:27:20 -0000 Subject: [wp-meta] [Making WordPress.org] #2811: WordCamp.org: Disable Jetpack JITM Message-ID: <051.3104a7e411f78d028bf065bfd1e1cce7@wordpress.org> #2811: WordCamp.org: Disable Jetpack JITM -------------------------------------+----------------- Reporter: kraftbj | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: WordCamp Site & Plugins | Keywords: -------------------------------------+----------------- Jetpack has some "just-in-time messaging" to encourage site admins, etc to do things such as enable backups, etc. Since WordCamp Central has all those things setup, we probably should disable the messaging outright? `add_filter( 'jetpack_just_in_time_msgs', '__return_false', 11);` -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 06:04:23 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 06:04:23 -0000 Subject: [wp-meta] [Making WordPress.org] #2811: WordCamp.org: Disable Jetpack JITM In-Reply-To: <051.3104a7e411f78d028bf065bfd1e1cce7@wordpress.org> References: <051.3104a7e411f78d028bf065bfd1e1cce7@wordpress.org> Message-ID: <066.0ccff3d8754f276c1b0f9364c480d638@wordpress.org> #2811: WordCamp.org: Disable Jetpack JITM -------------------------------------+------------------ Reporter: kraftbj | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: | -------------------------------------+------------------ Comment (by ocean90): Does [5323] not work? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 07:49:03 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 07:49:03 -0000 Subject: [wp-meta] [Making WordPress.org] #2788: Plugin Direction: Clarify language for submission errors In-Reply-To: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> References: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> Message-ID: <066.a3b32cf5b5cbd99c9ba5587c469fac00@wordpress.org> #2788: Plugin Direction: Clarify language for submission errors ------------------------------+------------------------- Reporter: Ipstenu | Owner: tellyworth Type: enhancement | Status: reopened Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: needs-patch | ------------------------------+------------------------- Changes (by ocean90): * keywords: has-patch needs-refresh => needs-patch * status: closed => reopened * resolution: fixed => Comment: Thanks for ignoring my comment... -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 08:55:12 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 08:55:12 -0000 Subject: [wp-meta] [Making WordPress.org] #2812: I can't find my plugin in search results of plugin directory use the translated plugin name. In-Reply-To: <051.49e1b590ceb99bca42e7a007957d12f7@wordpress.org> References: <051.49e1b590ceb99bca42e7a007957d12f7@wordpress.org> Message-ID: <066.1e1747f74f7661c592c0e3dd2826a92f@wordpress.org> #2812: I can't find my plugin in search results of plugin directory use the translated plugin name. ------------------------------+------------------------ Reporter: ooqwqoo | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: Plugin Directory | Resolution: duplicate Keywords: | ------------------------------+------------------------ Changes (by ocean90): * status: new => closed * resolution: => duplicate * milestone: Plugin Directory v3.0 => Comment: Duplicate of #1496. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 08:52:41 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 08:52:41 -0000 Subject: [wp-meta] [Making WordPress.org] #2812: I can't find my plugin in search results of plugin directory use the translated plugin name. Message-ID: <051.49e1b590ceb99bca42e7a007957d12f7@wordpress.org> #2812: I can't find my plugin in search results of plugin directory use the translated plugin name. ------------------------------+----------------------------------- Reporter: ooqwqoo | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Keywords: ------------------------------+----------------------------------- This is my plugin: https://wordpress.org/plugins/wx-custom-share/ I have translated the plugin and plugin readme to zh_CN, but when I use translated plugin name as keyword to search something in plugin directory, my plugin is not show in results. Is possible to do it? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 08:53:49 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 08:53:49 -0000 Subject: [wp-meta] [Making WordPress.org] #2661: Plugin Theme: Reviews schema is missing on plugin pages, resulting in missing star ratings in Google In-Reply-To: <053.554abb8b9fdf2d86d25e44164d924031@wordpress.org> References: <053.554abb8b9fdf2d86d25e44164d924031@wordpress.org> Message-ID: <068.ff3eef2f2d22e35c8e97fc735a65856b@wordpress.org> #2661: Plugin Theme: Reviews schema is missing on plugin pages, resulting in missing star ratings in Google ------------------------------+------------------------------------ Reporter: Dharm1025 | Owner: ocean90 Type: defect | Status: closed Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: fixed Keywords: | ------------------------------+------------------------------------ Changes (by ocean90): * status: accepted => closed * resolution: => fixed * milestone: Plugin Directory v3 - Future => Plugin Directory v3.0 -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 09:31:27 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 09:31:27 -0000 Subject: [wp-meta] [Making WordPress.org] #2594: Plugin Directory: List pending plugins on 'add' page In-Reply-To: <051.8682691f18de896a37086227c227a3cc@wordpress.org> References: <051.8682691f18de896a37086227c227a3cc@wordpress.org> Message-ID: <066.1fb7bba02716905cb9c315ac6163dc3c@wordpress.org> #2594: Plugin Directory: List pending plugins on 'add' page -------------------------------------+------------------------------------- Reporter: Ipstenu | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Component: Plugin Directory | Future Keywords: has-patch commit has- | Resolution: screenshots | -------------------------------------+------------------------------------- Comment (by SergeyBiryukov): Replying to [comment:4 SergeyBiryukov]: > That was my initial attempt, but it didn't work due to `Plugin_Directory::pre_get_posts()` altering the same query. Maybe it should bail early if not `$wp_query->is_main_query()`? The same issue now happens in #2787, see comment:7:ticket:2787. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 13:03:28 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 13:03:28 -0000 Subject: [wp-meta] [Making WordPress.org] #2811: WordCamp.org: Disable Jetpack JITM In-Reply-To: <051.3104a7e411f78d028bf065bfd1e1cce7@wordpress.org> References: <051.3104a7e411f78d028bf065bfd1e1cce7@wordpress.org> Message-ID: <066.3e4858d3b8b396df2a6f2ab940ad2a76@wordpress.org> #2811: WordCamp.org: Disable Jetpack JITM -------------------------------------+------------------ Reporter: kraftbj | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: | -------------------------------------+------------------ Comment (by richardmtl): Replying to [comment:1 ocean90]: > Does [5323] not work? I got a message yesterday on 2017.montreal.wordcamp.org asking to me backup my site, after I had Published a Ticket. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 13:34:55 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 13:34:55 -0000 Subject: [wp-meta] [Making WordPress.org] #2811: WordCamp.org: Disable Jetpack JITM In-Reply-To: <051.3104a7e411f78d028bf065bfd1e1cce7@wordpress.org> References: <051.3104a7e411f78d028bf065bfd1e1cce7@wordpress.org> Message-ID: <066.eacebade8a56c9df5817d44230d47846@wordpress.org> #2811: WordCamp.org: Disable Jetpack JITM -------------------------------------+------------------ Reporter: kraftbj | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: | -------------------------------------+------------------ Comment (by kraftbj): In [5323], it is filtering in a mu-plugin at priority 10, where it is then filtered later through Jetpack's normal processes also at 10, so I believe it is being trumped later. It makes sense to me for Jetpack to reduce it down to 9 or change how it activates it (default true instead of false + add_filter) so it's easier to disable without knowing about the way Jetpack enables it, but until that is updated, using priority 11 should catch it. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 13:39:36 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 13:39:36 -0000 Subject: [wp-meta] [Making WordPress.org] #2813: Profiles: Add WP-CLI Badge In-Reply-To: <054.8af312384d284740d2f9848107f1b4bc@wordpress.org> References: <054.8af312384d284740d2f9848107f1b4bc@wordpress.org> Message-ID: <069.4f12895b95197483ab71bdb0730771bc@wordpress.org> #2813: Profiles: Add WP-CLI Badge ------------------------+------------------ Reporter: schlessera | Owner: Type: defect | Status: new Priority: high | Milestone: Component: Profiles | Resolution: Keywords: | ------------------------+------------------ Comment (by casiepa): Already mentioned on https://make.wordpress.org/ , so that's great. But when you have the color defined, don't forget to update https://make.wordpress.org/meta/handbook/documentation/profile-badges/ -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 13:35:47 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 13:35:47 -0000 Subject: [wp-meta] [Making WordPress.org] #2813: Profiles: Add WP-CLI Badge Message-ID: <054.8af312384d284740d2f9848107f1b4bc@wordpress.org> #2813: Profiles: Add WP-CLI Badge ------------------------+----------------- Reporter: schlessera | Owner: Type: defect | Status: new Priority: high | Milestone: Component: Profiles | Keywords: ------------------------+----------------- The WP-CLI team needs a color and badges to be ready for inclusion into marketing material. As far as I can tell, the icon had already been chosen to be `.dashicons- arrow-right-alt2` (`\f345`). No color was chosen yet as far as I know. My personal suggestion would be `#424242` (http://www.color-hex.com/color/424242) This represents the terminal background while not being completely black, and also 42 is _the_ answer! I suppose that Design & Marketing teams will want to chime in on this, though... (set to high priority as Community team wants to print updated banners for WCEU) cc @danielbachhuber , @sheriebeth -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 13:48:16 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 13:48:16 -0000 Subject: [wp-meta] [Making WordPress.org] #2813: Profiles: Add WP-CLI Badge In-Reply-To: <054.8af312384d284740d2f9848107f1b4bc@wordpress.org> References: <054.8af312384d284740d2f9848107f1b4bc@wordpress.org> Message-ID: <069.095f42626957de8a19d4cbcaa110fad1@wordpress.org> #2813: Profiles: Add WP-CLI Badge ------------------------+------------------ Reporter: schlessera | Owner: Type: defect | Status: new Priority: high | Milestone: Component: Profiles | Resolution: Keywords: | ------------------------+------------------ Comment (by danielbachhuber): +1 works for me. I don't have a strong preference. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 14:06:46 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 14:06:46 -0000 Subject: [wp-meta] [Making WordPress.org] #2812: I can't find my plugin in search results of plugin directory use the translated plugin name. In-Reply-To: <051.49e1b590ceb99bca42e7a007957d12f7@wordpress.org> References: <051.49e1b590ceb99bca42e7a007957d12f7@wordpress.org> Message-ID: <066.77a614564152101898c9e14cd25e48e2@wordpress.org> #2812: I can't find my plugin in search results of plugin directory use the translated plugin name. ------------------------------+------------------------------------ Reporter: ooqwqoo | Owner: Type: defect | Status: reopened Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------ Changes (by gibrown): * status: closed => reopened * type: enhancement => defect * resolution: duplicate => * milestone: => Plugin Directory v3.0 Comment: @ocean90 I think we should leave this open. It seems to be different root cause than #1496. 1496 is working on the plugin search for that locale (ru). This plugin though is not showing up in search results at all even though it is clearly translated. https://cn.wordpress.org/plugins/wx-custom-share/ https://cn.wordpress.org/plugins/search/%E8%87%AA%E5%AE%9A%E4%B9%89%E5%BE%AE%E4%BF%A1%E5%88%86%E4%BA%AB/ It looks like the translated strings are not being properly synced (I see no translated strings for this plugin). -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 16:02:34 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 4 May 2017 16:02:34 +0000 (UTC) Subject: [wp-meta] [5474] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-developer: devhub/cli: Add a basic /cli/commands/ archive page Message-ID: <20170504160234.8BAC71080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Thu May 4 16:02:35 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 16:02:35 -0000 Subject: [wp-meta] [Making WordPress.org] #2465: Create new WPorg home for wp-cli.org/commands and wp-cli.org/docs/internal-api In-Reply-To: <059.b4f59d4a8621ef6ac581d70037e4aba9@wordpress.org> References: <059.b4f59d4a8621ef6ac581d70037e4aba9@wordpress.org> Message-ID: <074.efabedd09f7aa9f5f3cb11f278b6c50f@wordpress.org> #2465: Create new WPorg home for wp-cli.org/commands and wp-cli.org/docs/internal- api -----------------------------+-------------------------- Reporter: danielbachhuber | Owner: coffee2code Type: task | Status: closed Priority: normal | Milestone: Component: Developer Hub | Resolution: fixed Keywords: wp-cli | -----------------------------+-------------------------- Comment (by danielbachhuber): In [changeset:"5474"]: {{{ #!CommitTicketReference repository="" revision="5474" devhub/cli: Add a basic /cli/commands/ archive page See #2465 }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 16:38:10 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 4 May 2017 16:38:10 +0000 (UTC) Subject: [wp-meta] [5475] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-developer: devhub/cli: Add a custom template for displaying commands Message-ID: <20170504163810.2E33E1080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Thu May 4 16:38:10 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 16:38:10 -0000 Subject: [wp-meta] [Making WordPress.org] #2465: Create new WPorg home for wp-cli.org/commands and wp-cli.org/docs/internal-api In-Reply-To: <059.b4f59d4a8621ef6ac581d70037e4aba9@wordpress.org> References: <059.b4f59d4a8621ef6ac581d70037e4aba9@wordpress.org> Message-ID: <074.69006c239f0b4c196d0a4fb2b3847b82@wordpress.org> #2465: Create new WPorg home for wp-cli.org/commands and wp-cli.org/docs/internal- api -----------------------------+-------------------------- Reporter: danielbachhuber | Owner: coffee2code Type: task | Status: closed Priority: normal | Milestone: Component: Developer Hub | Resolution: fixed Keywords: wp-cli | -----------------------------+-------------------------- Comment (by danielbachhuber): In [changeset:"5475"]: {{{ #!CommitTicketReference repository="" revision="5475" devhub/cli: Add a custom template for displaying commands See #2465 }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 16:44:26 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 4 May 2017 16:44:26 +0000 (UTC) Subject: [wp-meta] [5476] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-developer/inc/extras.php: devhub: Don' t prefix command excerpts with post type Message-ID: <20170504164426.B133C1080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Thu May 4 16:44:27 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 16:44:27 -0000 Subject: [wp-meta] [Making WordPress.org] #2465: Create new WPorg home for wp-cli.org/commands and wp-cli.org/docs/internal-api In-Reply-To: <059.b4f59d4a8621ef6ac581d70037e4aba9@wordpress.org> References: <059.b4f59d4a8621ef6ac581d70037e4aba9@wordpress.org> Message-ID: <074.7a6a14dc870760ce686700eb6c607029@wordpress.org> #2465: Create new WPorg home for wp-cli.org/commands and wp-cli.org/docs/internal- api -----------------------------+-------------------------- Reporter: danielbachhuber | Owner: coffee2code Type: task | Status: closed Priority: normal | Milestone: Component: Developer Hub | Resolution: fixed Keywords: wp-cli | -----------------------------+-------------------------- Comment (by danielbachhuber): In [changeset:"5476"]: {{{ #!CommitTicketReference repository="" revision="5476" devhub: Don't prefix command excerpts with post type See #2465 }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 16:48:47 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 16:48:47 -0000 Subject: [wp-meta] [Making WordPress.org] #2811: WordCamp.org: Disable Jetpack JITM In-Reply-To: <051.3104a7e411f78d028bf065bfd1e1cce7@wordpress.org> References: <051.3104a7e411f78d028bf065bfd1e1cce7@wordpress.org> Message-ID: <066.9c78584c0615205f66d65c3899fb7cc1@wordpress.org> #2811: WordCamp.org: Disable Jetpack JITM -------------------------------------+--------------------------- Reporter: kraftbj | Owner: coreymckrill Type: defect | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: | -------------------------------------+--------------------------- Changes (by coreymckrill): * owner: => coreymckrill * status: new => accepted -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 17:02:56 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 4 May 2017 17:02:56 +0000 (UTC) Subject: [wp-meta] [5477] sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/ jetpack-tweaks/miscellaneous.php: WordCamp: Modify the priority of some Jetpack tweaks Message-ID: <20170504170256.9769D1080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Thu May 4 17:10:03 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 17:10:03 -0000 Subject: [wp-meta] [Making WordPress.org] #2811: WordCamp.org: Disable Jetpack JITM In-Reply-To: <051.3104a7e411f78d028bf065bfd1e1cce7@wordpress.org> References: <051.3104a7e411f78d028bf065bfd1e1cce7@wordpress.org> Message-ID: <066.8d9adbd1c7d8b907732b4b1b9c0ec2db@wordpress.org> #2811: WordCamp.org: Disable Jetpack JITM -------------------------------------+--------------------------- Reporter: kraftbj | Owner: coreymckrill Type: defect | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: | -------------------------------------+--------------------------- Comment (by richardmtl): Replying to [comment:5 coreymckrill]: > Updated in r5477. I wasn't able to duplicate the problem before the update (maybe because super admin?) @richardmtl do you still see the messages if you publish another ticket? I just created https://2017.montreal.wordcamp.org/wp- admin/post.php?post=409&action=edit I got this message: http://d.pr/i/U6dfh -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 17:06:07 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 17:06:07 -0000 Subject: [wp-meta] [Making WordPress.org] #2811: WordCamp.org: Disable Jetpack JITM In-Reply-To: <051.3104a7e411f78d028bf065bfd1e1cce7@wordpress.org> References: <051.3104a7e411f78d028bf065bfd1e1cce7@wordpress.org> Message-ID: <066.8b49a9fc6322cbffabec0b0fa215030d@wordpress.org> #2811: WordCamp.org: Disable Jetpack JITM -------------------------------------+--------------------------- Reporter: kraftbj | Owner: coreymckrill Type: defect | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: | -------------------------------------+--------------------------- Comment (by coreymckrill): Updated in r5477. I wasn't able to duplicate the problem before the update (maybe because super admin?) @richardmtl do you still see the messages if you publish another ticket? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 17:11:49 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 4 May 2017 17:11:49 +0000 (UTC) Subject: [wp-meta] [5478] sites/trunk/api.wordpress.org/public_html/events/1.0: Events: Ignore `en_US` locales to avoid false-positives Message-ID: <20170504171149.34D5E1080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Thu May 4 17:14:58 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 17:14:58 -0000 Subject: [wp-meta] [Making WordPress.org] #2811: WordCamp.org: Disable Jetpack JITM In-Reply-To: <051.3104a7e411f78d028bf065bfd1e1cce7@wordpress.org> References: <051.3104a7e411f78d028bf065bfd1e1cce7@wordpress.org> Message-ID: <066.708294332cfa679750a3fc69f6a5c5ad@wordpress.org> #2811: WordCamp.org: Disable Jetpack JITM -------------------------------------+--------------------------- Reporter: kraftbj | Owner: coreymckrill Type: defect | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: | -------------------------------------+--------------------------- Comment (by coreymckrill): @richardmtl Ok, thanks. I will keep digging. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 4 19:12:19 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 4 May 2017 19:12:19 +0000 (UTC) Subject: [wp-meta] [5481] sites/trunk/api.wordpress.org/public_html/events/1.0/index.php: Events: Skip IP searches when locations are passed Message-ID: <20170504191219.D74D21080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Thu May 4 19:12:10 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 4 May 2017 19:12:10 +0000 (UTC) Subject: [wp-meta] [5479] sites/trunk/api.wordpress.org/public_html/events/1.0/index.php: Events: Remove unnecessary `isset()` checks Message-ID: <20170504191210.394A91080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Thu May 4 19:12:14 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 4 May 2017 19:12:14 +0000 (UTC) Subject: [wp-meta] [5480] sites/trunk/api.wordpress.org/public_html/events/1.0/index.php: Events: Fallback to `REMOTE_ADDR` for private IP address arguments Message-ID: <20170504191215.015E91080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Thu May 4 19:40:33 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 4 May 2017 19:40:33 +0000 (UTC) Subject: [wp-meta] [5482] sites/trunk/wordpress.org/public_html/style/wp4.css: WordPress header styling: increase z-index of dropdowns to avoid a problem where they show up behind the header on support forums theme , add margin-left rule to prevent it being overridden with less specific rules and thus moving the menu out of position. Message-ID: <20170504194033.A83BF1080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Thu May 4 23:45:38 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 04 May 2017 23:45:38 -0000 Subject: [wp-meta] [Making WordPress.org] #2813: Profiles: Add WP-CLI Badge In-Reply-To: <054.8af312384d284740d2f9848107f1b4bc@wordpress.org> References: <054.8af312384d284740d2f9848107f1b4bc@wordpress.org> Message-ID: <069.0a0abb8a2a490e9262e1f11bd121083b@wordpress.org> #2813: Profiles: Add WP-CLI Badge ------------------------+------------------ Reporter: schlessera | Owner: Type: defect | Status: new Priority: high | Milestone: Component: Profiles | Resolution: Keywords: | ------------------------+------------------ Comment (by netweb): Also the finalised image should be added in Slack as a custom emoji for use with Slack integrations and emoji reactions A Slack admin can add that here: https://wordpress.slack.com/admin/emoji -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri May 5 16:38:44 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Fri, 5 May 2017 16:38:44 +0000 (UTC) Subject: [wp-meta] [5483] sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory/readme/class-parser.php: Plugin Directory: Use an empty array for an allowed HTML tag without any attributes. Message-ID: <20170505163844.4EFFB10803EA@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Sat May 6 07:28:32 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 06 May 2017 07:28:32 -0000 Subject: [wp-meta] [Making WordPress.org] #2771: Direct access to changelog via #changelog in URL not working anymore In-Reply-To: <052.7fec41b2b3a6abfd47dbd3a54c595761@wordpress.org> References: <052.7fec41b2b3a6abfd47dbd3a54c595761@wordpress.org> Message-ID: <067.008c949686e36357cb4b765cb156b328@wordpress.org> #2771: Direct access to changelog via #changelog in URL not working anymore ------------------------------+----------------------- Reporter: galbaras | Owner: Otto42 Type: defect | Status: accepted Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+----------------------- Comment (by galbaras): @Otto42 If the changelog stays in the Development tab, is it possible to have both #changelog and #developers working, at least for a while, to cater for those who have adapted? Thank you. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sat May 6 10:50:35 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 06 May 2017 10:50:35 -0000 Subject: [wp-meta] [Making WordPress.org] #2771: Direct access to changelog via #changelog in URL not working anymore In-Reply-To: <052.7fec41b2b3a6abfd47dbd3a54c595761@wordpress.org> References: <052.7fec41b2b3a6abfd47dbd3a54c595761@wordpress.org> Message-ID: <067.dbcfca50f2428aa95f169679d79b090d@wordpress.org> #2771: Direct access to changelog via #changelog in URL not working anymore ------------------------------+----------------------- Reporter: galbaras | Owner: Otto42 Type: defect | Status: accepted Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+----------------------- Comment (by Otto42): @galbaras Yes, that is indeed the plan. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sun May 7 02:16:08 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Sun, 7 May 2017 02:16:08 +0000 (UTC) Subject: [wp-meta] [5484] sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory/api/routes/class-query-plugins.php: Plugin Directory: Correctly set the 'page' value in the response, the method name is `get() ` not `get_query_var()`. Message-ID: <20170507021608.2C53D108060E@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Sun May 7 22:36:43 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sun, 07 May 2017 22:36:43 -0000 Subject: [wp-meta] [Making WordPress.org] #2814: Put latest version of twemoji on CDN Message-ID: <057.f4939a96a6d0fbf992b8f6420ef6eb5a@wordpress.org> #2814: Put latest version of twemoji on CDN ---------------------------+----------------- Reporter: peterwilsoncc | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: General | Keywords: ---------------------------+----------------- This is a sister ticket to [https://core.trac.wordpress.org/ticket/40615 wp#40615] Please deploy the [https://github.com/twitter/twemoji/releases latest version of twemoji] to the w.org CDN. A new directory will be required as a number of images have been replaced since the previous version in WP. In the past, we have included the following paths: hxxps://s.w.org/images/core/emoji//72x72/ hxxps://s.w.org/images/core/emoji//svg/ -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sun May 7 23:30:18 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sun, 07 May 2017 23:30:18 -0000 Subject: [wp-meta] [Making WordPress.org] #2814: Put latest version of twemoji on CDN In-Reply-To: <057.f4939a96a6d0fbf992b8f6420ef6eb5a@wordpress.org> References: <057.f4939a96a6d0fbf992b8f6420ef6eb5a@wordpress.org> Message-ID: <072.8167d07503c5bcc82abd40069654041d@wordpress.org> #2814: Put latest version of twemoji on CDN ---------------------------+----------------------- Reporter: peterwilsoncc | Owner: pento Type: defect | Status: assigned Priority: normal | Milestone: Component: General | Resolution: Keywords: | ---------------------------+----------------------- Changes (by pento): * owner: => pento * status: new => assigned -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 8 02:34:31 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 08 May 2017 02:34:31 -0000 Subject: [wp-meta] [Making WordPress.org] #633: Add sync for develop.git.wordpress.org with Github In-Reply-To: <050.5567621cdca267cdc75d67c2dd966981@wordpress.org> References: <050.5567621cdca267cdc75d67c2dd966981@wordpress.org> Message-ID: <065.6b2a8468faebeca7cf935c177d3cbcea@wordpress.org> #633: Add sync for develop.git.wordpress.org with Github -----------------------------+------------------ Reporter: jorbin | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Version Control | Resolution: Keywords: | -----------------------------+------------------ Comment (by netweb): Replying to [comment:26 pento]: > Systems request: https://make.wordpress.org/systems/2016/12/20/deploy- key-and-mirroring-for-github-repo/ A deploy key is ready to be deployed on GitHub for testing :+1: * https://make.wordpress.org/systems/2016/12/20/deploy-key-and-mirroring- for-github-repo/#comment-1228 * https://github.com/WordPress/wordpress-develop/settings/keys -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 8 02:48:29 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 08 May 2017 02:48:29 -0000 Subject: [wp-meta] [Making WordPress.org] #2814: Put latest version of twemoji on CDN In-Reply-To: <057.f4939a96a6d0fbf992b8f6420ef6eb5a@wordpress.org> References: <057.f4939a96a6d0fbf992b8f6420ef6eb5a@wordpress.org> Message-ID: <072.98cc899a556f1bd6ea6659db574ccb2f@wordpress.org> #2814: Put latest version of twemoji on CDN ---------------------------+--------------------- Reporter: peterwilsoncc | Owner: pento Type: defect | Status: closed Priority: normal | Milestone: Component: General | Resolution: fixed Keywords: | ---------------------------+--------------------- Changes (by pento): * status: assigned => closed * resolution: => fixed Comment: [[Image(https://s.w.org/images/core/emoji/2.2.5/72x72/1f44d-1f3fb.png)]] -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 8 03:35:14 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 08 May 2017 03:35:14 -0000 Subject: [wp-meta] [Making WordPress.org] #2815: Teams: Create Hosting Badge & Color Message-ID: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> #2815: Teams: Create Hosting Badge & Color --------------------------------------+------------------------------------ Reporter: mapk | Owner: Type: task | Status: new Priority: high | Milestone: Component: Make (Get Involved) / P2 | Keywords: 2nd-opinion ui- | feedback --------------------------------------+------------------------------------ Looks like we need a hosting badge and color picked out for the Hosting Team. 1. Let's pick an icon from [https://developer.wordpress.org/resource/dashicons/] 2. Select some color choices based off our current list here: [https://make.wordpress.org/meta/handbook/documentation/profile-badges/] -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 8 03:42:45 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 08 May 2017 03:42:45 -0000 Subject: [wp-meta] [Making WordPress.org] #2815: Teams: Create Hosting Badge & Color In-Reply-To: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> References: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> Message-ID: <063.b7f4cfedf94f8f18f2ae6145ab58d534@wordpress.org> #2815: Teams: Create Hosting Badge & Color --------------------------------------+------------------ Reporter: mapk | Owner: Type: task | Status: new Priority: high | Milestone: Component: Make (Get Involved) / P2 | Resolution: Keywords: 2nd-opinion ui-feedback | --------------------------------------+------------------ Comment (by mapk): @melchoyce came up with some color choices that work well with our other colors, but haven't been used yet. [[Image(https://cldup.com/DM2cwI_Q7l.png)]] They would fit in like this (the empty circles): [[Image(https://cldup.com/yKw2PDBDmC.png)]] Thanks, Mel! -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 8 04:18:21 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 08 May 2017 04:18:21 -0000 Subject: [wp-meta] [Making WordPress.org] #2815: Teams: Create Hosting Badge & Color In-Reply-To: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> References: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> Message-ID: <063.d04f9035a300d543941c6e07c78d4bdd@wordpress.org> #2815: Teams: Create Hosting Badge & Color --------------------------------------+------------------ Reporter: mapk | Owner: Type: task | Status: new Priority: high | Milestone: Component: Make (Get Involved) / P2 | Resolution: Keywords: 2nd-opinion ui-feedback | --------------------------------------+------------------ Comment (by netweb): FYI: GlotPress is using `#826eb4`: * [[Image(https://cloud.githubusercontent.com/assets/1514660/11732608 /b6207d3e-9f5a-11e5-9aaa-715c921bdbe5.png)]] -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 8 06:21:12 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 08 May 2017 06:21:12 -0000 Subject: [wp-meta] [Making WordPress.org] #2815: Teams: Create Hosting Badge & Color In-Reply-To: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> References: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> Message-ID: <063.d2af2bc32b708cb927749ee7db01729a@wordpress.org> #2815: Teams: Create Hosting Badge & Color --------------------------------------+------------------ Reporter: mapk | Owner: Type: task | Status: new Priority: high | Milestone: Component: Make (Get Involved) / P2 | Resolution: Keywords: 2nd-opinion ui-feedback | --------------------------------------+------------------ Comment (by mapk): Here's a few icons I thought worked for "Hosting". [[Image(https://cldup.com/piIuAUCfGa.png)]][[Image()]] [[Image(https://cldup.com/9kBdMaj6GI.png)]] [[Image(https://cldup.com/sHQDUtnWZT.png)]] -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 8 06:31:20 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 08 May 2017 06:31:20 -0000 Subject: [wp-meta] [Making WordPress.org] #2815: Teams: Create Hosting Badge & Color In-Reply-To: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> References: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> Message-ID: <063.17a75e7a6d8b93b353fe3e279de84a80@wordpress.org> #2815: Teams: Create Hosting Badge & Color -------------------------------------+------------------ Reporter: mapk | Owner: Type: task | Status: new Priority: high | Milestone: Component: Profiles | Resolution: Keywords: 2nd-opinion ui-feedback | -------------------------------------+------------------ Changes (by ocean90): * component: Make (Get Involved) / P2 => Profiles -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 8 07:52:19 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 8 May 2017 07:52:19 +0000 (UTC) Subject: [wp-meta] [5485] sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory/cli/i18n/class-readme-import.php: Plugin Directory: Remove an extra slash between SVN URL and readme file. Message-ID: <20170508075219.3AE071080433@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon May 8 10:08:33 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 08 May 2017 10:08:33 -0000 Subject: [wp-meta] [Making WordPress.org] #2816: Existing users missing from wp-admin users list Message-ID: <051.435c59ac608d8a93ac473b1a3a028313@wordpress.org> #2816: Existing users missing from wp-admin users list ----------------------------+----------------- Reporter: Clorith | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Support Forums | Keywords: ----------------------------+----------------- Occasionally, we'll have users that can't be found in wp-admin when we go to block them (this needs to be done via the user list and then the block applied as a bulk action, as we do not have Network Admin, which is required to access individual users). The users can be found via `profiles.wordpress.org/$user`, `/support/users/$username` and the old `/support/profiles/$user`, but '''not''' via `/wp-admin/users.php?s=tech2017`. The most recent user we've discovered like this is `tech2017`, the block was applied using the old bbPress 1.x profile link in the cases where we can't find the user in wp-admin, but I'm not sure if that will have an affect (the flag appears to be set as it should when comparing to profiles.wordpress.org at least) -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 8 10:40:03 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 08 May 2017 10:40:03 -0000 Subject: [wp-meta] [Making WordPress.org] #2816: Existing users missing from wp-admin users list In-Reply-To: <051.435c59ac608d8a93ac473b1a3a028313@wordpress.org> References: <051.435c59ac608d8a93ac473b1a3a028313@wordpress.org> Message-ID: <066.6c8643586cce28d56d393d6c00d36d5c@wordpress.org> #2816: Existing users missing from wp-admin users list ----------------------------+------------------ Reporter: Clorith | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: close | ----------------------------+------------------ Changes (by ocean90): * keywords: => close Comment: wp-admin lists only users that have a capability (like `bbp_participant`) on the site. `tech2017` hasn't so you can't find them. Blocking via bbPress 1.x has no real affect beside the flag on the profiles.w.org. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 8 16:39:39 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 08 May 2017 16:39:39 -0000 Subject: [wp-meta] [Making WordPress.org] #2817: Broken Development tab / fonts Message-ID: <051.7d235fee7f9554b3c8be528f7ccc6e17@wordpress.org> #2817: Broken Development tab / fonts ---------------------+----------------- Reporter: khromov | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: General | Keywords: ---------------------+----------------- https://wordpress.org/plugins/black-studio-tinymce-widget/ Repro steps: * Go to: https://wordpress.org/plugins/black-studio-tinymce-widget/ * Press Development tab * Reviews show up on top in weird font * Changelog etc is at the bottom -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 8 16:51:13 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 08 May 2017 16:51:13 -0000 Subject: [wp-meta] [Making WordPress.org] #2817: Broken Development tab / fonts In-Reply-To: <051.7d235fee7f9554b3c8be528f7ccc6e17@wordpress.org> References: <051.7d235fee7f9554b3c8be528f7ccc6e17@wordpress.org> Message-ID: <066.9a622495cf76ab8cdc1f6cb02e3e4812@wordpress.org> #2817: Broken Development tab / fonts ---------------------+------------------ Reporter: khromov | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: | ---------------------+------------------ Comment (by kevinwhoffman): It appears that the issue begins earlier in the readme, in the `How to embed video and other contents` FAQ. There is currently an embedded YouTube player and everything after it appears in the monospaced font. Check that area of the readme out and see if there is a missing closing tag or other syntax issue. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 8 17:03:09 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 08 May 2017 17:03:09 -0000 Subject: [wp-meta] [Making WordPress.org] #2817: Broken Development tab / fonts In-Reply-To: <051.7d235fee7f9554b3c8be528f7ccc6e17@wordpress.org> References: <051.7d235fee7f9554b3c8be528f7ccc6e17@wordpress.org> Message-ID: <066.be7241da49fd3c219cd4dd3fb175ed9a@wordpress.org> #2817: Broken Development tab / fonts ------------------------------+------------------ Reporter: khromov | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------ Changes (by ocean90): * component: General => Plugin Directory Comment: Related: #2270 The `[embed]` shortcode shouldn't get parsed there. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 8 20:10:52 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 08 May 2017 20:10:52 -0000 Subject: [wp-meta] [Making WordPress.org] #2611: translation consistency page has double language entries In-Reply-To: <053.093c1b841072a4e10aa71a92a38e944a@wordpress.org> References: <053.093c1b841072a4e10aa71a92a38e944a@wordpress.org> Message-ID: <068.2c5099d4ece93f6ca805e42c4b1a55e9@wordpress.org> #2611: translation consistency page has double language entries --------------------------------------+------------------------- Reporter: Presskopp | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Translate Site & Plugins | Resolution: worksforme Keywords: | --------------------------------------+------------------------- Changes (by Presskopp): * status: new => closed * resolution: => worksforme Comment: ..looks like it magically fixed itself, see Slack ;-) -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 8 20:40:02 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 08 May 2017 20:40:02 -0000 Subject: [wp-meta] [Making WordPress.org] #2817: Broken Development tab / fonts In-Reply-To: <051.7d235fee7f9554b3c8be528f7ccc6e17@wordpress.org> References: <051.7d235fee7f9554b3c8be528f7ccc6e17@wordpress.org> Message-ID: <066.61b62aad4b8a7eca36afb2c7847735dd@wordpress.org> #2817: Broken Development tab / fonts ------------------------------+--------------------- Reporter: khromov | Owner: Otto42 Type: defect | Status: closed Priority: normal | Milestone: Component: Plugin Directory | Resolution: fixed Keywords: | ------------------------------+--------------------- Changes (by Otto42): * owner: => Otto42 * status: new => closed * resolution: => fixed Comment: In [changeset:"5486"]: {{{ #!CommitTicketReference repository="" revision="5486" Plugin Directory: Remove filter that allows embed shortcode to work. Fixes #2817. Related: #2270 }}} -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 8 20:40:01 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 8 May 2017 20:40:01 +0000 (UTC) Subject: [wp-meta] [5486] sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory/class-plugin-directory.php: Plugin Directory: Remove filter that allows embed shortcode to work. Message-ID: <20170508204001.66E521080433@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Mon May 8 22:19:38 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 08 May 2017 22:19:38 -0000 Subject: [wp-meta] [Making WordPress.org] #2818: WordCamp: Add the new theme Message-ID: <051.55c628fc3ed7cd8bb5cf3c923f6e7f30@wordpress.org> #2818: WordCamp: Add the new theme -------------------------------------+----------------------- Reporter: Kau-Boy | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: WordCamp Site & Plugins | Keywords: has-patch -------------------------------------+----------------------- The WordCamp Europe design team has worked on a new default theme and we think it's time to add it to the meta repository. Please find the information and discussion in these blog posts: https://make.wordpress.org/community/2016/12/28/wceu17-design-team-is- building-improved-and-more-flexible-wordcamp-theme/ https://make.wordpress.org/community/2017/04/04/progress-update-new- wordcamp-theme-campsite-2017/ https://make.wordpress.org/community/2017/05/08/the-new-wordcamp-base- theme-campsite-2017/ The current version of the theme can be found on GitHub: https://github.com/2ndkauboy/campsite-2017 -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 8 22:49:25 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 08 May 2017 22:49:25 -0000 Subject: [wp-meta] [Making WordPress.org] #2815: Teams: Create Hosting Badge & Color In-Reply-To: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> References: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> Message-ID: <063.a84773e9da1cca16593714a031a79c9c@wordpress.org> #2815: Teams: Create Hosting Badge & Color -------------------------------------+------------------ Reporter: mapk | Owner: Type: task | Status: new Priority: high | Milestone: Component: Profiles | Resolution: Keywords: 2nd-opinion ui-feedback | -------------------------------------+------------------ Comment (by mikeschroder): I like the cloud best, with the house second. The blue @melchoyce/@mapk listed is nice. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Mon May 8 23:35:57 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 08 May 2017 23:35:57 -0000 Subject: [wp-meta] [Making WordPress.org] #2819: Image carousel jumps off-screen Message-ID: <048.4c8cf9e6e4ce2434e72e993af0422d24@wordpress.org> #2819: Image carousel jumps off-screen ------------------------------+----------------- Reporter: Cybr | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Keywords: ------------------------------+----------------- Related: #2273 (point 1) When scrolling through the images, the current image is always displayed on the ultimate left side. This calculation of the carousel is wrong because it eventually jumps off- container (Chrome on Windows 10): http://i.imgur.com/d5R4K7B.png Also, I believe the currently selected image should be displayed in the middle, so you subconsciously know that there are more images at either the left or right side. This is both a defect and enhancement, falling under one change. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 9 00:30:23 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 09 May 2017 00:30:23 -0000 Subject: [wp-meta] [Making WordPress.org] #2816: Existing users missing from wp-admin users list In-Reply-To: <051.435c59ac608d8a93ac473b1a3a028313@wordpress.org> References: <051.435c59ac608d8a93ac473b1a3a028313@wordpress.org> Message-ID: <066.542066693f016c26cba1e0d118cff813@wordpress.org> #2816: Existing users missing from wp-admin users list ----------------------------+------------------------- Reporter: Clorith | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Support Forums | Resolution: worksforme Keywords: | ----------------------------+------------------------- Changes (by netweb): * keywords: close => * status: new => closed * resolution: => worksforme Comment: Replying to [comment:1 ocean90]: > wp-admin lists only users that have a capability (like `bbp_participant`) on the site. `tech2017` hasn't so you can't find them. Ah, yes, this would do it, thanks @ocean90 +1 Lets close this ticket and add the ability for keymasters to perform this action in #1989 -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 9 03:07:36 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 09 May 2017 03:07:36 -0000 Subject: [wp-meta] [Making WordPress.org] #2815: Teams: Create Hosting Badge & Color In-Reply-To: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> References: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> Message-ID: <063.b4740c78d98a2c79f9f99418bb93bb94@wordpress.org> #2815: Teams: Create Hosting Badge & Color -------------------------------------+------------------ Reporter: mapk | Owner: Type: task | Status: new Priority: high | Milestone: Component: Profiles | Resolution: Keywords: 2nd-opinion ui-feedback | -------------------------------------+------------------ Comment (by EmpireOfLight): If it doesn't have to be a dashicon, that might work. If it does, then just the cloud I guess. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 9 11:49:48 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 09 May 2017 11:49:48 -0000 Subject: [wp-meta] [Making WordPress.org] #2815: Teams: Create Hosting Badge & Color In-Reply-To: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> References: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> Message-ID: <063.1dc486f128ccd513e7a4fe9b13ce7a96@wordpress.org> #2815: Teams: Create Hosting Badge & Color -------------------------------------+------------------ Reporter: mapk | Owner: Type: task | Status: new Priority: high | Milestone: Component: Profiles | Resolution: Keywords: 2nd-opinion ui-feedback | -------------------------------------+------------------ Comment (by sheriebeth): Replying to [comment:7 EmpireOfLight]: > If it doesn't have to be a dashicon, that might work. If it does, then just the cloud I guess. I like the color and the cloud! Who do we need to ask if it needs to be a dashicon? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 9 13:25:01 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 09 May 2017 13:25:01 -0000 Subject: [wp-meta] [Making WordPress.org] #2813: Profiles: Add WP-CLI Badge In-Reply-To: <054.8af312384d284740d2f9848107f1b4bc@wordpress.org> References: <054.8af312384d284740d2f9848107f1b4bc@wordpress.org> Message-ID: <069.31b86ce742e5e94f365b301c0b6eb5f5@wordpress.org> #2813: Profiles: Add WP-CLI Badge ------------------------+------------------ Reporter: schlessera | Owner: Type: defect | Status: new Priority: high | Milestone: Component: Profiles | Resolution: Keywords: | ------------------------+------------------ Comment (by sheriebeth): It doesn't seem there are any objections to the suggestion of #424242 for the WP-CLI badge color so we will proceed with that for the "Get Involved" material. If there are any changes, please let me know today if possible as we are working on finalizing the design. Thanks for your help! -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 9 13:37:30 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 09 May 2017 13:37:30 -0000 Subject: [wp-meta] [Making WordPress.org] #2813: Profiles: Add WP-CLI Badge In-Reply-To: <054.8af312384d284740d2f9848107f1b4bc@wordpress.org> References: <054.8af312384d284740d2f9848107f1b4bc@wordpress.org> Message-ID: <069.e2442c8735d49e171e8bbcbea1a0feec@wordpress.org> #2813: Profiles: Add WP-CLI Badge ------------------------+------------------ Reporter: schlessera | Owner: Type: defect | Status: new Priority: high | Milestone: Component: Profiles | Resolution: Keywords: | ------------------------+------------------ Comment (by schlessera): @sheriebeth Yes, I suppose this is ready to be used, then. Looking forward to seeing the finalized flyer... :) -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 9 13:50:38 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 09 May 2017 13:50:38 -0000 Subject: [wp-meta] [Making WordPress.org] #2815: Teams: Create Hosting Badge & Color In-Reply-To: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> References: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> Message-ID: <063.e9adb338c92fa38b703e4691266158dc@wordpress.org> #2815: Teams: Create Hosting Badge & Color -------------------------------------+------------------ Reporter: mapk | Owner: Type: task | Status: new Priority: high | Milestone: Component: Profiles | Resolution: Keywords: 2nd-opinion ui-feedback | -------------------------------------+------------------ Comment (by netweb): Replying to [comment:8 sheriebeth]: > Replying to [comment:7 EmpireOfLight]: > > If it doesn't have to be a dashicon, that might work. If it does, then just the cloud I guess. > > I like the color and the cloud! Who do we need to ask if it needs to be a dashicon? Adding it as a dashicon would be preferable, that way it can be reused across w.org with relative ease Once a decision has been made on which icon design to use, creating a pull request for it at https://github.com/wordpress/dashicons would be the next step -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 9 18:51:43 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 09 May 2017 18:51:43 -0000 Subject: [wp-meta] [Making WordPress.org] #2815: Teams: Create Hosting Badge & Color In-Reply-To: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> References: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> Message-ID: <063.8925c150cccadaa5599b1832901b9b8e@wordpress.org> #2815: Teams: Create Hosting Badge & Color -------------------------------------+------------------ Reporter: mapk | Owner: Type: task | Status: new Priority: high | Milestone: Component: Profiles | Resolution: Keywords: 2nd-opinion ui-feedback | -------------------------------------+------------------ Comment (by mikeschroder): I have no problems with the cloud dashicon, and presume that'd probably be the most expedient. If the designers in the room like something else better, I'm happy to defer. :) -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 9 19:03:07 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 09 May 2017 19:03:07 -0000 Subject: [wp-meta] [Making WordPress.org] #2811: WordCamp.org: Disable Jetpack JITM In-Reply-To: <051.3104a7e411f78d028bf065bfd1e1cce7@wordpress.org> References: <051.3104a7e411f78d028bf065bfd1e1cce7@wordpress.org> Message-ID: <066.ee2b541dd742f8b86a11ee4a25f341d5@wordpress.org> #2811: WordCamp.org: Disable Jetpack JITM -------------------------------------+--------------------------- Reporter: kraftbj | Owner: coreymckrill Type: defect | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: | -------------------------------------+--------------------------- Comment (by richardmtl): I got another one (the same "Backup" prompt) when setting up a ticket coupon. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 9 19:45:26 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 09 May 2017 19:45:26 -0000 Subject: [wp-meta] [Making WordPress.org] #2319: Scroll bar visible on plugin authors list In-Reply-To: <051.82ba653c9b5bfef127f2b0e27f0ccfc8@wordpress.org> References: <051.82ba653c9b5bfef127f2b0e27f0ccfc8@wordpress.org> Message-ID: <066.bf534db6d93b3cb4e956c276165a4369@wordpress.org> #2319: Scroll bar visible on plugin authors list -----------------------------------------+------------------------- Reporter: xavortm | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Plugin Directory | Resolution: worksforme Keywords: has-screenshots needs-patch | -----------------------------------------+------------------------- Changes (by coffee2code): * status: new => closed * resolution: => worksforme * component: General => Plugin Directory Comment: Thanks for the report! Since this ticket was made, the Plugin Directory theme was revamped and open sourced. This "Authors" widget is no longer present in this fashion and as such this is no longer an issue. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 9 19:52:41 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 09 May 2017 19:52:41 -0000 Subject: [wp-meta] =?utf-8?q?=5BMaking_WordPress=2Eorg=5D_=232730=3A_Profi?= =?utf-8?q?les=3A_Login_form_in_header_could_use_better_styling_on_mobile_?= =?utf-8?b?KDYuNDTigLIgc2NyZWVuKQ==?= In-Reply-To: <051.f72f5e0d0551644573fd94971136f50f@wordpress.org> References: <051.f72f5e0d0551644573fd94971136f50f@wordpress.org> Message-ID: <066.6646ecd50eeec312be84d97a46cb9118@wordpress.org> #2730: Profiles: Login form in header could use better styling on mobile (6.44? screen) -------------------------+--------------------- Reporter: alkesh7 | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: Profiles | Resolution: fixed Keywords: | -------------------------+--------------------- Changes (by coffee2code): * status: new => closed * resolution: => fixed Comment: @alkesh7: Thanks for the report! This has been addressed in [13121-dotorg]. From that (non-public) commit: > Remove login form from headline bar and instead link out to login.wordpress.org. >* Displays "Register" and "Log In" links for logged-out visitors. >* Displays "Logged in as: {user}" and "Log Out" for logged-in users. >* Reorganizes the headline bar links into an unordered list and gives them better styling. >* Improves display in smaller viewports. As for the second issue: as Sergey suggested above, please raise it as a separate ticket. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 9 22:50:12 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 09 May 2017 22:50:12 -0000 Subject: [wp-meta] [Making WordPress.org] #2815: Teams: Create Hosting Badge & Color In-Reply-To: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> References: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> Message-ID: <063.0d5f696d17b5f6b0866b6eda18de637c@wordpress.org> #2815: Teams: Create Hosting Badge & Color -------------------------------------+------------------ Reporter: mapk | Owner: Type: task | Status: new Priority: high | Milestone: Component: Profiles | Resolution: Keywords: 2nd-opinion ui-feedback | -------------------------------------+------------------ Comment (by mapk): If we go strictly with Dashicons, here it is with the cloud using # 5358A6 as the color. [[Image(https://cldup.com/rVeciAtjN4.png)]] -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Tue May 9 23:57:56 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 09 May 2017 23:57:56 -0000 Subject: [wp-meta] [Making WordPress.org] #2815: Teams: Create Hosting Badge & Color In-Reply-To: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> References: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> Message-ID: <063.7e60cf31264c54d340681046a251bbf4@wordpress.org> #2815: Teams: Create Hosting Badge & Color -------------------------------------+------------------ Reporter: mapk | Owner: Type: task | Status: new Priority: high | Milestone: Component: Profiles | Resolution: Keywords: 2nd-opinion ui-feedback | -------------------------------------+------------------ Comment (by mikeschroder): Replying to [comment:11 mapk]: > If we go strictly with Dashicons, here it is with the cloud using # 5358A6 as the color. > > [[Image(https://cldup.com/rVeciAtjN4.png)]] > > Looks good to me, thanks! -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 10 04:26:03 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 10 May 2017 04:26:03 -0000 Subject: [wp-meta] [Making WordPress.org] #633: Add sync for develop.git.wordpress.org with Github In-Reply-To: <050.5567621cdca267cdc75d67c2dd966981@wordpress.org> References: <050.5567621cdca267cdc75d67c2dd966981@wordpress.org> Message-ID: <065.93aca8bb7dcf6ee2e3d87b709448d9a0@wordpress.org> #633: Add sync for develop.git.wordpress.org with Github -----------------------------+--------------------- Reporter: jorbin | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: Version Control | Resolution: fixed Keywords: | -----------------------------+--------------------- Changes (by pento): * status: new => closed * resolution: => fixed Comment: Changes are now being pushed immediately. Changes to Core for the new repo can take place on core.trac, the meta part is done. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 10 16:44:18 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 10 May 2017 16:44:18 -0000 Subject: [wp-meta] [Making WordPress.org] #2820: Add Japanese meetups to event API Message-ID: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> #2820: Add Japanese meetups to event API -------------------------------------+------------------------- Reporter: mayukojpn | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: WordCamp Site & Plugins | Keywords: needs-patch -------------------------------------+------------------------- Since we are not using meetup.com as event platform for localization reasons. For now, we have own Google Calendar to list up events in Japan and add event by hand. https://calendar.google.com/calendar/embed?src=wpja.team at gmail.com We are woking for listing groups on Google Spreadsheet as well: https://docs.google.com/spreadsheets/d/18n6iktG_gn1SAbyGYfe8ZIw8Ca49l1fl8t_EBkrUGE8/edit#gid=0 Related: #1292 https://make.wordpress.org/community/2017/03/23/showing-upcoming-local- events-in-wp-admin/#comment-23211 https://github.com/coreymckrill/nearby-wordpress-events/issues/57 -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 10 18:43:31 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 10 May 2017 18:43:31 -0000 Subject: [wp-meta] [Making WordPress.org] #2820: Add Japanese meetups to event API In-Reply-To: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> References: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> Message-ID: <068.e483e8a789466e86ee25b8ed6da99717@wordpress.org> #2820: Add Japanese meetups to event API -------------------------------------+------------------ Reporter: mayukojpn | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: needs-patch | -------------------------------------+------------------ Comment (by mayukojpn): Does anyone know how I can see JSON output with local environment? I could see my code was worked with shortcode in an old version of "Official WordPress Events" plugin, but I can't check with new version. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 10 19:20:04 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 10 May 2017 19:20:04 -0000 Subject: [wp-meta] [Making WordPress.org] #2790: Blockquote styles enhancement In-Reply-To: <058.1519385a51fb59753db7156e002686b1@wordpress.org> References: <058.1519385a51fb59753db7156e002686b1@wordpress.org> Message-ID: <073.5a2be833d53c19877407be2ba018ffd0@wordpress.org> #2790: Blockquote styles enhancement ------------------------------+------------------------------------ Reporter: webdevmattcrom | Owner: mapk Type: enhancement | Status: reviewing Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------ Changes (by SergeyBiryukov): * component: General => Plugin Directory -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Wed May 10 23:47:31 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 10 May 2017 23:47:31 -0000 Subject: [wp-meta] [Making WordPress.org] #2821: Plugin Directory: Plugin slug should be Latin Characters Only Message-ID: <051.25e027265662218e64083f79ba18e777@wordpress.org> #2821: Plugin Directory: Plugin slug should be Latin Characters Only ------------------------------+------------------------- Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Keywords: needs-patch ------------------------------+------------------------- As much as it pains me to say this, due to integration with SVN and other tools, it's safest to keep our slugs using non-accented characters (? or ? or ? and so on). We can manually fix it but we should automate that. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 11 08:21:54 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 11 May 2017 08:21:54 -0000 Subject: [wp-meta] =?utf-8?q?=5BMaking_WordPress=2Eorg=5D_=232822=3A_Suppo?= =?utf-8?q?rt_forum_should_have_better_styling_on_mobile_=286=2E44?= =?utf-8?b?4oCyIHNjcmVlbik=?= Message-ID: <051.0184a6d9b92a11087e875b5ad50ccd9b@wordpress.org> #2822: Support forum should have better styling on mobile (6.44? screen) --------------------------+------------------------- Reporter: alkesh7 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Browse Happy | Keywords: needs-patch --------------------------+------------------------- Hi guys, I noticed some issues with wordpress.org support forum with my Mi Max smartphone (screens size - 6.444'). Gravatar image showing outside the content, http://prnt.sc/eu2eey There are lots of issues, not only single one that I have listed above. Someone need to play with the same smartphone and access whole wordpress.org site Regards, Alkesh -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 11 08:23:53 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 11 May 2017 08:23:53 -0000 Subject: [wp-meta] =?utf-8?q?=5BMaking_WordPress=2Eorg=5D_=232730=3A_Profi?= =?utf-8?q?les=3A_Login_form_in_header_could_use_better_styling_on_mobile_?= =?utf-8?b?KDYuNDTigLIgc2NyZWVuKQ==?= In-Reply-To: <051.f72f5e0d0551644573fd94971136f50f@wordpress.org> References: <051.f72f5e0d0551644573fd94971136f50f@wordpress.org> Message-ID: <066.946af2d91596d37dd229d909ebb0bbeb@wordpress.org> #2730: Profiles: Login form in header could use better styling on mobile (6.44? screen) -------------------------+--------------------- Reporter: alkesh7 | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: Profiles | Resolution: fixed Keywords: | -------------------------+--------------------- Comment (by alkesh7): Hi @coffee2code : Thanks for your update. As per your guideline, I have created new ticket and this is a link for same - https://meta.trac.wordpress.org/ticket/2822 -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 11 08:53:52 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 11 May 2017 08:53:52 -0000 Subject: [wp-meta] =?utf-8?q?=5BMaking_WordPress=2Eorg=5D_=232822=3A_Suppo?= =?utf-8?q?rt_forum_should_have_better_styling_on_mobile_=286=2E44?= =?utf-8?b?4oCyIHNjcmVlbik=?= In-Reply-To: <051.0184a6d9b92a11087e875b5ad50ccd9b@wordpress.org> References: <051.0184a6d9b92a11087e875b5ad50ccd9b@wordpress.org> Message-ID: <066.8b6acc186f7080ef0984959d2113dca5@wordpress.org> #2822: Support forum should have better styling on mobile (6.44? screen) ----------------------------+------------------ Reporter: alkesh7 | Owner: Type: enhancement | Status: new Priority: low | Milestone: Component: Support Forums | Resolution: Keywords: needs-patch | ----------------------------+------------------ Changes (by ocean90): * priority: normal => low * component: Browse Happy => Support Forums -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 11 19:24:46 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 11 May 2017 19:24:46 +0000 (UTC) Subject: [wp-meta] [5487] sites/trunk/api.wordpress.org/public_html/events/1.0/index.php: Events: Remove unused variable Message-ID: <20170511192446.19F391080409@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: From noreply at wordpress.org Thu May 11 20:00:07 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 11 May 2017 20:00:07 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results Message-ID: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------- Reporter: iandunn | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: API | Keywords: ---------------------+----------------- There are a couple problems with our current data set. They're not strictly related to each other, but I'm creating a single ticket for this because I'm guessing that the solution to both will be the same: switch from our current data source to a better one. * Problem !#1: Incorrect IPv4 results. No data source will be perfect, but [several online database had correct results for instances where ours weren't https://make.wordpress.org/core/2017/04/14/nearby-wordpress- events/#comment-32448]. * Problem !#2: No IPv6 support. Without this, the results will quickly lose effectiveness. As of May 2017, [https://www.google.com/intl/en/ipv6/statistics.html#tab=ipv6-adoption IPv6 adoption is at 18% globally] and rising relatively fast. Some countries are as high as 32%. It looks like our database was updated recently (March 2017), but I can't find any info on where the original data comes from. @dd32, @tellyworth, do either of you know? Do you have any thoughts on other potential sources? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 11 20:24:41 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 11 May 2017 20:24:41 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.334171d3eb4bf0013ca24a0a1c74d7a9@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+------------------ Reporter: iandunn | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+------------------ Comment (by Otto42): If you're using the data I think you're using, then it almost certainly comes from the free data set at http://www.geonames.org/ -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 11 20:29:48 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 11 May 2017 20:29:48 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.298c29a0c50aa1fe6d596dac5cceeed3@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+------------------ Reporter: iandunn | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+------------------ Comment (by Otto42): Oh, and the ip2location probably comes from here: http://lite.ip2location.com/database/ip-country-region-city-latitude- longitude May or may not be the free one. Not sure. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 11 20:44:47 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 11 May 2017 20:44:47 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.375b7a6e62fff1e6ce7d2f87cd5d8c77@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Changes (by iandunn): * owner: => iandunn * status: new => accepted Comment: Ah, yeah, it looks like `IP2LOCATION-LITE-DB5.csv`. It could also be the commercial version, but I'll need to look closer when I have time. Thanks! They've got IPv6 available. If we're not already using the commercial version, then it's probably worth upgrading. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 11 20:50:26 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 11 May 2017 20:50:26 -0000 Subject: [wp-meta] [Making WordPress.org] #2820: Add Japanese meetups to event API In-Reply-To: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> References: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> Message-ID: <068.631ec7c09430bd55e172c8e401c61dc9@wordpress.org> #2820: Add Japanese meetups to event API -------------------------------------+----------------------- Reporter: mayukojpn | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: has-patch | -------------------------------------+----------------------- Changes (by iandunn): * keywords: needs-patch => has-patch * owner: => iandunn * status: new => accepted Comment: Thanks! The patch looks pretty good. It sounds like right now, the only the only Japanese meetup group that has joined the chapter program is Tokyo. We're only promoting events for official groups, so the other groups will need to join the chapter program before the could be listed. I'll try to get this committed soon, so the Tokyo events show up in plenty of time for 4.8. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 11 21:15:29 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 11 May 2017 21:15:29 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.92e4320cd60d70e0b2505d72cba633c7@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by Otto42): At the time I first encountered those years ago, they were an outdated copy of the free version. I updated the data to the latest copy, but then we didn't use it for much, so I let it go. Looking at it now, it appears to have many more rows than the free version, so I suspect somebody updated it to the non-free version. They may still have access to that and can get the big dataset, if we know who updated it last. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 11 22:23:19 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 11 May 2017 22:23:19 -0000 Subject: [wp-meta] [Making WordPress.org] #2824: Changelog Permalink doesn't route to correct location in Plugin Directory Message-ID: <051.f87e7a7bdb518d057318b5dbea55e1d0@wordpress.org> #2824: Changelog Permalink doesn't route to correct location in Plugin Directory ------------------------------+----------------- Reporter: jimtrue | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Keywords: ------------------------------+----------------- The old Changelog link was: https://wordpress.org/plugins/pods/changelog/ this redirects now to: https://wordpress.org/plugins/pods/#changelog Which is invalid, it should go to: https://wordpress.org/plugins/pods/#developers or more specifically to the section head under that tab for the ChangeLog id=changelog-header which no longer has an anchor reference of any kind. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Thu May 11 22:26:09 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 11 May 2017 22:26:09 -0000 Subject: [wp-meta] [Making WordPress.org] #2824: Changelog Permalink doesn't route to correct location in Plugin Directory In-Reply-To: <051.f87e7a7bdb518d057318b5dbea55e1d0@wordpress.org> References: <051.f87e7a7bdb518d057318b5dbea55e1d0@wordpress.org> Message-ID: <066.2441181f1ac3554871cadd5f282f66e9@wordpress.org> #2824: Changelog Permalink doesn't route to correct location in Plugin Directory ------------------------------+------------------------ Reporter: jimtrue | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Plugin Directory | Resolution: duplicate Keywords: | ------------------------------+------------------------ Changes (by netweb): * status: new => closed * resolution: => duplicate Comment: Duplicate of #2771. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri May 12 06:06:22 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 12 May 2017 06:06:22 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.761a482dcb4e6d13a3e6d1bdd887550c@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by dd32): @tellyworth did you update that data during development? I seem to recall you wrote some kind of importer for some data source for something remotely related to this? -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri May 12 12:51:55 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 12 May 2017 12:51:55 -0000 Subject: [wp-meta] [Making WordPress.org] #1658: Meetings: Add a calendar view In-Reply-To: <051.5c0980b36066c9e8727629f1e7565ffd@wordpress.org> References: <051.5c0980b36066c9e8727629f1e7565ffd@wordpress.org> Message-ID: <066.6f1517cc983374a8686a7e03e27893ae@wordpress.org> #1658: Meetings: Add a calendar view --------------------------------------+----------------------- Reporter: ocean90 | Owner: iseulde Type: enhancement | Status: assigned Priority: normal | Milestone: Component: Make (Get Involved) / P2 | Resolution: Keywords: needs-patch | --------------------------------------+----------------------- Comment (by iseulde): No, haven't found the time so far. :) Not sure how to unassign. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri May 12 13:19:08 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 12 May 2017 13:19:08 -0000 Subject: [wp-meta] [Making WordPress.org] #2787: Plugin Directory: Reject plugin on duplicate slugs In-Reply-To: <051.2ac2a1bb741f1b18b5c20f5005ec290b@wordpress.org> References: <051.2ac2a1bb741f1b18b5c20f5005ec290b@wordpress.org> Message-ID: <066.ad52f4aff2090713896f328810f6fc76@wordpress.org> #2787: Plugin Directory: Reject plugin on duplicate slugs ------------------------------+------------------------- Reporter: Ipstenu | Owner: tellyworth Type: defect | Status: reopened Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------- Comment (by SergeyBiryukov): Added the relevant part of attachment:2594.patch:ticket:2594 here, just in case: [attachment:2787.2.patch]. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri May 12 16:08:10 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 12 May 2017 16:08:10 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.8e381e94d8bae2a1a636f588c694d2c4@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): There's a bin script for updating the geonames data, but I didn't see anything for the IP geolocation. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Fri May 12 22:03:06 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 12 May 2017 22:03:06 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.7b0cbb8a1ef25ffd201c9e47c9fa1882@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): `IP2LOCATION-LITE-DB5.csv` also has the names in proper Sentence Case, rather than all uppercase, so it's definitely not that source, unless something went really wrong during the import. Having the data improperly cased is [https://github.com/coreymckrill /nearby-wordpress-events/issues/55 another problem] that would be solved by upgrading. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sat May 13 00:13:08 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 13 May 2017 00:13:08 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.73a0bad058448af8d98dddc121608dea@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): Another instance of bad geolocation results: https://wordpress.slack.com/archives/C02RQBWTW/p1494634179842054 -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sat May 13 00:52:16 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 13 May 2017 00:52:16 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.cc12dcc0365b4cc3827cf7b94d5b6ef9@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): Another: https://wordpress.slack.com/archives/C02RQBWTW/p1494636637998774 -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sat May 13 03:17:23 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 13 May 2017 03:17:23 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.c421bcd7e3607ce156e6ef373fabe2df@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by barry): Howdy, There are a few problems here: 1) The ip2location data on WP.org is very very old. 2) WP.org doesn't have a subscription/license to use the data that I am aware of. 3) I don't think there is any legitimate use case to pass an ip in the query string - this just opens up the API to abuse and most likely violates the terms/EULA of using this data. 4) The query performance is very poor and probably won't scale to the volume that we need. For ip2location specifically we have already solved this problem on WordPress.com, so I would suggest looking at the code there. I haven't looked at the geonames code much, but I suspect it suffers from similar issues. 5) We need a way to keep the information always current if we are going to use it. It changes enough on a regular basis that once it's > 60 days old it starts becoming noticeably wrong. The first problem to solve is #2. I don't think we really need ipv6 support yet since the API should always use REMOTE_ADDR and the WordPress.org API currently doesn't have any AAAA records. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sat May 13 04:16:49 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 13 May 2017 04:16:49 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.63a61bd0edb4b19a503e16a3e9e73d28@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by dd32): > The first problem to solve is #2. I don't think we really need ipv6 support yet since the API should always use REMOTE_ADDR and the WordPress.org API currently doesn't have any AAAA records. The IP is not the REMOTE_ADDR in most cases - it's the WordPress user client IP, not the server IP. There's some "anonymisation" stuff in there ([see maybe_anonymize_ip_address () https://core.trac.wordpress.org/browser/trunk/src/wp-admin/includes/class- wp-community-events.php#L231]). The exception is when the client IP provided is a private range, in which case it uses REMOTE_ADDR. Would it be better if the client browser was making the request directly? (and not proxied through WordPress) - the detect-location call would need to be made on every request in that case, and not just on the first call / when user searches for a location change. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sat May 13 04:42:42 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 13 May 2017 04:42:42 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.18671357f56887e5c7a2c4588504104e@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by barry): I see why it was implemented this way, but I think it's a clear violation of the [https://www.ip2location.com/agreement EULA] and the endpoint will quickly be abused. I am not too worried about the traffic once #4 above is fixed, but I guess there are some general performance and privacy concerns that will need to be addressed if the implementation is changed. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sat May 13 08:09:49 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 13 May 2017 08:09:49 -0000 Subject: [wp-meta] [Making WordPress.org] #2825: The plugin search is defective Message-ID: <053.38e0089fb0367875df332d3cb578f005@wordpress.org> #2825: The plugin search is defective ------------------------------+----------------------------------- Reporter: picocodes | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Keywords: ------------------------------+----------------------------------- I have spent a couple of weeks trying out a few keywords on the plugin search and every time I notice a couple of irrelevant results on the first page simply because they have a lot of installs. For example, if you search for 'ajax search', you will notice more relevant results hidden on page 2 while irrelevant results sit on page 1. Using active installs as a ranking factor is a great idea. However, it's impact should be reduced to give newer plugins a chance. Maybe you can use a ratio of total downloads to active installs as a way of calculating a plugin's quality. I mean, if lot's of people who download the plugin end up uninstalling it then it's probably low quality. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sat May 13 14:51:07 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 13 May 2017 14:51:07 -0000 Subject: [wp-meta] [Making WordPress.org] #2825: The plugin search is defective In-Reply-To: <053.38e0089fb0367875df332d3cb578f005@wordpress.org> References: <053.38e0089fb0367875df332d3cb578f005@wordpress.org> Message-ID: <068.1e6783d888e2d8d7047b7e0f55fd4442@wordpress.org> #2825: The plugin search is defective ------------------------------+------------------------------------ Reporter: picocodes | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------ Comment (by jsmoriss): More updates = more downloads, so using the number of downloads vs active installs as a quality indicator would not work. ;-) js. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sat May 13 15:42:49 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 13 May 2017 15:42:49 -0000 Subject: [wp-meta] [Making WordPress.org] #2825: The plugin search is defective In-Reply-To: <053.38e0089fb0367875df332d3cb578f005@wordpress.org> References: <053.38e0089fb0367875df332d3cb578f005@wordpress.org> Message-ID: <068.19dc1c467983e8c7e31a97250a6de9f6@wordpress.org> #2825: The plugin search is defective ------------------------------+------------------------- Reporter: picocodes | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Plugin Directory | Resolution: worksforme Keywords: | ------------------------------+------------------------- Changes (by Otto42): * status: new => closed * resolution: => worksforme * milestone: Plugin Directory v3.0 => Comment: > For example, if you search for 'ajax search', you will notice more relevant results hidden on page 2 while irrelevant results sit on page 1. What results are you seeing, exactly? Because the results I see on page 1 are extremely relevant. Ajax Search Lite, SearchWP Live Ajax Search, Advanced Woo Search, YITH WooCommerce Ajax Search, Search ? Instant Search for WooCommerce Search, WordPress Infinite Scroll ? Ajax Load More, and so forth. Every single result on page one is a search system of some kind. Extremely relevant results for that search query. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sun May 14 12:33:54 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sun, 14 May 2017 12:33:54 -0000 Subject: [wp-meta] [Making WordPress.org] #1445: "Add translation" button should be re-enabled on error when saving In-Reply-To: <058.a926e9ec9c511d122ff7322084b6c513@wordpress.org> References: <058.a926e9ec9c511d122ff7322084b6c513@wordpress.org> Message-ID: <073.7d2d48d38bf3dc61a5e0a8b3d03d976f@wordpress.org> #1445: "Add translation" button should be re-enabled on error when saving --------------------------------------+--------------------- Reporter: SergeyBiryukov | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Translate Site & Plugins | Resolution: fixed Keywords: has-patch | --------------------------------------+--------------------- Changes (by ocean90): * status: new => closed * resolution: => fixed Comment: Looks like this was fixed by [2949]. -- Ticket URL: Making WordPress.org Making WordPress.org From noreply at wordpress.org Sun May 14 12:37:07 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sun, 14 May 2017 12:37:07 -0000 Subject: [wp-meta] [Making WordPress.org] #1280: tags on translate.wordpress.org In-Reply-To: <049.f852fdb0ce284a9d405c46451e66a27e@wordpress.org> References: <049.f852fdb0ce284a9d405c46451e66a27e@wordpress.org> Message-ID: <064.4edee0969df53e0894b638143a95afa5@wordpress.org> #1280: <title> tags on translate.wordpress.org --------------------------------------+---------------------- Reporter: ramiy | Owner: Type: defect | Status: closed Priority: lowest | Milestone: Component: Translate Site & Plugins | Resolution: wontfix Keywords: has-patch | --------------------------------------+---------------------- Changes (by ocean90): * status: new => closed * resolution: => wontfix Comment: This needs to be improved in GlotPress directly, closing as wontfix. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1280#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sun May 14 17:12:54 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sun, 14 May 2017 17:12:54 -0000 Subject: [wp-meta] [Making WordPress.org] #2826: Download failed, not found error when plugin update out of sync Message-ID: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> #2826: Download failed, not found error when plugin update out of sync ------------------------------+----------------- Reporter: brianhogg | Owner: Type: defect | Status: new Priority: high | Milestone: Component: Plugin Directory | Keywords: ------------------------------+----------------- After 27 hours the wordpress.org listing still doesn't show the latest update. This is fine and can happen when the servers are overloaded. However, WordPress sites with the plugin are showing that an update is available. The new update details do not appear when "view version details" is clicked, and trying to update results in "Update Failed: Download failed. Not Found" If the update cannot be downloaded, it should not be shown in WordPress sites. 'Update available' should be the last thing to be updated after the zip has been generated. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2826> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sun May 14 19:11:09 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sun, 14 May 2017 19:11:09 -0000 Subject: [wp-meta] [Making WordPress.org] #2826: Download failed, not found error when plugin update out of sync In-Reply-To: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> References: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> Message-ID: <068.1293e7d2084396855887c215dbe8a461@wordpress.org> #2826: Download failed, not found error when plugin update out of sync ------------------------------+------------------ Reporter: brianhogg | Owner: Type: defect | Status: new Priority: high | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------ Comment (by pigeonhut): Same happening for me across 2 plugins updated yesterday and today, have also had clients opening support tickets for it -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2826#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sun May 14 19:53:38 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sun, 14 May 2017 19:53:38 -0000 Subject: [wp-meta] [Making WordPress.org] #2826: Plugin Directory: Data not syncing/updating properly from SVN commits (was: Download failed, not found error when plugin update out of sync) In-Reply-To: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> References: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> Message-ID: <068.48569ce6f2338ac85c4847021f0657b4@wordpress.org> #2826: Plugin Directory: Data not syncing/updating properly from SVN commits ------------------------------+------------------ Reporter: brianhogg | Owner: Type: defect | Status: new Priority: highest omg bbq | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------ Changes (by Ipstenu): * priority: high => highest omg bbq Comment: We're doing a mass import to try and catch everyone, but this is going to take a while. I'm leaving this open so people can report more issues here, as it's basically ALL related to the sync jobs that run after you commit code to SVN. They're not behaving. Server team is looking, but it's Sunday :/ Issues you MAY be experiencing: * Version numbers not updating * Versions updating, but downloads failing * Downloads failing for SOME people In all cases, PLEASE DO NOT SUBMIT MULTIPLE UPDATES. You probably didn't do anything wrong, so just give it a while :/ It will work out but it's going to be slow until we figure out what broke. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2826#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sun May 14 21:23:41 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Sun, 14 May 2017 21:23:41 +0000 (UTC) Subject: [wp-meta] [5488] sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory: Plugin Directory: Replace `shell_exec()`/`system() ` calls with `exec()`. Message-ID: <20170514212341.D00A110803A7@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170514/5d36132b/attachment-0001.html> From noreply at wordpress.org Mon May 15 12:25:46 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 15 May 2017 12:25:46 -0000 Subject: [wp-meta] [Making WordPress.org] #2699: Add a new role to the forums: plugin/theme support In-Reply-To: <053.e04c8d0168f06e230413f4c13e10a319@wordpress.org> References: <053.e04c8d0168f06e230413f4c13e10a319@wordpress.org> Message-ID: <068.e5b69c72aa59472b96f54d5d0427b600@wordpress.org> #2699: Add a new role to the forums: plugin/theme support ----------------------------+------------------ Reporter: TacoVerdo | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Comment (by wfasa): I wanted to pitch in here and argue for the exact same thing but for a different reason. While I agree with all of the above, I think adding a support role could also increase security. If an account with commit privileges was compromised it could cause a lot of trouble for the plugin authors, plugin users and potentially also for wordpress.org staff (helping authors clean up the mess). Users who only work the forums providing support do not need commit privileges. So for security reasons, it makes sense to limit commit privileges to only those who actually need it. I'm therefore very much in favor of a separate support role that 1. Allows thread resolve but not code commit 2. Is not subject to spam filtering/rate limiting 3. Shows up with a "support" tag in the forums Thanks to @ocean90 for showing me this thread. And re:@kraftbj comment above, in Wordfence 6.3.5 we made a slight modification so readme.txt files will now only be flagged in scan if "High sensitivity" scan option is enabled. You may still see those warnings, but it shouldn't be as often. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2699#comment:26> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Mon May 15 17:25:29 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 15 May 2017 17:25:29 -0000 Subject: [wp-meta] [Making WordPress.org] #2818: WordCamp: Add the new theme In-Reply-To: <051.55c628fc3ed7cd8bb5cf3c923f6e7f30@wordpress.org> References: <051.55c628fc3ed7cd8bb5cf3c923f6e7f30@wordpress.org> Message-ID: <066.d1697e2daaa67543e4980377c342e22c@wordpress.org> #2818: WordCamp: Add the new theme -------------------------------------+----------------------- Reporter: Kau-Boy | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: has-patch | -------------------------------------+----------------------- Changes (by iandunn): * owner: => iandunn * status: new => accepted -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2818#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Mon May 15 18:49:26 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 15 May 2017 18:49:26 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.b35d0dd720d42e6a66b174a255b3437d@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): Replying to [comment:12 barry]: > 1) The ip2location data on WP.org is very very old. > 2) WP.org doesn't have a subscription/license to use the data > 3) I don't think there is any legitimate use case to pass an ip in the query string > 4) The query performance is very poor and probably won't scale to the volume that we need > 5) We need a way to keep the information always current if we are going to use it !#1, !#2, and !#5 are all easy to solve. == !#3 (EULA) == On a technical level, it's easy to switch the client to request the data directly from api.w.org instead of proxying through their WP site. For anyone who's concerned about privacy with that architecture, we can release a plugin that will disable the Events section of the Dashboard widget entirely. We could replace it with a simple link to [https://make.wordpress.org/community/events/ the Events page on make/Community]. Does anyone think that would not be enough to mitigate privacy concerns? == !#4 (performance) == I'm going to start digging into this and looking for ways to optimize. If you can say which queries you're concerned the most about, that would be helpful. Almost all of the queries are there to support extra functionality and edge cases. Worst case scenario, the queries in the following functions can all be disabled without preventing the majority of users from successfully retrieving events: `guess_location_from_ip()`, `guess_location_from_geonames_fallback()`, `get_valid_country_codes()`, `get_country_from_name()`, and `get_city_from_coordinates()` That can be done at-will on the API side without breaking the client in Core. We could even do it automatically during traffic spikes if we have some kind of signal from monitoring agents to check. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:15> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Mon May 15 20:51:22 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 15 May 2017 20:51:22 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.9fa913a0ede069c534d107582ab56b22@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by barry): I have been thinking about the EULA a bit, I think if we remove the actual passed IP geolocation data from the response and just return the events data it will be fine. We would then use the client IP geolocation internally, in "business logic" to figure out the closest events and return them. We still need to work on the other issues, but they are technical and thus easier to fix. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:16> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Mon May 15 22:03:37 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 15 May 2017 22:03:37 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.342e18f97feb29af0714cd331fc70958@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): That sounds like a good idea to me. I think the detailed steps look like this: 1. The initial request. The client doesn't have a location saved at this point. 1. Client requests events near `{ip address}` 1. API returns the `events` object like it does today, but no `location` object 1. Client parses the city name from first event (e.g. "Seattle"), and saves that as the location 1. The second request. The client has a city name saved at this point. 1. The client requests events near `{city name}`, just like it does today when a user manually types in a location 1. The API matches the city name to lat/long coordinates using the Creative Commons data from geonames.org 1. The API returns the `events` object, and a `location` object, just like it does today. 1. The client saves the full `location` object as its location 1. All future requests. The client has a saved `lat` and `long` at this time 1. These would be exactly the same as they are today. So, the client would have to make 2 requests instead of 1, but it would eventually get the same behavior as we have today. The client could do step !#2 asynchronously after the events received in step !#1 have been displayed, in order to make things a little smoother. All of the above only applies if the user hasn't manually entered a location. If they enter a location manually, then we skip step !#1, and go straight to !#2. @barry, does that sound right to you? If so, I'll get started on the necessary changes. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:17> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Mon May 15 22:13:18 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 15 May 2017 22:13:18 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.b5951399aa67463bd1e17167a91cd065@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): To clarify, are you thinking we'd remove the IP from the client's request and just use `REMOTE_ADDR` on the API side, or would the client still be able to specify an arbitrary IP? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:18> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Mon May 15 22:28:42 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 15 May 2017 22:28:42 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.f21551f0046d02d477f8306293439e26@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by barry): Replying to [comment:18 iandunn]: > To clarify, are you thinking we'd remove the IP from the client's request and just use `REMOTE_ADDR` on the API side, or would the client still be able to specify an arbitrary IP? Clients can specify an arbitrary IP. I was initially concerned about the privacy implications of the clients connecting directly to the .org API which would provide their full IP and not the truncated version that the current proxy approach uses. I thought this would be the only place that a .org site sends the client IP to WordPress.org (as opposed to the server IP which is sent in many places). However, I then remembered that we use the W.org CDN for serving emoji in core, so I am not sure if it's a huge problem. I'm ok with any approach that satisfies the "business requirements" of this widget and doesn't violate the EULA for the data source(s) we use. The rest of the stuff like performance and scaling we can figure out pretty easily. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:19> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Mon May 15 22:30:43 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 15 May 2017 22:30:43 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.5e4167968d527760754f3c17c2302766@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by barry): Oh, and I forgot, if we send arbitrary IPs we might need IPv6 support which I haven't looked at yet. If the privacy concerns aren't an issue, having the client connect directly to the API endpoint might be the cleaner implementation. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:20> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 02:52:55 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 02:52:55 -0000 Subject: [wp-meta] [Making WordPress.org] #2642: Better boosting for phrase matches (or add support for the user to specify a phrase) In-Reply-To: <051.6ac0b0ad0bb1fc49ee7e4ab29ad2ae98@wordpress.org> References: <051.6ac0b0ad0bb1fc49ee7e4ab29ad2ae98@wordpress.org> Message-ID: <066.1ca11310d63d1ec95b24747c90245fdc@wordpress.org> #2642: Better boosting for phrase matches (or add support for the user to specify a phrase) ------------------------------+------------------------------------------- Reporter: gibrown | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by gsexton): I'm seeing cases where search relevancy is overwhelmed by large numbers of downloads. For example, if you search for the single word "calendar", JetPack is listed in the results of page 1. I looked at the readme.txt file and found that it contains that keyword exactly one time. Evidently, it's massive installed base overwhelms many plugins that from a straight textual analysis are vastly more relevant. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2642#comment:27> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 13:21:30 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 13:21:30 -0000 Subject: [wp-meta] [Making WordPress.org] #2827: Change size font Message-ID: <055.fc679e415e8f94ab91cfe1260c56176e@wordpress.org> #2827: Change size font ---------------------------+----------------------------- Reporter: jommartinez | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Developer Hub | Keywords: has-screenshots ---------------------------+----------------------------- I think you could reduce the text size a bit so it would fit into a single line. In some low resolutions only the symbol of the arrow and it looks bad ...: S url : https://developer.wordpress.org/ [[Image(http://i65.tinypic.com/kda2bd.png)]] -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2827> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 13:22:35 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 13:22:35 -0000 Subject: [wp-meta] [Making WordPress.org] #2827: Change size font In-Reply-To: <055.fc679e415e8f94ab91cfe1260c56176e@wordpress.org> References: <055.fc679e415e8f94ab91cfe1260c56176e@wordpress.org> Message-ID: <070.c235bb9cb283a13b20e5cd20a087b610@wordpress.org> #2827: Change size font ---------------------------+------------------ Reporter: jommartinez | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Developer Hub | Resolution: Keywords: | ---------------------------+------------------ Changes (by jommartinez): * keywords: has-screenshots => -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2827#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 13:28:54 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 13:28:54 -0000 Subject: [wp-meta] [Making WordPress.org] #2826: Plugin Directory: Data not syncing/updating properly from SVN commits In-Reply-To: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> References: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> Message-ID: <068.8f09ce366e6938bdc026d0ef4345f005@wordpress.org> #2826: Plugin Directory: Data not syncing/updating properly from SVN commits ------------------------------+--------------------- Reporter: brianhogg | Owner: Type: defect | Status: closed Priority: highest omg bbq | Milestone: Component: Plugin Directory | Resolution: fixed Keywords: | ------------------------------+--------------------- Changes (by Otto42): * status: new => closed * resolution: => fixed Comment: The problems with our scheduler appear to have been fixed now, and the queue length has returned to normal levels. The issue was not specific to plugin updates, but plugin updates were the most obvious side-effect. We will continue to monitor the situation, and we have setup automatic alerts in case things go wrong again. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2826#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 13:47:57 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 13:47:57 -0000 Subject: [wp-meta] [Making WordPress.org] #2642: Better boosting for phrase matches (or add support for the user to specify a phrase) In-Reply-To: <051.6ac0b0ad0bb1fc49ee7e4ab29ad2ae98@wordpress.org> References: <051.6ac0b0ad0bb1fc49ee7e4ab29ad2ae98@wordpress.org> Message-ID: <066.604ba18e75f2cc07ce8073ef0f4f4a31@wordpress.org> #2642: Better boosting for phrase matches (or add support for the user to specify a phrase) ------------------------------+------------------------------------------- Reporter: gibrown | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by quantumcloud): 100% agreed. The search results are quite polluted with false positives from big names. I reported the issue multiple times but nothing has been done on it so far. The highest priority seems to be that the big names show up for the most popular searches on 1st page. All other searches and the search result quality are largely ignored at this point. Not to mention how next to impossible it has become for new plugin developers to gain any momentum as they start with 0 active installs. New WordPress plugin developers can pretty much forget about their plugins ever getting downloaded from the repository through organic searches. Truly hope that the situation is rectified asap. Replying to [comment:27 gsexton]: > I'm seeing cases where search relevancy is overwhelmed by large numbers of downloads. For example, if you search for the single word "calendar", JetPack is listed in the results of page 1. I looked at the readme.txt file and found that it contains that keyword exactly one time. Evidently, it's massive installed base overwhelms many plugins that from a straight textual analysis are vastly more relevant. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2642#comment:28> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 16:50:51 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 16:50:51 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.a90f160e43c5eaaf5676b9fdd6c5630b@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): @dd32 has a really good idea to modify the process a bit. I think will make things simpler on the client side, while still staying within the EULA. When the client makes a request for events and provides the IP, we geolocate that IP from `ip2location`, and fetch the events that are close to it. We do not return the location data provided by `ip2location` to the client. At this point, the `response` object being built looks like this: {{{ { 'location: {}, 'events: { { 'id' => 1234, 'date' => 194323423, 'type' => 'wordcamp', 'title' => 'WordCamp Seattle', 'location' => 'Seattle, WA, USA' }, // more events here } } }}} The `response.location` is empty. The `response.events[0].location` field above is pulled from `wporg_events`, and originally comes from the WordCamp.org API. The next step is to take that `response.events[0].location` field, and search our `geonames` table for it. `geonames` is Creative Commons licensed, and provides `latitude` and `longitude`. So now, we can populate the `location` field in the response with the data we've pulled from `geonames`. Now the `response` object looks like this: {{{ { 'location: { 'name' => 'Seattle', 'latitude' => '47.200324', 'longitude' => '-121.32523', 'country' => 'US', }, 'events: { { 'id' => 1234, 'date' => 194323423, 'type' => 'wordcamp', 'title' => 'WordCamp Seattle', 'location' => 'Seattle, WA, USA' }, // more events here } } }}} This way, we can still return a location to the client in the initial request, but we're not directly exposing the location details from `ip2location` at all. The previous approach was essentially the same thing, but the `response.location` lookup was being done in a subsequent request (see comment:17), rather than all at once. @barry, do you see any problems with that? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:21> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 18:57:33 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 16 May 2017 18:57:33 +0000 (UTC) Subject: [wp-meta] [5489] sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-cli/ inc/class-markdown-import.php: make/cli: Handbook manifest is at a new location Message-ID: <20170516185733.BCA5D10803B4@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170516/0473b5c1/attachment.html> From noreply at wordpress.org Tue May 16 21:08:27 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 21:08:27 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.5ed5e83e2734d691a8501824e3217aac@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): In [changeset:"5491"]: {{{ #!CommitTicketReference repository="" revision="5491" Events: Replace IP geolocated data with venue location data See #2823 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:23> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 21:08:22 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 16 May 2017 21:08:22 +0000 (UTC) Subject: [wp-meta] [5490] sites/trunk/api.wordpress.org/public_html/events/1.0/tests/ test-index.php: Events: Update IP test cases with current data Message-ID: <20170516210822.CB00310803B4@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170516/d613df36/attachment.html> From noreply at wordpress.org Tue May 16 21:08:23 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 21:08:23 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.5d9360c6b8bebff4032fcc342350ce2d@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): In [changeset:"5490"]: {{{ #!CommitTicketReference repository="" revision="5490" Events: Update IP test cases with current data The IP geolocation database was updated, and a few locations shifted as a result. See #2823 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:22> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 21:08:27 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 16 May 2017 21:08:27 +0000 (UTC) Subject: [wp-meta] [5491] sites/trunk/api.wordpress.org/public_html/events/1.0: Events: Replace IP geolocated data with venue location data Message-ID: <20170516210827.195C810803B4@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170516/6012e717/attachment-0001.html> From noreply at wordpress.org Tue May 16 21:16:57 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 21:16:57 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.f4a923e9346b97353f1ce57ad096c2a7@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): In [changeset:"5492"]: {{{ #!CommitTicketReference repository="" revision="5492" Events: Restore `location['description']` r5491 accidentally changed this, which caused the Core client to have an empty location description. See #2823 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:24> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 21:16:56 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 16 May 2017 21:16:56 +0000 (UTC) Subject: [wp-meta] [5492] sites/trunk/api.wordpress.org/public_html/events/1.0/index.php: Events: Restore `location['description']` Message-ID: <20170516211656.B15B510803B4@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170516/b133b548/attachment.html> From noreply at wordpress.org Tue May 16 21:22:49 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 21:22:49 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.02346be87c4bcaed23df39cb0217f660@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): It turned out to be even simpler than comment:21, since we already have the venue's location data in the events table. r5491 fixed !#3 from comment:15. Barry updated the geolocation data from ip2location.com, which fixed !#1 and !#2. That just leaves !#4 (performance), which Dion is working on, and !#5 (automatic updates), which I'll look into once higher priority tasks are done. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:25> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 22:39:37 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 16 May 2017 22:39:37 +0000 (UTC) Subject: [wp-meta] [5493] sites/trunk/api.wordpress.org/public_html/events/1.0/index.php: Events: Restore `no_location_available` behavior Message-ID: <20170516223937.E3E0110803B4@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170516/665c5cbf/attachment.html> From noreply at wordpress.org Tue May 16 22:39:38 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 16 May 2017 22:39:38 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.713d285c75e38e50b6786a407e411c56@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): In [changeset:"5493"]: {{{ #!CommitTicketReference repository="" revision="5493" Events: Restore `no_location_available` behavior r5491 introduced a new condition where the client might receive an unsuccesful `location` lookup, but it wasn't consistent with prior behavior. This commit applies the prior behavior to the new case, so that clients can expect a consistent `no_location_available` error if the location wasn't found. See #2823 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:26> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 16 23:30:48 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 16 May 2017 23:30:48 +0000 (UTC) Subject: [wp-meta] [5494] sites/trunk/common/includes/slack/announce/lib.php: Slack: Add a `/ deputies` command for the Commnunity team Message-ID: <20170516233048.7CC4D10803B4@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170516/fa25ca7e/attachment.html> From noreply at wordpress.org Wed May 17 01:27:43 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 01:27:43 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.2db1eb7fbcdfbba37ebc1b0fd77e6284@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by coreymckrill): Added the above patch to address Problem 2, IPv6 support. It will need to get updated once we know the name of the table with the IPv6 location data. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:27> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 03:25:01 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 03:25:01 -0000 Subject: [wp-meta] [Making WordPress.org] #2018: Add functionality to flag topics and replies NSFW In-Reply-To: <050.378a5271e359deb473eab0557a2f7cd7@wordpress.org> References: <050.378a5271e359deb473eab0557a2f7cd7@wordpress.org> Message-ID: <065.9d018b75faf870e1a6245cb6b5f209ea@wordpress.org> #2018: Add functionality to flag topics and replies NSFW ----------------------------+------------------ Reporter: netweb | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: needs-patch | ----------------------------+------------------ Comment (by netweb): Related: we should investigate doing similar for "Not a support question" at the same time -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2018#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 10:28:35 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 10:28:35 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.6aed0f0b5d0810d9d781e1a01af206b8@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by dd32): [attachment:2823.diff] takes a pretty harsh attack on some of the code in order to attempt to get the performance better for location searches. * `get_city_from_coordinates()` is gone - It's just not performant enough and I couldn't find an easy way to achieve decent performance for such an edgecase * `get_valid_country_codes()` wasn't actually being used (though was querying) * `guess_location_from_geonames_fallback()` and as a result `get_ideographic_counties()` is gone - this at first seems like a step backwards, however, I think what it's attempting to achieve was going about things the wrong way. * `REPLACE( alternatenames, CONCAT( asciiname, ' - ' ), '' ) LIKE` wasn't performant and there wasn't much of a chance of it being so * using a `alternatenames LIKE '%,Blah,%'` was working, but wasn't really fast In order to speed things up, I created a new table based off the `geoname` data, `geoname_summary` which expands the `(name, asciiname, alternatenames)` out into a single `name` column, and also adds variants (for example the city name without dashes). One major change in this is that if you type in, for example, `The Big Apple` the location returned will now be `The Big Apple` instead of `New York City`, similarly, if you search for `Wien` you'll get just that `Wien` not `Vienna`. Unfortunately typo's will stay as typo's (for example, `New Yorke` or `Lunden`). This might also make it easier to return multiple results in the future (`Springfield, MO` vs `Springfield, MA` for example, or allowing an en_AU locale to pull up `Wellington, NZ` instead of `Wellington, AU`). All the test cases that passed are still passing albeit with the new return data, but instead of the ~100 queries taking 4-6 seconds, it now takes 0.04s for a slightly fewer number of queries. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:28> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 11:31:57 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 11:31:57 -0000 Subject: [wp-meta] [Making WordPress.org] #2828: Minor change on extending-the-rest-api Message-ID: <053.a4a00602b615710ef29b2c778ee6495d@wordpress.org> #2828: Minor change on extending-the-rest-api ---------------------------+-------------------------- Reporter: rafasashi | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Developer Hub | Keywords: dev-feedback ---------------------------+-------------------------- In [https://developer.wordpress.org/rest-api/extending-the-rest-api /adding-custom-endpoints/] The given example works only replacing {{{ $data['id'] }}} by {{{ $data['URL']['id'] }}} ------------------------------------------------------------------------------ {{{ /** * Grab latest post title by an author! * * @param array $data Options for the function. * @return string|null Post title for the latest, * or null if none. */ function my_awesome_func( $data ) { $posts = get_posts( array( 'author' => $data['URL']['id'], ) ); if ( empty( $posts ) ) { return new WP_Error( 'awesome_no_author', 'Invalid author', array( 'status' => 404 ) ); } return $posts[0]->post_title; } }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2828> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 11:42:33 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 11:42:33 -0000 Subject: [wp-meta] [Making WordPress.org] #2828: Minor change on extending-the-rest-api In-Reply-To: <053.a4a00602b615710ef29b2c778ee6495d@wordpress.org> References: <053.a4a00602b615710ef29b2c778ee6495d@wordpress.org> Message-ID: <068.a73c9c0d6d09b17be3b26163ca70f184@wordpress.org> #2828: Minor change on extending-the-rest-api ---------------------------+---------------------- Reporter: rafasashi | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Developer Hub | Resolution: invalid Keywords: dev-feedback | ---------------------------+---------------------- Changes (by rafasashi): * status: new => closed * resolution: => invalid -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2828#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 17:08:13 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 17:08:13 -0000 Subject: [wp-meta] [Making WordPress.org] #2829: Enhancement Request - Clear the page parameter when filter changes the current view Message-ID: <059.efee59752d3a7d6fb09dc919a6704f8f@wordpress.org> #2829: Enhancement Request - Clear the page parameter when filter changes the current view -----------------------------+----------------- Reporter: garrett-eclipse | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: General | Keywords: -----------------------------+----------------- I originally posted this to GlotPress-WP but this is a WP issue and it's not part of the default GP install. Full Details - https://github.com/GlotPress/GlotPress- WP/issues/718#event-1085632935 -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2829> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 17:10:33 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 17:10:33 -0000 Subject: [wp-meta] [Making WordPress.org] #2829: Clear the page parameter when filter changes the current view (was: Enhancement Request - Clear the page parameter when filter changes the current view) In-Reply-To: <059.efee59752d3a7d6fb09dc919a6704f8f@wordpress.org> References: <059.efee59752d3a7d6fb09dc919a6704f8f@wordpress.org> Message-ID: <074.6eb61600f1c717212613f98b62326649@wordpress.org> #2829: Clear the page parameter when filter changes the current view --------------------------------------+------------------ Reporter: garrett-eclipse | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Translate Site & Plugins | Resolution: Keywords: | --------------------------------------+------------------ Changes (by ocean90): * component: General => Translate Site & Plugins Old description: > I originally posted this to GlotPress-WP but this is a WP issue and it's > not part of the default GP install. > > Full Details - https://github.com/GlotPress/GlotPress- > WP/issues/718#event-1085632935 New description: I originally posted this to GlotPress-WP but this is a WP.org issue and it's not part of the default GP install. Full Details - https://github.com/GlotPress/GlotPress- WP/issues/718#event-1085632935 -- -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2829#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 17:17:16 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 17:17:16 -0000 Subject: [wp-meta] [Making WordPress.org] #2829: Clear the page parameter when filter changes the current view In-Reply-To: <059.efee59752d3a7d6fb09dc919a6704f8f@wordpress.org> References: <059.efee59752d3a7d6fb09dc919a6704f8f@wordpress.org> Message-ID: <074.0d972bdd3305a364033cc67b381fe0d3@wordpress.org> #2829: Clear the page parameter when filter changes the current view --------------------------------------+------------------ Reporter: garrett-eclipse | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Translate Site & Plugins | Resolution: Keywords: | --------------------------------------+------------------ Comment (by garrett-eclipse): Thanks for the tweak @ocean90 -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2829#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 18:21:50 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 17 May 2017 18:21:50 +0000 (UTC) Subject: [wp-meta] [5495] sites/trunk/api.wordpress.org/public_html/events/1.0/index.php: Events: Prefer meetups over WordCamps to improve location accuracy Message-ID: <20170517182150.0BBEA108033F@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170517/3adc941c/attachment.html> From noreply at wordpress.org Wed May 17 18:21:50 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 18:21:50 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.1c554cc79545836c4828c41fb9f6de2b@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): In [changeset:"5495"]: {{{ #!CommitTicketReference repository="" revision="5495" Events: Prefer meetups over WordCamps to improve location accuracy See #2823 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:29> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 19:23:19 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 17 May 2017 19:23:19 +0000 (UTC) Subject: [wp-meta] [5496] sites/trunk/api.wordpress.org/public_html/events/1.0/tests/ test-index.php: Events: Track query execution time to aid optimization Message-ID: <20170517192319.74A73108033F@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170517/1f80e5fe/attachment-0001.html> From noreply at wordpress.org Wed May 17 19:23:19 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 19:23:19 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.26ebc9a4bc375974f8afe540a6845447@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): In [changeset:"5496"]: {{{ #!CommitTicketReference repository="" revision="5496" Events: Track query execution time to aid optimization The test suite isn't representative of real-world usage, because by nature it's weighted heavily towards edge cases. Establishing a performance baseline is still useful when optimizing, though. See #2823 Props dd32 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:30> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 20:30:29 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 17 May 2017 20:30:29 +0000 (UTC) Subject: [wp-meta] [5497] sites/trunk/api.wordpress.org/public_html/events/1.0: Events: Remove `get_city_from_coordinates()` to improve performance Message-ID: <20170517203029.77501108033F@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170517/a0b3239e/attachment.html> From noreply at wordpress.org Wed May 17 20:30:29 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 20:30:29 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.9f6f0d0b7a4df3fc29abd74ce7b0fe4f@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): In [changeset:"5497"]: {{{ #!CommitTicketReference repository="" revision="5497" Events: Remove `get_city_from_coordinates()` to improve performance The function was not performant, and it's not easy to make it that way. It's only needed for a few edge cases, and we can get the location from the events themselves (similar to r5491). So, removing this is a good trade-off. Because we are able to rebuild the location, no changes are needed in Core, and a new version of this endpoint is not needed. See #2823 Props dd32 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:32> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 21:06:36 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 21:06:36 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.7288bc361b9806a2cf3dcf650f527931@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by karmatosed): Its worth adding the oddity I experience here: [[Image(https://cldup.com/U3LohVCeQu.png)]] Firstly, I am nowhere near Romford (that's a pretty far away from where I am). Secondly, as someone from UK, showing US City in the box is a weird experience. Also, why only cities? In UK for example towns have meetups and a lot of people don't live in cities.. this I am sure happens in US :) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:34> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 21:21:15 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 21:21:15 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.73a94a9d13f537742af6ae92aae202bc@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): Replying to [comment:34 karmatosed]: > Secondly, as someone from UK, showing US City in the box is a weird experience. That string is internationalized, so you'll see a local city as soon as it's translated. > Also, why only cities? The database we have is primarily city-centric. It has some region information, but it's not detailed or comprehensive enough to fully support. The API does try to match inputs other than cities, but we only explicitly mention cities in the instructions because that's the only thing we can guarantee will work. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:35> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 22:12:03 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 22:12:03 -0000 Subject: [wp-meta] [Making WordPress.org] #1724: Readme parsing bugs In-Reply-To: <048.f0a4034ffeb07046bc76b987bdf394f2@wordpress.org> References: <048.f0a4034ffeb07046bc76b987bdf394f2@wordpress.org> Message-ID: <063.8828e938d862d956dcbf22ee72cd8e05@wordpress.org> #1724: Readme parsing bugs ------------------------------+------------------ Reporter: dd32 | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: close | ------------------------------+------------------ Changes (by Ipstenu): * keywords: => close Comment: I think we can close this and open up new ones as needed. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1724#comment:19> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 22:24:13 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 22:24:13 -0000 Subject: [wp-meta] [Making WordPress.org] #2594: Plugin Directory: List pending plugins on 'add' page In-Reply-To: <051.8682691f18de896a37086227c227a3cc@wordpress.org> References: <051.8682691f18de896a37086227c227a3cc@wordpress.org> Message-ID: <066.0209a346ebcd959a5ca37a0653c0f24e@wordpress.org> #2594: Plugin Directory: List pending plugins on 'add' page ----------------------------------------------+---------------------------- Reporter: Ipstenu | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Component: Plugin Directory | Directory v3.0 Keywords: has-patch commit has-screenshots | Resolution: ----------------------------------------------+---------------------------- Changes (by tellyworth): * milestone: Plugin Directory v3 - Future => Plugin Directory v3.0 -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2594#comment:8> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 23:22:37 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 23:22:37 -0000 Subject: [wp-meta] [Making WordPress.org] #2653: 404 on Browse url In-Reply-To: <054.96045bfc56395581132ce69301c6bac7@wordpress.org> References: <054.96045bfc56395581132ce69301c6bac7@wordpress.org> Message-ID: <069.69469ecabf6379084fe56d7d196e93ae@wordpress.org> #2653: 404 on Browse url ------------------------------+------------------------------------------- Reporter: tellyworth | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by joyously): > A redirect to https://wordpress.org/plugins/browse/featured/ slipped into r5248 This is bad UX since it takes an inclusive URL and turns it into a dead end. I think the intent of a URL like `https://wordpress.org/plugins/browse/` is to show everything that there is. I always thought it should show the main taxonomy of the plugin directory, with counts, and no actual plugins. If that idea isn't popular, my fallback would be to have it show plugins ordered by plugin name, with an alphabet of links to jump to the sections for each letter. It definitely should not be the same as `https://wordpress.org/plugins/browse/new/`, although the Browse page could have links to other ways to browse like New or Popular. I think Updated can be very useful, but not promoted with a link. It should work, though, if you know the URL. By the way, looking at the Featured page, why do they never change? Who determines what goes here? And why the confusing language of having "feature plugins" under "Beta Testing" and a few big plugins under "Featured"? I think the plugins that could go into core would get more interest and feedback if they were shown by default (featured), instead of always showing the same 6 everyone knows about. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2653#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 17 23:32:35 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 17 May 2017 23:32:35 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.ddcb2a72606a4a3fdf49724cf3ebb833@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by dd32): Replying to [comment:35 iandunn]: > Replying to [comment:34 karmatosed]: > > Also, why only cities? > > The database we have is primarily city-centric. It has some region information, but it's not detailed or comprehensive enough to fully support. The API does try to match inputs other than cities, but we only explicitly mention cities in the instructions because that's the only thing we can guarantee will work. Worth noting that the database we've been using says "city" but in this context, city means town. We've used a data source which includes town with a population of >1k (or an administrative area of 1k, so town X of 500 and 500 in the surrounding area, where X is the common point would be included). For `countrycode = GB` there were 3.6k 'towns' with 14k different spellings and alternate names. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:36> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 01:26:49 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 18 May 2017 01:26:49 +0000 (UTC) Subject: [wp-meta] [5498] sites/trunk/api.wordpress.org/public_html/dotorg/github-sync/ feature-plugins.sh: Feature Plugins Github Sync: Don't performa a commit/ version bump if nothing has changed. Message-ID: <20170518012649.13A0310805FB@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170518/3d259309/attachment.html> From noreply at wordpress.org Thu May 18 05:54:12 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 18 May 2017 05:54:12 +0000 (UTC) Subject: [wp-meta] [5499] sites/trunk/api.wordpress.org/public_html/events/1.0/index.php: Events: Stop using fuzzy locations for 4.8-beta2 Message-ID: <20170518055412.2E23E10805FB@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170518/917cfbfe/attachment-0001.html> From noreply at wordpress.org Thu May 18 05:54:12 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 05:54:12 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.2bcc76be157293419cb3da7c3aaed582@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): In [changeset:"5499"]: {{{ #!CommitTicketReference repository="" revision="5499" Events: Stop using fuzzy locations for 4.8-beta2 See #2823 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:37> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 07:07:40 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 18 May 2017 07:07:40 +0000 (UTC) Subject: [wp-meta] [5500] sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory/class-plugin-directory.php: Plugin directory: properly fix duplicate plugin slug issue. Message-ID: <20170518070740.853D01080394@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170518/b4384025/attachment.html> From noreply at wordpress.org Thu May 18 07:07:41 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 07:07:41 -0000 Subject: [wp-meta] [Making WordPress.org] #2787: Plugin Directory: Reject plugin on duplicate slugs In-Reply-To: <051.2ac2a1bb741f1b18b5c20f5005ec290b@wordpress.org> References: <051.2ac2a1bb741f1b18b5c20f5005ec290b@wordpress.org> Message-ID: <066.644d8b0b3345743f8b31c2c82a03f86d@wordpress.org> #2787: Plugin Directory: Reject plugin on duplicate slugs ------------------------------+------------------------- Reporter: Ipstenu | Owner: tellyworth Type: defect | Status: closed Priority: normal | Milestone: Component: Plugin Directory | Resolution: fixed Keywords: has-patch | ------------------------------+------------------------- Changes (by tellyworth): * status: reopened => closed * resolution: => fixed Comment: In [changeset:"5500"]: {{{ #!CommitTicketReference repository="" revision="5500" Plugin directory: properly fix duplicate plugin slug issue. Props @SergeyBiryukov Refines earlier fix in [5416] Fixes #2787 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2787#comment:10> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 09:29:58 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 09:29:58 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.6b706717eed8163de85d58bdc87af796@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by ocean90): Searching for "K?ln" gives me a "We couldn?t locate K?ln." error but a search for "Cologne" or "Koeln" returns the proper "K?ln". "M?nster" is working fine so I'm not sure if it's an issue with umlauts. Another oddity: "D?sseldorf" returns "D?sseldorf-Pempelfort" which is kinda unexpected because "Pempelfort" is just a city part of "D?sseldorf". -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:38> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 14:37:27 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 14:37:27 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.e1726318731cb072c7acf69fe4c49423@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by pbiron): As I mentioned in the devchat yesterday, searching for "Gardner, CO" gives events in Kansas City, MO...which is almost 700 miles away. Looking into the `community-events-location` meta_key, I see that the lat/lng stored is for KC, MO, which explains why it showing event for KC, MO. However, if [[https://meta.trac.wordpress.org/ticket/2823#comment:1|Otto's comment]] is correct that place name searches are using `geonames.org` data then that is odd, because http://www.geonames.org/search.html?q=gardner%2C+co&country= correctly finds Gardner, CO (with the correct lat/lng) as the 1st result. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:39> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 15:07:07 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 15:07:07 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.1bd9daa9db127321c26f1dc5d1014217@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): Replying to [comment:38 ocean90]: > Searching for "K?ln" gives me a "We couldn?t locate K?ln." error but a search for "Cologne" or "Koeln" returns the proper "K?ln". "M?nster" is working fine so I'm not sure if it's an issue with umlauts. > > Another oddity: "D?sseldorf" returns "D?sseldorf-Pempelfort" which is kinda unexpected because "Pempelfort" is just a city part of "D?sseldorf". I think most of the charset issues have been worked out, but there's still at least one that I know about (see the unit tests). @dd32 is working on upgrading our geocoding from geonames.org to Google's Geocoding API, which should fix all of that. See [attachment:2823.2.diff]. Replying to [comment:39 pbiron]: > As I mentioned in the devchat yesterday, searching for "Gardner, CO" gives events in Kansas City, MO...which is almost 700 miles away. Looking into the community-events-location meta_key, I see that the lat/lng stored is for KC, MO, which explains why it showing event for KC, MO. I think that's an edge case just because there's not enough information to distinguish between the two Kansas Citys, since they're so close to each other geographically. [wp40774] might be able to help there, though, since we could use the IP geolocation as a signal. We'd also like to have the API start returning a list of alternate locations, and have Core display those in a dropdown for the user to choose. That'll probably have to be 4.8.1, though. > However, if Otto's comment is correct that place name searches are using geonames.org data then that is odd, because http://www.geonames.org/search.html?q=gardner%2C+co&country= correctly finds Gardner, CO (with the correct lat/lng) as the 1st result. Otto's definitely correct, but the code does a lot of gymnastics to try and parse the query and look it up in a lot of ways. There could be a bug in there, or just some conflicting edge cases, etc. Dion's work to switch to Google's API should help there too. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:40> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 15:12:28 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 15:12:28 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.3fc74bb2144d19334fd2e82c72d51502@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by pbiron): Replying to [comment:36 dd32]: > Worth noting that the database we've been using says "city" but in this context, city means town. We've used a data source which includes town with a population of >1k (or an administrative area of 1k, so town X of 500 and 500 in the surrounding area, where X is the common point would be included). That probably explains the behavior I'm seeing...as Gardner, CO has a population of only **70**. If the surrounding farms are included, what I call "Greater Metropolitan Gardner", the pop balloons to a whopping **400**. Yes, I live in the sticks :-). -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:41> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 15:21:52 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 15:21:52 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.9457d08c834f2fbce8bc3bfd98d7408f@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by pbiron): Replying to [comment:40 iandunn]: > Replying to [comment:39 pbiron]: > > As I mentioned in the devchat yesterday, searching for "Gardner, CO" gives events in Kansas City, MO...which is almost 700 miles away. Looking into the community-events-location meta_key, I see that the lat/lng stored is for KC, MO, which explains why it showing event for KC, MO. > > I think that's an edge case just because there's not enough information to distinguish between the two Kansas Citys, since they're so close to each other geographically. Sorry, "KC, MO" was just my abbreviation for "Kansas City, MO"...I should have been more clear. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:43> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 15:20:14 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 15:20:14 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.976d1067d255e4a4b676715249c913cf@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): Replying to [comment:41 pbiron]: > Replying to [comment:36 dd32]: > > Worth noting that the database we've been using says "city" but in this context, city means town. We've used a data source which includes town with a population of >1k (or an administrative area of 1k, so town X of 500 and 500 in the surrounding area, where X is the common point would be included). > > That probably explains the behavior I'm seeing...as Gardner, CO has a population of only **70**. If the surrounding farms are included, what I call "Greater Metropolitan Gardner", the pop balloons to a whopping **400**. Yes, I live in the sticks :-). No shame in that :) I think the only reason we limited it to towns with > 1k population is just because, for an endpoint that will see as much traffic as this one, we don't have the server resources to do the database queries on larger data sets. Once we switch to Google's API, though, that should solve that problem. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:42> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 17:27:08 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 17:27:08 -0000 Subject: [wp-meta] [Making WordPress.org] #2753: Plugin directory search sorting and filtering In-Reply-To: <054.ea0beff6952873fe3a66bcfa513e7b6b@wordpress.org> References: <054.ea0beff6952873fe3a66bcfa513e7b6b@wordpress.org> Message-ID: <069.e5ffe04e38ed8e13796c8d13c82d383a@wordpress.org> #2753: Plugin directory search sorting and filtering -------------------------------------+------------------------------------- Reporter: tellyworth | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Component: Plugin Directory | Future Keywords: ui-feedback needs- | Resolution: screenshots | -------------------------------------+------------------------------------- Comment (by joyously): @gibrown, I put the filters that made sense to me into a mockup image (see attachments). I am of two minds on how the filters should behave. One is that each choice is a link (parameterized search) so the page reloads on each. The other is that it is a form that you set all the parameters and then submit once. When I have used these types of filters, my preference is one submit, but people with fast connections probably prefer each click to change the page. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2753#comment:5> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 18:02:55 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 18:02:55 -0000 Subject: [wp-meta] [Making WordPress.org] #2753: Plugin directory search sorting and filtering In-Reply-To: <054.ea0beff6952873fe3a66bcfa513e7b6b@wordpress.org> References: <054.ea0beff6952873fe3a66bcfa513e7b6b@wordpress.org> Message-ID: <069.2b6d36cf2ac0512c8ff5bb9345047bab@wordpress.org> #2753: Plugin directory search sorting and filtering -------------------------------------+------------------------------------- Reporter: tellyworth | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Component: Plugin Directory | Future Keywords: ui-feedback needs- | Resolution: screenshots | -------------------------------------+------------------------------------- Comment (by joyously): One thing that is unclear is whether it is different code that populates the plugin search results in the admin versus the page that looks the same on wordpress.org. Does this ticket cover both contexts? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2753#comment:6> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 20:28:08 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 20:28:08 -0000 Subject: [wp-meta] [Making WordPress.org] #2245: Migrate pending plugins In-Reply-To: <054.f162bbe9076a6f343bde09022707488c@wordpress.org> References: <054.f162bbe9076a6f343bde09022707488c@wordpress.org> Message-ID: <069.278d72244e9f3ea060046d2c00a9288b@wordpress.org> #2245: Migrate pending plugins ------------------------------+------------------------------------ Reporter: tellyworth | Owner: dd32 Type: task | Status: assigned Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------ Comment (by Ipstenu): @dd32 - Did we migrate the rejected plugins? I'd like to be able to close this out :) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2245#comment:8> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 20:31:26 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 20:31:26 -0000 Subject: [wp-meta] [Making WordPress.org] #2665: Plugin Directory Admins: Contact Plugin Author should open in new window In-Reply-To: <051.88b69e0e89d215bc69777301a3f89077@wordpress.org> References: <051.88b69e0e89d215bc69777301a3f89077@wordpress.org> Message-ID: <066.e55704f893a5312870b7e0b49f8b603b@wordpress.org> #2665: Plugin Directory Admins: Contact Plugin Author should open in new window ------------------------------+---------------------- Reporter: Ipstenu | Owner: Otto42 Type: enhancement | Status: closed Priority: normal | Milestone: Component: Plugin Directory | Resolution: wontfix Keywords: has-patch commit | ------------------------------+---------------------- Changes (by Ipstenu): * status: assigned => closed * resolution: => wontfix Comment: On review and having used the directory for a month now, I classify this as won't fix. We don't actually need it. I was wrong :) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2665#comment:7> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 20:39:06 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 20:39:06 -0000 Subject: [wp-meta] [Making WordPress.org] #2830: Plugin Directory: Include slug in submission emails Message-ID: <051.980ca4c7bb6bb49acc9857d3105e0019@wordpress.org> #2830: Plugin Directory: Include slug in submission emails ------------------------------+----------------------- Reporter: Ipstenu | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Keywords: has-patch ------------------------------+----------------------- To mitigate the accidents of "Oh no! I didn't want THAT slug!" we should let people know what the slug's going to be when the plugin is submitted. This patch tells them in two places: 1) The in-page notice of "Submission in!" 2) The email of "We got it!" Both detail what the slug is and remind developers not to resubmit and just email us if there's a problem. This MAY result in a lot of weird emails about "WooCommerce! We need woo!" but that's better than after- approval complaints about bad slugs. I think. If I'm wrong, we'll try again. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2830> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 20:47:15 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 20:47:15 -0000 Subject: [wp-meta] [Making WordPress.org] #2677: Plugin Directory: Admin email subjects to plugin author (s) improvements (was: Plugin Directory: Admin email to plugin author (s) improvements) In-Reply-To: <051.76e30163c28c8e10b716b6642fdc91d1@wordpress.org> References: <051.76e30163c28c8e10b716b6642fdc91d1@wordpress.org> Message-ID: <066.0b0030985e40ea6e31edb21cf4a75035@wordpress.org> #2677: Plugin Directory: Admin email subjects to plugin author (s) improvements ------------------------------+------------------------- Reporter: Ipstenu | Owner: tellyworth Type: enhancement | Status: reopened Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch commit | ------------------------------+------------------------- Comment (by Ipstenu): Agree with Sergey! Attached patch that also adds in a subject for rejected plugins so it's more clear there too. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2677#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 21:43:51 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 21:43:51 -0000 Subject: [wp-meta] [Making WordPress.org] #2831: On the Advanced view of a plugin the list of committers is imporperly formatted. Message-ID: <050.a1902e359d66d525b6d3ac015ea54721@wordpress.org> #2831: On the Advanced view of a plugin the list of committers is imporperly formatted. ------------------------------+------------------------------------------ Reporter: aguseo | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Keywords: has-screenshots ui-feedback ------------------------------+------------------------------------------ On the Advanced view of a plugin the list of committers is cascading vs being under each other. Screenshot here: https://cloudup.com/c_eWP58vjh5 It could be fixed with a bit of css like this: {{{ .committer-list li { clear: both; margin-bottom: 0.5rem; } }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2831> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 18 21:55:34 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 18 May 2017 21:55:34 -0000 Subject: [wp-meta] [Making WordPress.org] #2831: On the Advanced view of a plugin the list of committers is imporperly formatted. In-Reply-To: <050.a1902e359d66d525b6d3ac015ea54721@wordpress.org> References: <050.a1902e359d66d525b6d3ac015ea54721@wordpress.org> Message-ID: <065.0644df10955787fa1554274f31e8fe23@wordpress.org> #2831: On the Advanced view of a plugin the list of committers is imporperly formatted. -------------------------------------+------------------------------------- Reporter: aguseo | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Component: Plugin Directory | Future Keywords: has-screenshots ui- | Resolution: feedback reporter-feedback | -------------------------------------+------------------------------------- Changes (by Ipstenu): * keywords: has-screenshots ui-feedback => has-screenshots ui-feedback reporter-feedback Comment: @aguseo - what plugin is that on? And what browser/OS are you on. I can't reproduce that view. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2831#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 19 02:37:09 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 19 May 2017 02:37:09 -0000 Subject: [wp-meta] [Making WordPress.org] #2245: Migrate pending plugins In-Reply-To: <054.f162bbe9076a6f343bde09022707488c@wordpress.org> References: <054.f162bbe9076a6f343bde09022707488c@wordpress.org> Message-ID: <069.090fcd373b2cfbc8d0c4274745972b16@wordpress.org> #2245: Migrate pending plugins ------------------------------+------------------------------------ Reporter: tellyworth | Owner: dd32 Type: task | Status: assigned Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------ Comment (by dd32): Nope, never got to migrating them over. Sorry. I'll try to get to it in the next couple of weeks, hopefully after 4.8 ships. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2245#comment:9> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 19 08:35:39 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 19 May 2017 08:35:39 -0000 Subject: [wp-meta] [Making WordPress.org] #2832: Search result not working properly Message-ID: <057.58ee2aeb07cce0d41b56ca0079fe0edf@wordpress.org> #2832: Search result not working properly ------------------------------+--------------------------------------- Reporter: karan.gadhavi | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Keywords: 2nd-opinion needs-testing ------------------------------+--------------------------------------- Hi I searched for "Facebook Events" in plug-in directory and found surprising result. "EME Sync Facebook Events" Plug-in second and "Facebook Events Importer" & " Import Facebook Events" below it event both has many points better then EME Sync Facebook Events plig-in Here is comparison Search in Title Name Active Ins Search Term in Tag rating EME Sync Facebook Events 500 not exact 5 Facebook Events Importer 2000 exact 3 Import Facebook Events 1000+ exact 5 Import Facebook Events plug-in should came first i believe -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2832> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 19 08:55:14 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 19 May 2017 08:55:14 -0000 Subject: [wp-meta] [Making WordPress.org] #2831: On the Advanced view of a plugin the list of committers is imporperly formatted. In-Reply-To: <050.a1902e359d66d525b6d3ac015ea54721@wordpress.org> References: <050.a1902e359d66d525b6d3ac015ea54721@wordpress.org> Message-ID: <065.08b799fe1b3f378b235c8be4aec1ef14@wordpress.org> #2831: On the Advanced view of a plugin the list of committers is imporperly formatted. -------------------------------------+------------------------------------- Reporter: aguseo | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Component: Plugin Directory | Future Keywords: has-screenshots ui- | Resolution: feedback reporter-feedback | -------------------------------------+------------------------------------- Comment (by aguseo): Replying to [comment:1 Ipstenu]: > @aguseo - what plugin is that on? And what browser/OS are you on. > > I can't reproduce that view. Hi @Ipstenu, Sorry, I should have shared the link upfront. I found it on these urls so far: https://wordpress.org/plugins/gigpress/advanced/ https://wordpress.org/plugins/event-tickets/advanced/ https://wordpress.org/plugins/image-widget/advanced/ https://wordpress.org/plugins/advanced-post-manager/advanced/ I'm contributor to these plugins. It only seems to be like that when I'm logged in. That is when I see the committers list where this glitch happens. When I'm logged out I don't see committers. I'm using Windows 7 / 10 and Firefox 52 / 53, chrome 58.0.3029.110 (64-bit), IE11. I hope this helps, let me know if you need more info. Cheers -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2831#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 19 12:47:03 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 19 May 2017 12:47:03 -0000 Subject: [wp-meta] [Making WordPress.org] #2631: Plugin Directory: No way to view Recently Updated plugins In-Reply-To: <052.eb4400b9e45b87852011048965021979@wordpress.org> References: <052.eb4400b9e45b87852011048965021979@wordpress.org> Message-ID: <067.86909614abf4dc96771f153d402f2c26@wordpress.org> #2631: Plugin Directory: No way to view Recently Updated plugins ------------------------------+------------------------------------------- Reporter: infokurs | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: needs-patch | ------------------------------+------------------------------------------- Comment (by djr): Fortunately there's absolutely no spamming now in the Plugin directory... /sarcasm. https://wordpress.org/plugins/popup-master/ -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2631#comment:5> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 19 14:16:56 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 19 May 2017 14:16:56 -0000 Subject: [wp-meta] [Making WordPress.org] #2119: Profiles: Notifications should have an option to match whole words only In-Reply-To: <058.0e5ddec94026ef8887b7fb79e9528bc5@wordpress.org> References: <058.0e5ddec94026ef8887b7fb79e9528bc5@wordpress.org> Message-ID: <073.d922f0636c7a85988a8769bfda747147@wordpress.org> #2119: Profiles: Notifications should have an option to match whole words only ----------------------------+------------------ Reporter: SergeyBiryukov | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Profiles | Resolution: Keywords: | ----------------------------+------------------ Comment (by denisco): Is there a chance that this will be corrected in the near future? Or will the source code of notifications be opened? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2119#comment:6> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 19 14:22:19 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 19 May 2017 14:22:19 -0000 Subject: [wp-meta] [Making WordPress.org] #2832: Search result not working properly In-Reply-To: <057.58ee2aeb07cce0d41b56ca0079fe0edf@wordpress.org> References: <057.58ee2aeb07cce0d41b56ca0079fe0edf@wordpress.org> Message-ID: <072.fad0f93841a37d1ca836704204b40095@wordpress.org> #2832: Search result not working properly ---------------------------------------+----------------------------------- Reporter: karan.gadhavi | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory Component: Plugin Directory | v3.0 Keywords: 2nd-opinion needs-testing | Resolution: ---------------------------------------+----------------------------------- Description changed by SergeyBiryukov: Old description: > Hi > > I searched for "Facebook Events" in plug-in directory and found > surprising result. > > "EME Sync Facebook Events" Plug-in second and "Facebook Events Importer" > & " > Import Facebook Events" below it event both has many points better then > EME Sync Facebook Events plig-in > > Here is comparison > Search in Title Name Active Ins Search Term in Tag rating > EME Sync Facebook Events 500 not exact 5 > Facebook Events Importer 2000 exact 3 > Import Facebook Events 1000+ exact 5 > > Import Facebook Events plug-in should came first i believe New description: Hi I searched for "Facebook Events" in plug-in directory and found surprising result. "EME Sync Facebook Events" Plug-in second and "Facebook Events Importer" & " Import Facebook Events" below it event both has many points better then EME Sync Facebook Events plig-in Here is comparison ||Search in Title Name ||Active Ins ||Search Term in Tag ||rating || ||EME Sync Facebook Events ||500 ||not exact ||5 || ||Facebook Events Importer ||2000 ||exact ||3 || ||Import Facebook Events ||1000+ ||exact ||5 || Import Facebook Events plug-in should came first i believe -- -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2832#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 19 15:18:25 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 19 May 2017 15:18:25 -0000 Subject: [wp-meta] [Making WordPress.org] #2119: Profiles: Notifications should have an option to match whole words only In-Reply-To: <058.0e5ddec94026ef8887b7fb79e9528bc5@wordpress.org> References: <058.0e5ddec94026ef8887b7fb79e9528bc5@wordpress.org> Message-ID: <073.f353e497095ea6b4d6904b0400427a96@wordpress.org> #2119: Profiles: Notifications should have an option to match whole words only ----------------------------+------------------ Reporter: SergeyBiryukov | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Profiles | Resolution: Keywords: | ----------------------------+------------------ Comment (by fierevere): I'm getting 2/3 false notifications for "Yui", not just JqueryUi but random strings and even other usernames like {{{ Hi @tzyyyuin }}} matching should be done versus exact string, otherwise such notifications are close to useless -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2119#comment:7> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 19 17:40:40 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 19 May 2017 17:40:40 -0000 Subject: [wp-meta] [Making WordPress.org] #2831: On the Advanced view of a plugin the list of committers is imporperly formatted. In-Reply-To: <050.a1902e359d66d525b6d3ac015ea54721@wordpress.org> References: <050.a1902e359d66d525b6d3ac015ea54721@wordpress.org> Message-ID: <065.20f20bc2321cbacf12545aab3809c0fa@wordpress.org> #2831: On the Advanced view of a plugin the list of committers is imporperly formatted. -------------------------------------+------------------------------------- Reporter: aguseo | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Component: Plugin Directory | Future Keywords: has-screenshots ui- | Resolution: feedback reporter-feedback | -------------------------------------+------------------------------------- Comment (by Ipstenu): Oooh. So mine won't look like that when logged in because I'm an admin, and I have an extra line below it (for the email addresses). Interesting... I'm torn between "You shouldn't see committers at all if you're not a committer of that plugin" and "We should fix that!" -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2831#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 19 18:41:58 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 19 May 2017 18:41:58 -0000 Subject: [wp-meta] [Making WordPress.org] #2686: Plugin Search: Search should also take into account the number of ratings In-Reply-To: <051.6a8a8298224b7d93c0ff73de59c8a80c@wordpress.org> References: <051.6a8a8298224b7d93c0ff73de59c8a80c@wordpress.org> Message-ID: <066.ecc56d9dc66016b9019453b5533d789b@wordpress.org> #2686: Plugin Search: Search should also take into account the number of ratings ------------------------------+------------------------------------------- Reporter: bfintal | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by gibrown): Ah ha! Wilson score confidence interval for a Bernoulli parameter from http://www.evanmiller.org/how-not-to-sort-by-average-rating.html I think I will try putting something like this into the index. I need to figure how to make it work on a 5 star scale, but this addresses a lot of my concerns with hard coding any limits. Noting here mostly as a reminder. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2686#comment:11> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 19 18:53:30 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Fri, 19 May 2017 18:53:30 +0000 (UTC) Subject: [wp-meta] [5501] sites/trunk/api.wordpress.org/public_html/events/1.0: Events: Support IPv6 address geolocation. Message-ID: <20170519185330.0F4A51080374@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170519/d50927c7/attachment-0001.html> From noreply at wordpress.org Fri May 19 18:53:30 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 19 May 2017 18:53:30 -0000 Subject: [wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results In-Reply-To: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> References: <051.d19a1fefe110df86e0fbc9a866d51340@wordpress.org> Message-ID: <066.081773489b6a19a5b6d3d80085dad3fc@wordpress.org> #2823: Improve IP Geolocation Results ---------------------+----------------------- Reporter: iandunn | Owner: iandunn Type: defect | Status: accepted Priority: normal | Milestone: Component: API | Resolution: Keywords: | ---------------------+----------------------- Comment (by iandunn): In [changeset:"5501"]: {{{ #!CommitTicketReference repository="" revision="5501" Events: Support IPv6 address geolocation. See #2823 Props coreymckrill }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:44> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 14:08:29 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 14:08:29 -0000 Subject: [wp-meta] =?utf-8?q?=5BMaking_WordPress=2Eorg=5D_=232833=3A_A_lin?= =?utf-8?q?k_to_=E2=80=9CUnresolved_topics_for_this_plugin=E2=80=9D_displa?= =?utf-8?q?yed_to_plugin_contributors=2E?= Message-ID: <050.6143ae76b38ea6ef0c123b092eb36926@wordpress.org> #2833: A link to ?Unresolved topics for this plugin? displayed to plugin contributors. ------------------------------+----------------- Reporter: lapzor | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Keywords: ------------------------------+----------------- Show a link to ?Unresolved topics for this plugin? displayed to plugin contributors on their plugins support forum. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2833> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 14:09:46 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 14:09:46 -0000 Subject: [wp-meta] [Making WordPress.org] #2834: Give plugin contributors the right to lock a topic, or... Message-ID: <050.e7617ae4910ad984e73d420dab714c0d@wordpress.org> #2834: Give plugin contributors the right to lock a topic, or... -------------------------+----------------- Reporter: lapzor | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Keywords: -------------------------+----------------- Give plugin contributors the right to lock a topic in their plugins support forum, or automatically lock topics that are marked as resolved (no more replies allowed), or by default mark them as unresolved again when anyone replies. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2834> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 14:12:06 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 14:12:06 -0000 Subject: [wp-meta] [Making WordPress.org] #2835: Assign topic to specific plugin contributor Message-ID: <050.44e1cb2a6a38c93fdbc4e979b7a1f158@wordpress.org> #2835: Assign topic to specific plugin contributor -------------------------+----------------- Reporter: lapzor | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Keywords: -------------------------+----------------- Let plugin contributors assign a topic in their plugins support forum to a(nother) plugin contributor, that will receive a notification and maybe even highlight the thread for this user and/or show them under "Topics assigned to me" -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2835> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 14:14:13 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 14:14:13 -0000 Subject: [wp-meta] [Making WordPress.org] #2834: Give plugin contributors the right to lock a topic, or... In-Reply-To: <050.e7617ae4910ad984e73d420dab714c0d@wordpress.org> References: <050.e7617ae4910ad984e73d420dab714c0d@wordpress.org> Message-ID: <065.d17f590b280be30b62b902573606ba46@wordpress.org> #2834: Give plugin contributors the right to lock a topic, or... ----------------------------+------------------ Reporter: lapzor | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Changes (by lapzor): * component: General => Support Forums -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2834#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 14:13:42 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 14:13:42 -0000 Subject: [wp-meta] =?utf-8?q?=5BMaking_WordPress=2Eorg=5D_=232833=3A_A_lin?= =?utf-8?q?k_to_=E2=80=9CUnresolved_topics_for_this_plugin=E2=80=9D_displa?= =?utf-8?q?yed_to_plugin_contributors=2E?= In-Reply-To: <050.6143ae76b38ea6ef0c123b092eb36926@wordpress.org> References: <050.6143ae76b38ea6ef0c123b092eb36926@wordpress.org> Message-ID: <065.72ea9ede1e45ad37e311bb08e8d062b0@wordpress.org> #2833: A link to ?Unresolved topics for this plugin? displayed to plugin contributors. ----------------------------+------------------ Reporter: lapzor | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Changes (by lapzor): * component: Plugin Directory => Support Forums -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2833#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 14:14:33 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 14:14:33 -0000 Subject: [wp-meta] [Making WordPress.org] #2835: Assign topic to specific plugin contributor In-Reply-To: <050.44e1cb2a6a38c93fdbc4e979b7a1f158@wordpress.org> References: <050.44e1cb2a6a38c93fdbc4e979b7a1f158@wordpress.org> Message-ID: <065.86d4335a864bc832fb3e216578a3a6d4@wordpress.org> #2835: Assign topic to specific plugin contributor ----------------------------+------------------ Reporter: lapzor | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Changes (by lapzor): * component: General => Support Forums -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2835#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 14:50:20 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 14:50:20 -0000 Subject: [wp-meta] [Making WordPress.org] #2835: Assign topic to specific plugin contributor In-Reply-To: <050.44e1cb2a6a38c93fdbc4e979b7a1f158@wordpress.org> References: <050.44e1cb2a6a38c93fdbc4e979b7a1f158@wordpress.org> Message-ID: <065.482beb54788fa19f0ff0355a01e982dc@wordpress.org> #2835: Assign topic to specific plugin contributor ----------------------------+------------------ Reporter: lapzor | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Comment (by SergeyBiryukov): Hi @lapzor, welcome to WordPress Meta Trac! Thanks for the ticket. It's already possible to ping a plugin contributor (or any other WordPress.org user) by a username and ask them to take a look at the topic. Currently anyone can reply to any topic, what's the benefit of limiting that to a single person? That sounds more like a ticket system, forums generally don't work that way :) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2835#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 14:56:26 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 14:56:26 -0000 Subject: [wp-meta] [Making WordPress.org] #2834: Give plugin contributors the right to lock a topic, or... In-Reply-To: <050.e7617ae4910ad984e73d420dab714c0d@wordpress.org> References: <050.e7617ae4910ad984e73d420dab714c0d@wordpress.org> Message-ID: <065.d7194176732296a3fa50cd2201ce8d2d@wordpress.org> #2834: Give plugin contributors the right to lock a topic, or... ----------------------------+------------------------ Reporter: lapzor | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: Support Forums | Resolution: duplicate Keywords: | ----------------------------+------------------------ Changes (by SergeyBiryukov): * status: new => closed * resolution: => duplicate Comment: Hi @lapzor, welcome to WordPress Meta Trac! Thanks for the ticket. > Give plugin contributors the right to lock a topic in their plugins support forum We're already tracking this enhancement in #2598. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2834#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 15:02:21 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 15:02:21 -0000 Subject: [wp-meta] =?utf-8?q?=5BMaking_WordPress=2Eorg=5D_=232833=3A_A_lin?= =?utf-8?q?k_to_=E2=80=9CUnresolved_topics_for_this_plugin=E2=80=9D_displa?= =?utf-8?q?yed_to_plugin_contributors=2E?= In-Reply-To: <050.6143ae76b38ea6ef0c123b092eb36926@wordpress.org> References: <050.6143ae76b38ea6ef0c123b092eb36926@wordpress.org> Message-ID: <065.08446e3141efba2573c8b49bbd260a89@wordpress.org> #2833: A link to ?Unresolved topics for this plugin? displayed to plugin contributors. ----------------------------+------------------ Reporter: lapzor | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Comment (by SergeyBiryukov): Hi @lapzor, welcome to WordPress Meta Trac! Thanks for the ticket. I'm not sure I understand the suggestion, could you clarify a bit more? Where should the link be added? There's already an Unresolved Topics view for any plugin: https://wordpress.org/support/plugin/jetpack/unresolved/ -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2833#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 15:41:41 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 15:41:41 -0000 Subject: [wp-meta] =?utf-8?q?=5BMaking_WordPress=2Eorg=5D_=232833=3A_A_lin?= =?utf-8?q?k_to_=E2=80=9CUnresolved_topics_for_this_plugin=E2=80=9D_displa?= =?utf-8?q?yed_to_plugin_contributors=2E?= In-Reply-To: <050.6143ae76b38ea6ef0c123b092eb36926@wordpress.org> References: <050.6143ae76b38ea6ef0c123b092eb36926@wordpress.org> Message-ID: <065.c7d9ff471965ead6cd52c8fd2a079974@wordpress.org> #2833: A link to ?Unresolved topics for this plugin? displayed to plugin contributors. ----------------------------+------------------ Reporter: lapzor | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Comment (by jcastaneda): Both theme and plugins have those views by default as well. [[Image(plugin-views.png)]] [[Image(theme-views.png)]] Both are images of when a user is not signed on. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2833#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 15:52:52 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 15:52:52 -0000 Subject: [wp-meta] [Making WordPress.org] #2835: Assign topic to specific plugin contributor In-Reply-To: <050.44e1cb2a6a38c93fdbc4e979b7a1f158@wordpress.org> References: <050.44e1cb2a6a38c93fdbc4e979b7a1f158@wordpress.org> Message-ID: <065.3530c8c60245aeacda6843970c4a6094@wordpress.org> #2835: Assign topic to specific plugin contributor ----------------------------+------------------------- Reporter: lapzor | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: Support Forums | Resolution: worksforme Keywords: | ----------------------------+------------------------- Changes (by lapzor): * status: new => closed * resolution: => worksforme Comment: Replying to [comment:2 SergeyBiryukov]: > Hi @lapzor, welcome to WordPress Meta Trac! Thanks for the ticket. > > It's already possible to ping a plugin contributor (or any other WordPress.org user) by a username and ask them to take a look at the topic. Thanks, That will work :) > Currently anyone can reply to any topic, what's the benefit of limiting that to a single person? That sounds more like a ticket system, forums generally don't work that way :) Yes of course. I did not mean that others shouldn't be able to reply. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2835#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 15:53:40 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 15:53:40 -0000 Subject: [wp-meta] [Making WordPress.org] #2834: Give plugin contributors the right to lock a topic, or... In-Reply-To: <050.e7617ae4910ad984e73d420dab714c0d@wordpress.org> References: <050.e7617ae4910ad984e73d420dab714c0d@wordpress.org> Message-ID: <065.7252fdb45f60ce2b46bd35a35b739470@wordpress.org> #2834: Give plugin contributors the right to lock a topic, or... ----------------------------+------------------------ Reporter: lapzor | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: Support Forums | Resolution: duplicate Keywords: | ----------------------------+------------------------ Comment (by lapzor): thanks. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2834#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 15:55:07 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 15:55:07 -0000 Subject: [wp-meta] =?utf-8?q?=5BMaking_WordPress=2Eorg=5D_=232833=3A_A_lin?= =?utf-8?q?k_to_=E2=80=9CUnresolved_topics_for_this_plugin=E2=80=9D_displa?= =?utf-8?q?yed_to_plugin_contributors=2E?= In-Reply-To: <050.6143ae76b38ea6ef0c123b092eb36926@wordpress.org> References: <050.6143ae76b38ea6ef0c123b092eb36926@wordpress.org> Message-ID: <065.02f9359de581a795af01649c21bc2ada@wordpress.org> #2833: A link to ?Unresolved topics for this plugin? displayed to plugin contributors. ----------------------------+------------------------- Reporter: lapzor | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: Support Forums | Resolution: worksforme Keywords: | ----------------------------+------------------------- Changes (by lapzor): * status: new => closed * resolution: => worksforme Comment: Ah, I now see that i've been clicking on the wrong link, showing me all unresolved topics on the whole forum. Thanks :) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2833#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 20 21:23:56 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 20 May 2017 21:23:56 -0000 Subject: [wp-meta] [Making WordPress.org] #2383: Add a meta field in the Sponsor CPT for Twitter handle In-Reply-To: <059.52fb31ba9390e59e798830d188b97820@wordpress.org> References: <059.52fb31ba9390e59e798830d188b97820@wordpress.org> Message-ID: <074.a2d84c7cb267748f98b169a5d29e0d2b@wordpress.org> #2383: Add a meta field in the Sponsor CPT for Twitter handle --------------------------------------+----------------------- Reporter: andreamiddleton | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: good-first-bug has-patch | --------------------------------------+----------------------- Changes (by chandrapatel): * keywords: good-first-bug needs-patch => good-first-bug has-patch Comment: HI @iandunn I've added `Twitter Handle:` meta field in Sponsor CPT. I've attached a patch. [https://meta.trac.wordpress.org/attachment/ticket/2383/2383.diff 2383.diff] Please check and let me know if it's fine. Thanks, -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2383#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sun May 21 13:51:02 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Sun, 21 May 2017 13:51:02 +0000 (UTC) Subject: [wp-meta] [5502] sites/trunk/wordpress.org/public_html/wp-content/plugins: Translate : Avoid PHP notices if a translation set doesn't exist. Message-ID: <20170521135102.3948B1080374@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170521/532d40bf/attachment-0001.html> From noreply at wordpress.org Sun May 21 14:20:50 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Sun, 21 May 2017 14:20:50 +0000 (UTC) Subject: [wp-meta] [5503] sites/trunk/wordpress.org/public_html/wp-content/plugins/ wporg-gp-routes/inc/routes/class-locale.php: Translate: Replace query for translation set slugs with a hardcoded list to fix performance issue. Message-ID: <20170521142050.9520B1080374@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170521/b70c0eb3/attachment.html> From noreply at wordpress.org Mon May 22 16:53:38 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 22 May 2017 16:53:38 +0000 (UTC) Subject: [wp-meta] [5504] sites/trunk: Trac: Link to the WordPress HackerOne program. Message-ID: <20170522165338.3395B1080409@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170522/7c5b2719/attachment.html> From noreply at wordpress.org Mon May 22 16:58:16 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Mon, 22 May 2017 16:58:16 +0000 (UTC) Subject: [wp-meta] [5505] sites/trunk/trac.wordpress.org/templates/site.html: Trac: Replace one more instance of the security@ email with a link to the WordPress HackerOne program. Message-ID: <20170522165816.E1E241080409@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170522/a28abaa2/attachment.html> From noreply at wordpress.org Mon May 22 20:18:11 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 22 May 2017 20:18:11 -0000 Subject: [wp-meta] [Making WordPress.org] #2383: Add a meta field in the Sponsor CPT for Twitter handle In-Reply-To: <059.52fb31ba9390e59e798830d188b97820@wordpress.org> References: <059.52fb31ba9390e59e798830d188b97820@wordpress.org> Message-ID: <074.10802341b7d1815b11562b8de6c7c380@wordpress.org> #2383: Add a meta field in the Sponsor CPT for Twitter handle --------------------------------------+----------------------- Reporter: andreamiddleton | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: good-first-bug has-patch | --------------------------------------+----------------------- Comment (by iandunn): That looks good, thanks! Eventually we'll also want to add a corresponding field to the `multi- event-sponsors` plugin, and copy the value from those global sponsors to the `wcpt` sponsor posts when new sites get created. [attachment:2383.diff] can be committed without that, though. We've got a backlog of patches to review and commit, but I've added this one to the list. Hoping to find some time soonish. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2383#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Mon May 22 21:09:14 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Mon, 22 May 2017 21:09:14 -0000 Subject: [wp-meta] [Making WordPress.org] #2820: Add Japanese meetups to event API In-Reply-To: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> References: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> Message-ID: <068.b93c1bbe4d0664f50a4ba7b65e50f99a@wordpress.org> #2820: Add Japanese meetups to event API -------------------------------------+----------------------- Reporter: mayukojpn | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: has-patch | -------------------------------------+----------------------- Comment (by coreymckrill): @mayukojpn I haven't been able to retrieve any events from the Doorkeeper API using either the URL format in the patch or the one in their [https://www.doorkeeperhq.com/developer/api API docs]. Example: https://api.doorkeeper.jp/events?group_id=2504&time=0,3m or https://api.doorkeeper.jp/groups/2504/events In the docs it says "API requests without authentication will fail", so I'm wondering if maybe you were able to get events because you were currently logged in with a Doorkeeper account, and I'm not? We may need to set up a WordPress.org Community Team account on Doorkeeper and get an API token to get this to work... cc @iandunn -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2820#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 04:50:28 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 04:50:28 -0000 Subject: [wp-meta] [Making WordPress.org] #2686: Plugin Search: Search should also take into account the number of ratings In-Reply-To: <051.6a8a8298224b7d93c0ff73de59c8a80c@wordpress.org> References: <051.6a8a8298224b7d93c0ff73de59c8a80c@wordpress.org> Message-ID: <066.3989118072a3003dbc9053ea35d2dd3b@wordpress.org> #2686: Plugin Search: Search should also take into account the number of ratings ------------------------------+------------------------------------------- Reporter: bfintal | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Comment (by bfintal): @gibrown Looks promising! -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2686#comment:12> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 07:41:08 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 07:41:08 -0000 Subject: [wp-meta] [Making WordPress.org] #2836: Plugin favorites no longer showing on main Plugin Direcotry page Message-ID: <051.43f189427900e3e173e246f713f14763@wordpress.org> #2836: Plugin favorites no longer showing on main Plugin Direcotry page ------------------------------+----------------- Reporter: ahortin | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Keywords: ------------------------------+----------------- Up until recently there was a link to your saved plugin favorites at the bottom of the main plugin directory page on WordPress.org. This link used to appear after the list of Featured & Popular plugins, but it no longer exists. This means that you can no longer get to your plugin favorites (when logged in), from the main plugin page. The only way to get to your favourites is by viewing your profile page, or by using one of the Featured/Popular links and then selecting the Favorites link. Can you please fix the plugin directory page so that this link is available as it was previously. Thanks. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2836> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 08:40:47 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 08:40:47 -0000 Subject: [wp-meta] [Making WordPress.org] #2836: Plugin favorites no longer showing on main Plugin Directory page (was: Plugin favorites no longer showing on main Plugin Direcotry page) In-Reply-To: <051.43f189427900e3e173e246f713f14763@wordpress.org> References: <051.43f189427900e3e173e246f713f14763@wordpress.org> Message-ID: <066.892d4ee61a1e904920f5dbda53dd81ca@wordpress.org> #2836: Plugin favorites no longer showing on main Plugin Directory page ------------------------------+------------------ Reporter: ahortin | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------ -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2836#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 08:49:14 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 08:49:14 -0000 Subject: [wp-meta] [Making WordPress.org] #2836: Plugin favorites no longer showing on main Plugin Directory page In-Reply-To: <051.43f189427900e3e173e246f713f14763@wordpress.org> References: <051.43f189427900e3e173e246f713f14763@wordpress.org> Message-ID: <066.4972f7d0b6e38d67b6b4901ced64a6c1@wordpress.org> #2836: Plugin favorites no longer showing on main Plugin Directory page ------------------------------+------------------------------------ Reporter: ahortin | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: needs-patch | ------------------------------+------------------------------------ Changes (by ocean90): * keywords: => needs-patch * milestone: => Plugin Directory v3.0 Comment: Broken since [5500]. The query on the front page isn't the main query so the custom query vars don't get applied. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2836#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 16:16:37 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 16:16:37 -0000 Subject: [wp-meta] [Making WordPress.org] #2837: Change the name of the forum "Plugins & Hacks" to "Plugins" Message-ID: <051.c114815ad2125dae8baef24415f3a6b7@wordpress.org> #2837: Change the name of the forum "Plugins & Hacks" to "Plugins" ---------------------+----------------- Reporter: Shelob9 | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: General | Keywords: ---------------------+----------------- Since most users probably think "hacks" relates to sites being hacked, not the precursor to plugins that was deprecated 10+ years ago and is removed from WordPress about 2 years ago, I propose that a better name for the forum for support with plugins and hacks would be better named "Plugins." I'm sure those users on WordPress 1.4 or earlier will figure it out. Related: https://core.trac.wordpress.org/changeset/34291 -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2837> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 16:21:26 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 16:21:26 -0000 Subject: [wp-meta] [Making WordPress.org] #2838: In WordPress.org notification matchers, show forum name. Message-ID: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> #2838: In WordPress.org notification matchers, show forum name. ---------------------+----------------- Reporter: Shelob9 | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: General | Keywords: ---------------------+----------------- When I get an email from WordPress.org matcher, it shows the top level forum, not the child forum. For example, this is an email I got because of the use of the word "caldera" but it's not from the Caldera Forms plugin support forum. I had to click on that to know it. [[Image(http://i.imgur.com/JtDUYKz.png)]] In my opinion, the fact that it is in one of the ~50k child forums of the Plugins and Hack forum is less useful then which child forum it is in. On WordPress.org, the breadcrumbs show `Support ? Plugin: Hustle - Pop-Ups, Slide-ins and Email Opt-ins ? Conflicts with Caldera forms` which would be a way more useful bit of information to put in the email. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2838> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 16:29:14 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 16:29:14 -0000 Subject: [wp-meta] [Making WordPress.org] #2837: Change the name of the forum "Plugins & Hacks" to "Plugins" In-Reply-To: <051.c114815ad2125dae8baef24415f3a6b7@wordpress.org> References: <051.c114815ad2125dae8baef24415f3a6b7@wordpress.org> Message-ID: <066.cc1fbab3948b6923b01cce9ec6e85cd7@wordpress.org> #2837: Change the name of the forum "Plugins & Hacks" to "Plugins" -------------------------+------------------ Reporter: Shelob9 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: | -------------------------+------------------ Changes (by Otto42): * type: defect => enhancement -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2837#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 16:29:24 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 16:29:24 -0000 Subject: [wp-meta] [Making WordPress.org] #2838: In WordPress.org notification matchers, show forum name. In-Reply-To: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> References: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> Message-ID: <066.e21b675a88d4cd2b13e8ba8c8e5a2996@wordpress.org> #2838: In WordPress.org notification matchers, show forum name. -------------------------+------------------ Reporter: Shelob9 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: | -------------------------+------------------ Changes (by Otto42): * type: defect => enhancement -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2838#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 18:01:28 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 18:01:28 -0000 Subject: [wp-meta] [Making WordPress.org] #596: Create plugin icons for all plugins In-Reply-To: <051.6d2fbeb076c9d5730e02db5deb4c01ec@wordpress.org> References: <051.6d2fbeb076c9d5730e02db5deb4c01ec@wordpress.org> Message-ID: <066.5303191a87a632973722640bf749fa77@wordpress.org> #596: Create plugin icons for all plugins -------------------------------------------------+------------------------- Reporter: iandunn | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: General | Resolution: Keywords: good-first-bug needs-ui dev- | feedback has-patch | -------------------------------------------------+------------------------- Comment (by karmatosed): @danieltj how is it going with this ticket? @alwaysbrightblue that would be ace to have you involved. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/596#comment:24> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 18:01:41 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 18:01:41 -0000 Subject: [wp-meta] [Making WordPress.org] #2815: Teams: Create Hosting Badge & Color In-Reply-To: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> References: <048.878d66cf011e90b02a6df1c7cd5ca68f@wordpress.org> Message-ID: <063.31f2157ab8fae45b2489ad0fc01e8eff@wordpress.org> #2815: Teams: Create Hosting Badge & Color -------------------------------------+--------------------- Reporter: mapk | Owner: Type: task | Status: closed Priority: high | Milestone: Component: Profiles | Resolution: fixed Keywords: 2nd-opinion ui-feedback | -------------------------------------+--------------------- Changes (by coreymckrill): * status: new => closed * resolution: => fixed Comment: Fixed with [dotorg13169] -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2815#comment:13> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 18:00:43 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 18:00:43 -0000 Subject: [wp-meta] [Making WordPress.org] #2813: Profiles: Add WP-CLI Badge In-Reply-To: <054.8af312384d284740d2f9848107f1b4bc@wordpress.org> References: <054.8af312384d284740d2f9848107f1b4bc@wordpress.org> Message-ID: <069.5a41099e247a12d5a9cab19718269342@wordpress.org> #2813: Profiles: Add WP-CLI Badge ------------------------+--------------------- Reporter: schlessera | Owner: Type: defect | Status: closed Priority: high | Milestone: Component: Profiles | Resolution: fixed Keywords: | ------------------------+--------------------- Changes (by coreymckrill): * status: new => closed * resolution: => fixed Comment: Fixed with [dotorg13168] -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2813#comment:8> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 18:04:28 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 18:04:28 -0000 Subject: [wp-meta] [Making WordPress.org] #1340: Update screenshot on wordpress.org front page In-Reply-To: <049.68b7cf5a29938f40626acc7e037f5c2a@wordpress.org> References: <049.68b7cf5a29938f40626acc7e037f5c2a@wordpress.org> Message-ID: <064.2d13720e87aaf13ffb4893fd030a5a5c@wordpress.org> #1340: Update screenshot on wordpress.org front page ----------------------+---------------------- Reporter: GaryJ | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: General | Resolution: invalid Keywords: needs-ui | ----------------------+---------------------- Changes (by karmatosed): * status: new => closed * resolution: => invalid Comment: Closing as the design has now changed. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1340#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 18:20:02 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 18:20:02 -0000 Subject: [wp-meta] [Making WordPress.org] #718: Increase Support Visibility with Orange In-Reply-To: <051.61a401c8ed63f81d912010103afb6165@wordpress.org> References: <051.61a401c8ed63f81d912010103afb6165@wordpress.org> Message-ID: <066.2e779aae7ce952af4bdbdca978c0284c@wordpress.org> #718: Increase Support Visibility with Orange ----------------------------------+------------------ Reporter: macmanx | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: needs-ui ui-feedback | ----------------------------------+------------------ Comment (by karmatosed): If there is data that we are causing people to get lost then +1 for making this more obvious. If thats not the case the I think not doing anything works well. @macmanx are you still finding this issue with the site changes? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/718#comment:15> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 18:32:03 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 18:32:03 -0000 Subject: [wp-meta] [Making WordPress.org] #718: Increase Support Visibility with Orange In-Reply-To: <051.61a401c8ed63f81d912010103afb6165@wordpress.org> References: <051.61a401c8ed63f81d912010103afb6165@wordpress.org> Message-ID: <066.697cf0e50d7db6dae74f1665f71fe343@wordpress.org> #718: Increase Support Visibility with Orange ----------------------------------+------------------ Reporter: macmanx | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: needs-ui ui-feedback | ----------------------------------+------------------ Comment (by macmanx): It's hard to say on that front @karmatosed As you noted, we don't really have any data. Anecdotally, the prior observation was made based on the amount of folks reaching out on IRC and even WordPress.com forums because they couldn't find the WordPress.org forums, as well as a number of "WordPress has no Support" blog posts and such that were going around. Since the re-design, incoming support topics seem to have decreased some, but the misdirection and statements of no support appear to have stopped. There's no data, so it's really impossible to say if that's related in any way. Leaving it as-is would probably be fine at this point. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/718#comment:16> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 20:10:38 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 20:10:38 -0000 Subject: [wp-meta] [Making WordPress.org] #718: Increase Support Visibility with Orange In-Reply-To: <051.61a401c8ed63f81d912010103afb6165@wordpress.org> References: <051.61a401c8ed63f81d912010103afb6165@wordpress.org> Message-ID: <066.50e59e899f926fc7250617257d183a23@wordpress.org> #718: Increase Support Visibility with Orange ----------------------------------+------------------------- Reporter: macmanx | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: General | Resolution: maybelater Keywords: needs-ui ui-feedback | ----------------------------------+------------------------- Changes (by karmatosed): * status: new => closed * resolution: => maybelater Comment: @macmanx ok, lets close this then. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/718#comment:17> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 20:36:07 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 20:36:07 -0000 Subject: [wp-meta] [Making WordPress.org] #2837: Change the name of the forum "Plugins & Hacks" to "Plugins" In-Reply-To: <051.c114815ad2125dae8baef24415f3a6b7@wordpress.org> References: <051.c114815ad2125dae8baef24415f3a6b7@wordpress.org> Message-ID: <066.ad187aa1e4266f0b81ec3e22b760ec78@wordpress.org> #2837: Change the name of the forum "Plugins & Hacks" to "Plugins" -------------------------+------------------ Reporter: Shelob9 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: | -------------------------+------------------ Comment (by Clorith): Where are you seeing any relation to this forum? We made it hidden last year with the forum upgrade (we can't actually outright remove it from existence, as it's the base location for all plugin support forums, but this shouldn't matter as no user will see it). -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2837#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 20:49:37 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 23 May 2017 20:49:37 +0000 (UTC) Subject: [wp-meta] [5506] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-plugins/page-developers.php: Plugin Directory: Update path for the example `readme.txt`. Message-ID: <20170523204937.32CC11080287@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170523/9e269712/attachment.html> From noreply at wordpress.org Tue May 23 20:52:58 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 20:52:58 -0000 Subject: [wp-meta] [Making WordPress.org] #2838: In WordPress.org notification matchers, show forum name. In-Reply-To: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> References: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> Message-ID: <066.d01d0467fbfa9d04a98acaa5b4ed1657@wordpress.org> #2838: In WordPress.org notification matchers, show forum name. -------------------------+------------------ Reporter: Shelob9 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: | -------------------------+------------------ Comment (by Otto42): > the fact that it is in one of the ~50k child forums of the Yeah... that's kind of a trick. We don't actually have 50k "child forums". They're all threads in one single forum. We're just showing you a "view" of that forum which only includes the relevant threads for the plugin in question. Not to say that the email could not be improved, but it's not as simple as that. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2838#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 22:21:02 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 22:21:02 -0000 Subject: [wp-meta] [Making WordPress.org] #2820: Add Japanese meetups to event API In-Reply-To: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> References: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> Message-ID: <068.07bbb2f4c9889625d62b08a61400adcc@wordpress.org> #2820: Add Japanese meetups to event API -------------------------------------+----------------------- Reporter: mayukojpn | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: has-patch | -------------------------------------+----------------------- Comment (by iandunn): Replying to [comment:3 coreymckrill]: > We may need to set up a WordPress.org Community Team account on Doorkeeper and get an API token to get this to work... That makes sense. Do you see any obstacles to doing that? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2820#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 22:21:53 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 22:21:53 -0000 Subject: [wp-meta] [Making WordPress.org] #2820: Add Japanese meetups to event API In-Reply-To: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> References: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> Message-ID: <068.08cd27547c3c118238285b27e88eb0ee@wordpress.org> #2820: Add Japanese meetups to event API -------------------------------------+----------------------- Reporter: mayukojpn | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: has-patch | -------------------------------------+----------------------- Comment (by coreymckrill): Update: I figured out how to get some events from the API. I signed up for a Doorkeeper account and got an API key, which allowed me to make authenticated requests. Anonymous requests are actually allowed also, but the request limit is very low, so if anyone else is making anonymous requests at the same time you might get locked out. I also discovered that of all the group IDs listed in the array, only '''Tokyo WordPress Mokumoku Club''' has any events. Is that the one that's part of the chapter program? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2820#comment:5> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 22:30:52 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 23 May 2017 22:30:52 -0000 Subject: [wp-meta] [Making WordPress.org] #2820: Add Japanese meetups to event API In-Reply-To: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> References: <053.bfd00b0115ededfbc66195b7baac9d69@wordpress.org> Message-ID: <068.6ca66774ca997d888b114ac098f7b192@wordpress.org> #2820: Add Japanese meetups to event API -------------------------------------+----------------------- Reporter: mayukojpn | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: has-patch | -------------------------------------+----------------------- Comment (by coreymckrill): > Do you see any obstacles to doing that? We can probably just change the name/email address for the account I already created when the time comes. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2820#comment:6> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 23 23:00:52 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 23 May 2017 23:00:52 +0000 (UTC) Subject: [wp-meta] [5507] sites/trunk/api.wordpress.org/public_html/dotorg/github-sync/ feature-plugins.sh: Feature Plugins Github Sync: Bump the property later so that the no-files-changed check will correctly abort the update. Message-ID: <20170523230052.9A9CA1080287@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170523/c227b7df/attachment.html> From noreply at wordpress.org Wed May 24 00:30:40 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 00:30:40 -0000 Subject: [wp-meta] [Making WordPress.org] #2016: Subscription themes/plugins emails should include the theme/plugin name in the title In-Reply-To: <050.021524746837b0ca69dccfe332a72de6@wordpress.org> References: <050.021524746837b0ca69dccfe332a72de6@wordpress.org> Message-ID: <065.f2ec54e72cf18af8556125d405815a68@wordpress.org> #2016: Subscription themes/plugins emails should include the theme/plugin name in the title ----------------------------+------------------ Reporter: netweb | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: needs-patch | ----------------------------+------------------ Comment (by netweb): Related: #2838 -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2016#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 00:30:45 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 00:30:45 -0000 Subject: [wp-meta] [Making WordPress.org] #2838: In WordPress.org notification matchers, show forum name. In-Reply-To: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> References: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> Message-ID: <066.718a43be37fd65ffefff87e4d9b2372b@wordpress.org> #2838: In WordPress.org notification matchers, show forum name. -------------------------+------------------ Reporter: Shelob9 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: | -------------------------+------------------ Comment (by netweb): Related: #2016 -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2838#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 07:02:49 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 07:02:49 -0000 Subject: [wp-meta] [Making WordPress.org] #2837: Change the name of the forum "Plugins & Hacks" to "Plugins" In-Reply-To: <051.c114815ad2125dae8baef24415f3a6b7@wordpress.org> References: <051.c114815ad2125dae8baef24415f3a6b7@wordpress.org> Message-ID: <066.f22252a176a5cea68f8c11455ac59334@wordpress.org> #2837: Change the name of the forum "Plugins & Hacks" to "Plugins" ----------------------------+------------------ Reporter: Shelob9 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Changes (by SergeyBiryukov): * component: General => Support Forums -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2837#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 07:04:04 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 07:04:04 -0000 Subject: [wp-meta] [Making WordPress.org] #2838: In WordPress.org notification matchers, show forum name. In-Reply-To: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> References: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> Message-ID: <066.fe3aa94a2dc3c654371f9e2d22146c75@wordpress.org> #2838: In WordPress.org notification matchers, show forum name. ----------------------------+------------------ Reporter: Shelob9 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Changes (by SergeyBiryukov): * component: General => Support Forums -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2838#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 07:04:27 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 07:04:27 -0000 Subject: [wp-meta] [Making WordPress.org] #2838: In WordPress.org notification matchers, show forum name. In-Reply-To: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> References: <051.c5734218ec0bff5d7449a4487f52a967@wordpress.org> Message-ID: <066.11c4c517d017f021d39b975165837450@wordpress.org> #2838: In WordPress.org notification matchers, show forum name. -------------------------+------------------ Reporter: Shelob9 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Profiles | Resolution: Keywords: | -------------------------+------------------ Changes (by SergeyBiryukov): * component: Support Forums => Profiles -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2838#comment:5> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 07:05:39 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 07:05:39 -0000 Subject: [wp-meta] [Making WordPress.org] #2837: Change the name of the forum "Plugins & Hacks" to "Plugins" In-Reply-To: <051.c114815ad2125dae8baef24415f3a6b7@wordpress.org> References: <051.c114815ad2125dae8baef24415f3a6b7@wordpress.org> Message-ID: <066.c8625fed667dc49171bdf6c54aa683c5@wordpress.org> #2837: Change the name of the forum "Plugins & Hacks" to "Plugins" ----------------------------+------------------ Reporter: Shelob9 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: | ----------------------------+------------------ Comment (by SergeyBiryukov): Replying to [comment:2 Clorith]: > Where are you seeing any relation to this forum? It's still visible in notification emails, see #2838. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2837#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 11:28:02 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 11:28:02 -0000 Subject: [wp-meta] [Making WordPress.org] #200: "Download WordPress" button in header feels like a submit button for the search bar In-Reply-To: <053.e2aa5c22e12dc6e33fcf254e331ed8f5@wordpress.org> References: <053.e2aa5c22e12dc6e33fcf254e331ed8f5@wordpress.org> Message-ID: <068.eaccf3b06e8d28799521aba6ccf4644a@wordpress.org> #200: "Download WordPress" button in header feels like a submit button for the search bar -------------------------+------------------ Reporter: melchoyce | Owner: Type: enhancement | Status: new Priority: low | Milestone: Component: General | Resolution: Keywords: ui-feedback | -------------------------+------------------ Comment (by karmatosed): How about we get some ideas for what this could be? With the new design does anyone have some suggestions? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/200#comment:17> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 11:33:04 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 11:33:04 -0000 Subject: [wp-meta] [Making WordPress.org] #1173: 'Showcase' Not Responsive In-Reply-To: <054.880cf034fd82ff428c7b28a381084582@wordpress.org> References: <054.880cf034fd82ff428c7b28a381084582@wordpress.org> Message-ID: <069.0baa0e109b9cd622152565b4b0199a56@wordpress.org> #1173: 'Showcase' Not Responsive ----------------------------------------------+------------------ Reporter: atomicjack | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: ui-feedback needs-patch needs-ui | ----------------------------------------------+------------------ Comment (by karmatosed): @danetroup are you still interested in working on this? I would love to see if we can at least get this responsive. We do not need to change the design I feel at this point, just make what we have responsive. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1173#comment:8> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 11:35:43 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 11:35:43 -0000 Subject: [wp-meta] [Making WordPress.org] #2137: Full Reviews no longer show when looking at ratings. In-Reply-To: <051.fa4d463ecf1a348962cd4cbdefff3124@wordpress.org> References: <051.fa4d463ecf1a348962cd4cbdefff3124@wordpress.org> Message-ID: <066.b2de551c4cedb08d502a4000931c89ec@wordpress.org> #2137: Full Reviews no longer show when looking at ratings. -------------------------------------+------------------ Reporter: jdailey | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: ui-feedback ux-feedback | -------------------------------------+------------------ Changes (by karmatosed): * component: General => Plugin Directory Comment: I assume you are talking about the plugin directory here? Going to change the component to reflect this, let me know if not the case. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2137#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 11:36:45 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 11:36:45 -0000 Subject: [wp-meta] [Making WordPress.org] #1887: Site title should be a visible link In-Reply-To: <051.838a7d28e811bc68c9d8e0018f8f9f19@wordpress.org> References: <051.838a7d28e811bc68c9d8e0018f8f9f19@wordpress.org> Message-ID: <066.27782f6953abad568ac357cf42f2a262@wordpress.org> #1887: Site title should be a visible link -------------------------+---------------------- Reporter: La Geek | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: General | Resolution: wontfix Keywords: ux-feedback | -------------------------+---------------------- Changes (by karmatosed): * status: new => closed * resolution: => wontfix Comment: I think we are ok saying this is a design decision at this point, so closing. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1887#comment:10> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 14:57:12 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 14:57:12 -0000 Subject: [wp-meta] [Making WordPress.org] #2389: Move TOC to allow more space for the content In-Reply-To: <058.d3990b3f32e882e3f0da18968ec49800@wordpress.org> References: <058.d3990b3f32e882e3f0da18968ec49800@wordpress.org> Message-ID: <073.1abfacf7326af5f397632880aa38bdaa@wordpress.org> #2389: Move TOC to allow more space for the content -------------------------------------+------------------ Reporter: grapplerulrich | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Handbooks | Resolution: Keywords: ui-feedback ux-feedback | -------------------------------------+------------------ Comment (by karmatosed): @mapk what is the current state on this? Is it being rolled out, complete and ok to close? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2389#comment:13> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 17:20:42 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 24 May 2017 17:20:42 +0000 (UTC) Subject: [wp-meta] [5508] sites/trunk/common/includes/slack/announce/config.php: Slack Announce: Add users to whitelist Message-ID: <20170524172042.625621080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170524/714b2305/attachment.html> From noreply at wordpress.org Wed May 24 18:25:21 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 18:25:21 -0000 Subject: [wp-meta] [Making WordPress.org] #2383: Add a meta field in the Sponsor CPT for Twitter handle In-Reply-To: <059.52fb31ba9390e59e798830d188b97820@wordpress.org> References: <059.52fb31ba9390e59e798830d188b97820@wordpress.org> Message-ID: <074.0dedfa6465bec5b31e8bae3074d69cc7@wordpress.org> #2383: Add a meta field in the Sponsor CPT for Twitter handle --------------------------------------+----------------------- Reporter: andreamiddleton | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: good-first-bug has-patch | --------------------------------------+----------------------- Comment (by coreymckrill): In [changeset:"5509"]: {{{ #!CommitTicketReference repository="" revision="5509" WordCamp: Add Twitter Handle field to Sponsor CPT This commit adds the field to the Sponsor CPT on individual WC sites. A corresponding field in the `multi-event-sponsors` plugin still needs to be added. Refs #2383 Props chandrapatel }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2383#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 18:28:52 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 18:28:52 -0000 Subject: [wp-meta] [Making WordPress.org] #2383: Add a meta field in the Sponsor CPT for Twitter handle In-Reply-To: <059.52fb31ba9390e59e798830d188b97820@wordpress.org> References: <059.52fb31ba9390e59e798830d188b97820@wordpress.org> Message-ID: <074.09959f2300091139df6ce88227e89d56@wordpress.org> #2383: Add a meta field in the Sponsor CPT for Twitter handle ----------------------------------------+----------------------- Reporter: andreamiddleton | Owner: iandunn Type: enhancement | Status: accepted Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: Keywords: good-first-bug needs-patch | ----------------------------------------+----------------------- Changes (by coreymckrill): * keywords: good-first-bug has-patch => good-first-bug needs-patch Old description: > It would be a nice convenience for organizers if we had a field for a > sponsor's twitter handle, so it?s easier to tweet a thank you. This would > be particularly helpful in the case of global sponsors, but I could see a > use case for local sponsors as well. It would not need to be a required > field. New description: It would be a nice convenience for organizers if we had a field for a sponsor's twitter handle, so it?s easier to tweet a thank you. This would be particularly helpful in the case of global sponsors, but I could see a use case for local sponsors as well. It would not need to be a required field. '''Update:''' the Twitter Handle field has been added for the Sponsor CPT. A similar field still needs to be added to the `multi-event-sponsor` plugin, though. See [#3]. -- -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2383#comment:5> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 18:25:21 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 24 May 2017 18:25:21 +0000 (UTC) Subject: [wp-meta] [5509] sites/trunk/wordcamp.org/public_html/wp-content/plugins/ wc-post-types: WordCamp: Add Twitter Handle field to Sponsor CPT Message-ID: <20170524182521.438DA1080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170524/44ae38f0/attachment-0001.html> From noreply at wordpress.org Wed May 24 18:45:38 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 24 May 2017 18:45:38 +0000 (UTC) Subject: [wp-meta] [5510] sites/trunk/wordcamp.org/public_html/wp-content/plugins/wcpt/ wcpt-wordcamp/wordcamp-new-site.php: WordCamp: Update sponsorship link in Sponsors page content stub Message-ID: <20170524184538.3C2901080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170524/6560f63a/attachment.html> From noreply at wordpress.org Wed May 24 18:45:38 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 18:45:38 -0000 Subject: [wp-meta] [Making WordPress.org] #2579: Broken Multi Event Sponsorship Packages In-Reply-To: <052.808c278eee725572fc95dd92da28818a@wordpress.org> References: <052.808c278eee725572fc95dd92da28818a@wordpress.org> Message-ID: <067.16595ef2b9f72d7ce96605ce09465613@wordpress.org> #2579: Broken Multi Event Sponsorship Packages -------------------------------------+---------------------- Reporter: edpittol | Owner: iandunn Type: defect | Status: closed Priority: low | Milestone: Component: WordCamp Site & Plugins | Resolution: fixed Keywords: has-patch | -------------------------------------+---------------------- Changes (by coreymckrill): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"5510"]: {{{ #!CommitTicketReference repository="" revision="5510" WordCamp: Update sponsorship link in Sponsors page content stub This change also removes the link from the `gettext` string and inserts it via `sprintf` instead. Fixes #2579 Props edpittol, SergeyBiryukov }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2579#comment:5> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 19:44:21 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 19:44:21 -0000 Subject: [wp-meta] [Making WordPress.org] #2389: Move TOC to allow more space for the content In-Reply-To: <058.d3990b3f32e882e3f0da18968ec49800@wordpress.org> References: <058.d3990b3f32e882e3f0da18968ec49800@wordpress.org> Message-ID: <073.9f5bca5e3a97dad190ef99d1241bfc28@wordpress.org> #2389: Move TOC to allow more space for the content -------------------------------------+------------------ Reporter: grapplerulrich | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Handbooks | Resolution: Keywords: ui-feedback ux-feedback | -------------------------------------+------------------ Comment (by mapk): @karmatosed I think we're good to go, but it hasn't been implemented across the board. For example, the use case in the ticket subscription hasn't adopted the new design. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2389#comment:14> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 20:49:03 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 20:49:03 -0000 Subject: [wp-meta] [Making WordPress.org] #2826: Plugin Directory: Data not syncing/updating properly from SVN commits In-Reply-To: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> References: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> Message-ID: <068.eb367e4d20aff4b908688b13dac13c49@wordpress.org> #2826: Plugin Directory: Data not syncing/updating properly from SVN commits ------------------------------+--------------------- Reporter: brianhogg | Owner: Type: defect | Status: closed Priority: highest omg bbq | Milestone: Component: Plugin Directory | Resolution: fixed Keywords: | ------------------------------+--------------------- Comment (by brianhogg): @Otto42 After pushing an update today to The Events Calendar Shortcode, sites were showing the update as available but when trying to update you get a "Update Failed: Plugin update failed." message. After about 15 minutes it cleared up and the updates went through. Is this a related issue or should I open a new ticket? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2826#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 20:51:40 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 20:51:40 -0000 Subject: [wp-meta] [Making WordPress.org] #2826: Plugin Directory: Data not syncing/updating properly from SVN commits In-Reply-To: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> References: <053.7dce10893493c7b9d3dc334c747258bd@wordpress.org> Message-ID: <068.4ebc5504dc64e2dcca787ee831ecc51d@wordpress.org> #2826: Plugin Directory: Data not syncing/updating properly from SVN commits ------------------------------+--------------------- Reporter: brianhogg | Owner: Type: defect | Status: closed Priority: highest omg bbq | Milestone: Component: Plugin Directory | Resolution: fixed Keywords: | ------------------------------+--------------------- Comment (by Otto42): @brianhogg It is a related issue, and we know the cause. It will be fixed soon, but in the meantime, that window you noticed tends to be much shorter, on the scale of 2-3 minutes or so. The window will disappear entirely when the underlying problem is corrected. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2826#comment:5> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 22:15:53 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 22:15:53 -0000 Subject: [wp-meta] [Making WordPress.org] #2832: Search result not working properly In-Reply-To: <057.58ee2aeb07cce0d41b56ca0079fe0edf@wordpress.org> References: <057.58ee2aeb07cce0d41b56ca0079fe0edf@wordpress.org> Message-ID: <072.1c9c3f23e1296c14fe0dd684399dcbfd@wordpress.org> #2832: Search result not working properly ---------------------------------------+------------------------ Reporter: karan.gadhavi | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Plugin Directory | Resolution: duplicate Keywords: 2nd-opinion needs-testing | ---------------------------------------+------------------------ Changes (by gibrown): * status: new => closed * resolution: => duplicate * milestone: Plugin Directory v3.0 => Comment: This is another good example where the ranking can be adjusted a little bit for #2642 Link to the full results: https://wordpress.org/plugins/search/Facebook+Events/ I'm going to mark this as a duplicate since that other ticket is tracking the same thing. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2832#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 22:41:12 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 24 May 2017 22:41:12 +0000 (UTC) Subject: [wp-meta] [5511] sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory/shortcodes/class-upload.php: Plugin directory: list author's pending plugins on Add page, to reduce duplicate uploads. Message-ID: <20170524224112.1E3DA1080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170524/8fee1ddc/attachment-0001.html> From noreply at wordpress.org Wed May 24 22:41:12 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 22:41:12 -0000 Subject: [wp-meta] [Making WordPress.org] #2594: Plugin Directory: List pending plugins on 'add' page In-Reply-To: <051.8682691f18de896a37086227c227a3cc@wordpress.org> References: <051.8682691f18de896a37086227c227a3cc@wordpress.org> Message-ID: <066.cba99dbc3e2d7261a7fcbe7770c832e1@wordpress.org> #2594: Plugin Directory: List pending plugins on 'add' page ----------------------------------------------+---------------------------- Reporter: Ipstenu | Owner: tellyworth Type: enhancement | Status: closed Priority: normal | Milestone: Plugin Component: Plugin Directory | Directory v3.0 Keywords: has-patch commit has-screenshots | Resolution: fixed ----------------------------------------------+---------------------------- Changes (by tellyworth): * owner: => tellyworth * status: new => closed * resolution: => fixed Comment: In [changeset:"5511"]: {{{ #!CommitTicketReference repository="" revision="5511" Plugin directory: list author's pending plugins on Add page, to reduce duplicate uploads. Fixes #2594 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2594#comment:10> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 22:50:47 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 24 May 2017 22:50:47 +0000 (UTC) Subject: [wp-meta] [5512] sites/trunk/wordcamp.org/public_html/wp-content/plugins: WordCamp: Add organizer reminder trigger for pre-planning status Message-ID: <20170524225047.CA14B1080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170524/cb5903da/attachment.html> From noreply at wordpress.org Wed May 24 22:50:48 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 22:50:48 -0000 Subject: [wp-meta] [Making WordPress.org] #2346: WordCamp pre-planning status trigger In-Reply-To: <048.4c1f8a874991d1961b287cb2cbd1b048@wordpress.org> References: <048.4c1f8a874991d1961b287cb2cbd1b048@wordpress.org> Message-ID: <063.298b23732119b9445c6530362e223d1b@wordpress.org> #2346: WordCamp pre-planning status trigger -------------------------------------+---------------------- Reporter: nvwd | Owner: iandunn Type: enhancement | Status: closed Priority: normal | Milestone: Component: WordCamp Site & Plugins | Resolution: fixed Keywords: has-patch | -------------------------------------+---------------------- Changes (by coreymckrill): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"5512"]: {{{ #!CommitTicketReference repository="" revision="5512" WordCamp: Add organizer reminder trigger for pre-planning status Fixes #2346 Props nvwd }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2346#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 23:38:13 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 24 May 2017 23:38:13 -0000 Subject: [wp-meta] [Making WordPress.org] #2839: Update Twemoji on CDN to 2.3.0 Message-ID: <057.ebf0d9b54fb832c6e642f24d69981158@wordpress.org> #2839: Update Twemoji on CDN to 2.3.0 ---------------------------+----------------- Reporter: peterwilsoncc | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: General | Keywords: ---------------------------+----------------- Twemoji 2.3.0 was released overnight to support Emoji 5 Diff https://github.com/twitter/twemoji/compare/v2.2.5...v2.3.0 This includes modifications to existing emoji so will require a new directory on the CDN. Related core ticket https://core.trac.wordpress.org/ticket/40858 -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2839> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 24 23:42:00 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 24 May 2017 23:42:00 +0000 (UTC) Subject: [wp-meta] [5513] sites/trunk/wordcamp.org/public_html/wp-content/plugins: WordCamp: Remove non-functional organizer reminder trigger Message-ID: <20170524234200.BCEB21080292@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170524/0c660512/attachment-0001.html> From noreply at wordpress.org Thu May 25 00:23:54 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 25 May 2017 00:23:54 +0000 (UTC) Subject: [wp-meta] [5514] sites/trunk/common/includes/slack/announce/config.php: Slack: Give WCEU Happiness Bar Wranglers announce in their channel. Message-ID: <20170525002354.940A010805A0@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170525/92628ac7/attachment.html> From noreply at wordpress.org Thu May 25 01:11:00 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 25 May 2017 01:11:00 +0000 (UTC) Subject: [wp-meta] [5515] sites/trunk/trac.wordpress.org/templates/core/site-specific.html: Trac: Add the focus leads as committers, and tidy up some old titles. Message-ID: <20170525011100.7EDDD10805A0@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170525/1e7d24f2/attachment.html> From noreply at wordpress.org Thu May 25 01:28:33 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 01:28:33 -0000 Subject: [wp-meta] [Making WordPress.org] #2839: Update Twemoji on CDN to 2.3.0 In-Reply-To: <057.ebf0d9b54fb832c6e642f24d69981158@wordpress.org> References: <057.ebf0d9b54fb832c6e642f24d69981158@wordpress.org> Message-ID: <072.d19b81ebd308ecb89f366ee0ce005150@wordpress.org> #2839: Update Twemoji on CDN to 2.3.0 ---------------------------+--------------------- Reporter: peterwilsoncc | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: General | Resolution: Keywords: | ---------------------------+--------------------- Changes (by Otto42): * status: new => closed * type: defect => enhancement Comment: We don't really need a separate meta ticket for this, I feel. The existing core ticket to track the changes is fine, since it needs to be synced with core there anyway. One problem, one ticket. Marking as duplicate. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2839#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 02:27:07 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 25 May 2017 02:27:07 +0000 (UTC) Subject: [wp-meta] [5516] sites/trunk/common/includes/slack/announce/config.php: Slack: Revert [5514], because private channels don't need to be whitelisted. Message-ID: <20170525022708.06DF310805A0@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170525/3994772f/attachment-0001.html> From noreply at wordpress.org Thu May 25 11:10:02 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 11:10:02 -0000 Subject: [wp-meta] [Making WordPress.org] #2788: Plugin Directory: Clarify language for submission errors (was: Plugin Direction: Clarify language for submission errors) In-Reply-To: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> References: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> Message-ID: <066.e598dfe55d3f974e69bbec4a8d785420@wordpress.org> #2788: Plugin Directory: Clarify language for submission errors ------------------------------+------------------------- Reporter: Ipstenu | Owner: tellyworth Type: enhancement | Status: reopened Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: needs-patch | ------------------------------+------------------------- -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2788#comment:5> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 11:50:24 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 11:50:24 -0000 Subject: [wp-meta] [Making WordPress.org] #2137: Full Reviews no longer show when looking at ratings. In-Reply-To: <051.fa4d463ecf1a348962cd4cbdefff3124@wordpress.org> References: <051.fa4d463ecf1a348962cd4cbdefff3124@wordpress.org> Message-ID: <066.787dffb3161c76928a3f9ce0300ddc14@wordpress.org> #2137: Full Reviews no longer show when looking at ratings. -------------------------------------+------------------ Reporter: jdailey | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: ui-feedback ux-feedback | -------------------------------------+------------------ Changes (by SergeyBiryukov): * component: Plugin Directory => Support Forums Comment: It's about the Support Forums theme. The old one used to show review text in general list: [attachment:2137.PNG], the new one doesn't: [attachment:2137.2.PNG]. That said, the new plugin directory currently displays the latest reviews on the plugin page: [attachment:2137.3.PNG], although that might be changed in #2632. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2137#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 12:04:41 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 12:04:41 -0000 Subject: [wp-meta] [Making WordPress.org] #2677: Plugin Directory: Admin email subjects to plugin author (s) improvements In-Reply-To: <051.76e30163c28c8e10b716b6642fdc91d1@wordpress.org> References: <051.76e30163c28c8e10b716b6642fdc91d1@wordpress.org> Message-ID: <066.05595a7bda691e4dea630fc3d0694fef@wordpress.org> #2677: Plugin Directory: Admin email subjects to plugin author (s) improvements ------------------------------+------------------------------------ Reporter: Ipstenu | Owner: tellyworth Type: enhancement | Status: reopened Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch commit | ------------------------------+------------------------------------ Changes (by SergeyBiryukov): * milestone: => Plugin Directory v3.0 Comment: [attachment:2677.4.diff] switches to Yoda conditions, as per WP coding standards and for consistency with the check a few lines above. Moving to v3.0, as the ticket already has a commit that just needs a follow-up. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2677#comment:5> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 12:19:55 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 12:19:55 -0000 Subject: [wp-meta] [Making WordPress.org] #2788: Plugin Directory: Clarify language for submission errors In-Reply-To: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> References: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> Message-ID: <066.c410a2e10be321fa0bc288a1436e177b@wordpress.org> #2788: Plugin Directory: Clarify language for submission errors ------------------------------+------------------------------------ Reporter: Ipstenu | Owner: tellyworth Type: enhancement | Status: reopened Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------ Changes (by SergeyBiryukov): * keywords: needs-patch => has-patch * milestone: => Plugin Directory v3.0 Comment: [attachment:2788.4.diff] switches the email address to a placeholder and updates translator comments, as per comment:2. Moving to v3.0, as the ticket already has a commit that just needs a follow-up. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2788#comment:6> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 12:55:52 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 12:55:52 -0000 Subject: [wp-meta] [Making WordPress.org] #2830: Plugin Directory: Include slug in submission emails In-Reply-To: <051.980ca4c7bb6bb49acc9857d3105e0019@wordpress.org> References: <051.980ca4c7bb6bb49acc9857d3105e0019@wordpress.org> Message-ID: <066.66deb491ce281193e1337cd1a3f04c25@wordpress.org> #2830: Plugin Directory: Include slug in submission emails ------------------------------+------------------ Reporter: Ipstenu | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------ Comment (by SergeyBiryukov): [attachment:2830.2.diff] updates translator comments. [attachment:2830.3.diff] is a combined patch with the changes from #2788, as they have some overlap. Whichever one gets committed first, should fix the other one as well :) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2830#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 12:56:10 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 12:56:10 -0000 Subject: [wp-meta] [Making WordPress.org] #2788: Plugin Directory: Clarify language for submission errors In-Reply-To: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> References: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> Message-ID: <066.b0aa0f03c93dff2f0177a7c4d6e2b166@wordpress.org> #2788: Plugin Directory: Clarify language for submission errors ------------------------------+------------------------------------ Reporter: Ipstenu | Owner: tellyworth Type: enhancement | Status: reopened Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------ Comment (by SergeyBiryukov): [attachment:2788.5.diff] is a combined patch with the changes from #2830, as they have some overlap. Whichever one gets committed first, should fix the other one as well :) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2788#comment:7> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 13:14:58 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 13:14:58 -0000 Subject: [wp-meta] [Making WordPress.org] #2618: Plugin Directory: Translation needed banner omits language In-Reply-To: <051.eed73691dd5ba0b981c0645fe16da796@wordpress.org> References: <051.eed73691dd5ba0b981c0645fe16da796@wordpress.org> Message-ID: <066.60ebc2d6ce860cf1f0cf7232876f8775@wordpress.org> #2618: Plugin Directory: Translation needed banner omits language ------------------------------+------------------------------------------- Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------------- Comment (by SergeyBiryukov): @ocean90: Anything I can do to help move [attachment:2618.2.patch] forward? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2618#comment:8> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 13:15:31 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 13:15:31 -0000 Subject: [wp-meta] [Making WordPress.org] #2781: Plugin Directory: Add translator comments for placeholders in Stats Report tool In-Reply-To: <058.03697759c32f7f3c720db10da4f5a581@wordpress.org> References: <058.03697759c32f7f3c720db10da4f5a581@wordpress.org> Message-ID: <073.c936f0c22d13e1f8bd0e5d8b1bcb56d6@wordpress.org> #2781: Plugin Directory: Add translator comments for placeholders in Stats Report tool ------------------------------+------------------ Reporter: SergeyBiryukov | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------ Comment (by SergeyBiryukov): @ocean90: Anything I can do to help move [attachment:2781.patch] forward? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2781#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 13:23:01 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 13:23:01 -0000 Subject: [wp-meta] [Making WordPress.org] #2590: Enhance compatibility with per forum moderators In-Reply-To: <051.ef2c0624040c63d1e71b94d15700a274@wordpress.org> References: <051.ef2c0624040c63d1e71b94d15700a274@wordpress.org> Message-ID: <066.fe965a7b0d994e071b4de1e18bf0771a@wordpress.org> #2590: Enhance compatibility with per forum moderators ------------------------------+------------------ Reporter: ocean90 | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Support Forums | Resolution: Keywords: has-patch commit | ------------------------------+------------------ Comment (by SergeyBiryukov): @ocean90: Anything I can do to help move [attachment:2590.3.diff] forward? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2590#comment:8> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 16:32:09 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 16:32:09 -0000 Subject: [wp-meta] [Making WordPress.org] #2840: Abuse of popular list due to active installs count Message-ID: <057.09bf642953cbca24bb8745640714e0dc@wordpress.org> #2840: Abuse of popular list due to active installs count -----------------------------+----------------- Reporter: thinkupthemes | Owner: Type: defect | Status: new Priority: low | Milestone: Component: Theme Directory | Keywords: -----------------------------+----------------- There is possible abuse of the popular list by theme authors due to how active installs are counted. The popular theme list takes account of the active installs count based on the number of active installs over the past 2 weeks (I believe). Authors are able to abuse this submitting themes which have the same name as themes distributed elsewhere. It appears this issue is not best managed by the theme review team on a case by case basis due to the subjective nature of the issue. Having a check in place to ensure that the theme being counted when ranking is that which was distributed from .org, as opposed to some 3rd party platform will help combat this issue. A previous ticket was raised for this similar issue, however was subsequently closed: https://meta.trac.wordpress.org/ticket/2114 Thanks. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2840> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 16:43:53 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 16:43:53 -0000 Subject: [wp-meta] [Making WordPress.org] #2840: Abuse of popular list due to active installs count In-Reply-To: <057.09bf642953cbca24bb8745640714e0dc@wordpress.org> References: <057.09bf642953cbca24bb8745640714e0dc@wordpress.org> Message-ID: <072.360acc040dd464f314b3a0db4f6b8678@wordpress.org> #2840: Abuse of popular list due to active installs count -----------------------------+------------------------ Reporter: thinkupthemes | Owner: Type: defect | Status: closed Priority: low | Milestone: Component: Theme Directory | Resolution: duplicate Keywords: | -----------------------------+------------------------ Changes (by ocean90): * status: new => closed * resolution: => duplicate Comment: #2114 is still open. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2840#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 17:05:22 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 17:05:22 -0000 Subject: [wp-meta] [Making WordPress.org] #2114: Possible abuse on popular themes list based on active installs In-Reply-To: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org> References: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org> Message-ID: <066.2a3220a18da616afd53730334f84a4c6@wordpress.org> #2114: Possible abuse on popular themes list based on active installs -----------------------------+------------------ Reporter: acosmin | Owner: Type: defect | Status: new Priority: low | Milestone: Component: Theme Directory | Resolution: Keywords: close | -----------------------------+------------------ Comment (by MH Themes): Regarding the popular list issue like pointed out by @thinkupthemes in ticket #2840, wouldn't it already help if the time parameter in the algorithm would be adjusted? At the moment new themes will appear on the popular list after 2 weeks. You could for example adjust this to 3 months, that way it would be much harder to game the system because while it's quite easy to get 2-3k active installs, it's much harder to get 10-20k. Usually after 3 months most of the new themes with only 2-3k active installs rank already much lower because they fail to attract more users. So if you adjust the algorithm from 2 weeks to 3 months, that would possibly prevent new themes with only 2-3k active installs to appear in the top spots on the popular list right after release. If these themes really become popular and achieve 10-20k active installs or more, then they will rank accordingly anyway. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2114#comment:14> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 17:45:35 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 17:45:35 -0000 Subject: [wp-meta] [Making WordPress.org] #2389: Move TOC to allow more space for the content In-Reply-To: <058.d3990b3f32e882e3f0da18968ec49800@wordpress.org> References: <058.d3990b3f32e882e3f0da18968ec49800@wordpress.org> Message-ID: <073.c7fc523a9c5367118a718ab79ce594a1@wordpress.org> #2389: Move TOC to allow more space for the content -------------------------------------+------------------ Reporter: grapplerulrich | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Handbooks | Resolution: Keywords: ui-feedback ux-feedback | -------------------------------------+------------------ Comment (by karmatosed): @mapk cool...so how should we go about doing that? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2389#comment:15> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 17:58:32 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 17:58:32 -0000 Subject: [wp-meta] [Making WordPress.org] #2389: Move TOC to allow more space for the content In-Reply-To: <058.d3990b3f32e882e3f0da18968ec49800@wordpress.org> References: <058.d3990b3f32e882e3f0da18968ec49800@wordpress.org> Message-ID: <073.81073c05648061dd8d928632cdcb9474@wordpress.org> #2389: Move TOC to allow more space for the content -------------------------------------+------------------ Reporter: grapplerulrich | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Handbooks | Resolution: Keywords: ui-feedback ux-feedback | -------------------------------------+------------------ Comment (by mapk): Replying to [comment:15 karmatosed]: > @mapk cool...so how should we go about doing that? I'm really not sure. Either @samuelsidler helped with that, or the team contributors did. Maybe @pento or @coffee2code might have an idea? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2389#comment:16> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 18:05:11 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 25 May 2017 18:05:11 +0000 (UTC) Subject: [wp-meta] [5517] sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/ security.php: Security: Send `X-Frame-Origins` on the front end to mitigate clickjacking Message-ID: <20170525180511.F41501080287@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170525/8abd5de5/attachment.html> From noreply at wordpress.org Thu May 25 19:36:19 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Thu, 25 May 2017 19:36:19 +0000 (UTC) Subject: [wp-meta] [5518] sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/ wcorg-misc.php: WordCamp: Load `wordcamporg` text domain based on user locale Message-ID: <20170525193619.2DB511080287@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170525/e45978ff/attachment.html> From noreply at wordpress.org Thu May 25 20:39:45 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 20:39:45 -0000 Subject: [wp-meta] [Making WordPress.org] #2389: Move TOC to allow more space for the content In-Reply-To: <058.d3990b3f32e882e3f0da18968ec49800@wordpress.org> References: <058.d3990b3f32e882e3f0da18968ec49800@wordpress.org> Message-ID: <073.991bf0d65bcd33768c3a74c4197ed34b@wordpress.org> #2389: Move TOC to allow more space for the content -------------------------------------+------------------ Reporter: grapplerulrich | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Handbooks | Resolution: Keywords: ui-feedback ux-feedback | -------------------------------------+------------------ Comment (by samuelsidler): Looks like we need a patch for devhub. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2389#comment:17> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 22:08:07 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 22:08:07 -0000 Subject: [wp-meta] [Making WordPress.org] #2836: Plugin favorites no longer showing on main Plugin Directory page In-Reply-To: <051.43f189427900e3e173e246f713f14763@wordpress.org> References: <051.43f189427900e3e173e246f713f14763@wordpress.org> Message-ID: <066.8d41ac3025b98bb68f5324fb9175c908@wordpress.org> #2836: Plugin favorites no longer showing on main Plugin Directory page ------------------------------+------------------------------------ Reporter: ahortin | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------ Changes (by SergeyBiryukov): * keywords: needs-patch => has-patch Comment: [attachment:2836.patch] replaces [5500] with a more targeted fix. Double-checked to make sure it doesn't introduces any regressions in #2594 or #2787. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2836#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 23:24:16 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 23:24:16 -0000 Subject: [wp-meta] [Making WordPress.org] #2788: Plugin Directory: Clarify language for submission errors In-Reply-To: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> References: <051.7d61c35a1f4f8676961cb91dadfdf74f@wordpress.org> Message-ID: <066.d1c24e770bc7f73c273af63c1a004ba6@wordpress.org> #2788: Plugin Directory: Clarify language for submission errors ------------------------------+------------------------------------ Reporter: Ipstenu | Owner: tellyworth Type: enhancement | Status: reopened Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------ Comment (by SergeyBiryukov): [attachment:2788.6.diff] is the same as [attachment:2788.5.diff], but with raw email address converted to a `mailto:` link for better UX. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2788#comment:8> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 23:25:36 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 23:25:36 -0000 Subject: [wp-meta] [Making WordPress.org] #2830: Plugin Directory: Include slug in submission emails In-Reply-To: <051.980ca4c7bb6bb49acc9857d3105e0019@wordpress.org> References: <051.980ca4c7bb6bb49acc9857d3105e0019@wordpress.org> Message-ID: <066.0eac630f669726e9b6d4390c997263af@wordpress.org> #2830: Plugin Directory: Include slug in submission emails ------------------------------+------------------ Reporter: Ipstenu | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------ Comment (by SergeyBiryukov): [attachment:2830.4.diff] is the same as [attachment:2830.3.diff], but with raw email address converted to a `mailto:` link for better UX. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2830#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Thu May 25 23:51:22 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Thu, 25 May 2017 23:51:22 -0000 Subject: [wp-meta] [Making WordPress.org] #2830: Plugin Directory: Include slug in submission emails In-Reply-To: <051.980ca4c7bb6bb49acc9857d3105e0019@wordpress.org> References: <051.980ca4c7bb6bb49acc9857d3105e0019@wordpress.org> Message-ID: <066.24703561bcac40a67312f59163c6a0aa@wordpress.org> #2830: Plugin Directory: Include slug in submission emails ------------------------------+------------------ Reporter: Ipstenu | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------ Comment (by SergeyBiryukov): The new message looks like a wall of text: [attachment:2830.PNG]. [attachment:2830.5.diff] splits it into several paragraphs to make it more readable: [attachment:2830.paragraphs.PNG]. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2830#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 00:28:32 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 00:28:32 -0000 Subject: [wp-meta] [Making WordPress.org] #2821: Plugin Directory: Plugin slug should be Latin Characters Only In-Reply-To: <051.25e027265662218e64083f79ba18e777@wordpress.org> References: <051.25e027265662218e64083f79ba18e777@wordpress.org> Message-ID: <066.7934863b69a1d9c0f6b828cc6feaeec4@wordpress.org> #2821: Plugin Directory: Plugin slug should be Latin Characters Only ------------------------------+------------------ Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------ Changes (by SergeyBiryukov): * keywords: needs-patch => has-patch Comment: [attachment:2821.patch] replaces `sanitize_title_with_dashes()` with `sanitize_title()`, which includes `remove_accents()`. This doesn't cover Cyrillic/Arabic/Hebrew/Japanese characters ? do we need to block those as well, or removing accents would be good enough for now? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2821#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 00:37:03 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Fri, 26 May 2017 00:37:03 +0000 (UTC) Subject: [wp-meta] [5519] sites/trunk/trac.wordpress.org/templates/core/site-specific.html: Trac: Add aaroncampbell's long overdue Core Committer badge. Message-ID: <20170526003703.68C4F108053D@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170526/99760c0c/attachment.html> From noreply at wordpress.org Fri May 26 01:03:55 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 01:03:55 -0000 Subject: [wp-meta] [Making WordPress.org] #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ In-Reply-To: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> References: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> Message-ID: <065.0a1bcdfe6a8f2ada8419e6bc66511b1e@wordpress.org> #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ ----------------------------------------+----------------------- Reporter: netweb | Owner: iandunn Type: enhancement | Status: reopened Priority: low | Milestone: Component: General | Resolution: Keywords: needs-patch good-first-bug | ----------------------------------------+----------------------- Comment (by coreymckrill): > change the SVN URLs to be wrapped in code blocks so they are also easily cut & pastable How about something like the above? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1103#comment:21> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 01:16:22 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 01:16:22 -0000 Subject: [wp-meta] [Making WordPress.org] #2800: Plugin Directory: Ask for confirmation before removing someone as a committer In-Reply-To: <054.334261ed8da287672092be0c6c8fe2d4@wordpress.org> References: <054.334261ed8da287672092be0c6c8fe2d4@wordpress.org> Message-ID: <069.29a1740a4f563b5840c89cfc5b71ee7d@wordpress.org> #2800: Plugin Directory: Ask for confirmation before removing someone as a committer ------------------------------+------------------ Reporter: Nikschavan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------ Comment (by SergeyBiryukov): [attachment:2800.2.diff] uses an existing string from [source:sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin- directory/admin/class-customizations.php?rev=5335&marks=114#L105 Customizations::enqueue_assets()], which already has this confirmation when removing a committer on Edit Plugin page in the admin. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2800#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 10:04:05 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 10:04:05 -0000 Subject: [wp-meta] [Making WordPress.org] #2114: Possible abuse on popular themes list based on active installs In-Reply-To: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org> References: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org> Message-ID: <066.4bd9256fb58ca2afa26d223bf691210f@wordpress.org> #2114: Possible abuse on popular themes list based on active installs -----------------------------+------------------ Reporter: acosmin | Owner: Type: defect | Status: new Priority: low | Milestone: Component: Theme Directory | Resolution: Keywords: close | -----------------------------+------------------ Comment (by ThemeZee): Adding new themes to the popular list not until after three months is a disadvantage for all new themes, not just the ones with naming conflicts and gaming the system. Right now it is only a great advantage for new themes if they already have active installs before going live. It does not matter if these come from a different theme with the same name or from an existing user base. I would therefore measure the growth of active installs, not the total amount, as @ionutn said: - Save the initial active install count when theme gets live - Calculate active installs from day two with the difference of initial and current active installs -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2114#comment:15> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 10:12:15 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 10:12:15 -0000 Subject: [wp-meta] [Making WordPress.org] #2114: Possible abuse on popular themes list based on active installs In-Reply-To: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org> References: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org> Message-ID: <066.c1c0378e5487da943667a6a517857452@wordpress.org> #2114: Possible abuse on popular themes list based on active installs -----------------------------+------------------ Reporter: acosmin | Owner: Type: defect | Status: new Priority: low | Milestone: Component: Theme Directory | Resolution: Keywords: close | -----------------------------+------------------ Comment (by MH Themes): In general I think it's inappropriate to rank brand-new themes with a bunch of active installs (2-3k) in the ''Top 10-20'' on the popular list. These are not popular themes, they are trending, if at all. But users who don't know about these issues may think these themes are the best what .org has to offer and start using these themes even more which will keep these new themes high in the popular list based on a flaw in the algorithm. It's a self-fulfilling prophecy. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2114#comment:16> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 13:43:32 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 13:43:32 -0000 Subject: [wp-meta] [Making WordPress.org] #2700: Plugin Directory: Improve quality of automated emails and messages for submissions In-Reply-To: <051.597732bb57c7e553445129eb5c2ae020@wordpress.org> References: <051.597732bb57c7e553445129eb5c2ae020@wordpress.org> Message-ID: <066.f760cefc5b5c8aed140f62f800c3727b@wordpress.org> #2700: Plugin Directory: Improve quality of automated emails and messages for submissions -------------------------------------+------------------------------------ Reporter: Ipstenu | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch needs-refresh | -------------------------------------+------------------------------------ Changes (by SergeyBiryukov): * keywords: has-patch commit => has-patch needs-refresh Comment: Needs a refresh after [5471], but there's also some overlap with #2788 and #2830, so I guess I'd wait for those tickets to be committed rather than refresh several times. Seeing simple text changes like this taking weeks to commit is not exactly encouraging, luckily there's plenty of other tickets to work on in the meantime :) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2700#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 14:52:30 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 14:52:30 -0000 Subject: [wp-meta] [Making WordPress.org] #2796: Plugin Directory Admin: Limit State Switching for Plugin Statuses In-Reply-To: <051.ad8639951baef0ece119c495143919d3@wordpress.org> References: <051.ad8639951baef0ece119c495143919d3@wordpress.org> Message-ID: <066.d4abdaad39f792e7406828fb799f9aa4@wordpress.org> #2796: Plugin Directory Admin: Limit State Switching for Plugin Statuses ------------------------------+------------------ Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------ Changes (by SergeyBiryukov): * keywords: => has-patch Comment: [attachment:2796.patch] implements the described flow, including Rejected ? Pending. This first pass only works on Edit Plugin page, and doesn't cover the Status dropdown in Quick Edit (haven't found a non-hacky way to replace it yet). Maybe Quick Edit should be disabled for plugins altogether? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2796#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 15:37:59 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 15:37:59 -0000 Subject: [wp-meta] [Making WordPress.org] #2821: Plugin Directory: Plugin slug should be Latin Characters Only In-Reply-To: <051.25e027265662218e64083f79ba18e777@wordpress.org> References: <051.25e027265662218e64083f79ba18e777@wordpress.org> Message-ID: <066.2c2512f8761701931ffcf577e88d4039@wordpress.org> #2821: Plugin Directory: Plugin slug should be Latin Characters Only ------------------------------+------------------ Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------ Comment (by Ipstenu): We need to block those too :( It does weird things if we use non ... boring English (I'm sleepy and I can't remember the right word for non- accented English characters) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2821#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 15:39:15 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 15:39:15 -0000 Subject: [wp-meta] [Making WordPress.org] #2796: Plugin Directory Admin: Limit State Switching for Plugin Statuses In-Reply-To: <051.ad8639951baef0ece119c495143919d3@wordpress.org> References: <051.ad8639951baef0ece119c495143919d3@wordpress.org> Message-ID: <066.9afa18d09f40296233530018642b3c67@wordpress.org> #2796: Plugin Directory Admin: Limit State Switching for Plugin Statuses ------------------------------+------------------ Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------ Comment (by Ipstenu): > Maybe Quick Edit should be disabled for plugins altogether? That's fine. We don't use it and while I wish we could sometimes, since we've managed to mitigate the whole double-submission dance, it's not a requirement at all. tl;dr We can totally disable quick-edit for plugins. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2796#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 15:54:21 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 15:54:21 -0000 Subject: [wp-meta] [Making WordPress.org] #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ In-Reply-To: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> References: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> Message-ID: <065.ee9e40b7a0a46ccbcc869bda975f9850@wordpress.org> #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ ----------------------------------------+----------------------- Reporter: netweb | Owner: iandunn Type: enhancement | Status: reopened Priority: low | Milestone: Component: General | Resolution: Keywords: needs-patch good-first-bug | ----------------------------------------+----------------------- Comment (by iandunn): That looks pretty good to me. What does the `dashicons-external` link to? Does it open in new tab? We might want to consider adding the checkout/clone commands, like: > * Subversion: `svn checkout https://core.svn.wordpress.org/trunk` > * Git: `git clone git://core.git.wordpress.org/` That might make it easier for users who aren't familiar with SVN/Git at all, but it could also confuse people who use GUI clients, since they'd need to parse out the URL. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1103#comment:22> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 16:30:42 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 16:30:42 -0000 Subject: [wp-meta] [Making WordPress.org] #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ In-Reply-To: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> References: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> Message-ID: <065.32fd8939b790f7913f20ec6f8d2607d7@wordpress.org> #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ ----------------------------------------+----------------------- Reporter: netweb | Owner: iandunn Type: enhancement | Status: reopened Priority: low | Milestone: Component: General | Resolution: Keywords: needs-patch good-first-bug | ----------------------------------------+----------------------- Comment (by coreymckrill): > What does the `dashicons-external` link to? Does it open in new tab? It links to the SVN repo, not in a new tab. I included it because in the previous iteration the SVN URL was a link instead of copiable text. I would be fine removing it, but I do think it's useful to show people that they can look through the repo on their browser rather than having to do a checkout. > We might want to consider adding the checkout/clone commands In this case, I would probably prefer to leave them as just the URLs for simplicity. People who want to know what the repo URLs are need to have a basic level of understanding about SVN/Git in order to do anything with them anyway, so they should know which commands to use. For the same reason, my preference would be to leave off `/trunk`. Branches and tags are useful for some people, and checking out the whole repo doesn't take ''that'' long (unlike the Plugins repo). -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1103#comment:23> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 19:20:14 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 19:20:14 -0000 Subject: [wp-meta] [Making WordPress.org] #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ In-Reply-To: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> References: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> Message-ID: <065.55cb8d4a38dc2f32fa45ef8357554c46@wordpress.org> #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ ----------------------------------------+----------------------- Reporter: netweb | Owner: iandunn Type: enhancement | Status: reopened Priority: low | Milestone: Component: General | Resolution: Keywords: needs-patch good-first-bug | ----------------------------------------+----------------------- Comment (by iandunn): Replying to [comment:23 coreymckrill]: > It links to the SVN repo, not in a new tab. I included it because in the previous iteration the SVN URL was a link instead of copiable text. I would be fine removing it, but I do think it's useful to show people that they can look through the repo on their browser rather than having to do a checkout. I agree that's a useful feature. I think Trac offers a better online- browsing experience, though (syntax highlighting, AJAX folder expanding, etc). Just linking to Trac could confuse some people, though, since the distinction between `core.svn` and `core.trac` needs explaining. I wonder if something like this would be good? > The built WordPress source [...] can be [https://core.trac.wordpress.org/browser/trunk/src/ browsed online], or checked out locally: > > Subversion: `https://core.svn.wordpress.org/` > Git mirror: `git://core.git.wordpress.org/` ---- > In this case, I would probably prefer to leave them as just the URLs for simplicity. People who want to know what the repo URLs are need to have a basic level of understanding about SVN/Git in order to do anything with them anyway, so they should know which commands to use. Works for me. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1103#comment:24> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 20:14:40 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 20:14:40 -0000 Subject: [wp-meta] [Making WordPress.org] #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ In-Reply-To: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> References: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> Message-ID: <065.fd6c3485a8fd0d3e5d4507700ca63f68@wordpress.org> #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ ----------------------------------------+----------------------- Reporter: netweb | Owner: iandunn Type: enhancement | Status: reopened Priority: low | Milestone: Component: General | Resolution: Keywords: needs-patch good-first-bug | ----------------------------------------+----------------------- Comment (by coreymckrill): > The built WordPress source [...] can be browsed online, or checked out locally: Love it. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1103#comment:25> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 20:23:33 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 20:23:33 -0000 Subject: [wp-meta] [Making WordPress.org] #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ In-Reply-To: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> References: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> Message-ID: <065.ebfb5aeeead6ba7d2addc2d062f05e9b@wordpress.org> #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ ----------------------------------------+----------------------- Reporter: netweb | Owner: iandunn Type: enhancement | Status: reopened Priority: low | Milestone: Component: General | Resolution: Keywords: needs-patch good-first-bug | ----------------------------------------+----------------------- Comment (by coreymckrill): Hmm, is there a way to link to the Trac browser for the built version? https://core.trac.wordpress.org/browser goes to the development version... -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1103#comment:26> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 21:03:33 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Fri, 26 May 2017 21:03:33 +0000 (UTC) Subject: [wp-meta] [5520] sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/ wcorg-misc.php: WordCamp: Don't load `wordcamporg` text domain for en_US Message-ID: <20170526210333.8DC941080143@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170526/c13d32e0/attachment.html> From noreply at wordpress.org Fri May 26 21:17:45 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 21:17:45 -0000 Subject: [wp-meta] [Making WordPress.org] #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ In-Reply-To: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> References: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> Message-ID: <065.80cfd4d9c48fe06a9a877df455cb3a26@wordpress.org> #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ ----------------------------------------+----------------------- Reporter: netweb | Owner: iandunn Type: enhancement | Status: reopened Priority: low | Milestone: Component: General | Resolution: Keywords: needs-patch good-first-bug | ----------------------------------------+----------------------- Comment (by iandunn): Replying to [comment:26 coreymckrill]: > Hmm, is there a way to link to the Trac browser for the built version? Hmm, I don't think there is. For the use case of someone casually browsing the code, though, is that distinction important? If we link to `/browser/trunk/src/`, then the user lands in a familiar spot (wp-admin, wp-includes, etc). If they're aware of the unit tests, etc and want to see them, they can just browse up a few directories. It seems like just having the 1 link might be easier to describe in the paragraph too, rather than having to explain what each is. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1103#comment:27> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 22:10:14 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Fri, 26 May 2017 22:10:14 -0000 Subject: [wp-meta] [Making WordPress.org] #2821: Plugin Directory: Plugin slug should be Latin Characters Only In-Reply-To: <051.25e027265662218e64083f79ba18e777@wordpress.org> References: <051.25e027265662218e64083f79ba18e777@wordpress.org> Message-ID: <066.926f23da3357fe39cb7b747a72e84e98@wordpress.org> #2821: Plugin Directory: Plugin slug should be Latin Characters Only ---------------------------------------+------------------ Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch has-screenshots | ---------------------------------------+------------------ Changes (by SergeyBiryukov): * keywords: has-patch => has-patch has-screenshots Comment: In [attachment:2821.2.patch]: * Runs the plugin name through `remove_accents()`. * Strip any non-ASCII characters. * Run the rest through `sanitize_title_with_dashes()`. If the slug turns out to be empty, an error message is displayed: > The plugin has an unsupported name. Plugin names can only contain latin letters (A-z), numbers, spaces, and hyphens. Please change the `Plugin Name:` line in your main plugin file and upload it again. Suggestions for better text welcome :) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2821#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Fri May 26 23:30:19 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Fri, 26 May 2017 23:30:19 +0000 (UTC) Subject: [wp-meta] [5521] sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/ wcorg-misc.php: WordCamp: Change timing of text domain load to allow usage of user locale Message-ID: <20170526233019.978EC1080143@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170526/5177a24b/attachment-0001.html> From noreply at wordpress.org Sat May 27 00:46:30 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 27 May 2017 00:46:30 -0000 Subject: [wp-meta] [Making WordPress.org] #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ In-Reply-To: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> References: <050.bed2daef6e6cc120428ac89cb57ac81f@wordpress.org> Message-ID: <065.3998369d67e4efa3b3ff9a80a5d4964b@wordpress.org> #1103: Add WordPress Git & GitHub mirror docs to https://wordpress.org/download/ ----------------------------------------+----------------------- Reporter: netweb | Owner: iandunn Type: enhancement | Status: reopened Priority: low | Milestone: Component: General | Resolution: Keywords: needs-patch good-first-bug | ----------------------------------------+----------------------- Comment (by netweb): Replying to [comment:27 iandunn]: > Replying to [comment:26 coreymckrill]: > > Hmm, is there a way to link to the Trac browser for the built version? > > Hmm, I don't think there is. Yes, here it is https://build.trac.wordpress.org/browser > For the use case of someone casually browsing the code, though, is that distinction important? I don't think so, if someone wants to view the "built" source code they can view the contents locally via wordpress.zip -- Ticket URL: <https://meta.trac.wordpress.org/ticket/1103#comment:28> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 27 01:12:44 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 27 May 2017 01:12:44 -0000 Subject: [wp-meta] [Making WordPress.org] #2821: Plugin Directory: Plugin slug should be Latin Characters Only In-Reply-To: <051.25e027265662218e64083f79ba18e777@wordpress.org> References: <051.25e027265662218e64083f79ba18e777@wordpress.org> Message-ID: <066.4a378a04f4392acbe0ebe9a300ca7936@wordpress.org> #2821: Plugin Directory: Plugin slug should be Latin Characters Only ---------------------------------------+------------------ Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Plugin Directory | Resolution: Keywords: has-patch has-screenshots | ---------------------------------------+------------------ Comment (by Ipstenu): I think that's good to start with. My +1 for you, sir! -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2821#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sat May 27 19:12:08 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sat, 27 May 2017 19:12:08 -0000 Subject: [wp-meta] [Making WordPress.org] #2841: Theme Directory - Feature filter has a min-height Message-ID: <052.dbd7c1412cbe4187cbab2e45a4e36536@wordpress.org> #2841: Theme Directory - Feature filter has a min-height -----------------------------+----------------- Reporter: joyously | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Theme Directory | Keywords: -----------------------------+----------------- When using the Feature Filter of the theme directory, there are 3 sections. Each section lists the filters and then has a big white space. Is there some aspect of the filters that isn't developed yet that is supposed to go in the white space? Looking at the CSS, there is a class `filter-group` with a calculated width and `min-height: 710px`. Then another rule that overrides with `width:100%` and `height: auto`. Can the `min-height` be removed, please? (Actually, all four could be removed, but the min-height is the worst one.) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2841> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Sun May 28 03:12:39 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Sun, 28 May 2017 03:12:39 -0000 Subject: [wp-meta] [Making WordPress.org] #2842: REST API handbook contains incorrect links to Requests class Message-ID: <050.7d84eaea24beca2592bba48d6913fa20@wordpress.org> #2842: REST API handbook contains incorrect links to Requests class ---------------------------+----------------- Reporter: rmccue | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Developer Hub | Keywords: ---------------------------+----------------- Not sure where the code is that auto-links classes used in text, but for the REST API handbook, when `Requests` is used in the text (case- sensitively), it's linked to the Requests class. This is most visible in the [https://developer.wordpress.org/rest- api/#requests broken Requests section header] on the handbook's homepage. This code is in the [https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html /wp-content/themes/pub/wporg-developer/inc/formatting.php#L289 DevHub_Formatting::autolink_references] code, but is explicitly included there, so this seems intentional. Since "requests" is both the name of the class and a common English word, IMO this should err on the most common case, which is as an English word. References to the class itself can be manually linked by the page author. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2842> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 02:37:12 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 02:37:12 -0000 Subject: [wp-meta] [Making WordPress.org] #2753: Plugin directory search sorting and filtering In-Reply-To: <054.ea0beff6952873fe3a66bcfa513e7b6b@wordpress.org> References: <054.ea0beff6952873fe3a66bcfa513e7b6b@wordpress.org> Message-ID: <069.978c3cb5b1ced32b917155fd79bfe20f@wordpress.org> #2753: Plugin directory search sorting and filtering -------------------------------------+------------------------------------- Reporter: tellyworth | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Component: Plugin Directory | Future Keywords: ui-feedback needs- | Resolution: screenshots | -------------------------------------+------------------------------------- Comment (by gibrown): Replying to [comment:6 joyously]: > One thing that is unclear is whether it is different code that populates the plugin search results in the admin versus the page that looks the same on wordpress.org. > Does this ticket cover both contexts? It is different code. The core plugin search is separate, but it uses the same backend algorithm. I think we should focus on iterating on the design here before looking to improve the UI in core. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2753#comment:8> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 02:35:01 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 02:35:01 -0000 Subject: [wp-meta] [Making WordPress.org] #2753: Plugin directory search sorting and filtering In-Reply-To: <054.ea0beff6952873fe3a66bcfa513e7b6b@wordpress.org> References: <054.ea0beff6952873fe3a66bcfa513e7b6b@wordpress.org> Message-ID: <069.0e9f29a606b3b5805b016e249a71c170@wordpress.org> #2753: Plugin directory search sorting and filtering -------------------------------------+------------------------------------- Reporter: tellyworth | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Component: Plugin Directory | Future Keywords: ui-feedback needs- | Resolution: screenshots | -------------------------------------+------------------------------------- Comment (by gibrown): Thanks for adding some mockups. Helps to think through some of the complexities. For sorting: - I'm going back and forth a bit on the word "popularity" and wondering if we should just say "relevance" which is at least open to interpretation - I'm not sure what sorting by plugin name would be? Alphabetical? What use cases does that solve for us? Also, we won't always be able to page through all of the results, so I think it would be a broken experience Looking at the original design some more, I don't really like that the search box is in the upper right of the current design. Makes it hard to find and therefore hard to adjust. Feels to me that it should be in the center of the page, and much bigger than the text that says: "Showing results for:" We also need someplace to display any filters that have already been added to the search. Maybe just below a more prominent search box with a set of filters using something like https://select2.github.io/examples.html#tags (though maybe something better than that). For faceting, I think we should have the facets on screen at all times on large screens. That may mean reworking how the current results are displayed, but should make the search more browsable and interactive. I guess on small screens the faceting will have to slide in, or not exist at all. I'd also love to just skip straight to doing a React UI for the search interface to make interacting much faster, but that would make the project a fair bit bigger I think (or at least it would make it harder for me to implement). I was looking at these for instance: https://react.rocks/tag/Faceted_Search -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2753#comment:7> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 10:27:09 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 10:27:09 -0000 Subject: [wp-meta] [Making WordPress.org] #957: Create a community Code of Conduct In-Reply-To: <053.003b95e85f7c7cb56c4aa3750a9b223d@wordpress.org> References: <053.003b95e85f7c7cb56c4aa3750a9b223d@wordpress.org> Message-ID: <068.71cd81f2af9fa60c5241ad6f998a5ec2@wordpress.org> #957: Create a community Code of Conduct -------------------------+------------------ Reporter: melchoyce | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: General | Resolution: Keywords: | -------------------------+------------------ Comment (by mor10): Good news everyone! It took a lot longer than expected, but here's the proposal for the Community Code of Conduct Project: https://make.wordpress.org/updates/2017/05/19/proposal-wordpress- community-conduct-project/ Please sign up and let's get started! -- Ticket URL: <https://meta.trac.wordpress.org/ticket/957#comment:31> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 18:12:29 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 30 May 2017 18:12:29 +0000 (UTC) Subject: [wp-meta] [5522] sites/trunk/wordcamp.org/public_html/wp-content/plugins/ wc-post-types/wc-post-types.php: WordCamp Post Types: Show sponsors post type in the v2 REST API Message-ID: <20170530181229.7CE601080339@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170530/1ff5ae6c/attachment.html> From noreply at wordpress.org Tue May 30 18:31:31 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 18:31:31 -0000 Subject: [wp-meta] [Making WordPress.org] #2802: Credit to initial translator when validator uploads po-file In-Reply-To: <056.93036d4247cdee75d8b7445ebe57538d@wordpress.org> References: <056.93036d4247cdee75d8b7445ebe57538d@wordpress.org> Message-ID: <071.ba600497897702ed5c740e1dd8862dc1@wordpress.org> #2802: Credit to initial translator when validator uploads po-file --------------------------------------+---------------------- Reporter: tobifjellner | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: Translate Site & Plugins | Resolution: invalid Keywords: | --------------------------------------+---------------------- Changes (by ocean90): * status: new => closed * resolution: => invalid Comment: The GlotPress issue is the correct one in this case. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2802#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 20:30:07 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 20:30:07 -0000 Subject: [wp-meta] [Making WordPress.org] #148: Restyle/redesign the registration page In-Reply-To: <051.ab1c08ab370895eaf5a087029eef46c5@wordpress.org> References: <051.ab1c08ab370895eaf5a087029eef46c5@wordpress.org> Message-ID: <066.de0ece24a888a9edd99a9efd602d79ac@wordpress.org> #148: Restyle/redesign the registration page ------------------------------------+----------------------- Reporter: j.conti | Owner: dd32 Type: task | Status: assigned Priority: high | Milestone: Component: Login & Authentication | Resolution: Keywords: has-ui-feedback | ------------------------------------+----------------------- Changes (by karmatosed): * keywords: ui-feedback => has-ui-feedback -- Ticket URL: <https://meta.trac.wordpress.org/ticket/148#comment:49> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 20:30:53 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 20:30:53 -0000 Subject: [wp-meta] [Making WordPress.org] #148: Restyle/redesign the registration page In-Reply-To: <051.ab1c08ab370895eaf5a087029eef46c5@wordpress.org> References: <051.ab1c08ab370895eaf5a087029eef46c5@wordpress.org> Message-ID: <066.f83b460da177b0d2a341378a27126984@wordpress.org> #148: Restyle/redesign the registration page ------------------------------------+----------------------- Reporter: j.conti | Owner: dd32 Type: task | Status: assigned Priority: high | Milestone: Component: Login & Authentication | Resolution: Keywords: | ------------------------------------+----------------------- Changes (by karmatosed): * keywords: has-ui-feedback => -- Ticket URL: <https://meta.trac.wordpress.org/ticket/148#comment:50> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 20:32:06 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 20:32:06 -0000 Subject: [wp-meta] [Making WordPress.org] #148: Restyle/redesign the registration page In-Reply-To: <051.ab1c08ab370895eaf5a087029eef46c5@wordpress.org> References: <051.ab1c08ab370895eaf5a087029eef46c5@wordpress.org> Message-ID: <066.a37d427cda81d1751877c732bb2823f4@wordpress.org> #148: Restyle/redesign the registration page ------------------------------------+--------------------- Reporter: j.conti | Owner: dd32 Type: task | Status: closed Priority: high | Milestone: Component: Login & Authentication | Resolution: fixed Keywords: | ------------------------------------+--------------------- Changes (by ocean90): * status: assigned => closed * resolution: => fixed -- Ticket URL: <https://meta.trac.wordpress.org/ticket/148#comment:51> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 20:36:52 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 30 May 2017 20:36:52 +0000 (UTC) Subject: [wp-meta] [5523] sites/trunk/wordpress.org/public_html/wp-content/plugins: Support Forums: Pass post IDs to `moderate` capability checks. Message-ID: <20170530203652.3918C1080339@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170530/c98f51fe/attachment-0001.html> From noreply at wordpress.org Tue May 30 20:36:52 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 20:36:52 -0000 Subject: [wp-meta] [Making WordPress.org] #2590: Enhance compatibility with per forum moderators In-Reply-To: <051.ef2c0624040c63d1e71b94d15700a274@wordpress.org> References: <051.ef2c0624040c63d1e71b94d15700a274@wordpress.org> Message-ID: <066.e35b24b28a2443a942a5e25311d351b2@wordpress.org> #2590: Enhance compatibility with per forum moderators ------------------------------+---------------------- Reporter: ocean90 | Owner: ocean90 Type: defect | Status: closed Priority: normal | Milestone: Component: Support Forums | Resolution: fixed Keywords: has-patch commit | ------------------------------+---------------------- Changes (by ocean90): * owner: => ocean90 * status: new => closed * resolution: => fixed Comment: In [changeset:"5523"]: {{{ #!CommitTicketReference repository="" revision="5523" Support Forums: Pass post IDs to `moderate` capability checks. Props SergeyBiryukov. Fixes #2590. }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2590#comment:9> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 20:39:55 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 20:39:55 -0000 Subject: [wp-meta] [Making WordPress.org] #2618: Plugin Directory: Translation needed banner omits language In-Reply-To: <051.eed73691dd5ba0b981c0645fe16da796@wordpress.org> References: <051.eed73691dd5ba0b981c0645fe16da796@wordpress.org> Message-ID: <066.3bde2961fcfc73f9acb1868408f2b4cf@wordpress.org> #2618: Plugin Directory: Translation needed banner omits language ------------------------------+------------------------------------------- Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: | ------------------------------+------------------------------------------- Changes (by ocean90): * keywords: has-patch => Comment: Yeah, we're not going to use the name of a site for the banner. See https://meta.trac.wordpress.org/ticket/2517#comment:2 -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2618#comment:9> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 20:47:56 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 30 May 2017 20:47:56 +0000 (UTC) Subject: [wp-meta] [5524] sites/trunk/wordpress.org/public_html/wp-content/plugins/ wporg-gp-customizations/templates: Translate: Move the right parenthesis of `esc_url()` to the correct position. Message-ID: <20170530204756.5A1421080339@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170530/d9877b12/attachment.html> From noreply at wordpress.org Tue May 30 20:50:43 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 30 May 2017 20:50:43 +0000 (UTC) Subject: [wp-meta] [5525] sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-cli: make/cli: Add `cli-repo-list` shortcode Message-ID: <20170530205043.0B98D1080339@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170530/dd86b296/attachment-0001.html> From noreply at wordpress.org Tue May 30 21:17:19 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 21:17:19 -0000 Subject: [wp-meta] [Making WordPress.org] #2756: Improve search form styling and correct meeting time in 404 template on make/core P2 In-Reply-To: <051.492fbf3beaa5974f52535dcec2edb17b@wordpress.org> References: <051.492fbf3beaa5974f52535dcec2edb17b@wordpress.org> Message-ID: <066.10da8a0bbf939f9416d2bc00cb149c98@wordpress.org> #2756: Improve search form styling and correct meeting time in 404 template on make/core P2 --------------------------------------+---------------------- Reporter: alkesh7 | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Make (Get Involved) / P2 | Resolution: invalid Keywords: ui-feedback | --------------------------------------+---------------------- Changes (by karmatosed): * status: new => closed * resolution: => invalid Comment: I just tested this and seems that it with the new design is fixed, or at least not such an issue: [[Image(https://cldup.com/0Zc_sYImQc.png)]] As this has been fairly recent, going to mark as closed for now. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2756#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 21:22:25 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 21:22:25 -0000 Subject: [wp-meta] [Making WordPress.org] #2779: Single Plugin: Remove URL to Current Page from Plugin Title In-Reply-To: <053.d2026e74568a0d11713bdcfd28a44421@wordpress.org> References: <053.d2026e74568a0d11713bdcfd28a44421@wordpress.org> Message-ID: <068.be2efc2b42a7b301e6d316453fe45ef4@wordpress.org> #2779: Single Plugin: Remove URL to Current Page from Plugin Title ------------------------------+------------------------------------ Reporter: bmoredrew | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------ Changes (by karmatosed): * keywords: has-patch ux-feedback ui-feedback => has-patch -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2779#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 21:23:07 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 21:23:07 -0000 Subject: [wp-meta] [Making WordPress.org] #2756: Improve search form styling and correct meeting time in 404 template on make/core P2 In-Reply-To: <051.492fbf3beaa5974f52535dcec2edb17b@wordpress.org> References: <051.492fbf3beaa5974f52535dcec2edb17b@wordpress.org> Message-ID: <066.25431286c489fc2521061a8b430d81b3@wordpress.org> #2756: Improve search form styling and correct meeting time in 404 template on make/core P2 --------------------------------------+----------------------- Reporter: alkesh7 | Owner: Type: defect | Status: reopened Priority: normal | Milestone: Component: Make (Get Involved) / P2 | Resolution: Keywords: ui-feedback | --------------------------------------+----------------------- Changes (by SergeyBiryukov): * status: closed => reopened * resolution: invalid => Comment: https://make.wordpress.org/core/non-existing-url still displays both issues, exactly as on the screenshot. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2756#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 21:27:46 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Tue, 30 May 2017 21:27:46 -0000 Subject: [wp-meta] [Making WordPress.org] #2831: On the Advanced view of a plugin the list of committers is imporperly formatted. In-Reply-To: <050.a1902e359d66d525b6d3ac015ea54721@wordpress.org> References: <050.a1902e359d66d525b6d3ac015ea54721@wordpress.org> Message-ID: <065.b80e72c0fd7c36afa2cb3a81ba430d73@wordpress.org> #2831: On the Advanced view of a plugin the list of committers is imporperly formatted. -------------------------------------+------------------------------------- Reporter: aguseo | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Component: Plugin Directory | Future Keywords: has-screenshots ui- | Resolution: feedback reporter-feedback | -------------------------------------+------------------------------------- Comment (by karmatosed): I also wonder how useful this information is if you are just a user/viewer. Don't we need to fix though then for someone who is? It seems a less optimal visual experience otherwise. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2831#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Tue May 30 22:47:04 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 30 May 2017 22:47:04 +0000 (UTC) Subject: [wp-meta] [5526] sites/trunk/wordpress.org/public_html/wp-content/plugins: make/cli: Create a shortcode for listing issues Message-ID: <20170530224704.618F61080339@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170530/f2fa11a8/attachment-0001.html> From noreply at wordpress.org Tue May 30 23:26:06 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Tue, 30 May 2017 23:26:06 +0000 (UTC) Subject: [wp-meta] [5527] sites/trunk/wordpress.org/public_html/wp-content/plugins/ p2-new-post-categories/: P2 New Post Categories: Remove from repository because no longer used Message-ID: <20170530232606.6777A1080339@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170530/0f6c391d/attachment.html> From noreply at wordpress.org Wed May 31 02:53:19 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 02:53:19 -0000 Subject: [wp-meta] [Making WordPress.org] #2790: Blockquote styles enhancement In-Reply-To: <058.1519385a51fb59753db7156e002686b1@wordpress.org> References: <058.1519385a51fb59753db7156e002686b1@wordpress.org> Message-ID: <073.7578d6429a04fdc6718d91203cd6fdbf@wordpress.org> #2790: Blockquote styles enhancement ------------------------------+------------------------------------ Reporter: webdevmattcrom | Owner: mapk Type: enhancement | Status: reviewing Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------ Comment (by joyously): I don't think `blockquote` should be italic. Blockquote can have nested HTML, including `<em>`, which would be indistinguishable. I favor an indent, but not a background color change. After all, `blockquote` is for quoting an external source, not making something stand out. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2790#comment:8> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 12:28:18 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 31 May 2017 12:28:18 +0000 (UTC) Subject: [wp-meta] [5528] sites/trunk/common/includes/slack/announce/config.php: Slack: Give adamsilverstein announce in #core. Message-ID: <20170531122818.7590A108041E@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170531/9bf08184/attachment.html> From noreply at wordpress.org Wed May 31 15:58:48 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 15:58:48 -0000 Subject: [wp-meta] [Making WordPress.org] #2843: Slack: Add ?support Slackbot auto-response Message-ID: <053.567febe8b56a96cc1b1db44fb4ca23af@wordpress.org> #2843: Slack: Add ?support Slackbot auto-response -------------------------+----------------- Reporter: melchoyce | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Slack & IRC | Keywords: -------------------------+----------------- We get a lot of people on Slack asking for support. I think it would be helpful to create a `?support` Slack auto-response with a friendly reply directing people to the support forums. Maybe: > Welcome to the Making WordPress slack! This Slack is for discussion related to the creation of WordPress itself. For general support or questions, please check out the WordPress.org support forums https://wordpress.org/support/ or IRC https://make.wordpress.org/support /irc-support-channel/. (Need some smoothing) -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2843> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 17:06:01 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 31 May 2017 17:06:01 +0000 (UTC) Subject: [wp-meta] [5529] sites/trunk/wordcamp.org/public_html/wp-content/plugins/ wc-post-types/wc-post-types.php: WordCamp Post Types: Show track and level taxonomies in REST API Message-ID: <20170531170601.6AE39108041E@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170531/4614026b/attachment.html> From noreply at wordpress.org Wed May 31 19:16:21 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 19:16:21 -0000 Subject: [wp-meta] [Making WordPress.org] #2821: Plugin Directory: Plugin slug should be Latin Characters Only In-Reply-To: <051.25e027265662218e64083f79ba18e777@wordpress.org> References: <051.25e027265662218e64083f79ba18e777@wordpress.org> Message-ID: <066.2dd72cca59ec0cca017c64b22d208ff8@wordpress.org> #2821: Plugin Directory: Plugin slug should be Latin Characters Only ---------------------------------------+----------------------------------- Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory Component: Plugin Directory | v3.0 Keywords: has-patch has-screenshots | Resolution: ---------------------------------------+----------------------------------- Changes (by SergeyBiryukov): * milestone: => Plugin Directory v3.0 -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2821#comment:5> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 19:16:35 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 19:16:35 -0000 Subject: [wp-meta] [Making WordPress.org] #2721: Plugin Directory: Use a consistent font size for Committers and Contributors widgets In-Reply-To: <058.681e5903d68600d88138ab13d1c4f78d@wordpress.org> References: <058.681e5903d68600d88138ab13d1c4f78d@wordpress.org> Message-ID: <073.37412e92fba201997bf06387901653d0@wordpress.org> #2721: Plugin Directory: Use a consistent font size for Committers and Contributors widgets -------------------------------------+------------------------------------- Reporter: SergeyBiryukov | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Component: Plugin Directory | Future Keywords: has-patch commit has- | Resolution: screenshots | -------------------------------------+------------------------------------- Changes (by SergeyBiryukov): * milestone: => Plugin Directory v3 - Future -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2721#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 19:16:33 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 19:16:33 -0000 Subject: [wp-meta] [Making WordPress.org] #2830: Plugin Directory: Include slug in submission emails In-Reply-To: <051.980ca4c7bb6bb49acc9857d3105e0019@wordpress.org> References: <051.980ca4c7bb6bb49acc9857d3105e0019@wordpress.org> Message-ID: <066.2dca7d24903499943ca3cca5fd5a9c47@wordpress.org> #2830: Plugin Directory: Include slug in submission emails ------------------------------+------------------------------------ Reporter: Ipstenu | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------ Changes (by SergeyBiryukov): * milestone: => Plugin Directory v3.0 -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2830#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 19:16:37 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 19:16:37 -0000 Subject: [wp-meta] [Making WordPress.org] #2781: Plugin Directory: Add translator comments for placeholders in Stats Report tool In-Reply-To: <058.03697759c32f7f3c720db10da4f5a581@wordpress.org> References: <058.03697759c32f7f3c720db10da4f5a581@wordpress.org> Message-ID: <073.ad31ff40ea13943ee58a05d3eb5bd2f1@wordpress.org> #2781: Plugin Directory: Add translator comments for placeholders in Stats Report tool ------------------------------+------------------------------------------- Reporter: SergeyBiryukov | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------------- Changes (by SergeyBiryukov): * milestone: => Plugin Directory v3 - Future -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2781#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 19:16:40 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 19:16:40 -0000 Subject: [wp-meta] [Making WordPress.org] #2782: Plugin Directory: Use consistent punctuation in meta descriptions In-Reply-To: <058.2b0bc6e3e877dd01c767b417b2dfa077@wordpress.org> References: <058.2b0bc6e3e877dd01c767b417b2dfa077@wordpress.org> Message-ID: <073.ea68029d7ee177b353c914e9cdcca324@wordpress.org> #2782: Plugin Directory: Use consistent punctuation in meta descriptions ------------------------------+------------------------------------------- Reporter: SergeyBiryukov | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------------- Changes (by SergeyBiryukov): * milestone: => Plugin Directory v3 - Future -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2782#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 19:17:31 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 19:17:31 -0000 Subject: [wp-meta] [Making WordPress.org] #2843: Slack: Add ?support Slackbot auto-response In-Reply-To: <053.567febe8b56a96cc1b1db44fb4ca23af@wordpress.org> References: <053.567febe8b56a96cc1b1db44fb4ca23af@wordpress.org> Message-ID: <068.fcd9e983cd01f0573ff7dd7d5b1ba76a@wordpress.org> #2843: Slack: Add ?support Slackbot auto-response -------------------------+------------------ Reporter: melchoyce | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Slack & IRC | Resolution: Keywords: | -------------------------+------------------ Comment (by casiepa): You could also help them getting to their locals slacks. Something like : ''Or find a local slack (https://make.wordpress.org/polyglots/handbook/about/teams/local-slacks/) and ask your question there if it's related to something local.'' Another frequent question is about jobs. My standard response: ''Hi there, for job postings, please use one of the resources such as jobs.wordpress.net or jetpack.pro. Or find a local slack (https://make.wordpress.org/polyglots/handbook/about/teams/local-slacks/) and look for a job channel.'' So that could be a ?jobs or something -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2843#comment:1> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 19:17:48 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 19:17:48 -0000 Subject: [wp-meta] [Making WordPress.org] #2800: Plugin Directory: Ask for confirmation before removing someone as a committer In-Reply-To: <054.334261ed8da287672092be0c6c8fe2d4@wordpress.org> References: <054.334261ed8da287672092be0c6c8fe2d4@wordpress.org> Message-ID: <069.59b6c46309a905609e77bcf04942b4c6@wordpress.org> #2800: Plugin Directory: Ask for confirmation before removing someone as a committer ------------------------------+------------------------------------------- Reporter: Nikschavan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Plugin Directory v3 - Future Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------------- Changes (by SergeyBiryukov): * milestone: => Plugin Directory v3 - Future -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2800#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 19:24:52 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 19:24:52 -0000 Subject: [wp-meta] [Making WordPress.org] #2796: Plugin Directory Admin: Limit State Switching for Plugin Statuses In-Reply-To: <051.ad8639951baef0ece119c495143919d3@wordpress.org> References: <051.ad8639951baef0ece119c495143919d3@wordpress.org> Message-ID: <066.d5cd534690774782d0340343ddc87280@wordpress.org> #2796: Plugin Directory Admin: Limit State Switching for Plugin Statuses ------------------------------+------------------------------------ Reporter: Ipstenu | Owner: Type: defect | Status: new Priority: normal | Milestone: Plugin Directory v3.0 Component: Plugin Directory | Resolution: Keywords: has-patch | ------------------------------+------------------------------------ Changes (by SergeyBiryukov): * milestone: => Plugin Directory v3.0 Comment: Just realized the patch doesn't allow for plugins to be moved to Trash :) Is that something admins should be able to do (e.g. for spam submissions), or Rejected status would be sufficient? -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2796#comment:4> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 21:48:25 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 21:48:25 -0000 Subject: [wp-meta] [Making WordPress.org] #2843: Slack: Add ?support Slackbot auto-response In-Reply-To: <053.567febe8b56a96cc1b1db44fb4ca23af@wordpress.org> References: <053.567febe8b56a96cc1b1db44fb4ca23af@wordpress.org> Message-ID: <068.51721a0060bd17a1555c2db050ab4fc4@wordpress.org> #2843: Slack: Add ?support Slackbot auto-response -------------------------+------------------ Reporter: melchoyce | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Slack & IRC | Resolution: Keywords: | -------------------------+------------------ Comment (by netweb): This has been brought up multiple times and the general consensus is to not add a Slack bot for this https://wordpress.slack.com/archives/C02RQBWTW/p1484646847005814 * [[Image(https://cldup.com/oyJKG1d11k.png)]] There's a few more instances through my search foo was unable to find them :( -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2843#comment:2> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 22:10:56 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 22:10:56 -0000 Subject: [wp-meta] [Making WordPress.org] #2843: Slack: Add ?support Slackbot auto-response In-Reply-To: <053.567febe8b56a96cc1b1db44fb4ca23af@wordpress.org> References: <053.567febe8b56a96cc1b1db44fb4ca23af@wordpress.org> Message-ID: <068.23dec3d7d47cdeae80d779bf1c96a293@wordpress.org> #2843: Slack: Add ?support Slackbot auto-response -------------------------+------------------ Reporter: melchoyce | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Slack & IRC | Resolution: Keywords: | -------------------------+------------------ Comment (by melchoyce): I don't think we need a bot, just a manually-triggered Slack auto- response. -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2843#comment:3> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org From noreply at wordpress.org Wed May 31 22:18:31 2017 From: noreply at wordpress.org (noreply at wordpress.org) Date: Wed, 31 May 2017 22:18:31 +0000 (UTC) Subject: [wp-meta] [5530] sites/trunk/wordcamp.org/public_html/wp-content/themes/ wordcamp-central-2012: WordCamp Central: Add year to camp dates on the schedule Message-ID: <20170531221831.5526B108041E@svn1.lax.wordpress.org> An HTML attachment was scrubbed... URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20170531/7be1c464/attachment-0001.html> From noreply at wordpress.org Wed May 31 22:18:31 2017 From: noreply at wordpress.org (Making WordPress.org) Date: Wed, 31 May 2017 22:18:31 -0000 Subject: [wp-meta] [Making WordPress.org] #2065: Add year to dates on http://central.wordcamp.org/schedule/ In-Reply-To: <059.ac3962f242437219871b68a88feac608@wordpress.org> References: <059.ac3962f242437219871b68a88feac608@wordpress.org> Message-ID: <074.fcbb50f10aa4b1dc074e54e2f8309c98@wordpress.org> #2065: Add year to dates on http://central.wordcamp.org/schedule/ --------------------------------------+---------------------- Reporter: andreamiddleton | Owner: iandunn Type: enhancement | Status: closed Priority: low | Milestone: Component: WordCamp Site & Plugins | Resolution: fixed Keywords: good-first-bug has-patch | --------------------------------------+---------------------- Changes (by coreymckrill): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"5530"]: {{{ #!CommitTicketReference repository="" revision="5530" WordCamp Central: Add year to camp dates on the schedule Changes the Schedule page template to emulate the organization on the Past Camps page template, by grouping camps under a year header and including the year in each camp's date. This also adds a param to `WordCamp_Central_Theme::the_wordcamp_date` to include the year in the camp date output. The default is to not include it, for backcompat. Props frq Fixes #2065 }}} -- Ticket URL: <https://meta.trac.wordpress.org/ticket/2065#comment:6> Making WordPress.org <https://meta.trac.wordpress.org/> Making WordPress.org