[SOLVED] Wrong form.yaml-file-pointer on public server with subdomain using

Using Neos & Flow Installation & Deployment
1

Hey,
Have deploy first Neos 3 project on test-server. Most works fine. Only there is a folder-pointer-problem (I guess):

AN EXCEPTION WAS THROWN WHILE NEOS TRIED TO RENDER YOUR PAGE

The form identified by "recall-form" could not be loaded in 
"/var/www/vhosts/test.provider.com/subdomain.test.provider.com/Data/Forms/recall-form.yaml".

I guess it should point to
´`/var/www/vhosts/test.provider.com/subdomain.test.provider.com/```

Packages/Sites/Vendor.Site/Resources/Private/

Data/Forms/recall-form.yaml

###Settings:

#Vendor.Site/Configuration/settings.yaml   
Neos:
  Form:
    yamlPersistenceManager:
      savePath: 'resource://Vendor.Site/Private/Form/'
    presets:
      ########### CUSTOM PRESETS ###########
      preset1:
        title: 'Preset 1'
        parentPreset: 'default'
        formElementTypes:
          ### override default layout path ###
          'Neos.Form:Base':
            renderingOptions:
              layoutPathPattern: 'resource://Vendor.Site/Private/CustomElements/Layouts/{@type}.html'
          'Neos.Form:Form':
            renderingOptions:
              templatePathPattern: 'resource://Vendor.Site/Private/CustomElements/Form.html'

#Vendor.Site/Configuration/NodeTypes.Form.yaml
'Neos.NodeTypes:Form':
  properties:
    formIdentifier:
      ui:
        inspector:
          editorOptions:
            values:
              '': ~
              # Maps to the file Sites/Vendor.Site/Resources/Private/Form/recall-form.yaml
              'recall-form':
                label: 'Rückruf anfordern'

Yaml-file is existing:

#/var/www/vhosts/test.provider.com/subdomain.test.provider.com/Packages/Sites/Vendor.Site/Resources/Private/Data/Forms/recall-form.yaml

identifier: recall-form
label: Rückruf
renderingOptions:
    submitButtonLabel: Rückruf anfordern
renderables:
  -
    type: 'Neos.Form:Page'
    identifier: recall-page-one
    label: Rückruf 1
    renderables:
      -
        type: 'Neos.Form:SingleLineText'
        identifier: name
        label: Name
        validators:
          - identifier: 'Neos.Flow:NotEmpty'
        properties:
          placeholder: Name
        defaultValue: ''
      -
        type: 'Neos.Form:SingleLineText'
        identifier: telefon
        label: Telefon
        validators:
          - identifier: 'Neos.Flow:NotEmpty'
        properties:
          placeholder: 'Telefon'
        defaultValue: ''
finishers:
  -
#AND SO ON ...
```
### Fusion:

    #Vendor.Site/Resources/Private/Fusion/NodeTypes/Form.fusion
    prototype(Neos.NodeTypes:Form) {
        presetName = 'preset1'
    }

On local Server there is no problem with.

- ***What could interrupt the right pointing?***
- ***Is Ressource-pointer somewhere to set?*** 
- ***Maybe I have to change something for subdomain?***
2

When I copy the «"recall-form-yaml» to “/var/www/vhosts/test.provider.com/subdomain.test.provider.com/Data/Forms/recall-form.yaml” the next error is thrown:

AN EXCEPTION WAS THROWN WHILE NEOS TRIED TO RENDER YOUR PAGE
The Preset "preset1" was not found underneath Neos: Form: presets.
page<Vendor.Site:DefaultPage>/ body<Neos.Fusion:Template>/ content/ main<Neos.Neos:PrimaryContent>/ default<Neos.Fusion:Matcher>/
#...

So It sounds like all the stuff within the settings.yaml about

Neos:
  Form:
    yamlPersistenceManager:
      savePath: 'resource://Vendor.Site/Private/Form/'
    presets:
      ########### CUSTOM PRESETS ###########
      preset1:
        title: 'Preset 1'
    #...

does NOT made known to Neos…

  • Is there some yaml-File check-tool?
  • Or can I enable same Tree-overview while dispatch?
3

I remember to Settings.Browser:
Obviously there is some settings lost. I guess at least all from Vendor.Site/Configuration/settings.yaml

missing-form-settings.jpg1234×734 86.3 KB

  • Is there some best-practice to solve the knot and check, if there is some problem for Neos to find the file «settings.yaml» or to render it, because of typo?

Strange, because of on local server all is fine and on public server same file does not operate. Have download the «public»-file and did a Compare: No differences!

For safety I did also the rescan-stuff. No change :rage:

4

##FU**:triumph:,
Found the reason: Typo but not in File-content:
File-Name first-letter-capitalization: Settings.yaml instead of ***s***ettings.yaml

Public server seems to be more strictly then local one :cry:…

5

case (in)-sensitive filesystem. One of the reasons I develop Flow and Neos locally on a case sensitive filesystem. Good that you found it.

6

Good reason – saves a lot of time :grimacing: