-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[4.0]Remove manifest files and use existing XML info #16115
Conversation
dd71683
to
b556eca
Compare
updated the title to show it is for J4 |
I guess you need to first merge #15884 into the 4.0-dev branch, otherwise you will probably get merge conflicts. |
For sure. As I said I just want testing because I can't believe I can delete this much code for adding an extra 5 lines into 2 files...... Note there are unit test fails unrelated to this PR because of an issue in the upstream framework application library - this is a general issue for the J4 branch - not something related to this PR |
b556eca
to
69f9175
Compare
Rebased with the #15884 in 4.0 - can i please have some testing :) |
Tried installing extensions from Regular Labs and Akeeba, both of which return an alert, Same thing happes on Ajax repsonse is throwing this error:
|
69f9175
to
b5b9fb3
Compare
@wilsonge can you resolve conflicts please so this can be tested |
Forgot this was still open - me and Michael found a problem which meant (as is) this can't work for packages. I'll sit down and try again another day |
ok thanks |
Can you check your other open issues - maybe the same is true for some of them as well https://github.com/joomla/joomla-cms/pulls/wilsonge |
Summary of Changes
This is the first (in hopefully a series) of a cleanup of the Installer classes in Joomla 4, with the aim to make extension installs much more consistent and the classes more manageable.
Testing Instructions
Ensure installing libraries and packages is unchanged from the current state in 4.x
Documentation Changes Required
Classes removed.
Additional Notes
If this works after testing then of course the relevant deprecations must be made in 3.x but I'm not 100% confident of these changes (it feels far too easy) so I want some tests from others first.