Obsidian Registration Expired Discount Codes Throwing Exception #5430
Labels
Fixed in v14.3
Fixed in v15.1
Priority: High
Affects most production Rock installs in a way that will be noticed.
Topic: Event Registration
Related to Rock Event Registration.
Type: Bug
Confirmed bugs or reports that are very likely to be bugs.
Please go through all the tasks below
Please provide a brief description of the problem. Please do not forget to attach the relevant screenshots from your side.
When creating registrations for camps, we often have a series of discount codes for early registrations that expire before we expect final payment. On these registrations we do not require the total cost to be payed as soon as the registration is completed. This means that we often have people that used a discount code on their registration go back to make an additional payment on their registration after the discount code has expired.Previously, on the C# block, it would allow them to make the additional payment and it would keep the existing discount, even though the discount code is now expired. This is the expected result.The Obsidian block does not seem to have anticipated needing to be able to use expired discount codes and so when someone goes to make a payment on an existing registration that has an expired discount code, the block throws an unhandled NullReferenceException and redirects the user to an error page.The error page that is shown:
## Expected Behavior
Trying to make a payment on a registration with a discount code that was valid at the time, but has since expired should present the user with a payment screen that allows them to make additional payments. The existing discount code should still apply, even if it has expired since the registration was initially filled out.## Actual Behavior
Trying to make a payment on a registration with a discount code that was valid at the time, but has since expired presents the user with an error page.## Steps to Reproduce
Rock Version
14.3 (Although this is an issue from v13 - present)## Client Culture Setting
en-US
The text was updated successfully, but these errors were encountered: