WordPress.org

Making WordPress.org

{5} Accepted, Active Tickets by Owner (Full Description) (24 matches)

List tickets accepted, group by ticket owner. This report demonstrates the use of full-row display.

DrewAPicture (3 matches)

Ticket Summary Component Milestone Type Created
Description
#1866 Add a basic "suggest an edit" workflow to the handbooks plugin Handbooks task 07/29/16

We've talked about this quite a bit in the context of DevHub where User Contributed Notes are occasionally used as a feedback mechanism. Basically, we need a way for docs consumers to report problems or suggest edits of published documentation on .org.

The initial proposal would be to build or use something akin to Post Forking on the front-end of handbooks and eventually other places like DevHub or HelpHub.

Personally I don't think an MVP has to be a complete solution, it mostly needs to cover the rift drawn between moving away from the Codex where any user could edit anything to the now largely closed systems on .org.

I think starting with the handbooks would be the way to go.


#1913 Expand documentation of WP_Term_Query() in Code Reference. Developer Hub enhancement 08/17/16

With the release of 4.6, many devs will be researching WP_Term_Query() only to find that its Code Reference page has very little information. I was expecting documentation similar to WP_Query().

Upon further investigation, I found that much of the information I was looking for is actually in the docs of the WP_Term_Query::__construct() method. I only realized this after reading the DocBlock in the source code, which includes @see WP_Term_Query::__construct() for accepted arguments.. However that info is nowhere to be found in the Code Reference. The the only way to find it is to click __construct() in the Related section.

Can we better reflect the documentation from the __construct() page (specifically the acceptable arguments) in the docs for WP_Term_Query()? This could be accomplished either through examples, or at least a more obvious callout that refers you to the __construct() method for anyone researching how to format the query.


#620 developer.wordpress.org activity should appear on profiles Profiles enhancement 09/23/14

Now that developer.wordpress.org is truly taking shape, it would be great if we could start thinking about how we can get contributor activity appearing on a person's profile.

So far we have the following activity:

  1. Contributions to the theme and plugin developer handbooks:

https://developer.wordpress.org/plugin/credits-2/ https://developer.wordpress.org/theme/credits/

  1. Submitting a user contributed note

For example: https://developer.wordpress.org/reference/hooks/wp_get_attachment_image_attributes/#comment-61

And possibly (when the workflow is sorted)

  1. Having a suggestion approved for changes to curated code reference content

It would be cool if contributors could get a badge under the following circumstances:

  • anyone who is listed as contributing to the handbooks
  • anyone who has 10 or more user contributed notes approved in the code reference

Otto42 (3 matches)

Ticket Summary Component Milestone Type Created
Description
#2699 Add a new role to the forums: plugin/theme support Support Forums enhancement 04/07/17

Plugin and theme authors currently have the power to mark threads as resolved within their own support forum, which is great.

Problem description However, some of the larger plugin/theme shops have a support team to help out on their own support forums. I think it would be useful to be able to recognize those people in the support forums, like we’re able to recognize authors.

Proposal So what I would like to propose is adding a new role: Plugin/Theme Support. Everyone with this role should have rights to mark topics within their own support forum as resolved, and should not be affected by posting speed limitations for their own support forum. This role should also show in the forums as ‘Support’, similar to author.

The reason why I propose a new role, instead of adding the capability to the contributor role is because, in my opinion, they serve a different purpose. Let me explain.

A contributor is someone who helped your open source project forward. This can be by providing feedback, writing code, creating images, doing marketing or being a friend of the project, for example.

Someone working on support does contribute his/her (paid) time to your project and is in that way a contributor. However, I think there are more than enough valid use cases where you don’t want someone who contributed code (for example) once to be able to close support request on behalf of the author.

That’s why I think having a separate support role would be viable. It would show the community that this person is vetted and answering on behalf of the plugin/theme author.

Related ticket This proposal is related to ticket #2598.

