[SOLVED] inlineEditable doesn't work (afx)


(Sophie Tschuden) #1

Hi everyone,

I’m pretty new to NEOS and now I’m stucked to get an element inline editable. It’s just not editable and I’ve no idea what I’m missing. Thanks for any suggestions :slight_smile:

My code:

prototype(Projectname:Components.Atom.Section) < prototype(Neos.Fusion:Component) {
    sometext = ''

renderer = afx`
    <section>
    {props.sometext}
    </section>
` }

YAML:

'Projectname:Content.Structure.Section':
 superTypes:
   'Neos.Neos:Content': true
 childNodes:
   section:
   type: 'Neos.Neos:ContentCollection'
   constraints:
     nodeTypes:
       '*': false
       'Projectname:Content.Structure.Section': false
 ui:
   label: i18n
 properties:
   sometext:
     type: string
     defaultValue: 'some text here'
     ui:
       inlineEditable: true

Fusion

prototype(Projectname:Content.Structure.Section) < prototype(Neos.Neos:ContentComponent) {

    renderer = Projectname:Components.Atom.Section {
        sometext = Neos.Neos:Editable {
            property = 'sometext'
        }
    }
}

(Martin Ficzel) #2

You have an error in you nodeType.yaml. The key properties has to on the top level instead of below ui as in your code.

Can you try this?

'Projectname:Content.Structure.Section':
  superTypes:
    'Neos.Neos:Content': true
  ui:
   label: i18n
  properties:
    sometext:
      type: string
      defaultValue: 'some text here'
      ui:
        inlineEditable: true

(Sophie Tschuden) #3

Actually it is not below ui. Lost some formatting while copying it here :see_no_evil: i will edit my post


(Martin Ficzel) #4

Hello @Sophie i pasted the updated code into a local Neos and it works for me. I can insert the Node, see the default text and can edit it inline.

Can you provide some more details about your setup, the Neos version you are using and what actually happens. Can you see the defaultValue of sometext but cannot edit or is the section empty?


(Sophie Tschuden) #5

Hey @martoro its working now. It was not the code at all. Not sure if the browser wanted to make me crazy or its a Backendbug :woman_shrugging: The trick was switching the Editing Modes In-Place --> Raw Content and back. Now everything is working fine. Unfortunately i can’t reproduce that problem. Thanks a lot for your time!


(Martin Ficzel) #6

Can you prepend [SOLVED] to the topic of the thread to indicate to others no further support is needed.