WordPress.org

Making WordPress.org

Opened 5 years ago

Closed 5 years ago

#441 closed enhancement (fixed)

Capture the WordPress.org Usernames of WordCamp Attendees

Reported by: iandunn Owned by:
Milestone: Priority: normal
Component: WordCamp Site & Plugins Keywords: ux-feedback
Cc:

Description

We need to capture the WordPress.org usernames of WordCamp attendees so that we can incorporate that data on profiles.wordpress.org.

I've started work on this by creating a CampTix addon that requires the user to login before purchasing a ticket. Since WordCamp.org shares a user table with WordPress.org, that will get us their username.

It's been a few weeks since I had time to work on it, but IIRC the login workflow is working, but may need some finishing touches.

After that, we needs to store the username in the attendee meta, and then we need to update the notifier to push that to profiles.wordpress.org, and the activity handler to accept it. Storing the wporg username in attendee meta will eventually happen in the private camptix-extras plugin, but it can be built into the addon for now and I'll migrate it before deploying.

We also need to improve the notice on the login page to help users understand that they need to login with their WordPress.org username, and help them create one if necessary. Without this, many will be confused and try to login with the credientials from their self-hosted site.

@jenmylo, can you fill in any details that I missed?

Attachments (4)

camptix-require-login.diff (2.8 KB) - added by iandunn 5 years ago.
wcorg-login-message.php (981 bytes) - added by iandunn 5 years ago.
camptix.diff (3.9 KB) - added by nvwd 5 years ago.
added some hooks to camptix - they allow adding the meta to the attendee cpt
require-login.diff (6.4 KB) - added by nvwd 5 years ago.
completed the require login and added the functions to utilize the new camptix hooks to add the username attendee meta

Download all attachments as: .zip

Change History (15)

This ticket was mentioned in IRC in #wordpress-meta by iandunn. View the logs.


5 years ago

#2 @nvwd
5 years ago

  • Cc nowell@… added

#3 @nvwd
5 years ago

@iandunn,

Looking at camptix.php near line 5814, the form_checkout function starts looping over each attendee to insert the cpt(s). When someone purchases a block of tickets, we will only be able to capture the .org username for the person making the purchase.

This may have to be an optional piece of data for the attendee form.

Your thoughts?

cc: @jenmylo

#4 @iandunn
5 years ago

That's a good point. I don't think it will change the overall architecture, so it might be simplest to just start with the use case for buying a single ticket, and then add support for multiple tickets once that's finished and launched.

But yeah, I think we'd probably want to inject an extra field into the ticket questions to prompt for each attendee's wporg username.

This ticket was mentioned in IRC in #wordpress-meta by NowellVanHoesen. View the logs.


5 years ago

@nvwd
5 years ago

added some hooks to camptix - they allow adding the meta to the attendee cpt

@nvwd
5 years ago

completed the require login and added the functions to utilize the new camptix hooks to add the username attendee meta

#6 @nvwd
5 years ago

@iandunn,

The functions add the username field to attendee forms and save it in postmeta.
I have not commented any of the code yet.

Looking forward to any feedback.

#7 @iandunn
5 years ago

This looks really good, thanks @nvwd :)

@jenmylo, I took a few screencasts so you could see the workflow and give feedback.

  • Case 1: User has existing WordPress.org account and logs in via link in notice
  • Case 2: User has existing WordPress.org account and is forced to login after clicking Register button
  • Case 3: User doesn't have existing WordPress.org account and creates one

#8 @iandunn
5 years ago

  • Keywords ux-feedback added; needs-patch removed

I committed @nvwd's code in efb459dd54...467f96e3f5, and activated it for http://testing.wordcamp.org/tickets/ (but not the rest of wordcamp.org yet).

I think the workflow for users who already have an account and just need to login is pretty good, but it's not so great for those that need to create a new account, so we might want to look at some improvements to that process as part of this effort.

#9 @webvisuals
5 years ago

A thought on the workflow would be when the user clicks on the register button to have the registration information popup inside a shadowbox effect. This way the user still feels like they are on the same site while registering instead of the disconcerting effect of being taken to a different page to register for a wordcamp.

#10 @nvwd
5 years ago

@webvisuals,

Have the registration process in a popup like the new media manager? Backbone registration.

cc: @iandunn

#11 @iandunn
5 years ago

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

This was used for WCSF and worked, but it turned out to be kind of an ugly hack (see #595:comment:2), so we may decide to do it differently in the future.

Regardless, this ticket can be closed, and we can open a new one for any iterative improvements or refactoring.

Note: See TracTickets for help on using tickets.