This patch tags a post with its parents' terms (as requested in http://drupal.org/node/230131 and http://groups.drupal.org/node/14161).

Given the following taxonomy,

- Books
-- Fiction
-- Non-Fiction
- Magazines
-- Weekly
-- Monthly

a post tagged with 'Fiction' will also be tagged with 'Books'. Note that applying this patch may break modules relying on Drupal's default behavior.

CommentFileSizeAuthor
recursiveTags.patch1.4 KBklharris

Comments

damien tournoud’s picture

Version: 5.14 » 7.x-dev
Category: task » feature
Priority: Minor » Normal
Status: Needs review » Patch (to be ported)

This is a feature request, and feature requests need to be filled against the most current development version (D7).

likewhoa’s picture

nice patch, thanks.

catch’s picture

Status: Patch (to be ported) » Needs work

If you want this to go into core it'll at a minimum need to be re-rolled to match http://drupal.org/code-style and also to make this behaviour configurable.

Anonymous’s picture

Thanks catch - could you post your link again? I'm getting "page not found"

Thanks!

damien tournoud’s picture

OneTwoTait’s picture

Will this work for Drupal 6.x too?

OneTwoTait’s picture

I haven't had any luck with applying this patch to Drupal 6.x

wretched sinner - saved by grace’s picture

I like this :) Will try to have a look at it at some stage soon.

yulia-1’s picture

is there anything like this for Drupal 6?

MattDrupalee’s picture

Title: Recursive Tagging » Recursive Taxonomy Tagging

Also interested to know if there is something similar available in Drupal 6..?

amc’s picture

Issue tags: +taxonomy

Tagging.

catch’s picture

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

This would need to be a new field widget / validator now. Moving to Drupal 8.

dhigby’s picture

I am also interested in a way to enforce recursive tagging in D6.

OneTwoTait’s picture

Made some progress. Now, instead of doing nothing, it gives an error message when a node is saved: "user warning: Duplicate entry '24-0' for key 'PRIMARY' query: INSERT INTO term_node (nid, tid) VALUES (0, 24) in (site directory)/modules/taxonomy/taxonomy.module on line 720."

thomas1977’s picture

Just found this issue after having looked for a solution to save parent taxonomy terms automatically along with the child term in the node. Don't know if this is the right place to post - but has there been any progress on a possible solution to this (I'm on D7)? Any module? Anything?

Anonymous’s picture

Assigned: klharris » Unassigned

I'm still interested in this topic as well.

jibran’s picture

Version: 8.0.x-dev » 8.1.x-dev
Component: taxonomy.module » entity_reference.module
Issue summary: View changes

After #1847596: Remove Taxonomy term reference field in favor of Entity reference the field part of the taxonomy belongs to entity reference field. Feature requests are part of 8.1.x now.

jibran’s picture

Status: Needs work » Postponed
amateescu’s picture

Component: entity_reference.module » taxonomy.module
Issue tags: -taxonomy

Drupal\taxonomy\Plugin\EntityReferenceSelection\TermSelection is provided by the Taxonomy module, moving back to the right queue.

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

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now 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.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now 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.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now 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.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now 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.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now 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.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now 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.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.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.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). 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.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now 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: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

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

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.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.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.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.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now 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.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now 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.

Version: 10.1.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, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

Status: Postponed » Postponed (maintainer needs more info)
Issue tags: +stale-issue-cleanup

Thank you for sharing your idea for improving Drupal.

We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

smustgrave’s picture

Status: Postponed (maintainer needs more info) » Closed (outdated)

Since there's been no follow up and as a feature request. Going to close out. If still a valid request please re-open

Thanks all