Managing support role Of course, it should be possible for plugin authors to manage the list of support people. I see two reasonable ways to do so, which should be mutually exclusive.

One way is by adding the usernames to the readme.txt file, the same way contributors are currently added. The other way would be to add users the same way committers are currently added, on the Advanced View of the plugin.

Showing support staff To be transparent about this, we’d probably also need a place to list people in the support role. This could be the Advanced View page, or even the plugin page itself.


#2771 Plugin Directory: Direct access to changelog via #changelog in URL not working anymore Plugin Directory Plugin Directory v3.0 defect 04/21/17

Until the recent change to the plugin repository design, the changelog was a separate area, directly accessible via the URL reference "#changelog".

This no longer works.

Also, moving this section to the Development area labels it in a way that may discourage non-technical site owners from considering changes before applying them, which can create problems for them sometimes.


#3265 Serve auto-generated plugin icons via URL Plugin Directory defect 11/13/17

Currently the plugins auto-generated icons are passed around as base64'd data uri SVG's and output directly onto pages, and passed back directly to be displayed inline by clients. For example, the Debug Bar plugin has this in it's source:

<style>#plugin-icon-debug-bar { background-image: url('data:image/svg+xml;base64,....

With WordPress 4.9 displaying plugin icons in the update list, plugins which only have the auto-generated icon are not shown as the data wasn't available to the update API (as it's generated on every request where needed).

It'd be far simpler if these were available through a cached-SVG request, for example: https://s.w.org/plugins/generated-plugin-icon?name=$plugin&color=$color which would allow embedding into plugins pages, as well as being served as a fallback SVG in the APIs.


SergeyBiryukov (3 matches)

Ticket Summary Component Milestone Type Created
Description
#2204 Forum RSS Feed Issues Support Forums defect 11/03/16

The RSS feeds generated by the new Plugin Directory platform have a number of drawbacks/defects compared to the feeds that were generated by the old platform.

  1. When a new reply is posted to a topic:
  • The email message generated for "subscribers" to the topic also has the correct information, but the message comes as plain-text so markup for code blocks, lists, etc. is lost.
  1. When the original post in a topic was modified, the feed generates and ongoing stream of "updates" identical to the original except for the "This topic was modified 2 weeks, 6 days ago by ..." text. This makes it hard to identify topics with genuine updates.
  1. When updates are posted to old topics (e.g. started 8 months ago), no RSS feed update is generated. It is hard to know when new activity occurs in an old topic.

Minor notes:

  1. The subject line no longer includes the plugin name, which makes it harder to organize an archive by plugin.
  1. The subject line no longer includes the post author, which would be fine if the actual author value was set correctly.
  1. The subject line now identifies "[Resolved]" topics, but not any other status value.

In short, RSS updates should contain:

  • The actual text of the update, with HTML markup
  • The actual date/time of the update
  • The actual author of the update
  • A subject line that includes the plugin name and perhaps the current status in addition to the topic title.

#1955 Moving a topic from one forum to another forum results in a 500 error Support Forums defect 09/02/16

Steps to reproduce:

  1. Create a topic (with or without a reply)
  2. Move the topic to another forum by editing the topic and selecting a new destination forum, click submit

Result: 500 Error

Workaround: The topic and replies (if any) have actually moved to the new destination forum and no further action is required.

Caveat: Topic and Reply post and post meta data integrity should be verified here

Expected: Topic and replies to be moved without error


#3039 Plugin Directory: On approval, last updated says 2019 years ago Plugin Directory defect 08/11/17

When a plugin is approved, by default it says last updated 2019 years ago.

This is not really a huge problem as once the code is committed, it magically fixes it. Plus only the plugin dev and the site admins can even see it. But it is confusing to some people and scary.

Related: #2740


coffee2code (2 matches)

Ticket Summary Component Milestone Type Created
Description
#1424 Automate meta contributor badge assignment when receiving props Profiles defect 12/01/15

