Delete a text node don't work after publish the site

Using Neos & Flow
#1

Hi, strange thing. I delete in the backend a textnode. In the backend this text will disappear. Then I publish the page. Suddenly the textnode on it already. There is no error or warning message in the php5-fpm.log and nginx log.
How do I search the error? Any ideas about the reason?

#2

Have you also checked the Logs in Data/Logs in your neos directory?

#3

Hey @stefkey:

Got this error as well.
I think this problem will occur if you disable the neos.demo site. If the demo site is disabled, you disable the language dimensions. The textfield is stored two times in database, once with language and once without.

I deleted the content element manually in the database.
Make sure you delete the nodedimension as well.
But this is no common solution. Do this on your own risk!

I hope there is a safer way to accomplish this!

#4

Okay, I try it. Thanks a lot!

#5

I am having the same problem. In my case I am deleting a few document nodes and they reappear after I publish the changes.

I did get rid of the previously used language dimension and the demo site package, so those are probably saved with invalid dimensions like you said. ./flow node:repair gives me warnings like this:

Skipping node / because it has no dimension values set
Skipping node /sites because it has no dimension values set
Skipping node /sites/MYSITE/node-weqe5r5q3oknq because it has no dimension values set
Skipping node /sites/MYSITE/node-yyr11lefn3nup because it has no dimension values set
...

I checked where these nodes refer to and I notice they are nodes and childNodes of the problematic document nodes that I want to get rid of.

I would like to try to delete them like you mentioned, but seeing my root node ( / ) in the list makes me nervous. I’ll try with some other nodes and see how it turns out

UPDATE 1

I have removed the nodes with the given path from the database manually, like so:

DELETE FROM neos_contentrepository_domain_model_nodedata  WHERE path LIKE '/sites/MYSITE/node-weqe5r5q3oknq';
DELETE FROM neos_contentrepository_domain_model_nodedata  WHERE path LIKE '/sites/MYSITE/node-yyr11lefn3nup';
...

Now I will backup and try with the root node, the /sites node and a few others that probably break the site if deleted carelessly.

UPDATE 2

I managed to remove all nodes that had no dimension values set, except the root and the sites root (/ and /sites).

The Root is bound as a foreign key and if you delete the /sites, the site fails with an error Could not find "/sites" root node. I’ll try to set the dimensions manually somehow and see if that works.

Important node: Make sure to take a backup before doing any manual changes to the database and run a ./flow node:repair when you’re done.

UPDATE 3

I manually copy-pasted the dimensionvalues column of another row into the root and site root rows, then ran ./flow node:repair and I got this output in the end:

Removed content dimensions from root node
Removed content dimensions from root node
Removed content dimensions from node "/sites"

(the double root reference is from the two workspaces, one live and one from my user)
So, can anyone confirm if these two nodes should not have dimension values set ? Or is there still something I should do about this ?