Problem/Motivation

There are some modules from the Drupal 7 era that are still available for the current Drupal versions, e.g. Display Suite, Features and others. These modules have been superseded by more modern alternatives to reach the same goals.

Do we want to include and promote these modules in the Project Browser, or should we somehow inform new users that they should shy away from them and instead redirect them to the new modules or appropriate documentation as to how things are done now?

Comments

skourak created an issue. See original summary.

chrisfromredfin’s picture

chrisfromredfin
he/him/his
Primary language English
Location Portland, Maine
commented

Wondering how we might approach this.

  • A flag on d.o? (does one potentially already exist?)
  • Do we just leave it in the description? (put it in the template?)
lostcarpark’s picture

lostcarpark commented

It's a tricky one. Display Suite has over 45,000 installs on D8+ sites (compared to 70,000 odd for D7). It has a stable 3.x release, and an alpha 5.x version, both of which support D10. It seems to have a lot of active development.

Features has "only" 31,000 D8+ sites (plus 125,000 D7 sites), but seems to have its loyal followers. It doesn't yet support D10 in a release, but there seem to be D10 patches in progress. It does discourage sites from using it in the description, linking articles on why it shouldn't be used and pointing them to Config Split. However, there have been discussions in the issue queue on whether it is still needed, and a lot of people still want it. A new maintainer recently took over.

It seems harsh to tell module maintainers that their module won't be featured (or will be given a less favorable listing) in Project Browser when a lot of work is still going into these modules. Maybe the next iterations of these modules will move to a more modern architecture and the current favored alternatives will get complacent, so we can't be sure they won't be the preferred option again in later versions (though I realise the flags could be updated if that becomes the case).

I would favor the descriptions listing the alternative, and if possible linking to articles comparing them, but I guess the module maintainers would need to agree to that.

I think we are talking about a very small number of edge cases. In the vast majority of cases, the problem will take care of itself, as the module won't be updated, so won't match the current core version.

leslieg’s picture

leslieg commented
Status: Active » Closed (outdated)