- This topic has 4 replies, 3 voices, and was last updated 9 years, 3 months ago by
.
-
Posts
-
In the past this worked, but now the placeholder value for #_TRANSFER_NBR_BE97 is empty.
Using version 1.5.8 and WordPress 4.0.Ok, that was already in the previous version too, and the one before 🙂
But you caught it: the unique number only get generated when online payment was possible too.
This has now been corrected: the payment number gets generated if the booking price > 0.
I’ll release a new version for this today, until then see this change:Hi!
I need a “really” unique booking-ID or booking number.
New booking-ID and transfer number (#_TRANSFER_NBR_BE97) are created correctly on booking a seat an are unique – so far.
BUT: If e.g. the last booking is canceled, the previously booking-id and transfer number will be reassigned to a new booking! This can end up in troubles as well on payment as on booking issues.
Neither a previously used booking-id nor a transfer number should be reassigned, at least not for the same event!
The booking ID is an auto-increment, so should *never* decrease or get re-used. This means something is wrong in the db …
Hmmm … sorry for any inconvenience. You are absolutely right. Seems that i’ve bin friggin’ blind on my first test. Tested again today and watched all assigned IDs within the plugin and in the database. They where all unique, no reassign of any number.
Hope – if it happens again – that i can reproduce it.
Thanks for your quick answer!
- The forum ‘Bug fixed or feature request implemented’ is closed to new topics and replies.