• 1

Read this first!

We do not monitor these forums. The forum is provided to exchange information and experience with other users ONLY. Forum responses are not guaranteed.

However, please submit a ticket if you have an active subscription and wish to receive support. Our ticketing system is the only way of getting in touch with RSJoomla! and receiving the official RSJoomla! Customer Support.

For more information, the Support Policy is located here.

Thank you!

TOPIC: attendees workflow

attendees workflow 6 years 1 month ago #37934

Hello,

the attendees feature lacks of two features plus one improvement in my point of view - or please suggest sth to get it to work.

FIRST
Usually an attendee is able to book more than one ticket of events. Visitors are booking these often at our site, and I believe some other RSEvents admins would report the same.
But the visitor is not able to change the amount of tickets, he / she just could cancel the whole subscription. That is not appropriate.
Think, that the visitor just had one less participant because a friend became sick or sth like that. He/she could only cancel the whole subscription and do a new one. Is there another way in RSEventsPro? The described way is awkward and not user friendly.

SECOND
The website is used for subscribing to daily events. The admin needs emails for each action the visitors took, even cancellation of events. But such an email is not available. All other actions are included, but not cancelling?
How to achieve this?

THIRD
Plus, sometimes visitors accidently deleted their subscription, see FIRST task as example, but at a cancellation the whole case is completely deleted instead of setting a status like 'cancelled' - so the admin is not able to check earlier / cancelled subscriptions.
That is also an awkward and unusual behaviour of ticketing systems. The admin is not even able to check if there were some earlier status updates or changes. How could we (or you) resolve this without extending the core component?
FIRST & THIRD together are resulting in a not very well usuable event submission component.

---
I may, we are not the only ones who does need these improvements of usuability to use RSEvents for ticketing missions. So, please, lean us a hand to get these tasks solved, these standards should work in such a component, imho.

Best regards,
Pierre.
The administrator has disabled public write access.
  • 1

Read this first!

We do not monitor these forums. The forum is provided to exchange information and experience with other users ONLY. Forum responses are not guaranteed.

However, please submit a ticket if you have an active subscription and wish to receive support. Our ticketing system is the only way of getting in touch with RSJoomla! and receiving the official RSJoomla! Customer Support.

For more information, the Support Policy is located here.

Thank you!