Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Obsidian Registration Block Total does not match internal registration cost after discount applied. #5691

Closed
2 tasks done
rutledgek opened this issue Dec 7, 2023 · 5 comments
Labels
Fixed in v16.3 Status: Confirmed It's clear what the subject of the issue is about, and what the resolution should be. Type: Bug Confirmed bugs or reports that are very likely to be bugs.

Comments

@rutledgek
Copy link

Description

The Obsidian registration block total does not match the internal registration total when a discount is manually added to the registration. The Obsidian block shows a green success message that a discount was applied, but the discount is not reflected in the total.
Registration-Berwyn-UMC-RegistrationCost
Registration-Rock-RMS (1)

Actual Behavior

The total cost the obsidian block is showing for the registrar to pay is the full amount without the discount added manually.

Expected Behavior

The payment amount should be the same amount as shown on the internal registration

Steps to Reproduce

  1. Create a registration instance that has no cost but has fees. The fees should have a cost and allow for a quantity. Make sure that the fees have Discount Applies checked.
  2. Allow someone to register and select fees. In my instance they were 2 adults and 2 children for a total of 48.00.
  3. On the internal Rock Registration Edit page add a per registration discount of 8.00.
  4. Edit the registrant to ensure that discount applies is checked.
  5. Note that the total due on the registration is now 40.00.
  6. Send payment reminder email.
  7. When you click the payment reminder email, you will see a success alert that a discount of 8.00 was applied, but the total does not reflect that discount.

Issue Confirmation

  • Perform a search on the Github Issues to see if your bug or enhancement is already reported.
  • Try to reproduce the problem on a fresh install or on the demo site.

Rock Version

16.0

Client Culture Setting

en-US

@JDShuman
Copy link

JDShuman commented Dec 7, 2023

I tested this in our system (also running v16.0) and observed the same behavior.

@sparkdevnetwork-service sparkdevnetwork-service added Type: Bug Confirmed bugs or reports that are very likely to be bugs. Status: Confirmed It's clear what the subject of the issue is about, and what the resolution should be. labels Dec 7, 2023
@nairdo
Copy link
Member

nairdo commented Dec 14, 2023

@JDShuman We've attempted to reproduce this in the upcoming v16.1 without success. We made a number of updates to this block in both v15.3 and v16.1, so we can ask the alpha testers to confirm if they are able to reproduce this in their v16.1 alpha.

@JDShuman
Copy link

Thanks, @nairdo! We are thankful for the effort you and your team continue to pour into these issues. Thanks for going the extra mile in asking the alpha testers to focus some attention here.

@nairdo
Copy link
Member

nairdo commented Dec 15, 2023

@rutledgek When you say:

On the internal Rock Registration Edit page add a per registration discount of 8.00.

Do you mean put 8.00 into the "Discount Amount (per Registrant)" field?

Assuming this is the spot you are referring to, are you selecting a discount code or just applying a raw discount value without a code?

image

@rutledgek
Copy link
Author

add a per registration discount of 8.00.

Do you mean put 8.00 into the "Discount Amount (per Registrant)" field?

Just adding 8.00 discount without a code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed in v16.3 Status: Confirmed It's clear what the subject of the issue is about, and what the resolution should be. Type: Bug Confirmed bugs or reports that are very likely to be bugs.
Projects
None yet
Development

No branches or pull requests

5 participants