Many moons ago I filed issue https://www.drupal.org/node/778050 again Drupal. That didn't go anywhere, because the pager was not pluggable and needed to be database-agnostic.
Happily, Backdrop only supports MySQL, so the pager changes should in theory Just Work™. This means that complicated queries no longer need custom count queries and the database doesn't need to run two queries each time a pager is displayed on the site.
I ran a lot of beanchmarks on the original issue and there was no performance degradation for small tables, and improved performance for large tables. You can see details at http://cafuego.net/2010/05/26/fast-paging-real-world
GitHub Issue #:
404
Recent comments
Rookie move on my part, CKEditor 4 was still intalled, disabling it and CKEditor Inline IMage Style module fixed the issue. @izmeez, thank you for the link, it helped.
Backdrop CMS 1.32.0 Upgrade Issues or Feedback
Hi lias. Yes, the default value autopopulates the field. I'm not sure why this is not working for you: As for using tokens, you can use them if you choose Filtered text, AND enable...
Content type field Default value - shouldn't it display on new content ?
@john@delinuxco.com The problem with the ckeditor icons not displaying correctly is not just related to the GIN theme, but for every custom or contrib theme that uses a file named ckeditor5.css...
Backdrop CMS 1.32.0 Upgrade Issues or Feedback