Hello!
I posted my question in stackoverflow. i cant get the less files compiled...
https://stackoverflow.com/questions/46025225/bootstrap-package-sitepackagebuilder-less-files-compiling

Using the sitepackage from a local path repository with helhum/typo3-secure-web and bootstrap_package does not find the BP's theme.scss, the import directive has to be changed to @import "../../../../../../private/typo3conf/ext/bootstrap_package/Resources/Public/Scss/Theme/theme";.

I'm using the following composer settings:

  "repositories": [
    { "type": "path", "url": "extensions/*" },
    { "type": "composer", "url": "https://composer.typo3.org/" }
  ],
  "extra": {
    "typo3/cms": {
      "root-dir": "private",
      "web-dir": "web",
      "cms-package-dir": "{$vendor-dir}/typo3/cms"
    }
  }

The reason is because the sitepackage from extensions/sitepackage is symlinked to private/typo3conf/ext/sitepackage but the scss parser seems to use the source path of the extension and not the linked one. My guess it has nothing to do with typo3-secure-web.

The project is located at https://github.com/gilbertsoft/typo3-paradeis/tree/refactoring but the last changes aren't currently pushed to the branch. Will do so in the next hours...

I Installed a new sitepackage in a new typo3 installation. When i choose a backendlayout, there is only the message "Oops, an error occurred!". In addition to this, the backendlayout "Default" has no name in the backend. Instead of the name i can click on a white placeholder for the name.

Because i installed the sitepackage in a new typo3 installation, and because i followed step by step the youtube video from benji an mathias, i think there is a issu in the sitepackage.

Hi,
i used the site package builder already in version 9.5. There a newly created sitepackage (bootstrap) showed the additional Example-Layout. In version 10.2.2 / bootstrap-version 11.0.2 the additional template is not shown. Anyone facing the same issue - did I miss to adjust something?

EDIT: Just to clarify: I installed the sitepackage and assigned it in the root template. No other typo script was used, just the newly generated package.

Thanks and best regards
Florian

Hey there,
great package and great detail, I simply got one question:

How's development mode handled? Since there doesn't seem to be any documentation about it, I'm kinda lost .. how do I generate assets and all that?

I did however check out your slides about the anatomy of sitepackages, which was intriguing - thanks for your great work so far!

daybuggin'

Hi Benjamin, to install sitepackage with composer i have added to my composer.json
"repositories": [ {"type": "artifact", "url": "localRepository/"} ], "require": { "vendor/name": "^1" }
From https://sitepackagebuilder.com/ created sitepackage "name.zip" has been copied in my local directory "localRepository".
composer update get's an error alert: [UnexpectedValueException] Package / has no version defined.
I have added in the composer.json in the zip file: "version": "1"
After I put the changed composer.json back into the zip archive, the sitepackage was successfully installed with composer update.

From my point of view it would make sense if the version information of the sitepackagebuilder would not only be entered in ext_emconf.php but also in composer.json to allow a smooth installation with composer.

Thanks a lot
Ulrich

to get the contentCss in RTE must write
editor: config: contentCss: "EXT: ..."
not contentsCss ...
Love the sitepackagebuilder!
Matthias

TYPO3 Version: 10.4.21
Bootstrap Package Version: 11.0.3

The extension provides static TS included via Template -> Includes and a custom page via typeNum for handling AJAX requests. The TS config is as follows:

plugin.tx_mobilityprojects_ajaxapi {
    persistence {
        storagePid = 3
    }
    settings {
        ajaxPageTypes {
            projectUserActions = 1964651634
        }
    }
}

mobilityprojects_projectuseractions = PAGE
mobilityprojects_projectuseractions {
    typeNum < plugin.tx_mobilityprojects_ajaxapi.settings.ajaxPageTypes.projectUserActions
    10 < tt_content.list.20.mobilityprojects_ajaxapi

    config {
        disableAllHeaderCode = 1
        additionalHeaders.10.header = Content-Type: application/json
        xhtml_cleaning = 0
        admPanel = 0
        debug = 0
        no_cache = 1
    }
}

The plugin provides a Controller class which has an action to render JSON (via \TYPO3\CMS\Extbase\Mvc\View\JsonView).

When the extension TS is included before Bootstrap Package TS, the Controller action is not executed (thus no JSON response).
When the extension TS is included after Bootstrap Package TS, the action is executed and the JSON data is returned.

Any idea, why this happens? Or am I missing something very elementary in TS configuration, inheritance or similar?

Working:

Not working:

Thanks for getting back. If you need further information, please feel free to ask.

Cheers,

Hello, when I try to overwrite the labels of the FE [layout] in the pages appearance tab, the dynamic generated BE layouts [backend_layout] are no longer loaded.

Configuration/TsConfig/Page/TCEFORM.tsconfig:

TCEFORM.pages {
  layout {
    label = Choose Your Layout
	removeItems = 2,3
	altLabels {
      0 = The First Layout
      1 = The Second Layout
    }
}

Is there a way to overwrite the labels?

Hi, the Sitepackage-Builder is a great piece of work and makes creating new Sitepackage really easy.

But i can not figure out how i can include the new Site Configuration (/sites/sitepackagename/config.yaml) of TYPO3 9.5 in my own created package.
It should be installed together with my Sitepackage.

Is this possible at all?
I hope somebody can help me with that.

Will the Package Builder be updated to be compatible with Typo3 11 and Bootstrap Package 12?

Hello Benjamin, is there a solution for the incomatibility of the Sitepackage Builder with the new Bootstrap Package 12.x?
Is it enough to update the SASS variable or are further adjustments necessary?

By the way: Thank you for the great work with the Bootstrap Package and the Sitepackage Builder!

First, a big THANK YOU for the Sitepackage Builder. This is a great tool.

I tried the version with the bootstrap package.

In the file /Configuration/RTE/Default.yaml is included EXT:bootstrap_package/Resources/Public/Css/bootstrap4-rte.min.css". But correctly, it must be the file bootstrap5-rte.min.css.

The coding guidelines are for some file types not respected in the outputted .editorconfig of the packagebuilder.

yaml: 4 spaces instead of 2
typoscript: 4 spaces instead of 2
js: 4 spaces instead of 2

I can create a PR if you say it's a bug and not intended.

Hey there, I'm fairly new to Typo3 CMS so this might be an issue with the sitepackagebuilder or not ;-) If not any hint for the root of my problem would be highly appreciated.

I started with a fresh installation of Typo3 v10.2 with the Bootstrap extension installed and then followed the Video Tutorial on youtube about the sitepackage to create a new template. To adopt the generated package from Typo3 v9 and Bootstrap 10 I changed

'constraints' => [
    'depends' => [
        'typo3' => '8.7.0-9.5.99',
        'rte_ckeditor' => '8.7.0-9.5.99',
        'bootstrap_package' => '10.0.0-10.0.99'
    ],
    'conflicts' => [
    ],

to

'constraints' => [
    'depends' => [
        'typo3' => '10.2.0-10.2.99',
        'rte_ckeditor' => '10.2.0-10.2.99',
        'bootstrap_package' => '11.0.0-11.0.99'
    ],
    'conflicts' => [
    ],

in ext_emconf.php. After some minor changes to the generated template (exchange logo image, setting the primary color for Bootstrap) I got the following error message from Typo3 when calling the entry page

Core: Exception handler (WEB): Uncaught TYPO3 Exception: Argument 1 passed to TYPO3\CMS\Frontend\Controller\ErrorController::pageNotFoundAction() must implement interface Psr \Http\Message\ServerRequestInterface, null given, called in /var/www/typo3_src-10.2.2/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php on line 1361 | TypeError thrown in file /var/www/typo3_src-10.2.2/typo3/sysext/frontend/Classes/Controller/ErrorController.php in line 68. Requested URL: https://example.com/

Is this caused by some incompatibility between v10 and the generated sitepackage / my changes to the requirements? I saw that recently support for v10 was added to the buildpackage tool (#31) does it do additional changes to what I did to adopt the generated package?

On a sub-page I was mostly concentrating my work on for the design / template the error does not occur however.

As TYPO3 v10 is made for new projects I wanted to extend the bootstrap_package with a sitepackage in TYPO3 v10

But as seen below I could not choose TYPO3 v10 at "TYPO3 Version"

So my question is: will TYPO3 v10 be selectable?

Also: when it does and I'm already using the package for TYPO3 v9 will there be any issues?
If so: how to upgrade the Sitepackage? Starting it new? Overwriting the files with the new one?

Sorry for so many questions but could not find a duco or anything like this.

FILE: packagebuilder/src/BK2K/Sitepackage/GeneratorBundle/Resources/skeletons/BaseExtension/bootstrap_package/Configuration/TypoScript/constants.txt.twig

########################

CONTENT ELEMENTS

########################
plugin.bootstrap_package_contentelements {
view {
layoutRootPath = EXT:{{ package.extensionKey }}/Resources/Private/Layouts/
partialRootPath = EXT:{{ package.extensionKey }}/Resources/Private/Partials/
templateRootPath = EXT:{{ package.extensionKey }}/Resources/Private/Templates/
}
}

Should be:
plugin.bootstrap_package_contentelements {
view {
layoutRootPath = EXT:{{ package.extensionKey }}/Resources/Private/Layouts/ContentElements/
partialRootPath = EXT:{{ package.extensionKey }}/Resources/Private/Partials/ContentElements/
templateRootPath = EXT:{{ package.extensionKey }}/Resources/Private/Templates/ContentElements/
}
}

For sitepackages built for typo3 v8 through v10 the Resources/Public/Images/PhotoSwipe directory and the contents is missing.

This has the effect that all lightboxes will not have the navigation icons displayed, for image and carousel content elements.

To workaround, copy the directory from the bootstrap_package extension.

More info here - https://godlike.com.au/index.php?id=225

Both the local version and the version at https://www.sitepackagebuilder.com/ show an incorrect display (without CSS and JS) and therefore unfortunately do not work at the moment.


Console:

Currently sitepackages created on https://www.sitepackagebuilder.com are compatible to
'bootstrap_package' => '10.0.0-10.0.99'
so they are not compatible to bootstrap_package 11.x currently:

F. e.: Typoscript configuration still contains config.renderCharset although this configuration option was removed in TYPO3 8.0 (https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/8.0/Breaking-73794-RenderCharsetOptionRemoved.html).