Denny Lubitz

Same here. I assume this is caused by xdebug 2.8?

I tried to get this fixed, but I failed, due to my lack of GO knowledge. I'd like to share my findings, so maybe some else can fix it. Main...

@Sebobo Yes, still there on live websites, Also in UI 7.0.3. Unfortunately I have no Demo running at the moment to verify if there is something different. AFAIR this place...

You're right. It's not an issue on the Demo Page. Demo Page uses `Neos.Demo:Content.Columns.Four` NodeTypes, which have a different rendering as `Neos.NodeTypes.ColumnLayouts:FourColumn`. **Neos.Demo:Content.Columns.Four** ``` ... ``` **Neos.NodeTypes.ColumnLayouts:FourColumn** ``` ... ```...

As far as I see, this is already resolved. I could copy a node between two sites within a multi-site environment.

I would expect the kickstart package to ask for the target folder for the newly created package, because there are two different use cases: * Single git repository for developing...

You are right, the finisher needs also a change. Not sure how to implement it there properly. There are two scenarios: 1) The developer configures the interest groups within the...

Please check also the already created rector migrations: https://github.com/neos/rector/pull/39

What about a NodeMigration to rename the property?

@bwaidelich Actually this doesn't work, as the field value might be an array. So it can't replace the string placeholder. Bit hacky, but could work: ``` ids: ["{fieldName.0}", "{fieldName.1}", "{fieldName.2}"]...