Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-24625

Editing content with untranslatable fields in 2nd language on PlatformUI doesn't save changes

    Details

      Description

      Steps to reproduce:

      1. Ensure an ezpublish installation with three languages, eng-GB, fre-FR and ger-DE, for instance;

      2. On legacy admin backend create a folder "Folder EN" in eng-GB language;

      3. Edit it in fre-FR language and rename it to "Folder FR";

      4. Edit it in ger-DE language and rename it ti "Folder DE";

      5. Go to platformUI, to "Platform -> Content Structure";

      6. Click on "Content tree" on the leftside menu, and on the content tree, click on "Folder EN";

      7. On the language icon on the "Content" pane, pick fre-FR from the languages dropdown, then click on "Edit" on the action bar to the right;

      8. Verify you're on the editing context for the fre-FR version of the content "Folder EN", which in such version is instead titled "Folder FR";

      10. Rename it to "Folder FR v2" and publish it;

      11. Take notice that the name editing has NOT been changed, it is still titled "Folder FR";

      12. Repeat the same edition on "eng-GB" language editing context, by renaming it to "Folder EN v2"and publish it;

      13. Take notice that the name ediuting has been changed as expected, it is now titled "Folder EN v2";

        Issue Links

          Activity

          Show
          Mateusz Hyndle (Inactive) added a comment - PR: https://github.com/ezsystems/PlatformUIBundle/pull/377
          Show
          Mateusz Hyndle (Inactive) added a comment - Merged into master: https://github.com/ezsystems/PlatformUIBundle/commit/f150bd42eeeceb38428b83c173110948504ec9a3
          Hide
          Rui Silva (Inactive) added a comment - - edited

          Tested and approved by QA for master. <- Invalidated QA process, needs new test.

          Show
          Rui Silva (Inactive) added a comment - - edited Tested and approved by QA for master. <- Invalidated QA process, needs new test.
          Hide
          Rui Silva (Inactive) added a comment - - edited

          This issue does not pertain to content types in general afterall as thought when reported.
          It was in the meanwhile discovered that this issue is related to untranslatable fields, so can be tested only with some content types (those that have such fields).
          At QA time, it had been done with a content type (Link) that did not reflect this issue's cause afterall, and not with Folder, as reported in it, because I thought this problem of untranslatable fields was actually blocking this from being tested now at QA time. Thus, the test was adapted to use Link, but this is not correct afterall.
          Now, testing with Folder, I can't even get to the redirect after the publishing, like I could before when this was reported, because I get the console error:

          400 GET:
          A value is set for non translatable field definition 'show_children' with language 'fre-FR'
          

          and it doesn't get past it.

          Show
          Rui Silva (Inactive) added a comment - - edited This issue does not pertain to content types in general afterall as thought when reported. It was in the meanwhile discovered that this issue is related to untranslatable fields, so can be tested only with some content types (those that have such fields). At QA time, it had been done with a content type (Link) that did not reflect this issue's cause afterall, and not with Folder, as reported in it, because I thought this problem of untranslatable fields was actually blocking this from being tested now at QA time. Thus, the test was adapted to use Link, but this is not correct afterall. Now, testing with Folder, I can't even get to the redirect after the publishing, like I could before when this was reported, because I get the console error: 400 GET: A value is set for non translatable field definition 'show_children' with language 'fre-FR' and it doesn't get past it.
          Hide
          Rui Silva (Inactive) added a comment -

          Regarding the previous explanatory comment, test fails with given fix.
          Sending back to input queue.

          Show
          Rui Silva (Inactive) added a comment - Regarding the previous explanatory comment, test fails with given fix. Sending back to input queue.
          Hide
          Mateusz Hyndle (Inactive) added a comment -

          I can't reproduce the problem. I've done all steps as in scenario and everything is working correctly - edited translation is updated after publishing. I have tested it in both DEV and PROD environments.
          Here is screencast for my tests in PROD env: https://youtu.be/0aneSuBEf6g (quality is not the highest but you can see that content is updated after publishing)

          Show
          Mateusz Hyndle (Inactive) added a comment - I can't reproduce the problem. I've done all steps as in scenario and everything is working correctly - edited translation is updated after publishing. I have tested it in both DEV and PROD environments. Here is screencast for my tests in PROD env: https://youtu.be/0aneSuBEf6g (quality is not the highest but you can see that content is updated after publishing)
          Hide
          Rui Silva (Inactive) added a comment - - edited

          This issue does not seem to be reproducible any more.
          Some PR must have fixed it in the meanwhile.
          Sanity tests were executed in this scope, and nothing unusual to report.
          Will close this as fixed.

          Show
          Rui Silva (Inactive) added a comment - - edited This issue does not seem to be reproducible any more. Some PR must have fixed it in the meanwhile. Sanity tests were executed in this scope, and nothing unusual to report. Will close this as fixed.

            People

            • Assignee:
              Unassigned
              Reporter:
              Rui Silva (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day, 7 hours
                1d 7h