Query builder broken

Support
#1

Hi there,
I’ve been using the query builder to display CPT on our website for years. Somehow, the builder doesn’t function anymore. For testing purposes I’ve but date published after on 1 August 1900, and it still shows data. I can guarantee you that we didn’t post anything before 2000 :wink:

Our website is fully up to date and all caching has been fully disabled. Funnily enough, it does actually work for sections where I’ve already set the query builder up. But any changes mess it up completely.

The problem occurs both on the homepage in a looper provider as on the archive page of the CPT.

#2

Alright I think I know the problem. The date selector used to output something like Thu Oct 17 2024 14:56:00 GMT+0200

The date selector now outputs 17 oktober 2024 14:56, which is not interpreted right by the builder. A fix would be nice :slight_smile:

#3

Hello @Hindrik,

Thanks for writing in! I could not replicate the issue on my local install. We would be happy to double-check your site if we can log in. You can create a secure note in your next reply with the following info:
– Link to your site
– WP login URL
– WP username
– WP password
– WP Administrator Role
– Confirmation that we can access and make changes to your site

To know how to create a secure note, please check this out: How The Forum Works

image

In the meantime, kindly do the following:

  1. Confirm your exact versions – Please send the precise Pro/X and Cornerstone version numbers you are running. Since this worked for years and changed recently, the version boundary is what lets us identify which release altered the date selector output.

  2. Confirm the locale connection – The word “oktober” in the new output indicates the value is being formatted through your site language rather than as a standard date. Please go to Settings > General, temporarily set Site Language to English (United States), then re-open the query, re-select the date, save, and test again. If the filter starts working, that confirms the localised format as the trigger and also gives you a usable interim workaround.

  3. Capture the stored value – Please re-save one affected query with a date applied, then send us the exact string the date field displays afterwards. That string is the value being handed to the query, and it is what our developers will need in order to reproduce this.

  4. Confirm the scope – You mention this affects both homepage Looper Providers and CPT archive pages. Please confirm whether untouched existing queries still return correct results and only re-saved queries break. That distinction tells us whether the regression is in how the value is written or in how it is read back.

Best Regards.