Last page in a date range is not displayed in a listing if that page's frontmatter date field contains a time

Support
1

This is a continuation of a previous post as I’ve now narrowed it down to what I’m sure is a bug.

Notes:

  • the following steps have been carried out on on fresh installs of 1.7.48 and 1.8.0-beta.4 with no extras (no admin plugin, no additional plugins and only the default Quark theme).
  • I’m using EU date and time formats (dash separators, 24-hour clock without am/pm) but have tested both formats in page frontmatter and twig date ranges. The results are the same.
  • all edits were made with a text editor - i.e. no admin plugin.

Steps to reproduce:

  • unzip Grav download (and enable the debugger in system.yaml)
  • edit /user/themes/quark/templates/default.html.twig and add dump line in content block: {{ dump(page.collection.dateRange('01-01-2024', '31-12-2024')) }}
  • to make it easier to read, I also added a simple listing, so that default.html.twig looks like this:
{% extends 'partials/base.html.twig' %}

{% block content %}

    {{ dump(page.collection.dateRange('01-01-2024', '31-12-2024')) }}
    
    {{ page.content|raw }}
    
    <p>2024 page listing</p>
    <ul>
    {% for p in page.collection.dateRange('01-01-2024', '31-12-2024').order('date','desc') %}
		<li><a href="{{ p.permalink|e }}">{{ p.title|e }}</a> &mdash; {{ p.date|date|e }}</li>
	{% endfor %}
	</ul>
	
{% endblock %}
  • add new page collection. I called it Child test, folder name 03.child-test containing default.md which looks like this:
---
title: Child test
content:
  items: 
    '@self.children'
---
  • create 3 child pages inside 03.child-test i.e. 3 directories called child-one, child-two, child-three - each one containing one file called default.md with the following frontmatter:
---
title: Child one
date: 28-12-2024
---

---
title: Child two
date: 29-12-2024
---

---
title: Child three
date: 30-12-2024
---

Then open the site in a browser. In the menu you’ll see ‘Child test’ - click that and you’ll see all 3 pages listed (in date order, newest first).

Clockwork lists all 3 pages in its array:

Array(1) object: Grav\Common\Page\Collection
object: Grav\Common\Page\Collection
*items: Array(3)
/Users/simfin/Public/PHPServer/Grav-testing/user/pages/03.child-test/child-one: Array(1)
/Users/simfin/Public/PHPServer/Grav-testing/user/pages/03.child-test/child-three: Array(1)
/Users/simfin/Public/PHPServer/Grav-testing/user/pages/03.child-test/child-two: Array(1)
~iteratorUnset: false
*pages: Grav\Common\Page\Pages
*params: Array(2)

So far so good.

Now add a time to all 3 ‘child’ pages - in either 12-hour (with am/pm) or 24-hour format - so the 3 child page frontmatters now look like this:

---
title: Child one
date: 28-12-2024 13:45
---

---
title: Child two
date: 29-12-2024 08:15
---

---
title: Child three
date: 30-12-2024 19:02
---

Reload the Child test page and you’ll see that Child three (the last page in the listing) has disappeared from the listing.

The page is also missing from Clockwork’s array:

Array(1) object: Grav\Common\Page\Collection
object: Grav\Common\Page\Collection
*items: Array(2)
/Users/simfin/Public/PHPServer/Grav-testing/user/pages/03.child-test/child-one: Array(1)
/Users/simfin/Public/PHPServer/Grav-testing/user/pages/03.child-test/child-two: Array(1)
~iteratorUnset: false
*pages: Grav\Common\Page\Pages
*params: Array(2)

Now delete the time from Child three’s date field, reload your browser - and it appears again.

This happens no matter which time format or whether the time is before or after the date.

I have tested this with other date ranges with the same results.

2

I’m still not convinced there is a bug, because again I cannot reproduce the issue…

I literally followed your steps and copied all code and frontmatters.

  1. Result of pages without a time:

    {837008ED-9DDF-4C3C-AEA2-8DC2D05B6716}
    {837008ED-9DDF-4C3C-AEA2-8DC2D05B6716}368×264 4.2 KB

  2. Result when time is added to pages:

    {F15788BE-6D89-46E8-BC94-EFED1747BD7F}
    {F15788BE-6D89-46E8-BC94-EFED1747BD7F}480×314 13.1 KB

By the way, in your previous post you were complaining that pages with date: 12/31/2024 were missing from the dateRange() and now you’re not using the last day of december. Any reason?

3

Thanks for testing anon76427325. I’m still having this issue and have been testing/troubleshooting most of the weekend - including on different servers, with different date ranges and with different installs (1.7.48 and 1.8.0-beta.4).

To answer your question - the issue is that the last page in a date range listing is not displaying in the listing. That’s why I initially thought it was to do with the 31 Dec date - as it’s the last date in the year - and therefore the last post in a year date-range listing. Since then I’ve tested other date range listings (not ending in 31 Dec) with the same results - i.e. the last page is missing.

I’m now testing using a page with a full collection listing (so I can see it’s finding all the pages in a collection which works as expected) and then a date-range listing.

My default.html.twig now looks like this:

{% extends 'partials/base.html.twig' %}

{% block content %}
    
    <h1>Grav 1.7.48</h1>
    
    <h2>Collection listing</h2>
    <ul>
    {% for p in page.collection.order('date','desc') %}
		<li><a href="{{ p.permalink|e }}">{{ p.title|e }}</a> &mdash; {{ p.date|date|e }}</li>
	{% endfor %}
	</ul>
	
    <h2>Date range listing</h2>
    <ul>
    {% for p in page.collection.dateRange('01-01-2024', '31-12-2024').order('date','desc') %}
		<li><a href="{{ p.permalink|e }}">{{ p.title|e }}</a> &mdash; {{ p.date|date|e }}</li>
	{% endfor %}
	</ul>
    
{% endblock %}

I’m not getting consistent results so I won’t post my findings yet - but something odd is going on with date range listings and it definitely relates to page frontmatter.

I’ll post more when I’m more sure of what’s going on.

4

After much testing I’m sure I’ve narrowed down this issue to unexpected behaviour in date range listing when using EU date format (DD-MM-YYY).