cundd / cundd_composer Goto Github PK

Hey there,

thank you for the extension I think it s very usefull. I am experiencing problems trying to switch from shipping dependencies with my extension to installing them by yours.

On 4.7 the BE-Module is loading but on 4.5.22(extbase 1.3.4) I get the following error.

Fatal error: Call to a member function build() on a non-object in typo3conf/ext/cundd_composer/Classes/Domain/Repository/PackageRepository.php on line 87

Have you tested on 4.5 allready or might it be a missconfiguration/missing dep on my installation?

kind regards,

Nabil

When merging JSON files, the replace property should be merged too.

Repository configurations aren't merged. The second definition overwrites the first.

In ext_typoscript_setup.txt the paths to the views are wrong:

module.tx_cunddcomposer {
    view {
        templateRootPath = EXT:cundd_composer/Resources/Private/Backend/Templates/
        partialRootPath = EXT:cundd_composer/Resources/Private/Backend/Partials/
        layoutRootPath = EXT:cundd_composer/Resources/Private/Backend/Layouts/
    }
}

should be

module.tx_cunddcomposer {
    view {
        templateRootPath = EXT:cundd_composer/Resources/Private/Templates/
        partialRootPath = EXT:cundd_composer/Resources/Private/Partials/
        layoutRootPath = EXT:cundd_composer/Resources/Private/Layouts/
     }
}

Trying to install CunddComposer on a fresh instance of TYPO3 6.1.7 introductory package.

After the extension is placed in the typo3conf/ext folder I do:

1. chmod -R 777
2. chown -R www-data:www-data

After installing through the Extension Manager, I get the screenshot and then the admin is not usable anymore - it always displays the error... since I am a newbie with TYPO3, what I do is remove all the files, clear the database and re-install the introductory package.

Any ideas how to debug this?

Apache2 error log is empty.

A compass exception is thrown when the button "Merge and install development mode" is pressed and the require-dev configuration is empty:

...
"require-dev":[]
...

The reason is that an empty require-dev configuration will be transformed to a JSON array instead of a JSON object.