Not a problem. You might be able to just use “local_start_at” (without “event.”) instead of “published_at” if the only children of that page are events.

Good luck!

Amy, this totally worked.

In our case, we unfortunately had to go back and reorder the “published at” dates… I will take some time later to figure out if this can be sorted by other variables (like event.local_start_at), but we’re in a hurry to launch and this was the quickest way of doing things for now. Your code snippet was a lifesaver! You rock! Thanks!

Hi Rob, You can order any forloop using the sort variable:

You might need to fuss with this a bit, because I don’t have the specific syntax in front of me, but the general idea is to assign a variable to the sorted forloop:

{% assign ordered_children = page.children | sort: ‘published_at’ %}

{% for event in ordered_children %}

{% if event.type_name == “Event” %}

Have fun!

Amy, did you ever figure out a way to use page.children and still order the events chronologically? Huge thanks for this “sneaky” workaround!

Here’s a sneaky work-around for calendar pages:
Instead of using {% for event in page.calendar.events_upcoming } which limits to 10 posts before paginating, use { for event in page.children %}

If you have other subpages you want to skip then use:

{% for event in page.children }
{ if event.type_name == “Event” %}

Sneaky!

Here’s a sneaky work-around for calendar pages:
Instead of using {% for event in page.calendar.events_upcoming } which limits to 10 posts before paginating, use { for event in page.children %}

If you have other subpages you want to skip then use:

{% for event in page.children }
{ if event.type_name == “Event” %}

Sneaky!

I agree that it would be really helpful to be able to do “read next post” “read previous post.” Don’t know if you think it would work to set the number of posts viewable in a blog to 1 and then edit the code to show the full content of the blog post on the blog page?

This is a helpful answer, part-way. That documentation is definitely helpful, for instance. But I earnestly hope to be able to see at least twice as many items in the activity stream, and people listings, and suggestions. Is there any way at all to add more control there? I’d rather click through 3 pages instead of 7, or through 18 pages instead of 40… (I once set out to read all the suggestions on your community pages, and it just became so click-heavy, that I never made it through all of them. Usually I feel that I benefit from the full scope of information, and am willing to get through…) We imported 170 twitter followers. It’s not a huge amount, but even so, it is a barrier to see so few on the screen. (In that case, I’d rather they were all on one page, rather than 7…)

I realize that this may impact server demands (?) but I guess I make the case that the current per_page default is simply too low.

@slowdrive Might you be able to offer any insight on pagination, especially how to increase the posts and activity streams and people displaying per page?