|
Dallas REIG
|
September 28, 2015 at 1:53 pm
Hello. I noticed that when a default ticket is saved, it does not save the WP User Capability required for purchasing this ticket.
Can that be added? It would help to not have to retype in a capability every time we create an event, which we create a lot of.
Also, as a nice to have, it is possible to make the field a drop down of available capabilities instead of having to manually type in one. This allows for ease of remembering what the capability is and prevents typos.
Thanks in advance.
|
|
Tony
|
September 29, 2015 at 6:17 am
Hi Maceo,
I’ve created feature request tickets for both of those features to be discussed and considered for a future version of Event Espresso.
One problem I can see with the dropdown is that the capability list could end up being rather long on some sites, not a major issue but something we take into consideration with new features.
|
|
Dallas REIG
|
September 29, 2015 at 7:51 am
Thanks Tony. Makes sense on the dropdown but the default save is most important cause then we only need to do it once and really wont need the dropdown.
|
|
Tony
|
September 30, 2015 at 3:20 am
We are currently looking into saving the capabilities for the default tickets.
It looks like a hook will need to added to core and an update released for the WP Users Integration Add-on to use that hook.
We will update this thread with any news on this.
|
|
Josh
|
October 7, 2015 at 2:26 pm
Update: Default Tickets now save the ticket capability with the new version of the WP Users Integration add-on.
|
|
Dallas REIG
|
October 7, 2015 at 2:40 pm
Awesome, thanks, I will take a look.
|
