joomla-cms
joomla-cms copied to clipboard
[6.0] Move CMS Filesystem package to compat plugin
Summary of Changes
This PR moves the CMS Filesystem classes to the compat plugin, allowing legacy third party code to still run when the plugin is active, but making the first step to finally remove it from the CMS.
I've added the Composer Dependency Changed label because the PR requires composer i to be run.
Testing Instructions
Copy the following line in a view of your choice to generate a call to the legacy classes:
var_dump(\Joomla\CMS\Filesystem\Folder::listFolderTree(JPATH_BASE, '.'));
Make sure the compat plugin is enabled AND you have to run composer i to generate an updated class loader file
Visit the view you edited in the browser to see an output of the call to the legacy class. Disable the plugin and see an error thrown instead.
Link to documentations
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
Please move the "classes" folder outside of the src folder. Like it is now you have the src folder managed by a classloader and then the "classes" folder managed by another classloader. I would also rename the "classes" folder to legacy or so.
Done
Thanks for all the work on these @Hackwar, can you resolve this little conflict? Then we can merge.
I have tested this item :white_check_mark: successfully on f7007b8f766441d71cb7f010cc7b5b690a7fbdfa
Good test after full wipe.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/44240.
Tested that the folder did not exist and then it all worked. Better testing instructions please
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/44240.
I have tested this item :white_check_mark: successfully on f7007b8f766441d71cb7f010cc7b5b690a7fbdfa
When I worked out what was actually needed... it worked
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/44240.