User tests: Successful: Unsuccessful:
We are in the process of migrating away from the CMS filesystem package to use the framework version of it. This PR converts all remaining instances where File is used to use the framework version.
Test that you can install extensions and that you can update Joomla.
OR
Codereview.
Please select:
Documentation link for docs.joomla.org:
No documentation changes for docs.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed
Status | New | ⇒ | Pending |
Category | ⇒ | Administration com_installer com_joomlaupdate Libraries |
Labels |
Added:
PR-5.2-dev
|
Labels |
Added:
Feature
|
The problem is, that we are surpressing the error page by having debug mode disabled. And in API there is no error page.
that we are surpressing the error page by having debug mode disabled
Yes, but you still will not see error on screenshot, because response non 200.
And in API there is no error page.
hmhm, yea, that tricky
I have tested this item ✅ successfully on 16a0a1e
Installing and uninstalling works as expected
I have tested this item ✅ successfully on 16a0a1e
I was able to install 4-5 simple to large components and confirmed they worked and uninstalled them successfully.
Status | Pending | ⇒ | Ready to Commit |
RTC
RTC
Labels |
Added:
RTC
Removed: Feature |
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2024-08-26 10:28:43 |
Closed_By | ⇒ | pe7er |
@Hackwar a hint for debuging, hack the ErroDocument, and set status 200
joomla-cms/libraries/src/Document/ErrorDocument.php
Line 122 in e2170c8
The thing that cypress always show blank page when the response code non 200.
This hack will force it to render joomla error page (unless it handled by Symfony error handler), and see them on screen shots in Artifacts.