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

Unstable - Channel with imported resources changes to 'Unpublished View-only' #4647

Closed
pcenov opened this issue Aug 15, 2024 · 1 comment · Fixed by #4733
Closed

Unstable - Channel with imported resources changes to 'Unpublished View-only' #4647

pcenov opened this issue Aug 15, 2024 · 1 comment · Fixed by #4733
Assignees
Labels
bug DEV: frontend P0 - critical Priority: Release blocker or regression TAG: regression

Comments

@pcenov
Copy link
Member

pcenov commented Aug 15, 2024

Observed behavior

If I create a new channel and import some resources from one of my other channels then when I open both channels in 2 separate browser tabs I am seeing a 'Unpublished View-only' text for a channel with imported resources and the following error in the console:
Uncaught (in promise) TypeError: Invalid key provided. Keys must be of type string, number, Date or Array<string | number | Date>.

Expected behavior

It should be possible to keep editting a channel with imported resources when using multiple browser tabs.

Steps to reproduce the issue

  1. Go to https://unstable.studio.learningequality.org/en/accounts/#/ and sign in
  2. Create a new channel and import some resources from one of your existing channels
  3. Open both channels in 2 separate browser tabs and observe the incorrect behavior

Additional information

invalid-key-error.mp4

Console logs

invalid_key.log

Usage Details

@pcenov
Copy link
Member Author

pcenov commented Aug 15, 2024

@radinamatic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug DEV: frontend P0 - critical Priority: Release blocker or regression TAG: regression
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants