Note for basic backend editor form #313
Closed
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
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.
VIVO GitHub issue: resolves vivo-project/VIVO#3727
Related to #296 and vivo-project/VIVO#3717
What does this pull request do?
Adds a note to the backend property editing form that alerts the user that it does note support language tags.
What's new?
A simple note.
How should this be tested?
Ensure editing form includes new note:
Note: This form does not support the language tags required for multi-language sites. If required, use the front-end editor.Additional Notes:
The basic editing form here does not support i18n. The new note is hard-coded into the form which matches how the other strings are passed to the form.
Interested parties
@VIVO-project/vivo-committers