search

SchmidtWebmedia / grid-for-gridelements

Add an easy to use grid element with GridElements. It's Framework independent. Prepared for Bootstrap v4.
1 stars 2 forks source link

An elements vs Elements typo in composer.json? #3

Closed pixelplumber closed 4 years ago

pixelplumber commented 4 years ago

Hi. Not a developer, just an integrator of TYPO3, but trying out your extension in TYPO3 9.5 and I receive errors in the BE re. missing classes eg: "An error occurred trying to process items for field "twocol" (No class named SchmidtWebmedia\GridForGridElements\Controller\GridController)."

Is it because the composer.json line is lower case elements instead of Elements? Doesn't match the namespaces in the Classes folder?

https://github.com/SchmidtWebmedia/grid-for-gridelements/blob/b2527f215d3e09f710d3c2e3c9eb706eef36c30c/composer.json#L25

$ grep -Rin forgridelement * grep: bin/.ea-php-cli.cache: No such file or directory composer/autoload_psr4.php:75: 'SchmidtWebmedia\\GridForGridelements\\' => array($baseDir . '/public_html/typo3conf/ext/grid_for_gridelements/Classes'), composer/autoload_static.php:191: 'SchmidtWebmedia\\GridForGridelements\\' => 36, composer/autoload_static.php:564: 'SchmidtWebmedia\\GridForGridelements\\' => composer/installed.json:5657: "SchmidtWebmedia\\GridForGridelements\\": "Classes"

The namespaces in the Classes folder all have capital E.

pixelplumber commented 4 years ago

If I sed -i 's/GridForGridelements/GridForGridElements/g' on the composer autoload files and installed.json in vendor/composer/ the extension works. I tried changing the composer.json file included in the extension and clearing the composer cache and updating, but I assume it doesn't work as it pulls the lower case version off the typo3-ter repo?

SchmidtWebmedia commented 4 years ago

Sorry for late response. I didn't get any notification about an issue. Currently I have no instance running on Composer. Maybe you can checkout the current master and tell me if it work now?

pixelplumber commented 4 years ago

Hi Marco, no worries at all! Pulling that from github direct instead of ter that update fixes it for me. Cheers, Mark.