On Drupal.org we have few forums which we don't want to delete, but neither do we want people creating new forum topics or replying to the old ones - see #231728: Users still using deprecated forums.

A few things would be needed to do this smoothly:

1. A status for forum tids to state that they're locked
2. Mass updating of forum topics to comments read only when the parent forum is locked
3. Prevent posting of new forum topics when a forum is locked
4. When a forum topic is moved to a locked forum, it should be set to comments read only too

Comments

Leeteq’s picture

+1

heather’s picture

Thanks, catch!

Please also add a style declaration (e.g., "deprecated" ) in the body tag, and the div tags for the deprecated forum. This way the theme designer can control the look of the deprecated forum, to distinguish it from an active forum.

andypost’s picture

Version: 7.x-dev » 8.x-dev

I think we should extend {forum} table for this purpose. Also this can be done in contrib

langelhc’s picture

+1
I have to suppose that is going to happen the same action when the container is locked.

Taxoman’s picture

If forums should be set with locked status (maybe for long time), wouldn't we need to be able to assign permissions on a per-role basis?

I imagine that several "situations" will require admins to edit/delete/unpublish/make-sticky/edit-sticky/move selected content even after the forum is locked. That would solve some other use cases, too.

And this also makes #1360112: D7 port of comment_mover more important. :-)

andypost’s picture

Category: task » feature

This could be a great feature for forum

heilop’s picture

Issue tags: +dlatino
StatusFileSize
new5.51 KB

Hi, I was working in this issue. I attached is an initial version for this feature. Check It please.

develcuy’s picture

Just seen that the patch implements the foundation of the feature:
- A new table: forum_locked, that registers the tid, user and reason
- The UI: in the administration section forums, there is a link "lock forum" that directs to a form asking for confirmation on the given action

good job so far @heilop! Would be great to have some screenshots of your work.

develcuy’s picture

StatusFileSize
new19.15 KB
new8.64 KB

So, there is the link "lock forum":
Lock forum link

And the confirmation form:
Confirm Lock forum

langelhc’s picture

Hi,
I have been creating a modulo for Drupal 7.x, if you wish you can see it in:
http://drupal.org/sandbox/langelhc/1599552

Best Regards.

langelhc’s picture

StatusFileSize
new10.52 KB

Hi everybody, today I was coding with @heilop in this feature and this is the second version of the patch, still missing disable comment in topics.

develcuy’s picture

There is a print_r in your patch, need to re-roll without debug stuff.

langelhc’s picture

StatusFileSize
new10.1 KB

Thnks develCuy, I fixed it, here is the patch without debug stuff.

heilop’s picture

StatusFileSize
new10.97 KB

Hi everybody, this patch remove the forums locked when create a new topic. I was working with langelhc.

langelhc’s picture

StatusFileSize
new12.21 KB

Here is the patch that we have worked with develCuy and heilop.
We added the following:

- Remove 'Add New Forum Topic' Link from locked forum.
- Add locked tag to the list of locked forums in the node edit form.
- Lock a topic when it's moved to a forum locked and viceversa.

Thank you so much develCuy for the support.

heilop’s picture

Status: Active » Needs work

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Issue summary: View changes
Status: Needs work » Postponed

Forum is approved for removal. See #1898812: [policy] Deprecate forum module for removal in Drupal 11

This is now Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.

It will be moved to the contributed extension once the Drupal 11 branch is open.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Project: Drupal core » Forum
Version: 11.x-dev » 1.0.1
Component: forum.module » Code
Status: Postponed » Needs work
larowlan’s picture

Version: 1.0.1 » 2.x-dev