-
Notifications
You must be signed in to change notification settings - Fork 13
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
TYPO3 13.4 - Sitepackage not available to add in TypoScript record (include_Static_file) #83
Comments
I can confirm this error or behavior as well. Adjusting the settings in "Site Configuration" (Sites/Site Configuration/) under the "General" tab worked for me. In the "Sets for this Site" option field, you should be able to select the Sitepackage. Once selected, the configuration of the Sitepackage is applied. It appears that other extensions, such as felogin, are also activated through this setting. I wish significant changes like this were communicated more clearly. |
Yeah, I also thought of that. But if I remove bootstrap package in TypoScript and add my site package and BP in the site settings instead, I get a "No page confugured for type=0" error in the FE. |
I haven't tried the "Bootstrap Package", I can only report that it worked for me with the "Fluid Styled Content" version. |
Hi, I´ve got the same issue. Maybe it´s not a bug with the sitepackagebuilder, but with the bootstrap package: benjaminkott/bootstrap_package#1536 |
I see. Yeah might be... |
The site package must be included as site set, you don't need a TypoScript record anymore: https://docs.typo3.org/permalink/t3sitepackage:minimal-extension-siteset |
In ddev I did a fresh install with TYPO3 13.4 LTS, Bootstrap Package 15 and also installed a sitepacke, generated on sitepackagebuilder.com for v13.4 (Beta). The installation was successful, the sitepackage is listed in the Extensions Module, but when I want to add it to the TypoScript record, it's not found there...
![grafik](https://private-user-images.githubusercontent.com/56545341/384430971-390f8c1d-6dc7-4d49-b03c-fb37e21da7af.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxNzc0ODYsIm5iZiI6MTczOTE3NzE4NiwicGF0aCI6Ii81NjU0NTM0MS8zODQ0MzA5NzEtMzkwZjhjMWQtNmRjNy00ZDQ5LWIwM2MtZmIzN2UyMWRhN2FmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEwVDA4NDYyNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWUzZTA0M2IyOGRjNWUxNGNjZDI4Mjc0NDFiZWJkODFkZjA4NTNiNzdjZjE2MTYwNDk5MGIyZjVmNmMyN2UwNTYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.tGeP8UcrgA9CXMtz-EVS4cEOOOHqBaxvfxAJn5oxqPE)
Is this a known bug, You're working on? Or did I miss something?
The text was updated successfully, but these errors were encountered: