Actions
Bug #24563
closedJS error when opening directive form more than once
Pull Request:
Severity:
Trivial - no functional impact | cosmetic
UX impact:
It bothers me each time
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Small
Priority:
46
Name check:
To do
Fix check:
Checked
Regression:
No
Description
When in the groups page, when I click more that once either on an existing directive, or "Create" directive from a Technique, I get JS errors :
Uncaught Error: Your page is loading multiple Elm scripts with a module named Elm.Tags. Maybe a duplicate script is getting loaded accidentally? If not, rename one of them so I know which is which!
Uncaught Error: Your page is loading multiple Elm scripts with a module named Elm.FileManager. Maybe a duplicate script is getting loaded accidentally? If not, rename one of them so I know which is which!
Also the file manager cannot be loaded (and may not be useful at all) when opening an existing directive, there is a misplaced semicolon :
Uncaught SyntaxError: missing } after property list
This is an issue similar to #23400 and needs to be fixed by preventing the Elm JS files to be loaded each time the HTML/JS refreshes the rendering of the page
Updated by Clark ANDRIANASOLO 9 months ago
- Related to Bug #23400: JS error when clicking on a technique with several version in directive screen added
Updated by Clark ANDRIANASOLO 9 months ago
- Subject changed from JS error when clicking on any create directive button more than once to JS error when opening directive form more than once
Updated by Clark ANDRIANASOLO 9 months ago
- Status changed from New to In progress
Updated by Clark ANDRIANASOLO 9 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from Clark ANDRIANASOLO to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/5505
Updated by Clark ANDRIANASOLO 9 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|52a353b4ca435c06cb74fce8bc132190eec4b60e.
Updated by Vincent MEMBRÉ 9 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.0.7 which was released today.
Actions