Invalid TypoScript condition for CookieConsent in TYPO3 v13 ([{$page.theme.cookieconsent.enable} == 1])
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
Research direction
Open Configuration/TypoScript/CookieConsent/setup.typoscript and inspect the CookieConsent condition around page.includeJSFooterlibs. Reproduce on TYPO3 v13.4 by loading the frontend with the theme constants enabled, then verify that TypoScript parses without the reported error and the cookie-consent assets remain included.
Written by the indexing model from the issue text.
Description
Bug Report
Prerequisites
- Can you reproduce the problem on TYPO3 v11.5 LTS
- Can you reproduce the problem on TYPO3 v12.4 LTS
- Can you reproduce the problem on TYPO3 v13.4
- Did you perform a cursory search
to see if your bug or enhancement is already reported?
Description
The Bootstrap Package currently includes a TypoScript condition in Configuration/TypoScript/CookieConsent/setup.typoscript that is no longer valid in TYPO3 v12/v13:
[{$page.theme.cookieconsent.enable} == 1]
page {
includeJSFooterlibs {
contrib_cookieconsent = EXT:bootstrap_package/Resources/Public/Contrib/cookieconsent/cookieconsent.min.js
bootstrap_cookieconsent = EXT:bootstrap_package/Resources/Public/JavaScript/Dist/bootstrap.cookieconsent.min.js
}
}
[end]
Since TYPO3 v12, TypoScript conditions are parsed using the Symfony Expression Language. The legacy {$...} syntax is not supported anymore and causes a parse error.
Steps to Reproduce
- Install TYPO3 v13.x with Bootstrap Package.
- Enable the theme constants (default setup).
- Load the frontend.
Expected behavior
The TypoScript condition should be parsed correctly.
Actual behavior
TYPO3 throws an error during TypoScript parsing:
TypoScript condition [{$page.theme.cookieconsent.enable} == 1] could not be parsed:
Unexpected character "$" around position 1 ...
Versions
TYPO3 v13.x (tested with 13.4)
bootstrap_package (latest release via Composer)
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Automattic/static-site-importer#2958 ·
Maintainers usually reply within 1 day
-
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 77/100
asdf-community/asdf-php#213 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
php/pecl-networking-ssh2#111 ·