|
Dan Korvas
|
December 28, 2012 at 1:24 pm
Hi,
I am having an issue where questions to an event can only be saved to an existing attendee. In other words, question data cannot be saved when adding an attendee. Once the attendee has been registered for the event the record can be edited. This appears to be a bug. Can someone confirm?
WP 3.42
EE 3.1.29.1.P
|
|
Jonathan Wilson
|
December 28, 2012 at 8:06 pm
Hi Dan,
I can’t seem to recreate this issue. Try to rule out any plugin conflicts. Deactivate all non Event Espresso plugins and test to see if the issue is still occurring. If it is not, then we know it is a problem with another plugin. You can then find out which plugin it is by reactivating each plugin individually and testing to see if the problem starts happening after the activation. When it occurs after activating a plugin, then we know this is the culprit.
Let us know whether you find it.
|
|
Mary
|
January 11, 2013 at 8:22 pm
I too am having problems with this. I’m using the Question Groups plugin. I create a set of custom questions for an event, and when I try adding an attendee directly from the admin interface, it doesn’t save the answers on the initial attendee insert. However, it will save them perfectly fine if I go back in and re-edit (do an update as opposed to an insert). Any thoughts??
|
|
Dan Korvas
|
January 14, 2013 at 9:55 am
Hi,
I have tried disabling all plugins and the issue remains. Can EE please investigate? Thanks.
|
|
Josh
|
January 14, 2013 at 10:02 am
Hi Mary,
I’ve tested this on a few sites and I am not able to reproduce this.
What are the question names and question types that you have set up for this event?
|
|
Mary
|
January 14, 2013 at 6:08 pm
We have 399 custom questions that are grouped into many different groups, so I can’t list them all here, but…
— These default ones seem to save OK, on first try, but our other custom ones fail at insert
Group Name: Personal Information
Group Identifier: personal_information-1350938158
First Name: TEXT
Last Name: TEXT
Email: TEXT
— Sample of Custom questions
1. Address: TEXT
2. Address 2: TEXT
3. City: TEXT
4. State: TEXT
5. Country: TEXT
6. Zip: TEXT
7. Phone: TEXT
8. Alt. Phone: TEXT
9. Mobile Phone: TEXT
10. Date of birth: TEXT
11. Participant ID Number: TEXT
12. Spouse ID Number: TEXT
13. May we mail or email information to you about the programs we offer?: DROPDOWN
14. May we call and leave a message at this number?: DROPDOWN
15. May we call and leave a message at your alt. phone?: DROPDOWN
16. May we send text messages and/or leave a message at this number?: DROPDOWN
17. When is the best time to call?: DROPDOWN
18. What is your primary language?: DROPDOWN
19. Gender: DROPDOWN
20. Ethnicity: DROPDOWN
21. Marital Status: DROPDOWN
22. Are you attending this workshop with a romantic/dating partner or spouse?: DROPDOWN
23. Choose ONE from the list to let us know where you heard about the workshop.: DROPDOWN
24. If you selected “Other” please specify: TEXT
25. How many persons in your household?: DROPDOWN
26. How much do you make a year (combined as a household)?: TEXT
|
|
Dan Korvas
|
January 17, 2013 at 10:21 am
Hi,
Is there any update on this? Thank you.
|
|
Josh
|
January 17, 2013 at 1:17 pm
Hi Dan,
Your original question was whether we could confirm this as a bug. We’ve checked and checked again across a few different sites, and can’t confirm it.
The next step would be to try updating any questions that have any non-alphanumeric characters like single quotes or double quotes. A few releases back we added some escaping to make sure questions that contained single or double quotes would not break the JavaScript that makes the additional attendee dropdown work. If you had earlier entered a question like that and later changed it, it may not have gotten properly recorded into the database at the later point if that happened after the update.
Can you check to see if there are any questions like that in the system? If there are, you can re-enter the question (with or without the quotes is fine) and save it. Then you can try registering in the admin again.
|
