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

Incorrect Lava in Default Scheduling Response Email #5993

Open
2 tasks done
mikedotmundy opened this issue Aug 29, 2024 · 0 comments
Open
2 tasks done

Incorrect Lava in Default Scheduling Response Email #5993

mikedotmundy opened this issue Aug 29, 2024 · 0 comments
Labels
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

@mikedotmundy
Copy link

Description

There is some incorrect Lava in the default Scheduling Response Email that results in the information being emailed.

  1. {{ ScheduledItem.Location.Name }} should be {{ ScheduledItem.Occurrence.Location.Name }}
  2. {{ ScheduledItem.Schedule.Name }} should be {{ ScheduledItem.Occurrence.Schedule.Name }}
Screenshot 2024-08-29 at 12 53 04

Actual Behavior

Incorrect Lava - see description above

Expected Behavior

Lava should be correct - see description above

Steps to Reproduce

  • Go to https://rockrmslatest.com/Communications/System/29
  • See incorrect lava as described above.

Issue Confirmation

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

Rock Version

v16.6, v17.0

Client Culture Setting

en-US

@sparkdevnetwork-service sparkdevnetwork-service added the Status: Confirmed It's clear what the subject of the issue is about, and what the resolution should be. label Aug 29, 2024
@chead4 chead4 reopened this Sep 4, 2024
@sparkdevnetwork-service sparkdevnetwork-service added the Type: Bug Confirmed bugs or reports that are very likely to be bugs. label Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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

3 participants