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 Fee options hidden if a "Max Available" is not set and "Hide When None Remaining" is checked #5635

Closed
2 tasks done
leahjennings opened this issue Oct 17, 2023 · 1 comment
Labels
Fixed in v15.3 Fixed in v16.1 Status: Confirmed It's clear what the subject of the issue is about, and what the resolution should be. Topic: Event Registration Related to Rock Event Registration. Type: Bug Confirmed bugs or reports that are very likely to be bugs.

Comments

@leahjennings
Copy link
Collaborator

Description

We often have Registration Templates setup to where there is a Fee (set to Multiple) that has options with max available quantities and some that don't have a maximum. The ones that don't have a maximum, we just leave the Max Available blank for that option (see screenshot for example).

With the new Obsidian Registration block, if the "Hide When None Remaining" is checked, then any option that doesn't have a max available set is assumed to be "none left" and is hidden.
image

If Hide When None Remaining is not checked, then the fees without a Max Available set show up as expected and are able to be selected.

I saw bug #5408, but I believe this is different (albeit possibly related).

Ignore the purple in the screenshots, I promise I was on the demo site - someone else just must've been in there testing, too. 😄

Actual Behavior

When there is a fee [Options = Multiple] configured on a template, any option that doesn't have a Max Available set will be hidden if Hide When None Remaining is checked. Rock is assuming that an empty Max Available value should be 0 in that specific circumstance.

image

Expected Behavior

I would expect that Rock would assume that an empty Max Available value means there is no maximum.

Steps to Reproduce

  • On the demo site, navigate to Tools > Event Registration
  • Expand the General template category and click on Summer Camp
  • Edit the template, click to expand Fees, and then click the pencil for the Camp Shirt fee
image
  • Check the box for Hide When None Remaining
  • Add quantities to two of the sizes' Max Available, then click Save
image
  • Save the template
  • Click the + button to add a new instance of the template Summer Camp
  • Name it whatever you'd like, then click to Save
image
  • Click on the Linkages tab and create a new linkage
image
  • Navigate to Admin Tools > CMS Configuration, then click on Pages
  • Expand External Website > Calendar, then click on Registration
  • Remove the legacy "Registration Entry" block and add the new Obsidian Registration Entry block
image image

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

Rock McKinley 15.1 (1.15.1.1), 16.0 (1.16.0.12)

Client Culture Setting

en-US

@sparkdevnetwork-service sparkdevnetwork-service added 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. Status: In Dev Queue This issue is being worked on, and has someone assigned. labels Oct 17, 2023
@cabal95
Copy link
Member

cabal95 commented Oct 20, 2023

Hey @leahjennings, thanks for the detailed screenshots and reproduction steps. This got fixed today as part of commit d952a13. We found a number of issues internally related to some edge cases with how the new Obsidian Registration Entry block handles fees in commit.

I ran your test against the updated code and I believe it has also fixed the issue you saw.

image

image

@cabal95 cabal95 closed this as completed Oct 20, 2023
@cabal95 cabal95 added Topic: Event Registration Related to Rock Event Registration. Fixed in v16.1 Fixed in v15.3 and removed Status: In Dev Queue This issue is being worked on, and has someone assigned. labels Oct 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed in v15.3 Fixed in v16.1 Status: Confirmed It's clear what the subject of the issue is about, and what the resolution should be. Topic: Event Registration Related to Rock Event Registration. Type: Bug Confirmed bugs or reports that are very likely to be bugs.
Projects
None yet
Development

No branches or pull requests

3 participants