This problem has been present for quite a while - I've been too lazy to report it!
Unnecessary "more" button in custom PG
Graham Criddle
MVP Posts: 33,252 
(On Windows 8.1 and Logos 5.2a b5)
In the first expanded section of the custom PG below there is a "more" button suggesting that there are more commentaries to look at
but when I click it nothing happens
In the second expanded section there are fewer commentaries and no more button
It looks as though the algorithm is showing the more button when there are seven commentaries in that collection as opposed to only showing it if there are more than seven.
0
Comments
-
This problem has been present for quite a while - I've been too lazy to report it!
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Mark Barnes said:
This problem has been present for quite a while
I will admit its not a particularly urgent problem to fix!
Mark Barnes said:I've been too lazy to report it!
My excuse is I don't think I noticed it before[:)]
0 -
Graham Criddle said:
but when I click it nothing happens
In the second expanded section there are fewer commentaries and no more button
It looks as though the algorithm is showing the more button when there are seven commentaries in that collection as opposed to only showing it if there are more than seven.
I can reproduce this issue, and I will create a case for Development to investigate.
0 -
Angela Murashov said:
I can reproduce this issue, and I will create a case for Development to investigate.
Thanks Angela
Appreciated, Graham
0 -
Angela Murashov said:
I can reproduce this issue, and I will create a case for Development to investigate.
Hi Angela,
There is a similar issue effecting other sections of the passage guide reported here,
http://community.logos.com/forums/p/83469/585077.aspx#585077
0 -
Angela Murashov said:
I can reproduce this issue, and I will create a case for Development to investigate.
This should be fixed in 5.2b SR-3.
0
