[#45580] - [6.0] Features 60/mod articles legacy remove
- Pending
- Medium
- Build: 6.0-dev
- Draft PR
- # 45580
- Diff
- chmst:features-60/mod-articles-legacy-remove
User tests: Successful: Unsuccessful:
Pull Request for Issue # .
Summary of Changes
- Remove all article modules from new Joomla installations
- Remove the modules, their language files, other files
- Deprecate cleanCache for legacy modules in content
- Fix cleanCache for mod_articles
Testing Instructions
Make a fresh installation of Joomla 6.
Check that no files for the old modules are in the installation
Check that in content - site modules - new only mod article is present
Update an existing former Joomla version
Check that your old article modules and their overrides are working as before.
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
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Administration com_categories com_content Repository NPM Change SQL Installation Postgresql Language & Strings Modules Front End |
Te modules are not deleted on update. Users who have these modules and overrides should not be affected until J8
I am massively against this. It's removing something that has not been deprecated for zero benefit
We don't remove anything for existing applications. Just don't deliver old modules for new installations.
The benefit for NEW applications: Old artilce modules are no longer available. When a user wants to make a module with articles, he can select only the new mod_article where we have all features from the old articles.
This saves us a lot of files (lines of code) which are not at all DRY.
Old applications are not affected and wll work as usual until J8.
So it's ok to completely ignore our policies on deprecation etc?
I am adding deprecations right now. This is a draft and work in progress.
It needs also to remove the system tests, e.g. https://github.com/joomla/joomla-cms/tree/6.0-dev/tests/System/integration/site/modules/mod_articles_archive . Currently they are still running in Drone for this PR, and of course they are failing now as the modules are not available in a new installation.
Do I assume right that the modules shall not be deleted on update? If that is right, I have to add them to the list of exceptions in the build/deleted_file_check.php after this PR will be merged.