Bug: Fix issue #1292 #7440
Open
Bug: Fix issue #1292 #7440
+3
−6
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
…mes 2 characters or less. Removed local regex check as the new page model already prepends the locale.
…'t match individual living languages as acknowledged by ISO 639-1. Removed locales.js file as no longer needed
BPowell76
changed the title
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.
Fixed issue #1292 with new page creation being incorrectly caught in Regex pattern matching that didn't match a language locale.
The server page helper regex pattern now excludes everything that match a living language as recognized by ISO 639-1. New pages can now be created.
In resolving this issue, the locale Regex pattern matching was removed from the new page modal as it adds the locale to the root of the page path. This made the regex matching redundant.
Closes #1292