Project

General

Profile

Actions

Bug #2640

closed

Directive configuration is broken on modify/disable/modify series

Added by François ARMAND over 12 years ago. Updated over 12 years ago.

Status:
Released
Priority:
1 (highest)
Category:
Web - Config management
Target version:
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

Actions #1

Updated by François ARMAND over 12 years ago

  • Description updated (diff)

So, it does not seems to be link to #2632, because even when reverting the linked commit (c9e9ac57), the bug is here.

Actions #2

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.

Actions #3

Updated by François ARMAND over 12 years ago

  • Status changed from In progress to Pending technical review
  • % Done changed from 0 to 100
Actions #4

Updated by Nicolas CHARLES over 12 years ago

  • Status changed from Pending technical review to Released

This seems corrects, thank you Francois

Actions

Also available in: Atom PDF