bootstrap_package fields missing from content block
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
Research direction
Start with the generated content block from the typo3 make:content-block command and its config.yaml, focusing on the TYPO3/Appearance configuration. Compare the available fields with those provided by EXT:mask and check how the listed bootstrap_package fields are expected to be exposed. Done means the listed fields appear in the backend form for a content block using the documented configuration.
Written by the indexing model from the issue text.
Description
Bug Report
Prerequisites
- Can you reproduce the problem on TYPO3 v12.4 LTS
- Can you reproduce the problem on TYPO3 v13.4 LTS
- Did you perform a cursory search
to see if your bug or enhancement is already reported?
Description
Not sure if this is the right place to ask, but I just migrated a few EXT:mask content elements to EXT:content_blocks.
This worked quite well, but now I'm missing some fields from EXT:bootstrap_package in the appearance tab:
- frame_layout
- frame_options
- background_color_class
- background_image
- background_image_options
- background_image_options.behaviour
- background_image_options.parallax
- background_image_options.fade
- background_image_options.filter
- Maybe more?
They were still visible when using EXT:mask.
Steps to Reproduce
- Create new content block with CLI command "typo3 make:content-block". Additional fields are not necessary
- Add this to config.yaml of new content block
basics:
- TYPO3/Appearance
- TYPO3/Links
The second step may be correct, or there is more configuration needed for those fields to appear. I couldn't find it in the manual, though.
Expected behavior
Fields mentioned above are shown in backend form
Actual behavior
Fields are missing
Versions
TYPO3 13.4.27
bootstrap_package 15.0.4 and 16.0.0
content_blocks 1.4.3
- Dominant language
- PHP
- Stars
- 354
- Forks
- 209
- Avg merge
- 1m
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
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 benjaminkott/bootstrap_package
-
Difficulty 1/5 Under an hour Newbie friendliness 91/100
benjaminkott/bootstrap_package#1675 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
benjaminkott/bootstrap_package#1633 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 68/100
benjaminkott/bootstrap_package#1617 · 1 comment ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 68/100
benjaminkott/bootstrap_package#1575 · 4 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
benjaminkott/bootstrap_package#1484 ·
All issues in benjaminkott/bootstrap_package
Similar issues
-
Patient Portal
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
php/pecl-networking-ssh2#111 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Phauthentic/cognitive-code-analysis#94 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day