-
Notifications
You must be signed in to change notification settings - Fork 14
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
The status of "Publish Series on VIDEOPORTAL" does not get saved #212
Comments
The feature seems to me to be difficult to understand by design, I may need more information here: this is implemented (and works) in such a way that saving works if the following circumstances apply:
i can't say why this is the case, but it was already the case before. maybe we need to look at the feature together so that i understand it completely and why it has been implemented this way so far. |
Thanks for having looked into it. I was aware of the first two bullet points and have some reasons I'm happy to explain in a short meeting (see message in Element/Matrix). Maybe there, we could also come up with solution which is more reasonable or easier to understand. The third bullet point may cause the problem. In our template the additional templates only have READ activated, WRITE is not activated. So maybe saving the form independent of the status of READ and WRITE would be the solution. Let's discuss this in a short meeting. |
we remove the |
I did a retest with the merged PR #231 and can confirm that everything works now as expected. |
Describe the bug
If a course administrator activates the setting "Publish Series on VIDEOPORTAL", the chosen option does not get saved after clicking on 'Save'. The roles that get sent to Opencast are correct. But the setting "Publish Series on VIDEOPORTAL" gets shown as not activated. I assume that instead of saving and showing what was set, after hitting save the default template gets shown.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The chosen option should not get lost when clicking on "Save".
Environment (please complete the following information):
Additional context
I assume that the bug exists since merging the PR #186. Therefore, @chfsx could you please have a look at this issue?
The text was updated successfully, but these errors were encountered: