I created a vocab, linked it to a node type, and started creating nodes.

If I associate a node with the term that matches it, that term gets deleted from the taxonomy list (in the admin page, or shown in the node edit form). However, it still shows at the foot of the node that has the term. Clicking on the link makes the browser go into a 'loading....' state for a long time before giving this PHP error:

Fatal error: Maximum execution time of 60 seconds exceeded in D:\xampp\htdocs\drupal-cvs-nat\includes\database.mysql.inc on line 153

CommentFileSizeAuthor
#12 nat-194804-bug-nat-node-possible-to-assign-for-child-terms.patch2.12 KBanantagati

Comments

harry slaughter’s picture

harry slaughter
Location Omaha NE USA
commented

see also: http://drupal.org/node/155411

molenick’s picture

molenick commented

I am experiencing this issue as well.

theruslan’s picture

theruslan
he/him/his
Primary language Russian
Location Novi Sad, Serbia
commented

Subscribing

Zen’s picture

Zen commented
Version: master » 6.x-1.x-dev
Status: Active » Fixed

This should no longer be possible.

-K

Status: Fixed » Closed (fixed)

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

muhleder’s picture

muhleder commented
Status: Closed (fixed) » Active

Sorry to reopen, but I had this issue in the beta, upgraded to 6.x-1.x-dev, and it still seems to be happening.

I'm using some form validation in a custom module to stop editors classifying nat nodes with their nat categories.

Anonymous’s picture

Anonymous (not verified) commented

Just hit this bug - when saving a node tagged with it's own term, the term gets deleted and the script hangs.

kappaluppa’s picture

kappaluppa commented

I had the same problem today. The way I "forced" the term back was to do a search for it, then it shows up in the term page in the taxonomy manager. I assigned a parent to it, and it showed under that parent. Then I moved it out of the new parent to where it belongs. HOWEVER, If you do not remove the association in the list of taxonomy term options from within the node it re-generates what seemed to be an infinite number of itself as children of itself. Unlinking the term in the node removed the multiple instances of the term. Its sor of like when you look into two mirrors facing each other - you keep getting reflections of reflections...

Still having problems with the node being associated with the term it created....

hawleyal’s picture

hawleyal commented

just set the term assigned to the node to none.

the term reappears.

anantagati’s picture

anantagati commented
Title: adding a node's own term to itself deletes the term » Adding a node to children term of NAT causes problem
Priority: Normal » Critical
anantagati’s picture

anantagati commented

All children of NAT term has to be removed from Taxonomy select box, so user will not be able to choose wrong term.

anantagati’s picture

anantagati commented
Assigned: Unassigned » anantagati
Status: Active » Needs review
StatusFileSize
new nat-194804-bug-nat-node-possible-to-assign-for-child-terms.patch2.12 KB

Attached is a patch for for latest 6.x-1.x-dev.

It removes NAT term and its children from Taxonomy select on node edit form.

arlinsandbulte’s picture

arlinsandbulte commented

sub

anantagati’s picture

anantagati commented
Status: Needs review » Fixed

Commited.

arlinsandbulte’s picture

arlinsandbulte commented

Great job anantagati!
I had experienced this before too. Your fix seems to work great! (tested with NAT 6.x-1.2).
I was planning on testing this out earlier and (hopefully) set to RTBC, but I was too late. Oh well, it works well.

And thanks a bunch for taking ownership of this module. NAT really is a nice little gem of a module!
It is really good to see it getting taken care of.

Thanks again!

anantagati’s picture

anantagati commented

Thank you for encouragement arlinsandbulte.

Status: Fixed » Closed (fixed)

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

Zen’s picture

Zen commented
Assigned: anantagati » Zen
Priority: Critical » Normal
Status: Closed (fixed) » Active
Zen’s picture

Zen commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

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