I followed the documentation provided in the module.
I have 2 Vocabularies, Tags & Incoming Tags. Tags in the "good copy" of taxonomy i want, and Incoming Tags is my sandbox for new tags/un-wanted tags. All nodes from feeds are saved to a content type named Feed Item.
I am encountering a few issues:
- My Inherited Tag that i'm passing (New Feed.png) is being removed from the Feed Item nodes (PSD Feeds.png) that are being created by the feed.
- Look at the Photo Effects tag on the feed list of nodes (PSD Feeds.png). Photo Effects already existed in Tags (Terms in Tags - News Aggregator Site_1245904126014.png), so not sure why the new feed item has a reference to the Photo Effects in Tags, and creates a new term in Incoming Tags? shouldn't it reference the existing term in Tags and not create a new one in incoming tags?
Here's my process. I create a new feed, tag the feed if i want every node it creates to have a certain term (this example i want all new nodes from the feed at psdtuts to be tagged as Photoshop along with the original terms that come from the feed). I save the feed, then move over to the map tab to map the options->tags to the incoming tags vocabulary.
The behaviour i was expecting would be for taxonomy compare to check if the term is in my Tags Vobcabulary, and if it is, use that one and do not create/use a term in Incoming Tags.
I have attached Screen shots of all applicable configurations.
Cheers.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | Module List.png | 33.36 KB | rockitdev |
| Feed Item Content Type.png | 139.23 KB | rockitdev | |
| Feed Content Type.png | 145.43 KB | rockitdev | |
| View Feed.png | 43.92 KB | rockitdev | |
| Terms in Tags - News Aggregator Site_1245904126014.png | 49.33 KB | rockitdev |
Comments
Comment #1
indytechcook commentedHello,
Excellent description of the issue and the screenshots are great. I haven't been using this module for a while so it might be an issue with the latest versions of FeedAPI. What version are you running so I can debug? I will start with the latest DEV.
Comment #2
indytechcook commentedForget the question. It's not FeedAPI version.
This is the expected behavior. I will debug to see where the issue lies.
Comment #3
rockitdev commentedFeedAPI 6.x-1.7-beta2.
Comment #4
rockitdev commentedalso, i'm using Screengrab! a firefox add-on which makes it super easy to generate screenshots... just figured i'd share.
Comment #5
rockitdev commentedComment #6
indytechcook commentedI think the change was in feed element mapper. Originally if the incoming tags vocab was not associated to the content type then is would be associated to the node. Now it appears that even though the incoming tags vocab is not associated to the content type, it still links it to the node. I'm working on a fix.
Cheers,
Neil
Comment #7
indytechcook commentedI think it's fixed. A dev packed should be created in the next 12 hours. Please report back on the DEV package and I will make a new release.
Cheers,
Neil