Questions around the TYPO3 integration and plugins as well as Flow and NeosCMS
Forum rules: Always add your TYPO3/Flow, Aimeos and PHP version as well as your environment (Linux/Mac/Win)
#2172 by Michik
06 Dec 2015, 09:37
Hi all,

I'm trying to run the Aimeos package for Neos/Flow. If I call the page via http://www.domain/shop/list" everything seems to work fine, but when I add the Aimeos shop plugin I get this message:

An exception was thrown while Neos tried to render your page
Template file "resource://Aimeos.Shop/Private/Templates/NodeTypes/Plugin.html" could not be loaded

landingPage<TYPO3.Neos:Page>/
body<TYPO3.TypoScript:Template>/
content/
main<TYPO3.Neos:PrimaryContent>/
default<TYPO3.TypoScript:Matcher>/
renderer<TYPO3.Neos:ContentCollection>/
content<TYPO3.Neos:ContentCollectionRenderer>/
itemRenderer<TYPO3.Neos:ContentCase>/
default<TYPO3.TypoScript:Matcher>/
element<Aimeos.Shop:Plugin><Aimeos.Shop:Plugin>/

Also , the different plugin views for the Aimeos web shop are shown but nothing happens when I try to select.
Can you tell me how to fix it. I'm using Neos 2.0.4
Thanks for your help!

Best regards,

Michael K.
#2179 by aimeos
07 Dec 2015, 15:30
The integration into the Aimeos Flow package is only half done up to now. There's a "neos" branch that contains some further improvements to make it work in Neos but even that isn't complete yet. We need someone with a very good Neos expertise to get this done. If you or someone you know can help, we will be glad to push the Neos package forward.
#2193 by Michik
09 Dec 2015, 07:52
Unfortunately, I don't have that overall comprehension of Neos. Maybe a discussion thread at discuss.neos.io could help?
#2196 by aimeos
09 Dec 2015, 10:12
We've tried already in the past but got no answer. But you should create a new topic for your problem nevertheless. The more people show their interest in getting Aimeos in Neos to work, the more someone might be willing to help :-)
#2204 by Christian
11 Dec 2015, 10:12
I'am trying to get Aimeos to run with Neos 2.0, but composer can not integrate the neos branch because it depends on flow 2.0 and Neos 2.0 is using Flow 3.0. Anyway i was able to implement the master branch and i am also able to select Pluginviews. (the error above i was able to fix by creating the empty file - NodeTypes/Plugin.html) but if i save / publish the content the whole system crash and i only get mysterious error messages until i uninstall aimeos.

So i started to install Aimeos with Flow 3.0 standalone. Everything is fine but the "/shop/list" view. It results in an error: Template "basket/mini/body-default.php" not available. Can you help me there?
#2205 by aimeos
11 Dec 2015, 11:18
Christian wrote:I'am trying to get Aimeos to run with Neos 2.0, but composer can not integrate the neos branch because it depends on flow 2.0 and Neos 2.0 is using Flow 3.0. Anyway i was able to implement the master branch and i am also able to select Pluginviews. (the error above i was able to fix by creating the empty file - NodeTypes/Plugin.html) but if i save / publish the content the whole system crash and i only get mysterious error messages until i uninstall aimeos.


The "neos" branch only contains an additional policy yaml file as far as I could see. The rest is outdated and we will remove that branch now.

Christian wrote:So i started to install Aimeos with Flow 3.0 standalone. Everything is fine but the "/shop/list" view. It results in an error: Template "basket/mini/body-default.php" not available. Can you help me there?


One of yesterdays commits simplified the template handling but requires a small change which hasn't been integrated yet. This is fixed now.

As far as I remember, the main problem with Neos was that we haven't found out how to make the Aimeos node types configurable like in the TYPO3 backend. For example, the "Catalog List" component requires a reference to the page/route where the "Catalog Detail" component is placed. This must then be set in the Aimeos configuration.

If you know a bit of TYPO3, here is how it's made there:
https://github.com/aimeos/aimeos-typo3/blob/master/Configuration/FlexForms/CatalogList.xml

The settings from the Flexform are available as e.g. "plugin.tx_aimeos.settings.client.html.catalog.detail.url.target" and are then added to the Aimeos config object as "client/html/catalog/detail/url/target" = "<page or route>".
#2206 by Christian
11 Dec 2015, 12:45
Ok. Thanks a lot. Now it works fine with Neos.

The main problem was the Policy.yaml file wich was missing in Neos/Configuration. I added it as you described at https://github.com/aimeos/aimeos-flow

I even can select a plugin view. Only one problem left if i select the listview:

Class "\Aimeos\Client\Html\Catalog\List\Factory" not available

Any suggestions? :)
#2208 by Christian
11 Dec 2015, 14:43
The File:

.../Neos/Data/Temporary/Development/Cache/Code
/Flow_Object_Classes
/Aimeos_Shop_Controller_AbstractController.php

The Codeline:

$client = \Aimeos\Client\Html\Factory::createClient( $context, $tmplPaths, $clientName );
#2209 by aimeos
11 Dec 2015, 15:21
Christian wrote:I even can select a plugin view. Only one problem left if i select the listview:
Class "\Aimeos\Client\Html\Catalog\List\Factory" not available


A left-over reference to something we had to rename for PSR-4 compliance :-)
Could you update and try again?