Skip Navigation

[Resolved] Filter of view by DATETIME not functioning as expected. No results

This support ticket is created 6 years ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

This topic contains 4 replies, has 2 voices.

Last updated by Shane 6 years ago.

Assisted by: Shane.

Author
Posts
#1190499

I am trying to: Filter a view of a CPT with a custom date time field for all CPT's in the future. the View works fine without the filter. I can display all the CPT results and it shows the actual date time that I want to filter the view on, but when I try to set up a filter to only show CPTs for today and beyond, I get no results.

Link to a page where the issue can be seen:
hidden link

I expected to see:
results

Instead, I got:

#1190504

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Jeff,

Thank you for contacting our support forum.

Setting the filter to a number instead of a datetime resolves the issue. I've done this already for you and it should now be showing up now.

Thanks,
Shane

#1190509

My issue is resolved now. Thank you!

#1190529

One more issue. The sorting by that same field is off. If you look at the Children's Boutique Auction, it has a startdate of Jan 24, but it appears after Jan 25 auction. Originally it was a Jan 25 auction and I changed the start date to see the impact. Is there some sort of strange caching taking place that the sort does not consider?

#1190537

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Jeff,

This should be fixed now.

It seems there was an issue with the date on that post. Once I remove and re-added the date it sorted correctly.

Thanks,
Shane