I can't upgrade from 3.0.3 due to data loss.

Created on 12 June 2025, 2 days ago

When I update to a version higher than 3.0.3, when editing fields that use a custom field, the translations are blank.
The original version remains fine. When viewing, if I don't save the translation, it also looks fine.

I don't have any updatedb pending, writing this issue the updbdb made "8005 - Update field storage schema for all 'custom' fields." but with the same result.

With 3.0.3 version it works well

With any higher version, 3.1.10 for example:

ΒΏHas anyone experienced something similar?

πŸ› Bug report
Status

Active

Version

3.1

Component

Code

Created by

πŸ‡ͺπŸ‡ΈSpain Carlitus

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @Carlitus
  • πŸ‡ΊπŸ‡ΈUnited States apmsooner

    Did you mark the sub-fields as translatable? That feature was actually released in 3.0.3. Other than that, you may want to revisit the field settings and save again. I don't know otherwise why you would be experiencing this.

  • πŸ‡ΊπŸ‡ΈUnited States apmsooner

    I'm pretty sure the issue is a configuration issue in the field settings. Please verify that the custom field and the sub-fields (you want translatable) are marked as such. Thats really the only explanation as to why you're not seeing those fields in the form but there no updates that would have wiped out your data. You're just not seeing the values in the form from what i can tell from your screenshots and without those subfields being translatable, they are going to receive the default language value on save.

  • πŸ‡ͺπŸ‡ΈSpain Carlitus

    Perfect, it was what you said, it was just necessary to activate the translation in the subfields of the custom field.

    Thanks!

Production build 0.71.5 2024