Posted by geeklight on July 21, 2011 at 6:35pm
6 followers
Jump to:
| Project: | Feeds |
| Version: | 7.x-2.0-alpha7 |
| Component: | Feeds Import |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Hi,
Unclear to me if this is related to some others issues I see in the queue. I have Feeds using Feeds Xpath Parser (7.x-1.0-beta2) creating/updating nodes from a remote site, and correctly creating/associating terms to the nodes. Apparently working beautifully. However, if I visit a term page (even by following the link from the node itself), it claims 'there is currently no content classified with this term'.
It looks like if I edit one of the nodes, rows get created in taxonomy_index for the node's various relationships, and then that one node is associated with the term in a way the term page expects.
Happy to provide more info, or hear any workarounds. Thanks!
Pete (geeklight)
Comments
#1
Digging...looks like it's related to issues around the call to taxonomy_field_update() in taxonomy.module (line 1720). My log is full of errors such as Undefined property: stdClass::$status in taxonomy_field_update() (line 1720 of /Users/username/Sites/81/drupal-7.4/modules/taxonomy/taxonomy.module)., the implication of which is that the code to save the terms in the index isn't being executed. I'll try to figure out what this means, unless someone has a hint :)
#2
Okay...red herrings all(?). The log msg went away when I changed the Node Processor settings to "Update" rather than "Replace" since that looks per the code that is calls node_load instead of simply querying a few columns to load. But that by itself didn't fix the taxonomy_term row creation. Instead, I deleted all my vocabs, removed the mappings and term fields from the content type, cleared caches, etc. Then started over with one field, re-imported my data and it started to work (including the term page showing the associated nodes!). I'll just close this; there's something funny here, but I'm going to move on.
#3
Hi,
Set this to active again, having the same as original issue. Try now with Update instead of Replace..mat be this helps..
EDIT: The first feeds import goes great, but when the update cycle starts...the updated nodes term reference is somehow not correct.
I have to delete my feeditems entirely and then import the feed again, than it is working, but within the update cycle no go..
This is nice reading about this: http://gaiaes.com/content/understanding-node-processor-plugin-feeds-module
Greetings, Martijn
#4
This was a problem for me in "replace" mode, but I switched to "update", and it is working fine. I updated a node a few times, and it stays listed on the term page as expected. I verified that if I switch back to "replace" mode, it disappears from the term page. After switching to "update" again, it comes back without having to delete everything.
#5
This is still an issue with 7.x-2.0-alpha7. I imported nodes with taxonomy terms where feeds created/updated the nodes AND created taxonomy terms. It also properly linked the terms to the nodes, but did not create necessary records in the taxonomy_term_hierarchy table which prevents the terms from showing up on the vocabulary list terms page as well as select boxes on the node edit page even though they are there.
I haven't hacked into the module code, but if the feeds module is creating taxonomy terms it should be calling functions that create the proper records in all the necessary tables.
"Replace mode" is not an option for me because I have other records in my system that refer back to the nodes that I'm updating.
Here's a fairly simple fix to repair the problem after import. Just run an insert query like the one below to create the missing records:
insert into drupal_taxonomy_term_hierarchy(parent,tid)select 0, d.tid
from drupal_taxonomy_term_data d
left outer join drupal_taxonomy_term_hierarchy h on d.tid=h.tid
where h.tid is null
The above query creates missing term hierarchy records for each term that doesn't have one. I hope someone finds it useful.
#6
Hi, May be can someone set this into the right code, so it is working through the module? I am not a programmer, sorry..
greetings, Martijn