-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
Replace pagination widget with pagination core api #542
Comments
okmiim
added a commit
to okmiim/calendarize
that referenced
this issue
Apr 17, 2021
Instead of using the be.widget.paginate, the new pagination API is used. Additionally the option action is part of the list actions. Related lochmueller#542 Fixes lochmueller#535
okmiim
added a commit
to okmiim/calendarize
that referenced
this issue
Apr 17, 2021
Instead of using the be.widget.paginate, the events are now paginated with the new pagination API. Additionally the option action is now part of the list action. Related lochmueller#542 Fixes lochmueller#535
okmiim
added a commit
to okmiim/calendarize
that referenced
this issue
Apr 17, 2021
Instead of using the be.widget.paginate, the events are now paginated with the new pagination API. Additionally the option action is now part of the list action. Related lochmueller#542 Fixes lochmueller#535
okmiim
added a commit
to okmiim/calendarize
that referenced
this issue
May 8, 2021
Instead of using the widget.paginate, the indices are now paginated with the new pagination API. To limit the amount of pages, georgringer/numbered-pagination is suggested. Old templates with widget.paginate should still continue to work (in TYPO3 10 or until removed). Related: lochmueller#542
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Breaking: #92529 - All Fluid widget functionality removed
Pagination via Fluid widgets was removed in TYPO3 v11.
The pagination inside the FE and BE list need to be replaced in future versions.
The text was updated successfully, but these errors were encountered: