Skip to content
New issue

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

Non-orderable stacks lost their padding #9595

Closed
robdekort opened this issue Feb 27, 2024 · 0 comments · Fixed by #9597
Closed

Non-orderable stacks lost their padding #9595

robdekort opened this issue Feb 27, 2024 · 0 comments · Fixed by #9597

Comments

@robdekort
Copy link
Contributor

robdekort commented Feb 27, 2024

Bug description

Pre 4.50 non orderable stacks looked like this:
Screenshot 2024-02-27 at 13 20 16

In 4.50 they look like this:
Screenshot_2024-02-27_at_13 11 48

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

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

Installation

Fresh statamic/statamic site via CLI

Antlers Parser

None

Additional details

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants