7
No reason why you can't get an infinite scroll working in EE. Though really you don't need all the overhead of the infinite scroll plug-in, which forces its particular requirements on you as well. A small bit of jQuery can do this just as well. You just need to add one additional wrapper to your markup so that you can target the content you want to load ...
6
I don't know if you already have a anwser yet. But I had the same problem and I. I want to enable pagination within a Playa loop.
You need to do 2 things to enable pagination in a Playa loop.
Override the default disable of “categories|category_fields|member_data|pagination”.
Put var_prefix in your Playa tag and pagination tag.
You did a good override of ...
6
I believe it's a spelling issue in "libary" should be "library"
https://support.ellislab.com/bugs/detail/20172
5
UPDATE:
Got it working. This is what I have for those following:
set_list template:
{stash:embed:layouts:homepage}
{exp:stash:context name="100_list"}
{exp:stash:set_list
name="movie_list"
context="@"
parse_tags="yes"
save="yes"
scope="site"
refresh="1440"
replace="no"
}
{exp:channel:entries
channel="films"
...
4
The pagination will display at the top, bottom or top and bottom of the channel entries tag (depending on what you set in the paginate="" parameter). It doesn't matter where you place {paginate} it in the template code itself.
Either use a pagination addon (like AB Pagination) or use Stash.
Mark Croxton has an example of how he moves his pagination to ...
4
So thanks to Low stepping in and doing some testing with me, we worked out that the problem was down to an extension hook for Structure that was messing up ALL pagination across the site.
Low performed the following sql query to find the hook in question:
SELECT * FROM exp_extensions WHERE hook = 'channel_module_create_pagination'
and then removed the ...
4
You want to mosey on over to page_padding land.
https://docs.expressionengine.com/v2/templates/pagination.html#id3
{pagination_links page_padding="10"}
{/pagination_links}
This will show up to 10 page numbers on either side of the current page in the pagination links.
3
I just check your site using Integrity and it looks like you don't have this urls any more. Possible you had something in your old templates (I can see that Google cache had another design for pages like /caprice/P12).
I believe soon all old links will be removed by Google because of Status : 301. Just need to wait.
I saw also that you start using
<...
3
To display the total rows across all the pages of your pagination, you use {absolute_results} which can be found here in the EE Docs.
This variable will always display the absolute total number of results
that are returned by the tag, regardless of pagination.
The limit="" parameter is used to show a set number of entries per pagination page. Docs here....
3
Instead of limit="10", try using event_limit="10". From the {exp:calendar:events} documentation:
http://www.solspace.com/docs/calendar/events/#event_limit
3
Looks like you forgot about the protocol on the URL to the root of your site. Probably, you wrote domain.com instead of http://domain.com.
The duplicated part is added by the browser that is treating the URL as relative because of the absence of protocol.
3
Why is it linking to every 14th page?
It's not. I'm willing to bet that your channel:entries tag has a limit of 14. The links/url segments indicate entry offset, not page offset - but they achieve the same end result.
3
With - http://ellislab.com/expressionengine/user-guide/add-ons/channel/entry_linking.html
{exp:channel:next_entry}
<p>Next entry: <a href="{path='site/comments'}">{title}</a></p>
{/exp:channel:next_entry}
{exp:channel:prev_entry}
<p>Previous entry: <a href="{path='site/comments'}">{title}</a></p>
{/exp:...
3
You can fix this if you limit the entries outputted to those in the language you are in.
You can do this by adding the 'entry_id' parameter and using a Transcribe tag to output all the entry ids
The refined channel tags is:
{exp:channel:entries channel="blog"
dynamic="yes"
paginate="bottom"
limit="3"
entry_id='{exp:transcribe:entry_ids channel="blog"}'
...
3
Honestly, I wouldn't even mess with that plugin since that's what it's supposed to do. Just do a simple ajax call and append the data like this. Note the move of #articles to the main template, and paginate_base parameter in the embed template.
Main Template
<html>
<head></head>
<body>
<section id="articles">
...
3
When not using encoded queries, Low Search will try and add the GET vars to the pagination URLs automatically. If that fails, you can always add the query string manually, by using this as your pagination links:
<a href="{pagination_url}{low_search_query_string}">
2
Is the list of messages sorted, with the "10 latest messages" first (sort on date, descending), or last (sort on date, ascending)?
If the "10 latest messages" are first, they should be on the first page of results--which would be the URL with no P, or with P0.
In any case, if you know the offset--say you want messages 90-100, the channel entries tag Offset ...
2
Try following instructions on Blank Pages in EE docs and see if you get any errors reported.
2
You are missing the paginate parameter on your opening calendar:events tag. Try adding paginate="bottom" and see if that fixes your issue.
2
Have you tried following the instructions here: https://getsatisfaction.com/pixelandtonic/topics/pagination_in_playa#reply_6602199 ?
2
Render out the pagination in one block, framing the 2 styles of pagination:
{paginate}
<div id="top-pagination">
Showing results {abp_entry_from}-{abp_entry_to} of {abp_total_entries}. Show: 10 20 30 per page
</div>
<div id="bottom-pagination">
{pagination_links}
<ul>
{previous_page}<li><a href="...
2
I look into this and couldn't find any replacement. I suggest you to go with the default solution. It doesn't do everything you want to, but is better than keep all your system outdated.
I'm sorry.
2
You can do most of this with the default EE pagination tags, but I think in order to get the last number of the entries on the page you should check out the AB Pagination add-on. Using that add-on makes outputting pagination like "1 to 10 of 100" easy.
2
I've also read that it's not a good idea to put the channel forms tag inside the channel entries tag, but I'm doing it anyway for a site where I couldn't find another solution to the problem I was encountering and it's working.
So I would say (like Romans-8---31-39 said in the comment) try it as a separate tag if possible. If you can't try nesting it and ...
2
The code you posted is correct for what you're wanting to achieve.
{exp:channel:entries channel="news" limit="6" dynamic="no" orderby="date" sort="desc" paginate="bottom"}
This code will get you 6 entries per pagination page and your pagination URLs will increment by 6 because you have limit="6" set. If you change that to limit="10", you still see 10 ...
2
Check out Better Pagination by Bold Minded/Brian Litzinger.
You should be able to achieve what you need using the limit and offset parameters with that add-on.
On GitHub:
https://github.com/litzinger/better-pagination.eeaddon
2
The position of pagination is defined by the parameter paginate:
if it is set as top, the pagination code will be removed before parsing and added back at the top of the parsing results;
if it's set as bottom, the pagination code will be added to the bottom of the results;
set it as bothand it will be... Well, I got the idea;
hidden doesn't show the ...
2
If you check the documentation you'll find an example that is essentially exactly what you are looking for.
{paginate}
{pagination_links}
<ul>
{first_page}
<li><a href="{pagination_url}" class="page-first">First Page</a></li>
{/first_page}
{previous_page}
<li><a href="{...
2
You might take a look at AB Pagination add-on that would give you much more control over how it's output, as well as pointing back to your original template page for the first page link.
2
Try upgrading Low Search to the latest version. Version 3.1.6 has this bugfix:
Fixed a bug where a page URL could be falsely rewritten to maintain the query string
...which should probably fix the issue.
If it does not, try changing the hrefs of the pagination links to:
href="{pagination_url}?{current_query_string}"
Only top voted, non community-wiki answers of a minimum length are eligible
