Can you confirm the transaction ID lack issue or I have to create a ticket?
Thanks
P.S. And if I manually enter the first possible transactions ID will the following fix pull the ID's stored now somewhere in mysql and get thing messed?
Today I have to lunch my site anyway or I will simply get fired. So let me know as fast as possible.
Thanks
vosto - still working on a good fix for when users click the browser back button. We all know that they should NOT be doing that, but still, we know that some will. I just updated a couple files in the package. Please download and replace these two files for now:
components/com_dtregister/views/event/tmpl/groupnum.php
components/com_dtregister/controllers/event.php
What this will give you is a REAL Back button on the group number page so if someone goes to the group page then changes their mind, hopefully they'll click OUR back button and not the one in the browser. If they do, all is well. So implement this and then there's no reason why you can't launch your site.
We're looking at fixes for improper back button usage still right now and do a full update soon with that and some other items that are in progress. The trick is weeding out those unwanted sessions while keeping good ones used for multiple event cart registrations.
Also, there is no problem with transaction ID storage in records. Probably just was missing when you were having your messed up transactions with the back button testing. I don't see a reason why you can't manually put those missing transaction IDs in now though. Thanks.
Everyone, regarding what was commented earlier about 100% discounts and such still requiring payment, this is fixed. Update now to 2.7.2e to make sure free events are handled appropriately. Now all should be good.... outside of the improper back button usage. We're treating that as a separate issue and it will require more testing to make sure a fix for that doesn't mess up the cart feature.