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

BUG - History data not showing #482

Closed
bradystroud opened this issue Apr 22, 2021 · 3 comments · Fixed by SSWConsulting/SSW.Rules.Content#784
Closed

BUG - History data not showing #482

bradystroud opened this issue Apr 22, 2021 · 3 comments · Fixed by SSWConsulting/SSW.Rules.Content#784

Comments

@bradystroud
Copy link
Member

bradystroud commented Apr 22, 2021

Cc: @pierssinclairssw
Hi,

The history data for this rule is not showing
https://www.ssw.com.au/rules/Employee-YOLO-Day

  1. Investigate and fix

Screen Shot 2021-04-22 at 5 09 44 pm
Figure: No history data

This could be related to #459 but we are not sure.

Thanks,

-Brady

AB#61208

@bradystroud
Copy link
Member Author

@bradystroud
Copy link
Member Author

Reopening as GitHub automatically closed this issue when it was linked to this PR SSWConsulting/SSW.Rules.Content#784

@bradystroud bradystroud reopened this May 9, 2021
@bradystroud
Copy link
Member Author

@pierssinclairssw

Hi,

  1. Investigate and fix

Done - This bug occurs when a rule URI is changed but the folder name is not. I updated the folder names in this PR SSWConsulting/SSW.Rules.Content#784 which fixed the issue.

Implementing Netlify CMS should make it possible to automate this process and reduces the chance of this issue happening again. See issue #470. Until that is complete, I will closely monitor rule URI changes and ensure the folder name is changed as well.

https://www.ssw.com.au/rules/Employee-YOLO-Day
Screen Shot 2021-05-10 at 3 08 39 pm
Figure: Fixed history data

Thanks,

-Brady

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant