How decides Typo3 Neos which Settings.yaml to choose? -


I use a Neos installation for multiple domains with different content. Duplicate the package TYPO3.NeosDemoTypo3Org, removing the node-identifier and making some replacements require the things I need which I need.

But only the first settings found in packages / sites / pars. The man is parsed. All changes in settings.yaml found in other packages (Test 1 and Test 2 in the following example) are ignored.

Package / Sites / TYPO3.NeosDemoTypo3Org / Configuration / Settings.yaml

  TYPO3: Form: yamlPersistenceManager: savePath: 'Resource: //TYPO3.NeosDemoTypo3Org/Private/Form / '  

Package / Sites / UDF Test1 / Configuration / Settings.Yaml

  TYPO3: Form: yamlPersistenceManager: savePath:' Resource: // UDF .test1 / Private / Form / '  

Package / Sites / UDF Test2 / Configuration / Settings.ml

  TYPO3: Form: yamlPersistenceManager: savePath: 'Resources: //UDF.Test2/Private/Form/'   

When I first settings .asaml (packages / sites / UDF test2 / config Remove Grace / Settings.eml, next setting.Yamal is used alphabetically (package / site / UDF test1 / configuration / settings.AML) for all 3 site packages When I also delete this file, So UDF Seystyle settings. Yamal is used and anything like this happens.

It will be awesome if someone can highlight me. I'm new to flow and neo and any help is welcome, RTFM, I know, but as I have been told I have to believe it Should that work like I did?

Alternate way?

It is not possible to set the save sheet in the site package, but in general settings, the ./Packages/Application/TYPO3.Form/Configuration/Settings.yaml

{@package} View Placeholder base: ### Nomination: Base class is the renderable for everything 'TYPO3. Form: Base': Rendering Options: Template Path Pattern: Resources: // {@ packet} / private / form / {@ type}. HTML '

but it does not work here

  TYPO3: form: yamlPersistenceManager: #savePath:'% FLOW_PATH_DATA% form / 'sevette:' resource : // {@ package} / personal / form / '  

As you see that I do not really have experience with this stuff, but I am very motivated

All settings.yaml is used, but package packages are merged in order of loading. The loading sequence of packages is based on their dependence. All three packages probably have one dependency, so they are loaded after the second one (which will be required to check in sequence), so the third settings Yum is loaded, then the second settings. Yum loads and overwrites the third, then the first is full and then overwrites the other, so every setting path can be set only once, so

Whatever you are trying to archive will probably not work. This is one of the things we have to decide (site package dependent configuration).

A potential solution is using either a normal package with form configuration and is just set to save this package or using different subcontexts (such as Production / Domain 1 Production / Domain 2) and you want to set this setting according to each percontentext, you can define sub-text by domain (such as triggering through site domain).

Comments

Popular posts from this blog

Pass DB Connection parameters to a Kettle a.k.a PDI table Input step dynamically from Excel -

multithreading - PhantomJS-Node in a for Loop -

c++ - MATLAB .m file to .mex file using Matlab Compiler -