Problem
From a customer
I have discovered that the wording on the buttons when an AN tries to enroll in an event can be confusing. Some people interpret "Sign up" to mean sign up for the event rather than sign up for Open Social, and members who have accounts have encountered difficulty by clicking that option.
What do you think about changing the design to have buttons that say something like "Create an Account" "Log In" "Enroll as a Guest" and removing the "Enroll with account" and "Enroll without account" headings?
Solution
Change "Sign up" in the modal to "Create an account" and change "Sign up as guest" to "Enroll as guest".
As discussed with Xinyu and Natasha:
I think the problem is the sign up button. I agree that we should change the 'sign up' button into 'Create an account'.
I don't think we should remove the headings though, they are used to categorise these 2 options conceptually.
- Create an account
- Log in
- Enroll as guest
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | after_patch-3045772-6.PNG | 8.76 KB | Akanksha92 |
| #4 | 3045772-3.patch | 1.61 KB | kavbiswa |
Comments
Comment #2
Akanksha92 commentedComment #3
kavbiswa commentedComment #4
kavbiswa commentedPlease find the attached patch.
Comment #5
kingdutchChanges look good to me : ) Thanks!
Comment #6
Akanksha92 commented@kavbiswa the patch looks good. The patch applied to the module successfully. Please find the attached screenshot for the same.
Comment #7
kavbiswa commentedThanks for the review :)
Can you please give the fix credits ?
Comment #8
jaapjan commentedWill be in 5.x. You'll get the credits after it is released.
Comment #9
kavbiswa commentedThanks @jaapjan
Comment #10
kingdutchHi Kavbiswa,
Just some post merge feedback for future improvements to patches that I didn't come around to before :)
In Open Social we test using Behat. It's usually useful to check for texts that are changed in a ticket to also check if they appear in the Behat tests. If you don't know how to alter them there then you can leave a note in the ticket that some more work is needed. In this case I changed the tests after the ticket.
When you create a patch, be sure to create it from the root of the module or distribution. In this case your patch was made from your web root. This means that automated tools will not be able to apply it. You can see this by the patch containing
profiles/socialin the file paths. In this case thesocialfolder would be the root so you'd have to end up with onlymodules/social_features/social_event/modules/social_event_an_enroll/templates/event-an-enroll-dialog.html.twigas file path (from inside thesocialfolder).Thanks for your contribution!
~ Kingdutch
Comment #11
kingdutchSilly browser, changing the status.
Comment #12
kavbiswa commentedThanks @Kingducth for the inputs