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

[v16.0] Obsidian Following Event Type Detail Block Odd Behavior #5605

Closed
2 tasks done
mikedotmundy opened this issue Sep 16, 2023 · 6 comments
Closed
2 tasks done

[v16.0] Obsidian Following Event Type Detail Block Odd Behavior #5605

mikedotmundy opened this issue Sep 16, 2023 · 6 comments
Labels
Fixed in v16.1 Fixed in v17.0 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

The Obsidian Following Event Type Detail Block is exhibiting odd behavior. I have experienced this behavior 1), when adding a new Following Event Type and 2), when editing an existing Following Event Type.

See video:
https://github.com/SparkDevNetwork/Rock/assets/23226974/6c03a250-38b5-4b34-9448-93cf9c415b52

Based on my selection in the Event Type field, I have noticed incorrect Attributes for all of them at different times. I have not been able to figure out if there is one Event Type that is specifically causing the issue.

Also, while I was unable to reproduce this next result on the demo site (v1.17.0.2), this is what I am seeing on my dev site (v1.16.0.11):
Screenshot 2023-09-15 at 22 34 01

Actual Behavior

No issues adding/editing Following Event Types.

Expected Behavior

Issues with adding/editing Following Event Types.

Steps to Reproduce

See above.

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

v16.0, v17.0

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. Status: In Dev Queue This issue is being worked on, and has someone assigned. labels Sep 18, 2023
@mikedotmundy
Copy link
Author

mikedotmundy commented Sep 28, 2023

Will this be fixed in v16.0?

@sparkdevnetwork-service sparkdevnetwork-service changed the title [Alpha v1.16.0.11] Obsidian Following Event Type Detail Block Odd Behavior [v16.0] Obsidian Following Event Type Detail Block Odd Behavior Oct 3, 2023
@chead4
Copy link

chead4 commented Oct 9, 2023

@mikedotmundy HI Mike, this is planned to be fixed in v16.1

@PraveenMathew92 PraveenMathew92 added Fixed in v16.1 and removed Status: In Dev Queue This issue is being worked on, and has someone assigned. labels Oct 16, 2023
@sparkdevnetwork-service sparkdevnetwork-service added the Type: Bug Confirmed bugs or reports that are very likely to be bugs. label Nov 9, 2023
@chead4
Copy link

chead4 commented Nov 28, 2023

@mikedotmundy HI Mike, I wanted to keep you updated on this issue. We were planning to have this issue fixed in v16.1 but it is more complex than expected and will take longer to resolve.

@sparkdevnetwork-service sparkdevnetwork-service added the Status: In Dev Queue This issue is being worked on, and has someone assigned. label Nov 28, 2023
@jasonhendee
Copy link
Contributor

@mikedotmundy sorry for the back-and-forth on this issue. We spent some time yesterday getting to the bottom of it, and determined the following:

You've actually reported 2 separate issues:

  1. The video you provided from rockrmslatest.com showcases an issue where the attributes for a given Following Event Type fail to properly load as a whole.
    • This issue is not present in v16.0 or 16.1 of Rock; it was not introduced until very recently.
    • This issue was not fixed in commit f4fb9ce, which is why we re-opened the issue.
  2. The screenshot you provided (from your dev site) showcases an issue where Note Type Field Type attributes - specifically - failed to load.

Given this info, just know that we'll be closing this issue soon, once we've properly tackled both issues, but also know that v16.0 & v16.1 of Rock should no longer exhibit either issue.

@mikedotmundy
Copy link
Author

mikedotmundy commented Dec 7, 2023

Thank you @jasonhendee - No need to apologize - I appreciate you looking into this. So far as I can tell, the issue seems to be cleared up in my Alpha v16.1 instance. Are you saying that I should still be seeing a part of the issue in v16.1 Alpha?

@jasonhendee
Copy link
Contributor

So far as I can tell, the issue seems to be cleared up in my Alpha v16.1 instance.

@mikedotmundy This sounds correct; you should no longer be seeing the issue v16.1 Alpha. Thank you for confirming!

@sparkdevnetwork-service sparkdevnetwork-service removed the Status: In Dev Queue This issue is being worked on, and has someone assigned. label Dec 8, 2023
@nairdo nairdo added Status: In Dev Queue This issue is being worked on, and has someone assigned. Fixed in v16.1 labels Dec 8, 2023
@sparkdevnetwork-service sparkdevnetwork-service removed the Status: In Dev Queue This issue is being worked on, and has someone assigned. label Dec 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed in v16.1 Fixed in v17.0 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

6 participants