Fix com_installer errors reported as success#1870
Closed
pascal-meunier wants to merge 8 commits into2.4-mainfrom
Closed
Fix com_installer errors reported as success#1870pascal-meunier wants to merge 8 commits into2.4-mainfrom
pascal-meunier wants to merge 8 commits into2.4-mainfrom
Conversation
added 8 commits
March 9, 2026 16:37
…SON back from middleware; display user messages as a banner
… shell command; middleware will now return a boolean because the session number value was not used and interfered with how other calls expected different return values, leading to dead code and behaviors not matching intent
Contributor
Author
|
urgh, I meant to make a pull request into the 2.4 branch. |
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 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.
This is a fix for https://qubeshub.org/support/ticket/5149 where a custom extension was reported as successfully installed but "git pull" had failed internally.
in views/customexts/tmpl/merged.php the list of success and failed messages is handled separately and a success message won't overwrite a failure message.
There are 2 more messages in language/en-GB/en-GB.com_installer.ini depending on how the git pull failed.
In controllers/customexts.php we check for indications of problems: a null value, an empty array (success) and an array of error strings.