-
-
Notifications
You must be signed in to change notification settings - Fork 436
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
Replaced bundled Zend Framework with zf1-future #2787
Conversation
I also started with this ... but ... we cant just replace Zend. Im pretty sure a few files changed here and need comparison to zf1. (my idea was to adapt all changes from zf1 and see whats left over. yeah, takes some time ... :/) |
Maybe those changes are not even needed anymore, they were based on software that was old, maybe today's ZF or todays' OM already fixed those things... |
This should be all changes ... Update deprecated using ${var} (#2611) sv3n* 19.09.22, 03:46 f96f0b3 |
We have also to check |
I am an advocate for replacing the legacy Zend framework from Magento with ZF1-Future. I presented my arguments here: #2194 (Detailed information) #2191 (TLS issue) If replacing the /lib/Zend directory doesn't create trouble, I can't say the same about the /app/code/core/Zend directory. I did tests removing files/directories one by one and it worked 85%, but there were also some files without which OpenMage cannot work (those related to DB operations). Therefore, the replacement of Zend with ZF1-Future must also aim at updating these files, practically each one should be analyzed, the changes made by the Magento team understood and decided what exactly remains. It is not simple at all. If files will remain then with each new version of ZF1-Future one of us will have to update the ones from our distribution as well, if necessary and Composer will do its job of bringing the framework into /lib/Zend. |
@sreichel - I have checked some of the changes you listed before that target the /lib/Zend directory and they appear to be resolved in ZF1-Future. |
right, actually, we should remove code/Zend completely 😂😂 |
…. anyway this class should never be used anyway because of the eval
The main problem with app/code/core/Zend is that the comments reference to magento's internal ticketing system, with little to none explanation. it's almost impossible (to me at least) to understand why some patches were introduced. But, from what I see, they're extremely old code that's most probably referring to unused code (things that got removed later on), unsupported php versions and so on. |
I compared libZend to latest zf1-future an found some changes ... PRs at ZF1-future:
Left/ToDo:
Done. 😎 |
If it is necessary to create a custom version in /app/code/core, I am not opposed. The fact that we replace /lib/zend with zf1-future is a huge step forward. What would remain custom would be summarized in just a few files, that is something insignificant and that does not involve an effort to correlate with the changes in the ZF1 repository. I know that the ideal would be to have nothing left but this modification will require a long-term testing in the smallest details until we can say that nothing is affected. |
@fballiano we should carefully check these files ...
Other files:
At the end we can remove all files from app/code/core/Zend and apply changes with https://github.com/cweagans/composer-patches. (Patches can be created with https://github.com/symplify/vendor-patches) |
Continuing the effort of removing 3rd party code from out repo.
Notes: