Skip to content
This repository has been archived by the owner on Apr 29, 2022. It is now read-only.

Request: Edit the name of the speaker while updating the CFP #932

Closed
jlaurens opened this issue May 5, 2019 · 2 comments · Fixed by #934
Closed

Request: Edit the name of the speaker while updating the CFP #932

jlaurens opened this issue May 5, 2019 · 2 comments · Fixed by #934

Comments

@jlaurens
Copy link

jlaurens commented May 5, 2019

I have created my account with a google login which have a very special first name and last name : 'Marjôlen Rusée'.
When I submitted the CFP, the speaker name that I provided, 'LAURENS Jérôme' has been somehow modified by adding the first name of the google account name into 'LAURENS Jérôme Rusée', which is not appropriate.
May we have the possibility to edit this name while updating the CFP for example?

@umgelurgel
Copy link
Contributor

@jlaurens thanks for reporting this and sorry that your name got mis-adjusted by the system. For now, I can update the name associated with your account manually - to make sure I get the right account, could you send an email to helpdesk at europython.eu with the details of the email of the affected account and the name you'd like to be displayed? I'll take it over from there.

@artcz what do you think about giving users the ability to modify their speaker details, similar to how they can modify their talk proposals during cfp? I could add that and it could be reaused in #925

@artcz
Copy link
Contributor

artcz commented May 6, 2019

@umgelurgel yes, the data is stored in the AttendeeProfile and should be available for edit at all times, we just need to add a view that renders a correct form.

@artcz artcz closed this as completed in #934 May 8, 2019
artcz pushed a commit that referenced this issue May 8, 2019
* Add speaker edit views.

* Test speakers update view.

* Address review comments.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants