Okay, that's weird. When using on my community the &page parameter works like a pagination parameter as expected. So on your case
...?page_size=1&page=1
...should show the latest blog post.
...?page_size=1&page=2
...should show the second oldest and so on.
Hi,
Yes, Lithium is special and therefor uses the &page=2 parameter as the 1-based index of the page to be returned. :)
Thank you Claudius,
While that does work if you have two blogs, it doesn't offset the posts.
For example, if I'm using page-size=3, that gives me the 3 blog posts. What I am would like is to create a custom component which gives me the most recent blog post (page-size=1), then create 3 widgets under it to give me posts 2-4 (2, 3, and 4).
&page gives me posts from another blog (which is very helpful to know but not the solution I was actually looking for.
Okay, that's weird. When using on my community the &page parameter works like a pagination parameter as expected. So on your case
...?page_size=1&page=1
...should show the latest blog post.
...?page_size=1&page=2
...should show the second oldest and so on.
Glad I could help.
Just for the record: The page=# parameter is not the offset but the page of the pagination. So page=1 is the first result page and so on. I keep wondering why that's not working right for you...
