Actions
Bug #2640
closedDirective configuration is broken on modify/disable/modify series
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
When you modify a directive, then enable/disable it, then modify it again, then enable/disable it, you don't get the expected final state:
- sometimes, when enable/disable is used, the state before the last modification is restored;
- sometimes, when you modify, the enable/disable state before the last enable/disable is restored.
This is clearly viewable in event logs, with enable/disable action also having parameter modification, and parameter modifications also modifing the status.
It's perhaps due to #2632
Updated by François ARMAND over 12 years ago
- Description updated (diff)
Updated by François ARMAND over 12 years ago
- Description updated (diff)
- Status changed from 2 to In progress
OK, so it seems that we update the form part from the component, but the form part does not include Remove/Disable button, and so we end up with desynchonized state between what the action linked to a button know, and what the actual state is.
Updated by François ARMAND over 12 years ago
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
Applied in changeset 17d64f13d098613a68ed6caf393c58acd5629249.
Updated by Nicolas CHARLES over 12 years ago
- Status changed from Pending technical review to Released
This seems corrects, thank you Francois
Actions