I have enabled: FeedAPI, Common syndication parser, FeedAPI aggregator [these three seem to work fine alone], FeedAPI Node, FeedAPI Inherit [these last two seem broken].
I have attached a screen shot of the admin/content/feed path on my test site (first screen shot). The first feed listed was constructed using the simple feed content type and seems to work fine. I can click on the link and am given a choice to "Link to site" or "News items". However, the second feed, which uses the same RSS feed, shows that it found 10 items, but clicking on it only gives me the "Link to site" option (second screen shot). Looking at the admin listing of content shows that no nodes have been created.
The third screen shot shows the feed settings for the second feed, which I thought should be creating nodes. What am I doing wrong?
---------------------------------------
As a side note, the user documentation could be better - particularly in the usage/example category. I think there is a lot of potential here, and since you have decided to release an 'unfinished' module to the community, I think you owe it to yourself to gather as many early users as you can. The best way to do that is make it hard for them to misuse it by providing detailed usage instructions. See some of my modules' READMEs for examples; some are better than others.
---------------------------------------
****************************
A development question: would it be difficult to add a screen (html) scraper to create the very feeds that this parses? I have agreements with a few sites that are working on providing RSS feeds to scrape their sites in the mean time, but am currently using third party tools for that. It would be better to bring this under my control. I am willing to write the code if you think it would work well with this module.
****************************
| Comment | File | Size | Author |
|---|---|---|---|
| feedapi3.png | 47.5 KB | rconstantine | |
| feedapi2.png | 10.37 KB | rconstantine | |
| feedapi.png | 19 KB | rconstantine |
Comments
Comment #1
aron novakThanks, I find the problem. All the feeds that don't have a guid at the items did not work. The fix is committed.
---
Yes, user documentation should be better! We really appreciate any involvement to reach better documentation :) I cannot promise that I'll start to write documentation today, but in a long term, i agree that. I plan to create screencast about the features - howto use. And yes, the README can be enhanced too.
******
It's very easy. You just need to write a parser. You can learn parser writing from here and you can walk through how the current parsers work.
Comment #2
rconstantine commentedI now can browse the content link via the admin menu and see the nodes are created. I can also see the nodes show up in the group to which they are assigned, so that is good!!!
However, the feed itself still looks like the feedapi2.png in my first post - i.e. it is missing a link to the list of nodes (if one should be there). So I'm reopening this so you can check on that. I'm assuming it should be there because when I use the light weight version there is such a link.
Comment #3
rconstantine commentedbump
Comment #4
aron novakIf you'd like to get the link to the list of nodes, please install and enable FeedAPI Node Views module.
Comment #5
rconstantine commentedOh, my bad. I thought since the link showed up in the lightweight version without the FeedAPI Node Views module that it would here too. Thanks for the clarification. Perhaps you could change this to a task to add such a note to the documentation? If you don't like that I've changed it, do what you want. It's just a suggestion. Thanks again.
Comment #6
rconstantine commentedSince I mentioned above that the lightweight version has the link built in, it is not obvious that the FeedAPI Node Views module is required to get the same link to show up in regular nodes. Thanks for the module. I'll probably end up contributing to bug fixes and features in the near future as it makes sense to build on something rather than do my own from scratch. Cheers.
Comment #7
alex_b commentedClosing after extended period of inactivity.