-
Notifications
You must be signed in to change notification settings - Fork 63
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
Double setting for beginning of the year #3741
Comments
What happens, when issues for seasons with different starting month have to be created? The configuration in the ruleset is not flexible enough as the configuration in the frontend. |
This suggests leaving the input in the interface and deleting the setting in the ruleset. |
If it is possible, i am supporting the input in the interface. It is not unusual that one theater starts the season in August and another theater or a concert hall in September or even in October. I do not want to know what will come up, when other materials are digitized. |
In version 3, the beginning of the year must be defined in the ruleset.
In addition, a button for setting the start of the year exists in the calendar editor.
The beginning of the year must be entered exactly equal to the setting in the rule set, or processes with the wrong substructure are created, cf. issue #3637.
In addition, the dialog is too small to be usable:For layout of dialog, see #3846Further remark: It is confusing that a year is shown in the calendar that opens. One might think that one would have to go back to the beginning of the publication.How do we want to deal with it?
The text was updated successfully, but these errors were encountered: