Unable to set instruction position for fields inside Bard sets
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 66/100
Research direction
Reproduce the issue by creating a blueprint with a Bard field, a set, and a Text field with instructions. Start by comparing the instruction-position options for a Text field inside a Bard set with those for a regular field. Done when Below can be selected for the field inside the set.
Written by the indexing model from the issue text.
Description
Bug description
When modelling a new content type, I was using Bard with sets. I added a new set for displaying a left-aligned image.
After adding the instructions, I wanted to make them consistent with the instructions used by the other sets in the collection. While editing the instructions, I noticed that I was unable to select Below as an option.
How to reproduce
- Create a blueprint.
- Add a
Bardfield. - Add a set to the
Bardfield. - Add a
Textfield to the set. - Add instructions to the
Textfield. - Attempt to select
Belowas the instruction position.
https://github.com/user-attachments/assets/aa688781-f89a-4802-a528-078d8eba4a78
Logs
Environment
Environment
Laravel Version: 13.25.0
PHP Version: 8.4.24
Composer Version: 2.10.2
Environment: local
Debug Mode: ENABLED
Maintenance Mode: OFF
Timezone: Europe/Copenhagen
Locale: da
Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED
Drivers
Broadcasting: log
Cache: redis
Database: pgsql
Logs: stack / single
Mail: log
Queue: sync
Session: database
Storage
public/storage: NOT LINKED
Statamic
Addons: 3
License Key: Not set
Sites: 1
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 6.34.1 PRO
Statamic Addons
darinlarimore/statamic-postmaster: 1.1.0
statamic/seo-pro: 7.14.3
visuellverstehen/statamic-classify: 4.0.0
Installation
Existing Laravel app
Additional details
No response
- Dominant language
- PHP
- Stars
- 4.9k
- Forks
- 647
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 100
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from statamic/cms
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
There's a default crop when cropping imagesPossibly taken A pull request linked to this issue is open or already merged. Openassets
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
accessibility
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
antlers
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
WordPress/hosting-handbook#506 ·
Maintainers usually reply within 2 days
-
Installing a plugin with composer_packages installs dev dependencies and breaks the autoloader (Error 500)Possibly taken @Boy132 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
nginx: static-file locations drop the security headers, and the dotfile deny is matched after themOpenbug Low Security
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
backdrop-contrib/commerce#60 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100