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

Changes in "Sub-folders and METS file groups" cannot be saved #4067

Closed
andre-hohmann opened this issue Oct 28, 2020 · 5 comments · Fixed by #4242
Closed

Changes in "Sub-folders and METS file groups" cannot be saved #4067

andre-hohmann opened this issue Oct 28, 2020 · 5 comments · Fixed by #4242
Labels

Comments

@andre-hohmann
Copy link
Collaborator

Problem

If in the project settings, the values in the "Sub-folders and METS file groups" are changed, the save-button does not turn blue and the changes cannot be saved.
Only if values in "Folder use" or "METS parameter" are changed, the save-button turns blue and the changes can be saved.

Solution

It must be possible, that changes in "Sub-folders and METS file groups" can be directly changed.

@solth
Copy link
Member

solth commented Nov 2, 2020

I cannot reproduce this error. Adding new folders and editing or removing existing folders all cause the "Save" button to be acitvated.
@andre-hohmann can you try again and be more specific about which action doesn't activate the button?

@andre-hohmann
Copy link
Collaborator Author

It occurs when changes are conducted in the following fields.

  • Generate images
  • Width / Scale / Resolution
  • Link in METS file
  • ...

If the following buttons are changed, the save-button turns blue:

  • Create empty folder on process creation
  • Validate contents
  • Copy on DMS export

Specifically, i wanted to change the width of the derivates and the save-button was not activated after the changes have been applied.

@solth
Copy link
Member

solth commented Nov 2, 2020

Thanks for the clarification. I just tested it again with the additional information you provided and it seems the problem occurs in the preview branch, but is already fixed in the master branch.

@andre-hohmann
Copy link
Collaborator Author

Perfect - thank you. I will have a look on it after the next update of the preview system.

@matthias-ronge
Copy link
Collaborator

Related: #3346

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

Successfully merging a pull request may close this issue.

3 participants