Hi Klaus,
the «MixinSmarterLink» NodeType is only the abstraction Layer I use.
With change in first and last Line I wrote above - I guess, you don’t have to use my MixinSmarterLink.yaml.
So you can use your direct declared property «teaserCollection» or the «destination» (
In the end, just the property with LinkEditor defined) from:[quote=“energyWinner, post:1, topic:1262”]
2. a “destination” page with a LinkEditor, to choose the sourcePage.
[/quote]
My code and the Mixin is only a copy & paste from working code.
If the ts2 looks complicated. It’s only a problem for Neos (if I’m not completely wrong: No uri/link from neos-link.node ViewHepler with node-identifier (Paths must not contain two consecutive slashes.)) to find nodes with the «node://» in front. So
- the pregReplace only delete this «node://».
- the findByINdentifier call an find() with «#» in front of the identifierHash.
- the getContainer/getTeaserCollection only go to children with this pathName.
###Debug
I will give a try, but at first glance your code could be the almost same like:
#.ts2-file
value = ${q(node).children('teasercollection').property('_path')}
#fluidTemplate-file
<f:debug title="valueFrom_teaserCollection_Path">{value}</f:debug>
If no big different: This code would be easier to read, I think. But I have to tryout the differences first.
Same nice and sunny weekend for you!
Later on…
Now I see: Maybe It’s the different places, we use our code.
You in page TS-Object [quote=“energyWinner, post:4, topic:1262”]
Put this inside your page TS-Object
[/quote]
I use it in the Prototype from SmarterCollector…