IBX-4031: Forced published non-translatable field to be shown in current field #71
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6 tasks
|
@mnocon seems like Behat is failing, changes are unrelated. Most likely we will have a similar issue on the main branch. |
|
@barw4 could you backport this change ibexa/content-forms#44 into your PR? This should solve it |
|
@mnocon looks all good now, thank you |
Nattfarinn
approved these changes
Aug 4, 2023
ViniTou
approved these changes
Aug 4, 2023
webhdx
approved these changes
Aug 4, 2023
konradoboza
approved these changes
Aug 7, 2023
|
Kudos, SonarCloud Quality Gate passed!
|
|
Regression tests passed: |
bogusez
approved these changes
Aug 10, 2023
konradoboza
deleted the
ibx-4031-force-published-non-translatable-field-form
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
v3.3Following PR assures that in content edit form there is a 'fresh' value set for fields that are non-translatable. Those values are taken from main published version.
Related PR: ezsystems/ezplatform-kernel#380
Checklist:
$ composer fix-cs).@ezsystems/engineering-team).