Profile badges don't seem to automatically appear for all areas. My core and plugins badges appeared on my profile on their own (as far as I can tell), but my Speaker badge had to be added manually with some difficulty, and my Meta badge hasn't appeared at all after getting first props a few weeks ago (see [2016]).


#3168 WordPress.tv: Too small font size in handbook menu Make (Get Involved) / P2 defect 09/27/17

The sidebar menu on https://make.wordpress.org/tv/handbook/ has a few issues:

  1. The font is too small (10px) when compared to other handbooks like Core Contributor Handbook (13px).
  2. A search form should be added above the Chapters menu for consistency with other handbooks.

Looking at the markup, the first issue has to do with WPTV handbook using a custom menu instead of the Handbook Pages widget. The widget uses a specific font size:

#secondary aside.widget_wporg_handbook_pages {
    font-size: 16px;
}

The WPTV custom menu uses the default P2-Breathe font size, which is too small here:

#secondary aside {
    font-size: 1.2em;
}

The easiest fix is probably to use the Handbook Pages widget, same as other handbooks do.


coreymckrill (6 matches)

Ticket Summary Component Milestone Type Created
Description
#2849 Add sessions list and other details to speaker pages WordCamp Site & Plugins enhancement 06/05/17

For the new CampSite theme we had the idea to include a speakers bio page with an improved sessions list not only showing the session title, but also an excerpt as well as links to the slides and WordPress.tv video. We decided against a page template and rather add this additional markup to the post types plugin.


#2893 Admin Flags: Add Attendee filtering by Flag WordCamp Site & Plugins enhancement 06/22/17

Currently the Camptix Attendee Flags doesn't allow filtering by flag, it'd be great if it did.

If you've got a flag Speaker set, you can't display all attendee's who are flagged as a Speaker unless you export it.

The attached patch adds the Flags as filter views on the Attendee post type listing.


#2894 Admin Flags: Internationalise the post-status-change label WordCamp Site & Plugins defect 06/22/17

When toggling a status in the Flag section, the toggle afterwards is missing the capitalisation, this is because it just sets the label afterwards to the command, rather than the textual label for it.

The attached patch adds internationalised Enable/Disable text which it switches in/out instead of using the command. It's hard-coded inline with the JS, as that's the format of the current JS and changing it up further probably deserves a rethink of the entire flagging UI and storage.


#3122 Documentation for prefilling coupon field in CampTix via query string WordCamp Site & Plugins enhancement 09/11/17

To save time and avoid typos, it would be great to support a means of that prefilling the coupon field.

For example: city.wordcamp.org/tickets?coupon=2017volunteer

Volunteers, sponsors, speakers, organizers, scholarship recipients, and others rely on coupon codes, and this would enable organizers to ensure they get the coupon code right on the first try.


#2923 Layout / Responsive issue on Opera for Android (Central Wordcamp) WordCamp Site & Plugins defect 07/04/17

Hi guy's,

This is the first time I write a ticket here. Do not hesitate to give me advice if it is not the usual way to fill a ticket.

I would like to bring to your attention that there are problems about the layout on the website https://central.wordcamp.org/ for Opera users on Android.

Here is an example on this screenshot, but there are probably others :

http://i.imgur.com/Nz9xrbfm.png

I posted this info on slack yesterday and @coreymckrill recommended me filling a ticket here.

Regards, Jason


#3003 Tagregator - Twitter resets settings randomly WordCamp Site & Plugins defect 07/26/17

Hello,

While I was working on these tickets: #2100 and #2907

I've noticed that my error log was getting grumpy and I saw this error:

[22-Jul-2017 11:26:20 UTC] PHP Notice: Undefined index: consumer_key in tggr-source-twitter.php on line 152

For some reason when you view the results page on the front end the twitter module bugs out randomly ( not all times ) and after that php error all the settings are getting reset so you are losing all login information etc.

I haven't been able to find out why.

@dipeshkakadiya is on it for a solution so we can implement it on gwtd3 new website as well.

Pointers for devs: Grab the /trunk of Tagregator through svn, apply the extra patches to have the latest as they have not been implemented yet and then work on this ticket.


iandunn (3 matches)

Ticket Summary Component Milestone Type Created
Description
#3244 Data Protection and Bank Detail issues WordCamp Site & Plugins defect 11/02/17

Within the Reimbursement back end of the WordCamp Sites personal details are being stored forever, and any organiser who has access can still see everyones personal details.

  1. Scrub the financial bank details after the set auditing time or at time of reimbursement.

Solution: I am aware that WordCamp will have to store financial data for a while but it is important to know that volunteers bank details will not be stored after they are no longer needed. WordCamp can retain the amounts but scrub the bank details as soon as they are allowed to. I do generally believe that personal bank details should be scrubbed as soon as the claim is paid, mostly because WordCamp should of stored this information somewhere more secure when making payments and also because you have receipts which are proof of payment.

  1. Currently any organiser continues to have access to the back end of any WordCamp site they were an organiser for and all of these sites hold peoples personal addresses and bank details too.

Solution: Deny access to all financial information apart from budgets once the camp has been signed off.

I am concerned about data protection and a little about financial conduct, I have a good understanding about data protection too, and kind of feel some of these changes need to be considered carefully. If WordCamp was hacked it is potentially a identity theft goldmine as it stores peoples home addresses and bank details.


#2823 Improve IP Geolocation Results API defect 05/11/17

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.

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?


#977 dot removed from username in WordCamp.org (Edit Organizer -> wordpress.org user name) WordCamp Site & Plugins enhancement 03/27/15

Hi,

When I add my user name (j.conti) in the field wordpress.org user name at WordCamp.org admin -> Edit organizer, the dot is removed.


obenland (1 match)

Ticket Summary Component Milestone Type Created
Description
#475 Open source WordPress.tv theme/plugins WordPress.tv enhancement 05/14/14

If it were open source then the community could contribute to it.

Since it runs on WordPress.com, we should add a file with stubs for any WordPress.com functions, so that the theme can be run locally.


ocean90 (2 matches)

Ticket Summary Component Milestone Type Created
Description
#2288 API output : incoherent Locale names Translate Site & Plugins defect 12/02/16

On the translate.wordpress.org, all pages correctly mention Portuguese (Portugal), Portuguese (Brazil) and others. However the API seems to mention incorrectly the following ones "name":"Brazilian Portuguese" "name":"Portuguese" "name":"Spanish" "name":"French" "name":"Venezuelan Spanish" "name":"Chilean Spanish" "name":"Kurdish" "name":"Burmese" "name":"Romansh" "name":"Peruvian Spanish" "name":"Portuguese Informal" "name":"Tigrigna"

Please change the API output to match the official Locale names as mentioned on https://make.wordpress.org/polyglots/teams/

Example API call: https://translate.wordpress.org/api/projects/wp-plugins/jetpack/stable

Thanks, Pascal.


#668 Open-source News Theme General enhancement 10/23/14

While we were building the new bbPress theme we discovered that the WordPress theme live on https://wordpress.org/news/ would've been the best starting point. We now had to hack together stuff from various places.

Wouldn't it make sense to open-source that theme used at /news/ as well?


tellyworth (1 match)

Ticket Summary Component Milestone Type Created
Description
#2467 Plugins not showing on plugin-install screen Plugin Directory Plugin Directory v3.0 defect 02/02/17

Not sure if this is a Meta issue, nevertheless, it could be related to the plugins directory. I was doing a plugin search on plugin-install screen of a 4.7.2 site and got a strange behaviour: the search didn't return all the items available. The number is right – 5 items –, but I can only see 4 items on te screen: http://g.recordit.co/yMeHcCzUSY.gif


Note: See TracReports for help on using and creating reports.