The ability to have an MN Feed's tag(s) automatically applied to all news stories imported via that Feed is a *huge* benefit of 6.x.1.1 -- it saves us a horrific work-around of using Yahoo Pipes and a whole slew of regex to get needed feed-specific tag into every individual feed item! But I'm having a very strange problem where tags' geodata disappears once items are imported.
Here's whats happens:
1. Clean install of Managing News 6.x.1.1
2. Go to /import/terms/delete-items?display=views-mode-map and delete all the default terms.
3. Go to /import/terms?display=views-mode-map and import CSV of our desired terms, including their lat/lon data.
4. Go to /admin/content/taxonomy/1, and verify that terms imported with lat/lon data. They do, and the "Use for term extraction" checkbox is checked.
5. Go to /node/add/feed, and create a new feed -- taggging it using on of the just-imported "tag" terms.
6. Upon creation, feed items are imported, and the map in the right sidebar shows no dots.
7. Go back to /admin/content/taxonomy/1, and check out the term in question. It now has no lat/lon data, and the "Use for term extraction" box is no longer checked.
This happens every time. I can go back to /import/terms, and re-import my CSV file (after overriding that feed importer at /admin/build/feeds/edit/terms/settings/ExtractorTermProcessor to "Update Existing Terms" -- at which point the geodate and "Use for term extraction" setting go back to the way they were in Step 4. But the next time a feed updates, the same purge happens.
I have not yet tested to see if this will happen for MN's default location terms if they're assigned to a feed. But is there something I'm doing wrong here, or is this a truly a bug with the new term-inheritance feature?
Comments
Comment #1
TKS commentedQuick Update: I did a test on another MN install, and the same problem exists when using the location terms that are included by default. If you add a tag to a feed, that tag's lat/lon and "Use for term extraction" checkbox get purged.
Comment #2
Will White commentedThanks for the report. We will investigate. Bumping up priority.
Comment #3
Will White commentedFixed with this patch to data_taxonomy: http://drupal.org/node/937606
and this commit to Managing News: http://drupal.org/cvs?commit=434300
Comment #4
TKS commentedI can confirm that the data_taxonomy patch fixed this on our install. Thanks Will!
TKS