We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pre 4.50 non orderable stacks looked like this:
In 4.50 they look like this:
Which is probably a side effect of: #9579
Not an issue persé, but probably also not intended.
Add a stack selector limited to 1.
No response
Environment Laravel Version: 10.45.1 PHP Version: 8.3.3 Composer Version: 2.7.1 Environment: local Debug Mode: ENABLED Maintenance Mode: OFF Cache Config: NOT CACHED Events: NOT CACHED Routes: NOT CACHED Views: CACHED Drivers Broadcasting: log Cache: statamic Database: mysql Logs: stack / single Mail: smtp Queue: sync Session: file Livewire Livewire: v3.4.6 Statamic Addons: 8 Antlers: runtime Sites: 1 Stache Watcher: Enabled Static Caching: Disabled Version: 4.50.0 PRO Statamic Addons edalzell/forma: 2.1 jonassiewertsen/statamic-livewire: 3.0.0 rias/statamic-color-swatches: 2.2.0 statamic-rad-pack/mailchimp: 4.1.1 studio1902/statamic-peak-browser-appearance: 3.3.4 studio1902/statamic-peak-commands: 5.0.2 studio1902/statamic-peak-seo: 8.2.0 studio1902/statamic-peak-tools: 4.4.2
Fresh statamic/statamic site via CLI
None
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Bug description
Pre 4.50 non orderable stacks looked like this:
![Screenshot 2024-02-27 at 13 20 16](https://private-user-images.githubusercontent.com/69107412/308163596-0c0eb838-11fe-4426-8d4b-0c44bf594cf8.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU0NTE4MTYsIm5iZiI6MTcyNTQ1MTUxNiwicGF0aCI6Ii82OTEwNzQxMi8zMDgxNjM1OTYtMGMwZWI4MzgtMTFmZS00NDI2LThkNGItMGM0NGJmNTk0Y2Y4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MDQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTA0VDEyMDUxNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTEwMjYzMTA1YWJhMTcwZWFlMWYwMjBjMzJiMmMyNjEwNWY0YTdkNzEyNjFiOTM4ZTEyOTcwYzQ1MjEzYTA3YTgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.Wn8ScAppB37i7wLaxTHanpGvapQ3XeUtPD6mzTQA58s)
In 4.50 they look like this:
![Screenshot_2024-02-27_at_13 11 48](https://private-user-images.githubusercontent.com/69107412/308164138-a3ee8ba4-a74d-4ea8-876c-6a7eafef7ccc.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU0NTE4MTYsIm5iZiI6MTcyNTQ1MTUxNiwicGF0aCI6Ii82OTEwNzQxMi8zMDgxNjQxMzgtYTNlZThiYTQtYTc0ZC00ZWE4LTg3NmMtNmE3ZWFmZWY3Y2NjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MDQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTA0VDEyMDUxNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWU3NWZlYzM2MTVhNmU2NDI2MGU1YjhlMmNhNDRkMzJjMjQyN2UxNzEwMzJhYTZmMmU3OGY3ZTAxMmEyMzUwZTkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.0iFuxNG_qELaCZOKN4uXWgeo54XEjCt2ydqqGdZP-gc)
Which is probably a side effect of: #9579
Not an issue persé, but probably also not intended.
How to reproduce
Add a stack selector limited to 1.
Logs
No response
Environment
Installation
Fresh statamic/statamic site via CLI
Antlers Parser
None
Additional details
No response
The text was updated successfully, but these errors were encountered: