Making WordPress.org

Opened 11 years ago

Closed 4 weeks ago

#681 closed defect (bug) (duplicate)

Community profile badges disappear for WordCamp organisers of two different WordCamps

Reported by: petya's profile petya Owned by:
Milestone: Priority: normal
Component: Profiles Keywords: close
Cc:

Description

When a WordPress.org username gets added to the Organisers of a second WordCamp, the community profile badge disappears.

Here's the use case:

I noticed that my community badge had disappeared after my profile was added to the organisers of WordCamp Europe 2014. Adding a second entry for my profile as an organiser made the badge appear again. But then I was listed as an organiser for the same WordCamp twice on the Organisers page. Deleting the second profile got rid of the badge again.

Clearing the username, updating and then adding it again seemed to do the trick - the badge appeared again.

Tested it with JJJ at #wcsf14 contributor day who suggested it had something to do with the fact that WordCamp organisers are not supposed to be a part of more than one organising team. He advised me to file it here.

It's a cool bug.

Change History (38)

This ticket was mentioned in Slack in #community by extendwings. View the logs.


11 years ago

This ticket was mentioned in Slack in #meta by extendwings. View the logs.


11 years ago

This ticket was mentioned in Slack in #meta by iandunn. View the logs.


11 years ago

#4 @adityakane
11 years ago

I had a similar issue - I was organizer for WordCamp Mumbai 2014 and now for 2015 - and my badge seemed to have disappeared. Removed the username, updated and added username and updated again - and issue was fixed - badge shows.

This ticket was mentioned in Slack in #meta by iandunn. View the logs.


11 years ago

#6 @nukaga
10 years ago

  • Cc nukagajunko@… added

She is the organizer team of “WordCamp Kansai 2014” and “WordCamp Kobe 2013”, “WordCamp Osaka 2012”.
But badge is not displayed.
Join in the activity is displayed.
This same bug?
https://profiles.wordpress.org/luchino_

#7 @iandunn
10 years ago

I tried removing their username from their speaker posts and then adding it again, because that normally will fix the problem temporarily, but that didn't work in this case. It may be a different bug, or just a different facet of this bug.

This ticket was mentioned in Slack in #meta by iandunn. View the logs.


10 years ago

This ticket was mentioned in Slack in #meta by iandunn. View the logs.


10 years ago

This ticket was mentioned in Slack in #meta by coffee2code. View the logs.


10 years ago

This ticket was mentioned in Slack in #meta by sergey. View the logs.


10 years ago

This ticket was mentioned in Slack in #meta by sergey. View the logs.


10 years ago

#13 @davidjlaietta
10 years ago

Confirming that this occurred for all organizers of WordCamp Orlando 2015 as well, for organizers that have been involved for more than one year.

This ticket was mentioned in Slack in #meta by ocean90. View the logs.


10 years ago

This ticket was mentioned in Slack in #meta by sergey. View the logs.


9 years ago

#17 @valeriosza
9 years ago

All organizer WordCamp Belo Horizonte 2016 too have problem.

This ticket was mentioned in Slack in #forums by williampatton. View the logs.


9 years ago

This ticket was mentioned in Slack in #community-events by bph. View the logs.


8 years ago

This ticket was mentioned in Slack in #community-events by andreamiddleton. View the logs.


8 years ago

#21 @SergeyBiryukov
8 years ago

#3055 was marked as a duplicate.

This ticket was mentioned in Slack in #community-team by bph. View the logs.


8 years ago

This ticket was mentioned in Slack in #meta by sergey. View the logs.


8 years ago

#24 @dejliglama
7 years ago

Have the problem too.

To fix, do I need to find the latest WordCamp that added me as a speaker, and ask them to remove and then re-add me ?

#25 @iandunn
7 years ago

That should work. You can also mention it in the #meta-wordcamp channel on Slack, and one of the devs re-can the badge.

This ticket was mentioned in Slack in #community-team by andreamiddleton. View the logs.


7 years ago

This ticket was mentioned in Slack in #meta-wordcamp by coreymckrill. View the logs.


7 years ago

This ticket was mentioned in Slack in #meta-wordcamp by iandunn. View the logs.


7 years ago

This ticket was mentioned in Slack in #community-team by nao. View the logs.


7 years ago

This ticket was mentioned in Slack in #meta by sergey. View the logs.


7 years ago

#31 @iandunn
6 years ago

Related: #703

This ticket was mentioned in Slack in #meta-wordcamp by iandunn. View the logs.


6 years ago

#33 @mimitips
6 years ago

Hi. I was a lead organizer of WordCamp Tokyo 2019, and had the same problem for a speaker.

It might be hard to fix this bug, but we might get a little better the operation.
I was wondering we should have the link to their profile nearby the input area of their WordPress.org ID in the wordcamp.org editor.

This ticket was mentioned in Slack in #meta-wordcamp by iandunn. View the logs.


5 years ago

This ticket was mentioned in Slack in #meta-wordcamp by iandunn. View the logs.


4 years ago

#36 @dd32
4 weeks ago

I think this has been resolved as of 2019, at least, for organisers/speakers who have spoken multiple times since 2019, via #703.

It appears that this is the commit that should've handled this on the WordCamp side (Which is what is telling us to add/remove the badge)

https://github.com/WordPress/wordcamp.org/commit/e406a0a523735f2414005ba98ce0f5d835c3457b

It's not clear if the user meta required for the above was backfilled to previous events, so it's possible that being a speaker in 2013, being marked as a speaker in 2025, and then having the 2025 speaker confirmation retracted could trigger the badge removal still.

This should likely be closed as a duplicate of #703 - I don't recall seeing many cases of reports of this same problem recently.

#37 @dd32
4 weeks ago

  • Keywords close added

#38 @dd32
4 weeks ago

  • Resolution set to duplicate
  • Status changed from new to closed

Data appears to have been backfilled. Marking as a duplicate of #703 as the underlying cause was the same.

Note: See TracTickets for help on using tickets.