<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Move a rule always move by one step</title> 
  <pubDate>Fri, 10 Apr 2026 13:36:24 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/10172</link> 
  <atom:link rel="self" type="application/rss+xml" title="Move a rule always move by one step" href="https://bugs.horde.org/ticket/10172/rss" /> 
  <description>Move a rule always move by one step</description> 
 
   
   
  <item> 
   <title>In Ingo 2.0.1, when i move a rule by more than one step, usi</title> 
   <description>In Ingo 2.0.1, when i move a rule by more than one step, using the rightest input form field corresponding to the rule and indicating the new number, the rule is always move by one, not by the specified number.

It seems to be a bug in ingo/filters.php, for case rule_up and rule_down...
    case &#039;rule_up&#039;:
        $filters-&gt;ruleUp($vars-&gt;rulenumber, $vars-&gt;steps || 1);
        break;

    case &#039;rule_down&#039;:
        $filters-&gt;ruleDown($vars-&gt;rulenumber, $vars-&gt;steps || 1);
        break;
The expression &quot;$vars-&gt;steps || 1&quot; always returns a true boolean value, not the form indicated step !!</description> 
   <pubDate>Wed, 01 Jun 2011 18:38:52 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/10172#t65225</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in Git for this ticket:

[jan] Fix mo</title> 
   <description>Changes have been made in Git for this ticket:

[jan] Fix moving rules to an explicit position (Bug #10172).

 3 files changed, 5 insertions(+), 4 deletions(-)
http://git.horde.org/horde-git/-/commit/e5c69f499a5f1efd220ee81137e82bb64e23bbe6</description> 
   <pubDate>Thu, 02 Jun 2011 19:51:18 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/10172#t65276</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
