Hello, I'm trying to use the OPML import process but I'm having a problem.
When I import the OPML file, the feed items created, do not use the setting that i set in the feed node.

Let me explain my self better:

I have these content types:
name: Feed type: feedapi_node
name: feep_post type:feeppost

The content type feed is configured to create feed_post items, but when i import my opml files, the Feed creates Story nodes!

If you need anything else to reproduce this problem, please let me know.

I think that the problem is that in the import process, the nodes created are not taking in account the setting from the Feed node, for example all the feed posts generated by the feed node imported from the OPML file, do not have the correct creation timestamp and author.

Thanks a lot.
Claudio.

Comments

cacciaresi’s picture

No news about this issue?

Thanks a lot!
Claudio.

alex_b’s picture

Thanks for reporting.

I just committed a patch. The issue should be solved now.

http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/feedapi/fee...

Check it out and let me know whether it works.

Before and now the feeds get downloaded and parsed when you are creating them. This is probably not ideal when creating lots of nodes with OPML import. Let me know whether there are any problems in regards to that. How many feeds are you importing (how many batches, avareage number of feeds in batch?).

Alex

cacciaresi’s picture

Hello!, first of all, thanks a lot for the patch.
I've update my site with the patch, but it does not solve the problem.

When I do an OPML import, the feeds items created from the feed, do not have the configuration set in the feed content type.

I understand that the desired functionality would be that the feed items created from the feed content type match the configuration from the feed content type, for example, in the Feed content type I set that the items have to be feed-items nodes but the OPML import procees, generates Story nodes. the same happens with the date of the items nodes, I set "Retrieve from feed", but all the "Story" nodes has the date of the import process execution.

Please, if you need another info, don't hesitate to tell me.

Regards,
Claudio.

cacciaresi’s picture

Hello again .. :).

I just want to add some info, after importing the feed, if i "Refresh" the feed, all its items are updated, following the content type configuration, like the creation date.

If the process can be changed to do the same that is done in the refresh process, I think that it would be perfect. :).

Regards,
Claudio.

cacciaresi’s picture

I think this is the last comment :).
I think that the problem, is not related to the OMPL import process.

I did the following test, I took my Feed content type, i added a new Feed, and the items of this feed, have the same behavior, but If i "Refresh" the Feed created, all its items are modify in such a way, that they follow all the configuration set in the Feed content type.

So, the problem is (i think..) in the creation of the Feed.

Bye!
:)

alex_b’s picture

hey claudio - could you update to the latest version of today and try again? (make sure that http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/feedapi/fee... is in) The settings were a bit messed up in the dev version for a while. there might be an interaction with the issue fixed in this last patch.

be sure to run all update scripts. (backup before).

does the settings issue still occur?

cacciaresi’s picture

Hello! I downloaded the last dev version, and the problem is still there.
In fact, the problem is worse, because before this changed, when i refresh the feed, it was working fine, but now, it is not following the specified configuration in the content type.

I do not know if I am being clear enough, please do not hesitate to ask me for more information.

PS: In comment number 3, I think that is the best description of the problem that I'm having. :)

aron novak’s picture

Assigned: Unassigned » aron novak
Status: Active » Fixed

Please test how opml import works now. It is fixed.
Let's do before the testing, but after the module's source is updated: (in some cases this is required):
- create a new content-type and enable it for being a feed.
- do the opml import to the previously created content-type.

Feel free to skip the above method if you experience that after the upgrade everything is ok. If not, you should to according this.

(just a quick note: you can create a feed via block, it uses the same mechanism. maybe it's easier to test to use a block)

cacciaresi’s picture

Hello, I create a new content type, but the problem still exists, the node items, are not following the configuration set in the content type. :(.

What do you mean when you say "you can create a feed via block", do you mean that i can just create a content of the desired content type...

I hope that you can test this, because i may be doing something wrong.. :)

thanks a lot for your time

aron novak’s picture

Thanks for the fast feedback.
I have some guess why you experience this:
- http://drupal.org/node/200037 - please read this carefully. If something is wrong with FeedAPI environment or like this, these tests are the best indicator of these problems
- If i understand you correctly, you'd like to set that the imported feed's items should get their date info from the feed itself. Maybe it's possible that simply your feed does not contain this information. Please supply here a feed URL.
- If you use the devel package, not the CVS, it's possible that you simply downloaded an old package when you tried it out. (your comment is after the auto-update of the package, this is the most unlikely problem, of course)

Because for me the opml-imported feed's items are created according what is set in the content-type settings.

"you can create a feed via block" means that if you go to admin/build/block , you'll see FeedAPI: blocks. You can turn them on and you get a fast way to create a feed w/ 1 click :)

cacciaresi’s picture

Oops, I've being using the dev version! not the CVS version! I thought that the dev version was the same than the CVS version!
I'm going to checkout the project!

Thanks, i'll test this, and give you my feedback :)

Anonymous’s picture

Status: Fixed » Closed (fixed)

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