You are viewing limited content. For full access, please sign in.

Question

Question

Laserfiche Directory Server UI only displaying first 20 groups maximum

asked on May 4, 2021

Laserfiche Directory Server Version 11.0.0.981 

 

We're in the early phase of a migration to Laserfiche 11 systems and we've encountered a UI bug while testing and building out some initial LFDS Groups.

From the 'Accounts' > 'Groups' section of the Web UI, when we add more than 20 LFDS Groups, they fail to display and there is no pagination offered either. So any groups beyond the first 20 will simply appear to not exist and this leads to some confusion.

We have verified the Groups do exist and have been successfully added to the LFDS database. These Groups are also able to be discovered via the 'Filter groups' search / input field located on the same screen, and they will be displayed properly, but only after you've filtered for the specific Group name or partial keywords of the otherwise hidden Groups.

We've verified this to be the case on our LFDS system when accessed in recent Safari and Chrome web browsers.

 

Is this a known bug and / or is there an update available that might address it?

LFDS-20-GRP-DSPLY-LMT.jpg
0 0

Replies

replied on May 6, 2021

After further experimentation I've discovered that this is a bug in the LFDS UI that is triggered by browser window height.

 

I'm on a very "tall" 5k display and I typically run my web browser in full screen. Same goes for my RDP sessions and their web browsers. Large screen real estate, why not use it? 

 

The problem is the frontend UI logic is restricting the number of records displayed on the Groups page to 20, unless the browser window height is less than 'X' (or scroll / viewport etc).

So this bug has had me scratching my head because it's consistent until I logged onto a laptop with a smaller resolution and noticed that immediately the previously hidden records were right there on display and scrollable. To test I immediately RDP connected to the same laptop (in my native 5k resolution, and the records were all on display still, and only after a browser refresh / page render would they disappear). 

 

I've now verified that by toying with the browser window height, you can successfully reproduce the issue with more than 20 LFDS Groups to display.

I've attached a short video (mpeg4) – hopefully that's all it takes to narrow it down. 

4 0
replied on May 6, 2021

Hi Roberto, thanks for the tip. I can reproduce the problem now and we'll look into it.

1 0
replied on May 4, 2021

Hi Roberto, I am unable to reproduce this issue with Chrome 90 or Firefox 88. Do you see any errors in the browser console when loading the Groups page with developer tools open? Also, do multiple machines see this problem or only one? It might be worth rebooting the LFDS machine and the client machine to see if that helps.

0 0
replied on May 4, 2021 Show version history

This is the case within multiple web browsers (versions listed below) from different desktop clients at different locations, and from Chrome on the server itself. 

This particular virtual host is scheduled to reboot nightly, so a reboot doesn't appear to resolve the issue. 

There is no console output when viewing the inspect panel in Chrome (While adding a new test group). 

 

Safari Version 14.0.3 (16610.4.3.1.7)

Chrome Version 90.0.4430.93 (Official Build) (x86_64)

 

Thanks for your response, and please let me know if there's any additional data I can provide. 

0 0
replied on May 4, 2021

In that case, I recommend having your SP open a support case so we can gather more data.

0 0
replied on May 4, 2021

Got it. Thank you. 

0 0
replied on May 5, 2021

We have confirmed that there is a trigger in LFDS which can limit the viewable groups to 20, you can still search and find any group though, up to 20.

The problem is, it never seems to happen when using a console connection to the host OS and a local browser. It intermittently happens when using RDP to the server, and it almost exclusively happens when using a browser from a remote workstation and manually entering your credentials at the IIS Windows Auth prompt.

My suggestion was to continue to use console for a bit to confirm that it never does happen over a console connection.

The fact that it stops at listing 20, and in the inspector we can see that the 20th group listed is the last object in the DOM layer (nothing is hidden or having display issues), means the DS server MUST have some code that intermittently limits the view to 20 though.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.