Bug #2851
closed
paging fails if limitbox is disabled as the JS needs the input
Added by krileon about 13 years ago.
Updated over 12 years ago.
Start date:
30 September 2011
Description
When limitbox is disabled the paging will fail because it needs the input as part of the submit. So a hidden input still must be rendered to ensure it continues to function even if limitbox was disabled.
- Subject changed from paging fails if limitbox is disabled as the JS needs to input to paging fails if limitbox is disabled as the JS needs the input
Fix is to remove the if/else statement on executing the function or not, but instead using the following.
getLimitBox( false )
The above would render only the hidden input, IF statement would tell it true or false.
Actually:
- you should not display the paging at all in front-end if there is only 1 page. Just clutters the display.
- reply comments should not have searchboxes, as it's confusing to have 2 searchboxes for 1 thread.
- you should not display the paging at all in front-end if there is only 1 page. Just clutters the display.
Agreed, reviewing for implementation.
- reply comments should not have searchboxes, as it's confusing to have 2 searchboxes for 1 thread.
Don't agree, should be up to the admin as searchbox for replies can be disabled on an install by install basis through GJ configuration.
- Status changed from New to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by