Baxter Jones

Hi @interdixit

We’ve confirmed the issue with random sorting in Post Selections and have resolved it in the latest release.

Thanks for flagging this.

Hi @rkim888

By default there is nothing that should prevent the shortcode from displaying the information.

The most common thing overlooked is, is there actually something filled in the fields you added to your layout?
How are you using the shortcode, is it the Layout shortcode on the post you have the fields?
Or are you using a Post Selection on a page to show posts?

Hi @aubreygb

Thank you for reporting this.

We’re not currently aware of any cache-related conflicts with Advanced Views. If clearing the cache consistently resolves the issue, it does suggest the error may be related to how cached responses are being served rather than the view rendering itself. If you’re able to share more details about your caching setup (plugin, server cache, CDN, etc.), we’d be happy to investigate further.

That said, we completely understand your concern. In production environments, it’s often preferable to show nothing rather than display a visible red error message to site visitors.

Starting from Advanced Views 3.8.3, the red error message is now only shown to authorized users (e.g., logged-in users with appropriate permissions). Regular site visitors will no longer see the error output on the front end.

Please update to the latest version and let us know if the issue persists.

Hi,
Here’s a short video I made for you on how to use Advanced Views.
https://youtu.be/k1rAaUROI1M

We are working on new official video tutorials.

There’s been no reply for a week, so I’ll close this ticket for now.
Please reply here if you still need help.

Hi

Firstly, our sincere apologies for the confusion and disruption after updating to v3.8.1. With this release we renamed Views → Layouts and Cards → Post Selections, but all your existing entries should still be safely in the database.

If your lists are showing as empty, it’s most likely due to caching. Please try clearing the following caches on your site:

• Redis (database/object cache)
• PHP Opcache

Once those are cleared, your Layouts and Post Selections should reappear, and your shortcodes will work as expected.

If the issue persists after clearing caches, please let me know and I’ll help you look deeper into it.

Hi there,

Thanks for sharing those logs — especially the one that mentions:

DateTime::__construct(): Failed to parse time string (1800–1866)...

This error happens when Advanced Views tries to render a field that’s expected to contain a valid date (like 2024-07-14), but the actual value is something else — in this case, a year range like 1800–1866.

Advanced Views automatically handles Date Picker fields by using the ACF API and passing the value through PHP’s DateTime. That usually works well — unless the field content isn’t actually a valid date string.

Here are a few things to check:

1. Check the ACF field type

Go to Custom Fields → Field Groups, find the field that’s causing the error (likely something like event_start), and confirm it’s set to Date Picker.

If the content is more of a year range or something not meant to be an actual date, consider changing the field type to Text instead — this will prevent it from being automatically treated as a DateTime object.

2. Check the content saved in that field

Edit the post or entry where the error is coming from and look at the field value. If it contains something like 1800–1866 or Unknown, that will cause the error.

If you need to allow those kinds of values, it’s best to:

• Change the field type to Text, or
• Add a separate custom text field for ranges and keep the Date Picker just for actual dates.

Once the field type and content match what’s expected, the view should render without issue.

Let us know what you find — happy to help further if you’d like a second look at the field setup!

Cheers,
Baxter – from the Advanced Views team