Contrib.social

Add debug informations on translation error message regarding "untranslatable" fields or "untranslatable revisions"

Open on Drupal.org →
Created on 20 December 2019, almost 5 years ago
Updated 2 February 2024, 10 months ago

Hi,

I'm facing an issue with content translation on nodes containing paragraphs (containing nodes, medias etc).

The issue is that for some reasons, some paragraphs have been created at a point when some fields were translatable, and some of these fields are no longer translatable.

Easy fix: remove those paragraphs and create them back you'd say !

Not so easy, since paragraph doesn't allow to "add" new paragraphs on node translations. So we would have to remove the whole translation and create it back. And the error message also pops out on original content sometimes...

What does it have to do with Drupal core? The translation error message is not so helpful in my opinion: "Non-translatable fields can only be changed when updating the current revision.", current revision of what entity? What field is causing that?

So I made a patch I will attach right after, to log what field of what entity causes the error message, so administrators can have an idea of where to look at and maybe figure out a solution.

It may not help anyone but me, but hey, 1 person is more than none !

✨ Feature request
Status

Closed: outdated

Version

9.5

Component
Entity  →

Last updated about 20 hours ago

Created by

🇫🇷France barig

Live updates comments and jobs are added and updated live.
  • Needs change record

    A change record needs to be drafted before an issue is committed. Note: Change records used to be called change notifications.

  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment almost 2 years ago →
    🇺🇸United States smustgrave

    This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request → as a guide.

    Adding a new parameter to the constructor it should default to NULL and throw a trigger_error that it will be required in D11.

    Will need test coverage asw ell.

    But not sure what steps were taken so moving to PNMI for that.

  • Status changed to Closed: outdated 10 months ago
  • Comment 10 months ago →
    🇺🇸United States smustgrave

    Since there hasn't been a follow up going to close for now. If still a desired feature please reopen updating issue summary.

    Thanks.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024