-
Notifications
You must be signed in to change notification settings - Fork 123
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
Disable Pagination, Lazy Loading not working in new version? #352
Comments
I also have this question. @fabianpimminger did you get this resolved? |
+1 I am also wondering this |
No, unfortunately not :( @corydavidwilliam |
I am also looking for a way to get the "Load more" button back at the bottom of the page after a certain number of entries, instead of the "XX new entires available" button on the top of the page. The "Load more" button is just a lot more suited for the style of my page. While looking for a way to do this, I have just set the pagination to: display: none; in the app.css file and increased the number of default entries to show to a lot more than five, as a temporary fix. |
I hopefully will be working on adding a "load more" feature for 1.8 |
At the moment, the pagination has replaced the lazy loading feature. We may consider re-introducing the option to have lazyloading so I'll leave this open for now. |
We have lazyloading in our version. It's available behind a filter, so pagination can still be used. |
As @paulschreiber said, #442 uses a filter to change the pagination type: https://github.com/Automattic/liveblog/pull/442/files#diff-28777d3571d16955065ce562c6cd7466R12 |
We are deploying an updated visual design of our liveblog on CNNEspanol.com and we would love to have lazy load on the plugin. Could you please help us speed it up? |
@jamunfer I'm not sure what you're asking. Are you concerned about the performance of the lazy loading? |
Hi,
is there a possibility to disable the new pagination? Also, is the filter liveblog_enable_lazyloader not working anymore?
Cheers, Fabian
The text was updated successfully, but these errors were encountered: