|
jaclyn goldberg
|
February 5, 2016 at 12:40 pm
I need to delete some custom Questions, but I can’t because we were doing some testing and have 2 attendees who answered those questions. I can’t delete the attendees because there are active transactions. I can’t find anywhere to delete the transactions. All of the info I find in the forums is about deleting transactions in EE4. We have to use EE3 because we need recurring events.
|
|
Josh
|
February 5, 2016 at 1:57 pm
Hi Jaclyn,
May I ask, what’s happening when you go to delete those questions? Normally when you go to delete a question in EE3, it will let you delete it even if the question has been answered somewhere. Along with that, you can delete attendees records from the Attendee Reports List table. I’m not aware of a limitation where those can’t be deleted due to an active transaction, but if you can share a link to a screenshot of what’s happening when you try to delete the test attendees/questions, we can look further into this.
|
|
jaclyn goldberg
|
February 5, 2016 at 2:07 pm
What happens is nothing. 😉 In the Questions screen, if I mouse over the Question I want to delete and click on the red delete link under it, nothing happens. The page does not even stop to thing or anything — it’s just like I did nothing at all. Ditto if I check the box next to it and click the “Delete Question” button. No response at all.
|
|
Josh
|
February 5, 2016 at 2:16 pm
Okay thank you for clarifying. Normally when you click that delete link it will fire a JavaScript alert that basically asks “Are you sure you want to delete?” If there’s a JavaScript error happening earlier on that page then that could prevent the alert from firing. Can you find out if the error is being caused by another plugin or the active WordPress theme? This is ruled out by temporarily switching to the default WordPress theme and temporarily deactivating any other installed WordPress plugins.
|
|
jaclyn goldberg
|
February 5, 2016 at 2:59 pm
I will give that a try later today. It’s not really a big deal right now, but I can see it being confusing later.
|
