spicywebau / craft-neo

A Matrix-like field type for Craft CMS that uses existing fields
Other
402 stars 63 forks source link

Lost some data and content after upgrading from Craft 4 to Craft 5 #943

Open bhashkar007 opened 1 month ago

bhashkar007 commented 1 month ago

Bug Description

I had built a website using Craft 2.6.3019 several years ago and Neo field is widely used with the combination of Matrix field. Now we are planning to upgrade it to Craft 5 (latest version). So I did:

Please help for it.

Steps to reproduce

Expected behaviour

No response

Neo version

5.2.5

Craft CMS version

5.4.2

What is the affected Neo field's propagation method?

No response

Does this issue involve templating, and if so, is eager-loading used?

This is not a templating issue

LinneaHarts commented 1 month ago

This is happening to me too, just in an upgrade from 4 to 5. And it was working before, so I think a new neo upgrade may have done it.

LinneaHarts commented 1 month ago

I pinned my neo to 5.2.2 and re-upgraded and it seems to have fixed the problem at least so I can go forward with my upgrade

bhashkar007 commented 1 month ago

@LinneaHarts It didn't work for me. I re-upgraed from Craft 4 to Craft 5 with Neo v5.2.2 and still having same problem.

ttempleton commented 1 month ago

Are there any particular field types that are losing content?

LinneaHarts commented 1 month ago

EDIT: sorry, complete different issue

bhashkar007 commented 1 month ago

Thank you, @ttempleton I found this issue in entries of different sections basically with the field types like:

ttempleton commented 1 month ago

If possible, could you please send both your Craft 4 and 5 composer.json/lock files, and your Craft 4 database backup (so I can see the expected content on Craft 4 and then attempt the upgrade to see where the content is being lost) to plugins@spicyweb.com.au, and we'll have a look.

navneetshukla9 commented 1 month ago

@bhashkar007 I have also faced the same issue, It gets fixed when you just re-save the field again from Settings->Fields.

daveguillory commented 1 week ago

Confirming that I also had the same issue, specifically with CKE fields, and it was resolved by following @navneetshukla9's suggestion of re-saving each Neo field in Settings->Fields.

ttempleton commented 6 days ago

My above request remains open for anyone experiencing this.