- 🇩🇪Germany sleitner
The issue should be fixed in the Development version: 2.1.x-dev , see issue #3505261
Automatically closed - issue fixed for 2 weeks with no activity.
We have a page where we list all the upcoming and past events connected to our organization. This page is paged by year.
While using 'year' granularity and after upgrading the module to 8.x-1.x-dev - 2ae7449f, the date pager does not work anymore in our website.
This seems to be related with a mismatch between the format expected by the new code for fields of type `daterange` and the format these dates are currently stored in the database.
For `daterange` the query in now built expecting timestamps, but our database actually stores date strings already formatted. Thus the query fails to return any result.
1. Add a date field of the core type "datetime_range" (not smart date) to the content type your are paging.
2. Create a view paging by year the various entries of the content type in 1.
3. Check that all pages are empty.
Add "daterange" to the field types that are matched via %LIKE in line 331 of DatePager.php
So the line becomes:
if ($this->dateFieldType == 'datetime' || $this->dateFieldType == 'daterange') {
None
None
None
None
This is tested on Drupal 8.9.19 with PHP 7.4.19
Fixed
2.1
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
The issue should be fixed in the Development version: 2.1.x-dev , see issue #3505261
Automatically closed - issue fixed for 2 weeks with no activity.