User tests: Successful: Unsuccessful:
Pull Request for Issue # .
This Pull Request (PR) adds a missing return statement to the upload
function in file administrator/components/com_joomlaupdate/controllers/update.php
.
This fixes the issue that a 403 "Not allowed" error happens when an exception is raised by the Joomla Update Component's Upload & Update function when uploading a file fails for some reason.
The issue is valid for J4, too, and will be fixed in J4 when this PR has been merged into staging and later that has been merged up into 4.0-dev.
Code review should be enough, but if you want to make a real test ...
On a clean current staging or recent 3.9 nightly build or a 3.9.19, login to backend and go to "Components -> Joomla Update".
Go to tab "Upload & Update" and select zip file with zero byte size for upload.
Hint: You can create a zero size zip file as follows:
touch test.zip
copy nul test.zip
Result: See section "Actual result BEFORE applying this Pull Request" below.
Apply the patch of this PR.
Repeat steps 1 and 2.
Result: See section "Expected result AFTER applying this Pull Request" below.
First a 403 "Access forbidden" error is shown.
After that when navigating or using the "Back to Control Panel" button, the alert with the exception message is shown.
Hint: The not translated language string will be solved with PR #29899 .
The alert with the exception message is shown on the Joomla Update Component page. There is no 403 "Access forbidden" error.
None.
When doing the test with one of the language strings COM_INSTALLER_MSG_...
used in one of the exceptions thrown in that function, you will see that these language strings are not trantlated. This is a separate issue not within the scope of this PR. I will later check if there is already an issue or not.
What remains to be clarified is: Shall we make com_joomlaupdate load the strings from com_installer, or shouldn't we better duplicate the necessary strings into the com_joomlaupdate language file and change their name so we have COM_JOOMLAUPDATE_MSG_...
? @infograf768 What do you think?
Status | New | ⇒ | Pending |
Category | ⇒ | Administration com_joomlaupdate |
Works for me, you can test it with a 0 byte .zip file, then you don't need to modify and files in j!
Works for me, you can test it with a 0 byte .zip file, then you don't need to modify and files in j!
@HLeithner Thanks, I've updated testing instructions accordingly.
@HLeithner Was that a good test from you? If yes, shall I set the test result in the tracker, or will you do that?
I have tested this item
I have tested this item
Status | Pending | ⇒ | Ready to Commit |
RTC
Labels |
Added:
?
?
|
Thanks for testing
By the way, the issue fixed by this PR here is valid for J4, too, and will be fixed in J4 when this PR has been merged into staging and later that has been merged up into 4.0-dev.
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-07-18 11:03:22 |
Closed_By | ⇒ | rdeutz | |
Labels |
I have tested this item✅ successfully on 6c16fef
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/29881.