[3.10] Change the Potentially Serious Problem string to Potential Upgrade Issue @softforge #34771
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
|
Thanks! |
|
Docs updated |
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.
Pull Request for Issue #34599 (comment)
Summary of Changes
Change the pre upgrade message from
Potentially Serious Problem.toPotential Upgrade IssueTesting Instructions
Take the packages from here and notice the changed strings: #34754
Actual result BEFORE applying this Pull Request
Potentially Serious Problem.Expected result AFTER applying this Pull Request
Potential Upgrade Issuefor extensions that are not compatible but run with system, user, authentication, actionlog, twofactorauthDocumentation Changes Required
https://docs.joomla.org/Pre-Update_Check
cc @softforge @wilsonge