6.0.0-beta1
7/4/25

[#13643] wrong rule disabled/enabled after sort
Summary wrong rule disabled/enabled after sort
Queue Ingo
Queue Version 3.2.1
Type Bug
State Resolved
Priority 2. Medium
Owners mrubinsk (at) horde (dot) org
Requester lukas.weiss (at) raiffeisen (dot) it
Created 10/21/2014 (3909 days ago)
Due
Updated 07/27/2015 (3630 days ago)
Assigned
Resolved 07/27/2015 (3630 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
07/27/2015 05:30:37 PM Michael Rubinsky Comment #3
Assigned to Michael Rubinsky
State ⇒ Resolved
Reply to this comment
Ingo 3.2.6
07/27/2015 05:27:55 PM Git Commit Comment #2 Reply to this comment
Changes have been made in Git (FRAMEWORK_5_2):

commit 7574ff751e5c8840cd056edbffa1b322c30db6c3
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date:   Mon Jul 27 13:25:35 2015 -0400

     Bug: 14064 and Bug: 13643  Fix reordering of rules.

     Rules were properly reordered in the backend, and the dom id of
     the rules was updated, but the existing links that contained the
     rule number was not. This should fix any remaining ordering issues.
     Note that this does not need to be merged up to Git master since that
     code was already heavily refactored to use rule uids instead of sort
     position.

  ingo/js/filters.js |   14 +++++++++++++-
  1 files changed, 13 insertions(+), 1 deletions(-)

http://github.com/horde/horde/commit/7574ff751e5c8840cd056edbffa1b322c30db6c3
10/21/2014 07:36:23 AM lukas (dot) weiss (at) raiffeisen (dot) it Comment #1
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ Ingo
Summary ⇒ wrong rule disabled/enabled after sort
Type ⇒ Bug
State ⇒ Unconfirmed
Reply to this comment
if i want to disable/enable a rule after sorting, the wrong rule gets 
disabled/enabled. the rulenumber param in the rules href is not 
changed after sorting.

Saved Queries