You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in scheduletemplates/templates/admin/scheduletemplates/shifttemplate/shift_template_inline.html
To Reproduce
Steps to reproduce the behavior:
Login as admin or manager with permission to edit schedule templates
Make sure, at least one schedule template exists
Start to edit schedule template
Open Web Developer Tools or any other javascript console
See error
Additional context
As it seems, the error is not new to this release, but undetected in currently productive version too.
If intended feature is not used (anymore), code could be cleaned up and simplified.
The text was updated successfully, but these errors were encountered:
Django jQuery tabularFormset function exptects first parameter to be a
selector and second parameter to be options.
Seems it used to be different once upon a time and selector was not
required, because function is called on already selected object.
But ... an empty selector is good enough, so we make jQuery happy, for
jQuery being able to make us happy.
Now there's an "Add" link again show in inline tabular form. :)
Django jQuery tabularFormset function exptects first parameter to be a
selector and second parameter to be options.
Seems it used to be different once upon a time and selector was not
required, because function is called on already selected object.
But ... an empty selector is good enough, so we make jQuery happy, for
jQuery being able to make us happy.
Now there's an "Add" link again show in inline tabular form. :)
Describe the bug
In schedule template change page there's a javascript error:
Uncaught TypeError: options is undefined
Maybe it originates from jQuery javascript
in
scheduletemplates/templates/admin/scheduletemplates/shifttemplate/shift_template_inline.html
To Reproduce
Steps to reproduce the behavior:
Additional context
As it seems, the error is not new to this release, but undetected in currently productive version too.
If intended feature is not used (anymore), code could be cleaned up and simplified.
The text was updated successfully, but these errors were encountered: