Add Drupal 11.x as option in new forum posts

Removing the taxonomy terms for old Drupal versions would remove that taxonomy term from forum posts. I know those posts are probably old enough not to be taken as new posts, but I would prefer to still be able to search between Drupal 4.x posts, if necessary.

Since Drupal 9.x and Drupal 10.x are already added to the Drupal version field, Drupal 11.x should be added too.

This task requires somebody who can administer taxonomy terms on drupal.org. As site moderator, I can only delete or rename issue tags.

But can't posts with those ancient tags (4.5, 4.6, 4.7, etc.) be re-tagged with a "Drupal 6.x or older" tag, and then those old tags deleted?

Of course, it would be nice to keep the tags for the posts, but hide in the form, if that's possible. It doesn't make a lot of sense to include 4.5, 4.6, 4.7, etc. under "Drupal version" when creating a new Forum post in 2024.

The new 11.x term was added.

The height of the multiple select could be changed, but I don't see an issue with that as it's common not to see all values in multiselect fields.

apaderno → credited fjgarlin → .

But can't posts with those ancient tags (4.5, 4.6, 4.7, etc.) be re-tagged with a "Drupal 6.x or older" tag, and then those old tags deleted?

Yes, they can. There are few people who can do that, though; probably they all have the administrator role and few time to follow this issue queue.

Asking on Slack is probably the quicker way to reach them.

(The Drupal 11.x tag has been added.)

Thanks @fjgarlin. Actually, simply reversing the sort order would solve it, and let the older tags live at the bottom. I updated the Issue Summary, adding this suggestion:

• Drupal 11.x
• Drupal 10.x
• Drupal 9.x
• Drupal 8.x
• Drupal 7.x
• Drupal 6.x or older
• None

Update Issue summary.

If we agree on that being the desired order I can reorganize.

Don't worry about slack. Sometimes we might get quicker replies there, but anything "official" usually happens via issues. Slack is a nice (but entirely optional) add-on.

Thanks @jgarlin, that would be fantastic, making "Reduce tag options" and "Taller select box" redundant.

The order was reversed now.

This is great, much better, thanks @fjgarlin.

PS. Since it seems like you have database access @fjgarlin: Just in case you have time, the Planet Drupal has been flooded recently, and deleting the recent 47 old posts would be a huge improvement: #3402661-16: Clean up Drupal Planet for old posts → .

I have higher access level in www.drupal.org via the UI, but I do not have access to the database.

If this is something that needs to happen often, maybe we need an issue to create a script (or even better a UI admin page) that does this for us, where we input the URLs and the scripts searches and changes the timestamps automatically. Relying on a person to do a repetitive task on the live database is high risk.

Ok, thanks for clarifying, and I agree that direct database wrangling is risky, and that script or UI is preferred.

I do think this should be prioritized, for all the reasons I list in the Issue Summary of 📌 Clean up Drupal Planet for old posts Active . Feel free to reopen that issue, and add a "Create script or UI, to remove old, duplicate posts" under "Remaining tasks" and set to "Needs Work", if you agree that it's a good idea :-)