You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you have a search index configured, you'll need the relevant fields to be indexed or it won't be able to sort by them. For example: if you're wanting to sort by "Size", you'll need to add size to your index's fields array.
When you have a search index configured, you'll need the relevant fields to be indexed or it won't be able to sort by them. For example: if you're wanting to sort by "Size", you'll need to add size to your index's fields array.
Bug description
When you search for an asset, the ordering filters "Size" and "Last Modified" stop working.
I have only tested this using an S3 container, with a search index on the container.
How to reproduce
Set-up an S3 container with assets in, search for an asset and attempt to re-order the results.
Video displays the issue: https://www.loom.com/share/034d9ff1f5224af1aaf67e5a424f5b62
Logs
No response
Environment
Installation
Fresh statamic/statamic site via CLI
Additional details
This error occurs when using an S3 bucket as an assets container, we also have the below index on the assets container:
The text was updated successfully, but these errors were encountered: