-
-
Notifications
You must be signed in to change notification settings - Fork 527
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Element/Template/GetList processor for >20 templates in manager #16145
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works as advertised!
The limit line should not make any difference. limit = 0 is sent with the initial The sorting should be moved to an additional prepareQueryAfterCount method
for two reasons:
|
@Jako - Unless the sorting (in it's current placement) is affecting the number of returned results, altering the limit might be necessary, as it's set to 20 in one of the ancestor classes ( |
@Jako |
I have tested my comment and there was no issue with about 25 templates. It is somehow a BC if the default limit is changed. Setting the limit has to go in the JS code. |
Sure. Feel free to change this PR or create a new one. |
Closing in favor or #16160. |
What does it do?
Currently the Element/Template/GetList processor always returns a 'total' value of
0
. This causes the pagination of the template-dropdown to not work properly.Also in the "Create Document" window, there is no pagination and the filtering happens without further AJAX-requests. Therefore the processor should return all templates if no limit is specified.
(Maybe a better fix would be to send a limit =
0
request parameter from the form though.)Why is it needed?
If you have more than 20 templates, not all of them can be selected when creating/updating a resource in the manager.
How to test
Create more than 20 templates.
Create/update a resource and test if all templates can be selected.
Related issue(s)/PR(s)
Resolves #16135