developing book review -- two blocks or two modules?
hi im working on a book review module to allow multiple reviews (the existing one only supports a single review per module) I plan to so there will be two objects - a book - and a review Is it better to have both as two blocks in the same module ? or have two separate modules? Any good places to check on this ? tnx in advance. srimal.
Actually, you're better off having a book node, and a "review of something or other" node that's then applied to a book (or anything!). The book is just a data node so should be trivially easy, or can even be done with flexinode or cck. As for reviews: NodeReview module: http://drupal.org/node/59051 It allows one review per user per node being reviewed, and is fully customizable. Users can go back and edit their reviews as well, or see all reviews that have been written (assuming necessary permissions, etc.) If that's only 80% of what you need, please send patches! I'd much rather we beef up one first-rate review module than have a dozen floating around. On Friday 02 June 2006 06:07, Srimal Jayawardena wrote:
hi
im working on a book review module to allow multiple reviews (the existing one only supports a single review per module)
I plan to so there will be two objects - a book - and a review
Is it better to have both as two blocks in the same module ? or have two separate modules?
Any good places to check on this ?
tnx in advance.
srimal.
-- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson
Wouldn't the node review module be a place to start? http:// drupal.org/node/59051 I'm only just now trying it on a new site, but it seems to do much of what you ask. -1 for using the book node structure. The hard-wired aspects of books displays make it a poor candidate to use as a foundation for building something else, in my view from the theming and usability perspective. Laura On Jun 2, 2006, at 8:22 AM, Larry Garfield wrote:
Actually, you're better off having a book node, and a "review of something or other" node that's then applied to a book (or anything!). The book is just a data node so should be trivially easy, or can even be done with flexinode or cck. As for reviews:
NodeReview module: http://drupal.org/node/59051
It allows one review per user per node being reviewed, and is fully customizable. Users can go back and edit their reviews as well, or see all reviews that have been written (assuming necessary permissions, etc.)
If that's only 80% of what you need, please send patches! I'd much rather we beef up one first-rate review module than have a dozen floating around.
On Friday 02 June 2006 06:07, Srimal Jayawardena wrote:
hi
im working on a book review module to allow multiple reviews (the existing one only supports a single review per module)
I plan to so there will be two objects - a book - and a review
Is it better to have both as two blocks in the same module ? or have two separate modules?
Any good places to check on this ?
tnx in advance.
srimal.
-- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012
"If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson
Please allow me to correct myself. What I meant to refer to is "userreview" by dado -- http://drupal.org/node/53611 Laura On Jun 2, 2006, at 10:21 AM, Laura Scott wrote:
Wouldn't the node review module be a place to start? http:// drupal.org/node/59051 I'm only just now trying it on a new site, but it seems to do much of what you ask.
On Friday 02 June 2006 06:07, Srimal Jayawardena wrote:
hi
im working on a book review module to allow multiple reviews (the existing one only supports a single review per module)
I plan to so there will be two objects - a book - and a review
Is it better to have both as two blocks in the same module ? or have two separate modules?
Any good places to check on this ?
tnx in advance.
srimal.
-- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012
"If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson
userreview.module and nodereview.module were developed at the same time. I don't think either of us knew about the other when we were writing them. I'm of course partial to the one I wrote, but I've not tried the other. I also didn't mean to use book.module. nodereview.module lets you review any node type. So create a "book" node type (or "product" or "thing" or "whatever" node), and then review that. -- Larry Garfield On Fri, June 2, 2006 2:56 pm, Laura Scott said:
Please allow me to correct myself. What I meant to refer to is "userreview" by dado -- http://drupal.org/node/53611
Laura
On Jun 2, 2006, at 10:21 AM, Laura Scott wrote:
Wouldn't the node review module be a place to start? http:// drupal.org/node/59051 I'm only just now trying it on a new site, but it seems to do much of what you ask.
On Friday 02 June 2006 06:07, Srimal Jayawardena wrote:
hi
im working on a book review module to allow multiple reviews (the existing one only supports a single review per module)
I plan to so there will be two objects - a book - and a review
Is it better to have both as two blocks in the same module ? or have two separate modules?
Any good places to check on this ?
tnx in advance.
srimal.
hey tnx for the ideas .. really appreciate the active list. but i get the following error when i try to add a review using nodereview: * warning : Invalid argument supplied for foreach()in /var/www/drupal-4.7.2/modules/nodereview/noderiview_node_nodereview.inc on line 134 * warning : Invalid argument supplied for foreach()in /var/www/drupal-4.7.2/modules/nodereview/noderiview_node_nodereview.inc on line 214 But it says your review was created However it says 'Page not found' when i click to display reviews. I have the following versions : drupal - 4.7.2 nodereview = 4.7.0 (cvs) views module = cvs votingapi = cvs cvs - as of 3/6/2006 today am i missing something? tnx srimal. On 6/3/06, Larry Garfield <larry@garfieldtech.com> wrote:
userreview.module and nodereview.module were developed at the same time. I don't think either of us knew about the other when we were writing them. I'm of course partial to the one I wrote, but I've not tried the other.
I also didn't mean to use book.module. nodereview.module lets you review any node type. So create a "book" node type (or "product" or "thing" or "whatever" node), and then review that.
-- Larry Garfield
On Fri, June 2, 2006 2:56 pm, Laura Scott said:
Please allow me to correct myself. What I meant to refer to is "userreview" by dado -- http://drupal.org/node/53611
Laura
On Jun 2, 2006, at 10:21 AM, Laura Scott wrote:
Wouldn't the node review module be a place to start? http:// drupal.org/node/59051 I'm only just now trying it on a new site, but it seems to do much of what you ask.
On Friday 02 June 2006 06:07, Srimal Jayawardena wrote:
hi
im working on a book review module to allow multiple reviews (the existing one only supports a single review per module)
I plan to so there will be two objects - a book - and a review
Is it better to have both as two blocks in the same module ? or have two separate modules?
Any good places to check on this ?
tnx in advance.
srimal.
Hm, I remember fixing that before. Please file a bug report in the issue queue and I'll look into it ASAP. (I've got a similar setup that I'm upgrading from 4.7.0 to 4.7.2 later today, so I hope I don't run into the same issue. <g>) Thanks. On Saturday 03 June 2006 10:25, Srimal Jayawardena wrote:
hey
tnx for the ideas .. really appreciate the active list.
but i get the following error when i try to add a review using nodereview:
* warning : Invalid argument supplied for foreach()in /var/www/drupal-4.7.2/modules/nodereview/noderiview_node_nodereview.inc on line 134
* warning : Invalid argument supplied for foreach()in /var/www/drupal-4.7.2/modules/nodereview/noderiview_node_nodereview.inc on line 214
But it says your review was created
However it says 'Page not found' when i click to display reviews.
I have the following versions :
drupal - 4.7.2 nodereview = 4.7.0 (cvs) views module = cvs votingapi = cvs
cvs - as of 3/6/2006 today
am i missing something?
tnx
srimal.
On 6/3/06, Larry Garfield <larry@garfieldtech.com> wrote:
userreview.module and nodereview.module were developed at the same time. I don't think either of us knew about the other when we were writing them. I'm of course partial to the one I wrote, but I've not tried the other.
I also didn't mean to use book.module. nodereview.module lets you review any node type. So create a "book" node type (or "product" or "thing" or "whatever" node), and then review that.
-- Larry Garfield
On Fri, June 2, 2006 2:56 pm, Laura Scott said:
Please allow me to correct myself. What I meant to refer to is "userreview" by dado -- http://drupal.org/node/53611
Laura
On Jun 2, 2006, at 10:21 AM, Laura Scott wrote:
Wouldn't the node review module be a place to start? http:// drupal.org/node/59051 I'm only just now trying it on a new site, but it seems to do much of what you ask.
On Friday 02 June 2006 06:07, Srimal Jayawardena wrote:
hi
im working on a book review module to allow multiple reviews (the existing one only supports a single review per module)
I plan to so there will be two objects - a book - and a review
Is it better to have both as two blocks in the same module ? or have two separate modules?
Any good places to check on this ?
tnx in advance.
srimal.
-- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson
Hi, Would you consider reconsidering this module as a whole purpose review module following closely (but not the T), the shopping catalog of a company like Amazon. Here's why : Say I have a book called "Yoga for Drupal developers". The book covers yoga, stress management, php and drupal. For me as a publisher, to capitalize on this review, I could run the book review module with amazon items so that I can add to the page purchases related to the book. The problem is that, just like you say, you can only have one review on a page. And worst for non-techies like me, the Amazon items module, albeit a good idea in theory, has an effective execution given that these items can only appear on the permalink page (not the node or index page) of the acompanying node. Unless I code it by hand (which I haven't tried yet), I cannot have those items running on a sidebar either. SoOoOoOoOo ... The challenge would be to create a general purpose review page that takes a page out of the bookreview module but kicks it up a notch by : (1) allowing multiple reviews on a page (2) making it easy to manage with CSS a block of sale items (so you can choose to have them appear on the index page or permalink page) (3) making it easy to generate a sideblock with X# of all the reviewed items (4) Hopefully use the Amazon API so that it easily pulls out ISBN, images and links (just like the Amazon-Items module) but this time with the option to show the prices (an option, BTW, that should be controlled per/post not globally). Now, if you really want to be a code hero, this module would organize my paperwork, dust my library and calculate my tax returns :) ON THAT NOTE : Here is a good example of why POLL should not be a separate node. I should be able to write a post about X topic and then run a poll about said topic immediately. This is becoming standard in the SCOOP run blogging world and sorely needed by bloggers like me using Drupal. Actually, if it were up to me, modules like these would extend NODE, not be separate modules. Everything should plug into NODE --polls, events, surveys, reviews, forums, recipes, even dare I say gallery images. The developers in Drupal think about the different technology issues revolving around these modules but to us users, they are not that different. What we want to do is : (1) Write a blog entry (2) Do it with the least amount of tech effort Being able to go to one page --ONE PAGE-- and click off choices of what sections for a post we want ( poll, review items, mass mailing, etc ) and have that all generated in one page ... just the thought of it makes my brain tingle. Liza Sabater, Publisher www.culturekitchen.com www.dailygotham.com TEL - 646.552.7365 AIM - cultkitdiva SKYPE - lizasabater NOTICE: Due to Presidential Executive Orders, the National Security Agency may have read this email without warning, warrant, or notice. They may do this without any judicial or legislative oversight. You have no recourse nor protection save to call for the impeachment of President George W. Bush and Vice-President Richard Cheney, for high crimes and misdemeanors. On 02.Jun.2006, at 07:07, Srimal Jayawardena wrote:
hi
im working on a book review module to allow multiple reviews (the existing one only supports a single review per module)
I plan to so there will be two objects - a book - and a review
Is it better to have both as two blocks in the same module ? or have two separate modules?
Any good places to check on this ?
tnx in advance.
srimal.
On Jun 2, 2006, at 7:51 AM, blogdiva@culturekitchen.com wrote:
Hi,
Would you consider reconsidering this module as a whole purpose review module following closely (but not the T), the shopping catalog of a company like Amazon. Here's why :
Say I have a book called "Yoga for Drupal developers". The book covers yoga, stress management, php and drupal. For me as a publisher, to capitalize on this review, I could run the book review module with amazon items so that I can add to the page purchases related to the book.
Actually you should make you consult with the un-official Drupal Yogi first: http://yogaforgeeks.com ;-) K
The problem is that, just like you say, you can only have one review on a page. And worst for non-techies like me, the Amazon items module, albeit a good idea in theory, has an effective execution given that these items can only appear on the permalink page (not the node or index page) of the acompanying node. Unless I code it by hand (which I haven't tried yet), I cannot have those items running on a sidebar either.
SoOoOoOoOo ...
The challenge would be to create a general purpose review page that takes a page out of the bookreview module but kicks it up a notch by :
(1) allowing multiple reviews on a page
(2) making it easy to manage with CSS a block of sale items (so you can choose to have them appear on the index page or permalink page)
(3) making it easy to generate a sideblock with X# of all the reviewed items
(4) Hopefully use the Amazon API so that it easily pulls out ISBN, images and links (just like the Amazon-Items module) but this time with the option to show the prices (an option, BTW, that should be controlled per/post not globally).
Now, if you really want to be a code hero, this module would organize my paperwork, dust my library and calculate my tax returns :)
ON THAT NOTE : Here is a good example of why POLL should not be a separate node. I should be able to write a post about X topic and then run a poll about said topic immediately. This is becoming standard in the SCOOP run blogging world and sorely needed by bloggers like me using Drupal.
Actually, if it were up to me, modules like these would extend NODE, not be separate modules. Everything should plug into NODE -- polls, events, surveys, reviews, forums, recipes, even dare I say gallery images. The developers in Drupal think about the different technology issues revolving around these modules but to us users, they are not that different. What we want to do is :
(1) Write a blog entry (2) Do it with the least amount of tech effort
Being able to go to one page --ONE PAGE-- and click off choices of what sections for a post we want ( poll, review items, mass mailing, etc ) and have that all generated in one page ... just the thought of it makes my brain tingle.
Liza Sabater, Publisher www.culturekitchen.com www.dailygotham.com
TEL - 646.552.7365 AIM - cultkitdiva SKYPE - lizasabater
NOTICE: Due to Presidential Executive Orders, the National Security Agency may have read this email without warning, warrant, or notice. They may do this without any judicial or legislative oversight. You have no recourse nor protection save to call for the impeachment of President George W. Bush and Vice-President Richard Cheney, for high crimes and misdemeanors.
On 02.Jun.2006, at 07:07, Srimal Jayawardena wrote:
hi
im working on a book review module to allow multiple reviews (the existing one only supports a single review per module)
I plan to so there will be two objects - a book - and a review
Is it better to have both as two blocks in the same module ? or have two separate modules?
Any good places to check on this ?
tnx in advance.
srimal.
participants (5)
-
blogdiva＠culturekitchen.com -
Kieran Lal -
Larry Garfield -
Laura Scott -
Srimal Jayawardena