[Meta] Tasks to deprecate Forum

Created on 1 March 2022, over 2 years ago
Updated 6 March 2024, 4 months ago

Problem/Motivation

This issue is to coordinate and track the steps needed to move Forum to contrib. See Remove a core module and move it to a contributed project of the deprecation policy.

The contrib project is Forum

The removal of Forum was approved in #1898812: [policy] Deprecate forum module for removal in Drupal 11

Proposed resolution

Remaining tasks

  1. Begin finding someone to maintain the contrib version of the extension.
  2. Move integrations implemented by other modules to the extension.
    Create child issues or child meta issues, as needed, to address the following points. Not all points will apply to all extensions.
  • Do a thorough search of core for any remaining references to the extension. If references are found, outside of the extension, then create issues to remove the references.
  • Create the contrib project with a stable release.
  • Deprecate the core extension. Use the Issue Summary template or core extension deprecation 📌 Deprecate Forum module in Drupal 10 Postponed .
  • User interface changes

    API changes

    Data model changes

    Release notes snippet

    🌱 Plan
    Status

    Fixed

    Version

    11.0 🔥

    Component

    forum.module

    Created by

    🇳🇿New Zealand quietone New Zealand

    Live updates comments and jobs are added and updated live.
    Sign in to follow issues

    Comments & Activities

    Not all content is available!

    It's likely this issue predates Contrib.social: some issue and comment data are missing.

    • 🇳🇿New Zealand quietone New Zealand

      Update to latest template from the policy .

    • 🇳🇿New Zealand quietone New Zealand
    • 🇳🇿New Zealand quietone New Zealand
    • 🇳🇿New Zealand quietone New Zealand

      Because forum is in a quite a few migration I made an issue to check them separately.

    • 🇳🇿New Zealand quietone New Zealand

      There are references to forum in the following

      • core/tests/Drupal/KernelTests/Config/Schema/MappingTest.php:
      • core/modules/system/tests/src/Functional/Update/Y2038TimestampUpdateTest.php:
      • core/modules/node/tests/src/Functional/NodeTypeTest.php:

      This could be an issue for comments;

      $ grep --exclude-dir={vendor,node_modules,forum,themes} -riw 'forum' core | grep -v phpstan-baseline.neon | grep -v Test | grep -vi migrat | grep -vi "drupal[6|7].php" 
      core/lib/Drupal/Core/Extension/InfoParserInterface.php:   * See forum.info.yml for an example of a module .info.yml file.
      core/lib/Drupal/Core/Entity/entity.api.php: * - The Forum module defines a content type in node.type.forum.yml and a
      core/lib/Drupal/Core/Config/Entity/ConfigDependencyManager.php: * dependencies key. For example, the Forum module provides the forum node type
      core/lib/Drupal/Core/Config/Entity/ConfigDependencyManager.php: * and in order for it to be deleted when the forum module is uninstalled it has
      core/lib/Drupal/Core/Config/Entity/ConfigDependencyManager.php: * an enforced dependency on the module. The dependency on the Forum module can
      core/lib/Drupal/Core/Config/Entity/ConfigDependencyManager.php: * type configuration entity that depends on functionality provided by the Forum
      core/lib/Drupal/Core/Logger/RfcLoggerTrait.php: * @see https://groups.google.com/forum/#!topic/php-fig/Rc5YDhNdGz4
      core/lib/Drupal/Core/Render/theme.api.php: *     when the forum is rendered, following render array can be used:
      core/lib/Drupal/Core/Render/theme.api.php: *       '#theme' => array('forum__' . $tid, 'forum'),
      core/lib/Drupal/Core/Render/theme.api.php: *       '#forum' => $forum,
      core/lib/Drupal/Core/Render/theme.api.php:  // Kill the next/previous forum topic navigation links.
      core/modules/comment/comment.module: * Users can post comments to discuss a forum topic, story, collaborative
      core/modules/system/tests/modules/url_alter_test/url_alter_test.install:  // Set the weight of this module to one higher than forum.module.
      core/modules/path/path.module:      $element['value']['#description'] = t('Specify the existing path you wish to alias. For example: /node/28, /forum/1, /taxonomy/term/1.');
      core/modules/field/src/Entity/FieldStorageConfig.php:   * classic use case for this is node body field storage since Book, Forum, the
      core/MAINTAINERS.txt:Forum

      And there are plenty of references in themes.
      grep --exclude-dir={vendor,node_modules,forum} -riw 'forum' core | grep -v phpstan-baseline.neon | grep -v Test | grep themes | grep -vi migrat | grep -vi "drupal[6|7].php"

    • 🇳🇿New Zealand quietone New Zealand
    • 🇳🇿New Zealand quietone New Zealand
    • 🇬🇧United Kingdom catch
    • 🇳🇿New Zealand quietone New Zealand
    • 🇳🇿New Zealand quietone New Zealand

      Removing 📌 [11.x] Remove forum CSS from themes and profiles Closed: duplicate from the Issue Summary. That will be done when Forum is removed.

    • Status changed to Fixed 4 months ago
    • 🇳🇿New Zealand quietone New Zealand

      Thanks to everyone who worked on the child issues to make this happen!

      I am adding credit to myself for the overall admin required to keep this on track.

    • Automatically closed - issue fixed for 2 weeks with no activity.

    Production build 0.69.0 2024