687: Allow users that can import glossaries to flush them at import #680
Conversation
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
Allow users that can edit glossaries to flush them at import.
ocean90
changed the title
ocean90
approved these changes
Mar 15, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
It would be great if users that are able to import glossaries to also be able to flush them at import.
If users with the right permissions are not able to flush at import, it's quite a mess. If the import file contains entries that are already in the glossary these will be added once again at each import.
For reference, the Romanian Team uses an exported file from Google SpreadSheets to update the glossary. Since there is no way to flush at import or to delete the glossary we're facing lots of duplicates: https://translate.wordpress.org/locale/ro/default/glossary. Furthermore there is no bulk-action to delete the entries, which makes the cleanup process quite hard.
IMHO, allowing users that can import glossaries to also flush them is the best approach.
Fixes #687.