|
Atharveda
|
November 17, 2016 at 5:10 am
Hi,
1. In our application, user provides us the event details & we as a admin submit/publish the event. In our application, when user login, he lands on his personal dashboard. We want to show the user his event that admin has published. Since admin posts the event, events are assigned to admin. Is there someway so that we can assign/map the event to another user?
2. EE4 Ticket Scanning Add-on provides a shortcode for ticket scanning. In our case, user who has submitted the event can verify the tickets from his dashboard by login into our application. Currently it shows all the events in the drop down, we want the user to see only the event he/she has posted & not the other events in the drop down. How can we achieve this? If there is no such option, please provide us some technical advice as to how we can do this by some hooks or extending the functionality?
Thanks,
Atharveda
|
|
Josh
|
November 18, 2016 at 9:03 am
The solution to both 1&2 involves assigning the user as the Author of that event. They’ll need a user account with a role that has ‘level_1’ capability added to it. That same user role will need the ‘read_others_events’ capability removed.
There’s more information about Event Espresso 4’s capability system in this documentation wiki:
https://eventespresso.com/wiki/event-espresso-4-roles-permissions/
|
|
Atharveda
|
November 19, 2016 at 3:44 am
Thanks Josh.
I created an user & assigned him “Events Administrator” role & removed the “read_others_events” capability from this role. Now when i login with this user, i still can see the other events in drop down. Please check the screen shot below:
http://pasteboard.co/t489A7F5X.png
Only user’s own event should be visible in dropdown & not all the other’s events.
Thanks,
Atharveda
|
|
Josh
|
November 22, 2016 at 8:37 am
Hi Atharveda,
Someone will need to add that feature to the ticket scanning add-on. I’ll update this thread when there’s something available for testing.
|
|
Atharveda
|
November 22, 2016 at 10:22 am
Thanks Josh. Any estimated timeline for this?
In the meanwhile, can you please help us technically as to how we can implement this feature in the ticket scanning add-on? In form of some plugin or something so that we can update EE4 plugin without overriding this fix?
Thanks,
Atharveda
|
|
Josh
|
November 22, 2016 at 12:55 pm
In the meanwhile, can you please help us technically as to how we can implement this feature in the ticket scanning add-on? In form of some plugin or something so that we can update EE4 plugin without overriding this fix?
No I’m afraid not. Like I mentioned before, there’s a developer that’s been tasked to work on this issue. How long it takes to fix this will depend on what’s involved with making the fix happen. I’ll be sure to update this thread when we have something that’s ready for testing.
|
