Skip to content
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

[5.2] Usability: One Articles Module to Rule Them All #43404

Open
pe7er opened this issue Apr 30, 2024 · 6 comments · May be fixed by #43610
Open

[5.2] Usability: One Articles Module to Rule Them All #43404

pe7er opened this issue Apr 30, 2024 · 6 comments · May be fixed by #43610
Assignees
Labels
Feature Maintainers Checked Used if the PR is conceptional useful No Code Attached Yet
Milestone

Comments

@pe7er
Copy link
Contributor

pe7er commented Apr 30, 2024

In Joomla 5.2 we would like to have one new “Site Articles” module with parameters to replace all individual Site Article modules in the future:

  • Articles - Archived
  • Articles - Categories
  • Articles - Category
  • Articles - Latest
  • Articles - Most Read
  • Articles - Newsflash
  • Articles - Related

In Joomla 5.2 we just want to have this module as extra module.
From Joomla 6 on, we could consider to stop shipping the old modules with new installations,
and automatically convert them to the new module.

The new module should allow multiple category selection using the "fancy select" class.

@webgras compared the functionality of the old Articles modules in a spreadsheet:
https://docs.google.com/spreadsheets/d/13893BpWLdTBL1Wpe3PH3O6G7zQOFE_8oiqMBeh95f6M/edit#gid=0

@brianteeman
Copy link
Contributor

While I support the idea of a NEW module the idea that there could ever be a migration/conversion would be almost impossible to achieve. You only need to read the JCM etc to see some of the creative ways that these modules have been used with layouts and overrides. Thinking of just a few of my own I cant see anyway that they could be migrated/converted

@HLeithner
Copy link
Member

I would suggest not to write migration code and it's not really needed, we just don't ship mod_articles_* in the future (maybe directly starting with 5.2) and have a good documentation how the migration could be done manually.

So you don't need to implement all features the old modules have and which maybe doesn't make sense anymore and on the other side you can make new features not having a b/c issue.

@chmst chmst added the Feature label May 6, 2024
@rdeutz rdeutz added the Maintainers Checked Used if the PR is conceptional useful label May 6, 2024
@brianteeman
Copy link
Contributor

Is this the sort of thing you are looking for

image

image

image

@drmenzelit
Copy link
Contributor

Yes

@brianteeman
Copy link
Contributor

Should be ready for review by the end of the week

@brianteeman brianteeman linked a pull request Jun 3, 2024 that will close this issue
4 tasks
@brianteeman
Copy link
Contributor

Please see #43610

@Fedik Fedik linked a pull request Jun 3, 2024 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Maintainers Checked Used if the PR is conceptional useful No Code Attached Yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants