Merged
Conversation
Member
|
Cursorbot in that PR even pointed out that it shouldn't have changed. 
I think maybe it was just misunderstanding during that PR that the customization needs to go in your own messages.php, not in Statamic's. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This pull request fixes an issue where it wasn't possible to customize the "Create Entry" translation.
This was due to the
statamic::prefix being added in #12598, causing it to look at Statamic's translations instead of the app's translations. I'm not sure why it was added but the custom translation shows fine in card view 🤷♂️Fixes #14078