you're probably going to be swamped this weekend wiht the new Amazon field. but i thought i would ask for this feature, as it might be easier to do while you're in there.
the "We Recommed" block note
would it be possibl to have an "option" is setting that would allow the node to pull from the current list of books randomly like it is already doing - which is cool and saves a lot of wrok
but to also be able to pull from a different "esspecailly created list" (seperate list) just for that node
thanks for considering
Comments
Comment #1
Prometheus6 commentedNot to be rude, but I actually don't do feature requests on GPL stuff for free.
Bug fixes, even help with nasty install problems I will do.
Comment #2
green monkey commentedthat makes sense, you would probably be working your tail off everyday, doing freebies. I didn't find your statement rude at all.
Comment #3
boris mann commentedHey Prometheus...it's fine if *you* don't want to do it, but someone else might like to. Can we leave this open so that people can find it? And if/when we get a status of "bounty", you might be interested in implementing it.
Comment #4
Prometheus6 commentedAt that point, I guess there's a couple old feature requests that could be reopened...
Comment #5
solipsist commentedProm: I understand your point of view but he asked a polite question, and I'm sure he understands that people can't do stuff for free all the time.
I'd like to see a similar feature, maybe the possibility of using flexinodes a custom field for for storing ASINs or keywords related to the node which the amazon module can use to pull data from amazon.com or using data from local amazon-nodes.
Anyway, I love this module and I'd gladly donate some money by PayPal or any other means.
Comment #6
Prometheus6 commentedThe particular feature isn't useful to me, but I can be bribed. The easy way is to modify the module so that the ASINs in the related products field drives a block instead of producing a list of links at the bottom of the node. Second easiest is to add another field. Third is to let Amazon pick up to ten books based on the content of $node->body (I can't guarantee the quality of topic match).
The other thing is, such a module would be for version 4.6 OR 4.7.
Comment #7
solipsist commentedWell, I made this little modification myself, it checks whether the node has any ASINs associated with it, if so it loads one of them randomly and shows in the block, otherwise it pulls one randomly from the database. My original idea was to add a Product Keywords field to every node type which I would use with a SELECT ... LIKE query to find matching Amazon items, it would be more flexible but failing to figure out how to modify the nodeapi hooks and stuff (I have only been using Drupal for a short time) I went with this somewhat simple implementation. Hope it works for you too. Around line 777, replace the existing code with:
Credits goes to Morbus Iff who helped me figure out how to load the node. The code isn't pretty, especially
so I'm sure Prometheus6 could come up with something nicer. You're welcome to commit it if you like.
Comment #8
green monkey commentedyou guys are the best :-)
can't wait to try it out
much thanks
Comment #9
Prometheus6 commentedThis is the block that doesn't show up on the blog page, isn't it?
On the user blog page, where does "node" show up in the url? Also
This ain't working. When you load the node, you don't just get an array of ASINs. You get an array of matching amazonitem records. So once you do node_load(), count the items in $node->amazonnode_data, pick one at random and stuff it into the block.
And please, do this:
instead of this
Now, having done that (because you've been nice) I need to yell at you. You really can't come to me for support of code you've modified because I have no idea what you've done.
Comment #10
Prometheus6 commented