Site View Pagination Switch #259
Labels
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: joomla/Component-Builder#259
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Steps to reproduce the issue
Currently, JCB automatically creates the pagination script/code to display the pagination on each of the site views. Although good to have, it limits the ability of developers to create custom pagination.
Example...some of my views are loading all the records on some of the views with ajax/javascript filtering. Basically, on initial open it loads all records, then each filter performs a javascript filter on the loaded records, bypassing the need of having a page reload every time a filter is utilized.
However, with the default Joomla pagination, that doesn't work, since if you go to page 2, then the ajax/js is no long in use. What was needed was my implementing a javascript pagination, which works, except that the default Joomla pagination that JCB adds only loads the number of records saved in limit_list in the Joomla config.
Expected result
The ability to choose between adding or not adding pagination on a per site view basis.
Add a switch on site views in the Joomla Component in JCB to Add Pagination? Yes/No.
If yes, then it adds the pagination as it currently does.
If no, then the pagination code is left out of the compiled component, allowing for custom code to easily be added.
Actual result
Currently, core pagination is added to all site views.
System information (as much as possible)
Additional comments
The dynamic get has the option to load or not load the pagination, is that not enough?
If you are using the same dynamic get, then just copy it so there is two of the same dynamic get... then make the one to use pagination and the other not to use pagination.
So pagination is set per dynamic get, if getType is
getListQuery
I was completely missing it there. And now, seeing it again, I do recall it. I haven't had to go into gets in a while now.