Permissions to view bookings

[Chris Hirst]

I have the Pro version installed, and I have created some test events by different event organisers and ticket purchases.

However, wen I log in as an event organiser I can see all the other events created, and all the ticket purchasers and buyers details. I cannot edit others details, just those of the logged in user.

My question is – is this how it should be? That is with any event organiser being able to see everyones events, and ticket purchase details? That seems a little odd as the contact details for each ticket buyer are available to view on screen.

Perhaps I have some permissions set incorrectly, but can you let me know if there is a fix for this please. It would seem more appropriate for an event organiser only to be able to see their own events, and bookees who have bought tickets for their events only.

Thanks for any help you can give.

[Tommy Johnson]

This is the same functionality I have with my implementation and there isn’t a business need to restrict access to all created events or purchaser lists. If that were to happen, I’d look at creating a custom helper plugin to modify permissions as I haven’t seen anything in the standard settings that would allow for such functionality.

[Chris Hirst]

Thanks for that. It does seem a little odd that event organisers need to be logged in to see. and manage, their own events, and while logged in they can see every other event AND email addresses of every ticket buyer for all events. It just does not look too professional and seems to open up access for anyone to ‘liberate’ email addresses.

I am allowing event organisers to take payment for their own ticket sales, and as such manage their bookees, so I would anticipate a number of event organisers on the system.

Are there any shortcodes to limit access? Maybe that would be the way to go

Thanks

[Stephen Harris]

This snippet will be prevent an event organiser from seeing bookings for other events.

Use with caution though, as it’s fairly low level (makes assumptions about the database schema, is not using a public API), and so you should check after a x.0.0 or x.y.0 in case it breaks (though there is currently no plans for the 3.0 or 3.1 release to do so).

https://gist.github.com/stephenharris/f441d7f5fd1fca9d49e4011848edbba5

[Author]

Posts