Hello everybody,
I came here to find out how to configure this great module to create books from feeds. I explain : I have a feed that works very well but the point is that I want it to be merged into a single book called after the feed title, each pages of this book being an item of the feed.
I can create book pages but I can't link them to a specific parent.

Do you have a little idea how to do such thing ? I'm so impressed by the capabilities of drupal that I'm pretty sure that there is a way somewhere for it !

Thank you for the time dedicated to make such great modules !!

Comments

aron novak’s picture

Well, at the moment there is no way to handle book-specific things. It can be done with some additional coding.
Suggestions to start: see feedapi_inherit, i think it can be a good starting point.

docmorphe’s picture

Well thanks Aron but I don't catch the use of mapping taxonomy terms ? Is there a connection between taxonomy and the parent/child relation ?
I found out where was the book hierarchy recorded in the DB, it seems to be in the table "drupal_book" where there is 3 fields : "mlid" "nid" and "bid"

Won't I be wrong forcing the module to insert a new record in this table for every new node, associating it to my book ? In this case a simple scrolling list with each BID in my node/add page would be very helpfull, allowing people to associate their new book node with a parent.

The thing is I don't know where to look into the module code, neither how to correctly code my sql query. In the end It doesn't seems to be a very hard mod but sure it is a very usefull feature ! Maybe we could change the issue category to feature request ?

Thanks again for your time all of you !

docmorphe’s picture

Category: support » feature

Please Aron can you look into my problem, being able to choose a default parent for each feed would be a great feature for your module. Moreover it doesn't seem to be very difficult. I would have done it myself with pleasure but my skills are far too insuficient to go into your code. Maybe someone else here ?

The best I think would be that drupal include the possibility to specify a default parent for each content type, so you would not have to change anything... but modify your code is one thing, modifying drupal core is another.

kreynen’s picture

Was there a solution developed for this? We want to do something similar for the Open Media System's documentation. We will write this if it doesn't exist.

Just looking for an update from either Aron or docmorphe.

aron novak’s picture

It's not ready.