Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUGFIX: Change aloha.placeholder labels to new editorOptions #2761

Merged
merged 1 commit into from Nov 6, 2019

Conversation

markusguenther
Copy link
Member

@markusguenther markusguenther commented Nov 2, 2019

This changs the language label ids for the placeholders of the base mixins.

@kdambekalns
Copy link
Member

From original comment:

How to verify it
Create a text node or an image node with caption. The placeholders will look like that before the change and the labels will be rendered correctly after the change.

Bildschirmfoto 2019-11-02 um 19 18 16

Copy link
Member

@kdambekalns kdambekalns left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this really supposed to go into master? It is declared a bugfix, so it should go into the lowest affected branch.

Also, shouldn't there be a fallback in Neos when resolving those automated translation ids? Or was the id in the placeholder changed by hand to a non-existent value?

@markusguenther
Copy link
Member Author

Oh your right ... so will need to go back to 5.0 I guess but will check that :)

@markusguenther markusguenther changed the base branch from master to 5.0 November 4, 2019 14:06
@markusguenther
Copy link
Member Author

@kdambekalns It was introduced in 5.0 with the following commit.
33f415b

So base branch is now 5.0.

@daniellienert
Copy link
Member

I am always in favor to get such things cleaned up. But couldn't that be breaking if someone changed that label in its own code?

@markusguenther
Copy link
Member Author

@daniellienert Maybe but then it is broken since the 5.0 release when we changed the yaml configuration. We can also provide the old labels, but as we don`t use it in the core it doesn't make so much sense. Or did I miss something.

Copy link
Member

@kdambekalns kdambekalns left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fine with me.

The question about B/C remains, but is out of scope for this change: what happens to translations I have in my XLIFF files that are no longer found, because Neos builds a different ID now when I use label: i18n?

@markusguenther
Copy link
Member Author

When you use i18n and the id has changed and you don`t have a matching label in the in xliff files - you will see the new id or if you define a default value the default.

@kdambekalns kdambekalns merged commit 373f7bb into neos:5.0 Nov 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants