Making WordPress.org

Opened 9 years ago

Closed 2 years ago

#683 closed defect (bug) (fixed)

Profile: WordCamp Speaker badge missing from profile

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

Description

I have confirmed as a speaker of WordCamp Tokyo 2014 3 weeks ago.
But my profile page has no speaker badge.

Change History (31)

#1 follow-up: @iandunn
9 years ago

I see two activity items for the badge being added, so it looks like it was added, then removed, then added a second time, then removed a second time. Your Speaker post currently has your WordPress.org username, so it looks like a bug. Possibly related to #681.

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


9 years ago

#3 in reply to: ↑ 1 @extendwings
9 years ago

@iandunn
I'm a speaker of 2 sessions at WCT2014. I guess that this may be related to badge disappearance.

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


9 years ago

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


9 years ago

#6 @thewanderingbrit
9 years ago

I'm in the same position. I spoke at WordCamp Orlando 2013, and noticed a badge on my page several months ago, but then it disappeared. Most recently, I spoke at WordCamp Tampa, but still don't have the badge. Not sure where .org pulls this information from…?

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


9 years ago

#8 follow-up: @Idealien
9 years ago

I'm in the same boat as well. Spoke at WCToronto a few years ago:
http://wordpress.tv/2008/10/27/wordpress-beyond-a-blog-slides/
http://wordpress.tv/2009/01/14/wordcamp-toronto-2008-jamie-oastler-on-pushing-wordpress-beyond-blogging/

What's the connection point between profile and badge and/or is there any way to help make it work from profile / user side of things?

#9 in reply to: ↑ 8 @iandunn
9 years ago

Replying to Idealien:

What's the connection point between profile and badge and/or is there any way to help make it work from profile / user side of things?

The organizers of the camp control who is added from within wp-admin of the camp's site. Until the bug is fixed, the only workaround is for them to remove and then re-add your WordPress.org username from your Speaker post on the site.

#10 @iandunn
9 years ago

  • Summary changed from Profile: WordCamp Speaker Badge to Profile: WordCamp Speaker badge missing from profile

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


9 years ago

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


9 years ago

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


9 years ago

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


8 years ago

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


8 years ago

#17 @iandunn
7 years ago

#2142 was marked as a duplicate.

#18 @anthonydpaul
7 years ago

I did some testing from the organizer side. The easiest remedy is removing a speaker's org username from within their speaker profile in the WordCamp's wp-admin panel, then re-adding their org username and saving.

Notes:

  • If you save only it will not add the activity. (You have to remove the username and add it again.)
  • When you add the activity, it is timestamped as a current activity even though the WordCamp is likely over.
  • If you do the remove/add/save recursively, the activity will show up in the speaker's profile twice for the same WordCamp.

I noticed the activity is only missing from my original speakers because their org username was submitted as part of their application. Speakers I added later as replacements already had the speaker activity because I manually added their org username.

I suspect the function that registers the activity is not getting run when the speaker applies (which makes sense) and it is prevented from running every time the post is updated, unless the username value changes. That means it's also not getting run when the speaker is published, because the value for the username is not changing.

To remedy this, the activity would need to be part of the publish action rather than the create action. However, speakers who get published also sometimes do not end up speaking. A better approach may be to not tie this activity feature to the profile management process at all and to instead schedule a task to grab all published speaker org usernames on the date of the WordCamp—to run the activity bot one single time with the latest schedule.

Last edited 7 years ago by anthonydpaul (previous) (diff)

#19 @SergeyBiryukov
7 years ago

#3055 was marked as a duplicate.

#20 @SergeyBiryukov
7 years ago

#3056 was marked as a duplicate.

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


6 years ago

#22 @mrwweb
6 years ago

Quick note; I just noticed all the WC Seattle organizers didn't have organizer badges. The same bug and workaround apply to that post type.

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


6 years ago

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


6 years ago

#25 @iandunn
5 years ago

#3860 was marked as a duplicate.

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 by sergey. View the logs.


5 years ago

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

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


3 years ago

#31 @sippis
2 years ago

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

Going to close this ticket. There's already #681 to track the issue, I think everyone reported here as their badge now and Community Team has now procedures to handle similar reports in #community-events channel on Slack or via email.

Note: See TracTickets for help on using tickets.