Hughsp
Forum Replies Created
-
Forum: Plugins
In reply to: [SeatReg] Limit seats per userHi 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!
Forum: Plugins
In reply to: [SeatReg] Limit seats per userThanks for your follow-up!
- 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.
- You’re right, an interesting option to have. Unfortunately not the one we need though.
Thanks again!
Forum: Plugins
In reply to: [SeatReg] Limit seats per userThanks 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!
Forum: Plugins
In reply to: [SeatReg] Limit seats per userThat 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!
Forum: Plugins
In reply to: [SeatReg] Limit seats per userHi 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! 😊
Forum: Plugins
In reply to: [SeatReg] Limit seats per userHi,
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 ! 😊
Forum: Plugins
In reply to: [SeatReg] Limit seats per userBy 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!
Forum: Plugins
In reply to: [SeatReg] Limit seats per userHi!,
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!Forum: Plugins
In reply to: [SeatReg] Stripe not loadingHi!
Much better! 🙂 Ideally (I don’t know if possible) Stripe would not let you pay twice for the same booking even if you click in the link but at least removing the link is good although it looks a little funny to have the iframe refreshed whenever you jump in/out the tab.
Thanks very much for your quick fix!
Forum: Plugins
In reply to: [Germanized for WooCommerce] New MandateThank you!
Forum: Plugins
In reply to: [SeatReg] Stripe not loadingHi,
I think this change brought an important issue. Since now the Stripe gateway opens in a new tab/window, the original tab/window where the link to pay is available (the bar at the bottom with credit card icons) is still visible. That means that after paying in Stripe in the new tab/window, you can come back to the original one and click over the credit card icons to proceed AGAIN to the payment. I don’t know if there’s something wrong with my config. but at least I could make the payment again as many times as I like and even if I get the white empty page with the message “The payment is already proccessed or doesn’t exist”, ACTUALLY the payment went through in Stripe, charging as many times again for the same booking as times I clicked on the payment icons.
That could not happen before because everything was loaded on the same page and after the payment couldn’t go back (unless clicking on “back”) to the payment button. But now, it is very explicit.
Could you please double check in case it is not only me?
Thanks!
Forum: Plugins
In reply to: [SeatReg] Booking Modal windowThat makes sense 🙂 No worries! and thanks anyway for your support and implication with this plugin.
Forum: Plugins
In reply to: [SeatReg] Personal InformationIn my case it is for a school, so the users who are booking are families. When they book, they book as a family really, not individually (even if they book several seats). So in cases like that, even if the arrow helps, the purpose does not really apply.
Please point me in the right direction in case you think there could be an easy way to implement “one single set of personal info for all seats” workaround even if it’s manipulating part of the code.
Once again, thanks very much!Forum: Plugins
In reply to: [SeatReg] Booking Modal windowAwesome!… is there any estimated time for implementation?
Thanks in advance!
Forum: Plugins
In reply to: [SeatReg] Stripe not loadingHi!
Yes, I have “Booking redirect to status page” enabled.
Thanks for the update, that is awesome as a fix. Probably loading inside the iframe would be better in the future to avoid ad/pop-up blockers from blocking when opening a new tab/window. But anyway, that’s is a perfect workaround that works for me for now.
Thanks very much for your quick support!