<?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>Ajax: Enhanced permissions Admin: Users for per-user permissions are not alphabetically sorted</title> 
  <pubDate>Fri, 10 Apr 2026 18:58:36 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/10205</link> 
  <atom:link rel="self" type="application/rss+xml" title="Ajax: Enhanced permissions Admin: Users for per-user permissions are not alphabetically sorted" href="https://bugs.horde.org/ticket/10205/rss" /> 
  <description>Ajax: Enhanced permissions Admin: Users for per-user permissions are not alphabetically sorted</description> 
 
   
   
  <item> 
   <title>When I enter advanced permissions admin in kronolith ajax vi</title> 
   <description>When I enter advanced permissions admin in kronolith ajax view, I see the users not sorted by username but by the time they were added to the ldap database. This could easily be solved by a simple sort.

</description> 
   <pubDate>Tue, 07 Jun 2011 12:44:58 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/10205#t65455</link> 
  </item> 
   
  <item> 
   <title>&gt; When I enter advanced permissions admin in kronolith ajax </title> 
   <description>&gt; When I enter advanced permissions admin in kronolith ajax view, I see 
&gt; the users not sorted by username but by the time they were added to 
&gt; the ldap database. This could easily be solved by a simple sort.
&gt;
&gt;
This applies to all shares edited through kronolith&#039;s ajax view but not through the traditional interface.</description> 
   <pubDate>Tue, 07 Jun 2011 15:19:19 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/10205#t65462</link> 
  </item> 
   
  <item> 
   <title>&gt;&gt; When I enter advanced permissions admin in kronolith ajax</title> 
   <description>&gt;&gt; When I enter advanced permissions admin in kronolith ajax view, I see
&gt;&gt; the users not sorted by username but by the time they were added to
&gt;&gt; the ldap database. This could easily be solved by a simple sort.
&gt;&gt;
&gt;&gt;
&gt; This applies to all shares edited through kronolith&#039;s ajax view but 
&gt; not through the traditional interface.

In traditional view, sort() is called after $auth-&gt;listUsers
This does not happen in ajax mode
I wonder if sorting should rather happen in the backend instead of fixing it in the inc file</description> 
   <pubDate>Tue, 07 Jun 2011 15:28:37 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/10205#t65463</link> 
  </item> 
   
  <item> 
   <title>&gt; I wonder if sorting should rather happen in the backend in</title> 
   <description>&gt; I wonder if sorting should rather happen in the backend instead of 
&gt; fixing it in the inc file
I tend to say no, because sometimes you don&#039;t need the user list for displaying and can save a few cycles if you don&#039;t sort.</description> 
   <pubDate>Tue, 07 Jun 2011 15:57:59 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/10205#t65464</link> 
  </item> 
   
  <item> 
   <title>commit e64f4407ca0953fb66ff839d6fdca4b38f6c68f6 should fix t</title> 
   <description>commit e64f4407ca0953fb66ff839d6fdca4b38f6c68f6 should fix that.</description> 
   <pubDate>Thu, 09 Jun 2011 18:26:33 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/10205#t65545</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in Git for this ticket:

Revert &quot;[#10</title> 
   <description>Changes have been made in Git for this ticket:

Revert &quot;[#10205] Now sorts users in ajax perms view and reuses the sort result&quot;
This reverts commit e64f4407ca0953fb66ff839d6fdca4b38f6c68f6.

 1 files changed, 2 insertions(+), 4 deletions(-)
http://git.horde.org/horde-git/-/commit/059d57de36fcdfaa438245b8e41aa586ec46c2cb</description> 
   <pubDate>Tue, 05 Jul 2011 11:33:49 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/10205#t66160</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
