Duncan McClean

In your particular case, you might be able to swap out `->whereTaxonomy()` for `->whereJsonContains()`: ```diff - $query->whereTaxonomy('resource_type::customer-cases') + $query->whereJsonContains('resource_types', 'customer-cases') ->where('status', 'published') ->whereNotNull('logo') ->whereNotNull('logo_asset_exists'); ```

This seems similar to #10612, where the value of the item in context is being passed to the wildcard tag, instead of the plain key. 🤔 You shouldn't need to...

Yes, it is indeed a workaround. We can fix the core issue in v6, which is coming next year. I think the workaround Jason suggested is fine until then (considering...

This will be fixed in [Statamic 6](https://statamic.dev/release-schedule-support-policy#support-policy).

We've made a bunch of timezone-related improvements in https://github.com/statamic/cms/pull/11409, which'll be released [as part of Statamic 6](https://statamic.dev/release-schedule-support-policy#support-policy). The date fieldtype will display dates using the user's timezone, but they'll be...

I understand why you want this... but until you actually create the entry, there's nothing actually in Statamic to "autosave" to, apart from what's in your browser.

Yep, I agree.

Would you be able to add a test for this fix? We have tests for the collection:previous/next tags in [`CollectionTest`](https://github.com/statamic/cms/blob/5.x/tests/Tags/Collection/CollectionTest.php#L305).

Thanks!

Will be fixed in the next version of the Eloquent Driver.