Users/groups etc. sorted by length tree view?

[MikeCTZA]

I've just been looking to update our old old instance of your tool to v2, I got the docker working OK and can do everything I need.
I had to increase the max_execution_time in the /usr/local/etc/php/php.ini as it would timeout getting data from out main users OU that had about 800 items. But that is fine and not part of what I wanted to ask.

Everything in the tree view / records are sorted by the length of their CN/OU, is that expected? I would have expected it to be alphabetical. I had a look but wasn't obvious if I had missed something config wise

[leenooks]

Everything in the tree view / records are sorted by the length of their CN/OU, is that expected?

Actually that might be co-incidental? Or your ldapserver is returning the records that way? (Just checked the demo site, and in the Flintstones tree, they are not sorted by length.)

I just looked at the code, and I'm have not implemented sorting yet. In 1.2 it was a configuration item - so I'll look at putting that back.

The need to increase the max_execution_time also concerns me. My test environment is quite small - so I do need to create a large test environment and see if there are any performance optimisations that should be implemented.

[MikeCTZA]

if I do a CLI ldapsearch I get the records displayed in UID order so it doesn't feel like that but could be, its not a big problem for us we use custom code mostly to our ldap box we just have phomyldapdmin as a backup incase we need to see something directly, so we just for a Ctrl+F and search for the user and then we are all good, so its not a show stopper for us to upgrade our aging ldap server.
Our ldap server is slapd/openldap on ubuntu.
I saw the php execution timeout when I enabled the debug logging and inside the container looked at /app/storage/logs/laravel*.log

[MikeCTZA]

Just did it now to get it ... on the GUI I see Load Error! internal server
and in the logs
[2025-03-19 12:13:32] production.ERROR: Maximum execution time of 30 seconds exceeded {"exception":"[object] (Symfony\\Component\\ErrorHandler\\Error\\FatalError(code: 0): Maximum execution t ime of 30 seconds exceeded at /app/vendor/laravel/framework/src/Illuminate/Cache/FileStore.php:316) [stacktrace] #0 {main} "}

[leenooks]

I just committed eab4f04 which will sort entries by their DN (until I implemented custom sorting), as well as performance improvement when retrieving records for the tree.
I loaded my test server with 10,000 entries, changed the sizelimit to 2000 and the tree rendered in around 13s (so shouldnt need to mess with the execution time). Tree navigation with that many entries is probably not ideal anyway, so I will look at different ways to manage a large list of entries in a branch.

[MikeCTZA]

Many thanks, that's great I'll give that a go now as I was testing my Ansible playbooks to deploy a restored LDAP server anyway so is ideal timing

[leenooks]

If you might want to apply that patch to 2.0.3 - Ive made a few changes to master to support attribute tags, so editing will trigger errors until I complete that work.