This repository was archived by the owner on Sep 6, 2021. It is now read-only.
Fix #3422: Can't find the string: LK4: NO_DISABLED_DIRECTORY#3586
Merged
redmunds merged 1 commit intoadobe:masterfrom May 7, 2013
TomMalbran:tom/fix-issue-3422
Merged
Fix #3422: Can't find the string: LK4: NO_DISABLED_DIRECTORY#3586redmunds merged 1 commit intoadobe:masterfrom TomMalbran:tom/fix-issue-3422
redmunds merged 1 commit intoadobe:masterfrom
TomMalbran:tom/fix-issue-3422
Conversation
ghost
assigned
Contributor
|
Merging. |
redmunds
added a commit
that referenced
this pull request
May 7, 2013
Fix #3422: Can't find the string: LK4: NO_DISABLED_DIRECTORY
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
For issue #3422.This just removes the unused NO_DISABLED_DIRECTORY string from all the languages except fr and ja.
I also tried to reproduce the steps, but installing an extension did not created the disabled folder. I think that the string might be used for the Extension Disable feature, if so, we can just close this request, and when that is implemented, the string could be used with a different text probably.