Limit seats per user

Would they still be able to skip the restriction by creating a new user on WordPress site?

Hi!,

Apologies for explaining myself so badly… I managed (probably not in the best way possible) to introduce a new column in the seatreg_bookings table with the currently logged wordpress user ID. That way each booking has all its information + the user ID of the user who made the booking.

Where I’m stuck is in the verification that would consist on doing: if the current user has booked more than X seats for this particular event, then display an error message. That is, basically to introduce a limitation per WP user and event. It is too complex for my knowledge but probably simple for you since actually you already implemented that!… it’s just that instead of using the current WP user ID you used the email address introduced in the booking form.

That would provide the extra flexibility that I would need for the implementation in our school, making the plugin ready to be used! ??

Does it make more sense now?… Sorry again for my poor explanations and thanks a bunch for your help!

By the way, just to provide more background, I used the action seatreg_action_booking_submitted to introduce the WP user ID in the table, but I’m not sure if that was the right place.

Thanks!

But user can still make many WordPress accounts on your site? That way he/she can bypass the limitation and create more than one booking. Are WordPress account creation limited by somehow?

Hi,

Yes, sorry again. The user’s account creation is limited by the ultimate members plugin, but the reference we are interested in is simply the wp user id. Users are forced to register filling a mandatory field (national id) that must be unique (and that is contrasted from a list of defined values), therefore no duplicated users could exist. Certainly there could be ways around it but most probably not happening in our school.

Thanks a lot ! ??

Okay I see. Will create the tasks to implement this feature.

Hi again thesiim,

The other features (one personal info for al seats and more direct check-out with less modal windows) are supernice improvements but the process is still operational for us with things as they are right now. So that’s good.

However this feature is definitely a requirement for our user case (it could be a mess if more seats are booked per user).

Once it is ready we will test the app, which is expected to meet its purpose of counting/verifying seats with the QR, and then this will become the perfect plugin to meet our needs in the school. Congrats on this full-featured plugin! ??

Thanks in advance for you work and support and we’re looking forward to hearing from your updates! ??

Hey. I updated the plugin to version 1.52.0
It now has 2 new options you can use.
One of them allows only logged in users to make bookings. The other will set the limit how many bookings can one logged in user make.

That is very awesome, thank you!… Just a few notes for future improvement:

• When you say “Max bookings per WordPress user” actually.. shouldn’t it say “max. seats per WP user”? For example, with a limitation of 2, a user could book 2 seats, in the same booking but also in 2 different booking processes (1 each time).
• I set the limit per WP user to 2, also the option “max. seats per booking” to 3. The result was that on a first booking I could actually book 3 seats. In a second booking with the same user, then I got the max. seats per WP user warning. That means that “max seats per booking” has to match the limit per WP user if you really want to enforce the WP user limitation. Ideally that could be mentioned in the options. Alternatively, a possible improvement would be to give priority to the “Max bookings per WP user” option over the “max. seats per booking” just to make sure the first is enforced.
• When the “same email” limit is reached, a message in red is displayed at the bottom of the form when filling the infomation. Nice. However, when the “wordpress user” limit is reached, a message with the image of a monkey with broken wires is displayed… not bad, but it suggests more an error than a restriction which can be a little confusing.

I’m sorry for being a pain! but I hope it helps improve the plugin. That’s all for now, I need to do more testing and will let you know if I find anything else.

Thanks for your great support and development!

The “Max bookings per WordPress user” option specifies how many bookings can user make (one booking can have many seats and that can be configured separately).

The second point you made is little confusing. Might be related to the fact that one booking can have many seats.

I will create a task to make the “wordpress user” limit reached message better (so no monkey picture will be shown =) ).

Thanks for your quick reply!

Apologies for being a little confusing, let me try again:

1- You say: “The ‘Max bookings per WordPress user’ option specifies how many bookings can user make”. In that sense:

I set that option to 1. However I could make 2 bookings of 1 seat each with same WP user: bug?

2- To limit bookings per WP user was never the request of this support entry. It is irrelevant for us and I think it is also in general for the plugin itself. Why would I not allow a user to book more seats later if they want, as long as the total number of seats allowed is respected?

What we relly need is to limit the number of seats per WP user and event (what you call “registration”).

I.e.: We need WP users to be able to book as many times as they want, as long as they do not exceed the limit of seats each event has assigned (not per booking).

I hope it helps to better understand the purpose and thanks again for your great support!

1. Do you also have “Booking email verification” turned on? Booking can have 3 states (waiting, pending, approved). When booking is in the waiting state (with email verification) it will not be taken into account (on the first step of validation) when checking the max booking limit. After the email verification it is taken into account.
2. I think I now understand. Yes the “bookings per WP user” is not really what you wanted but I think someone still might need it.
   
   I will create a ticket to add the total allowed seats per WP user.
   Thank you for providing valuable feedback.
   

Thanks for your follow-up!

1. No, I never used or tested “Booking email verification”. Actually I could reproduce the issue again: “Max bookings per WP user” set to 1, “Max seats per booking” set to 2. Result: I could make 2 bookings of 1 seat each one with no problems just by refreshing the registration page on the front end using shortcode.
2. You’re right, an interesting option to have. Unfortunately not the one we need though.

Thanks again!

Updated the plugin to version 1.53.0
It adds the feature you are looking for and also fix the “Max bookings per WP user”

Hi Siim,

I have no words. The issue was fixed and the new feature was implemented perfectly (including error messages). After some testing I could not find any issues and it meets all our requirements!

Now I’m trying to customize some minor details in the code (redirect to homepage after payment, adding the other parent user_id to check limitation (this one more particular to our case), custom messages, etc. but all looks very promising.

I can thank you enough!… Once we complete the final customizations we will buy the APP for final working test and will let you know if we have any other questions.

Thanks very much for your quick support and excellent work!