Book review module:

the place this should be asked in in the issue query of the project

moved to proper query.

I second the query: is anyone working to upgrade book review to D6?

Bump

I intend to, but only after the book review for D5 goes to release.

Also looking forward to a D6 release.

I notice that both the 4.x and 5.x versions are devel snapshots. Could you be more specific as to when the 5.x version will be officially released?

I also need this module for 6.x. I have many content based on book review module. I even do not know if it is possible to convert them automatically using CCK. Please can you update this module to 6.x. Thanks a lot!

Bump.

I reiterate: is there a timeline for getting a release for ANY Drupal version, or should I go forward with some CCK hack?

'Nother metoo for 6.x

Given Jeremy's statement at http://drupal.org/node/111511 on his lack of time and need for a (co-)maintainer..., if you're willing to port to 6.x David, I'm sure that would make a lot of user very happy.

jsambrook-- Thanks for the suggestion. Trust me when I say that I would be less than helpful in porting the module to 6.x

I've been pretty inattentive to this, but it has occupied my attention and driven me to despair every time I've thought about it. So I'll solicit opinions as to how I can go forward.

Jeremy told me (and I don't know whether this was a strict instruction or a casual suggestion) that I would have to finish 5.x before moving to 6.x. Trouble is, every time I look at 5.x I get stymied. With all due respect to Jeremy, there's too much that needs fixing. One of the bugs I'm supposedly fixing is caused by the bookreview node having both a body and a "review" when in my opinion, it should have only one of these things.

If the "review" is removed, that will break the module for many people. If the body is removed (and can a node exist without a body? not sure about that) then there are a number of things that will be much harder to fix AND it will break the module for many people.

So accept my apologies for dropping the ball when I said I wanted to help and accepted the mantle of co-maintainer (which by now may have been revoked), but I don't have a path for moving forward.

I jumped in because I wanted to help make a 6.x version. I really have no desire trying to make the 5.x version work when those efforts are likely to make it work worse for existing users.

In my last conversation with Jeremy, he suggested something I'd been holding my tongue about: implementing Bookreview with CCK.

If I had my way, Bookreview 6.x would be built largely from the ground up relying heavily on CCK. But I don't know how we'd create a clear and seamless upgrade path from 5.x to 6.x. Since that seems to be a Drupal commandment, I think I'm stuck.

I actually have the time to work on this, but I'm sorry, I don't feel any fire in my belly to put a lot of time and thought into 5.x when my goal here is to get my own site running with a 6.x bookreview.

So I've just complained a bunch here and haven't offered solutions, which I consider a no-no. I apologize for that. I'd very much like to hear any suggestions about the future of Bookreview specifically regarding the 5.x fixes and radical changes with 6.x. I'll also go ask other maintainers and read some more. I'm sure this is not a unique situation for a module to be in.

A 5.x release is preferable, but not a requirement by any means. An upgrade path from the 5.x version to the 6.x version is preferable, but again is not a requirement. If you're not interested in supporting 5.x, and nobody else is stepping up for the job, then I say run with your plans for 6.x... Especially if you've got the time! Branch of a 6.x version, and start working there. If someone else wants to fix the bugs in the 5.x version, they still can.

Jeremy and Splicer:
I'd like to thank you both for the work you've already done, and for stepping forward at this point with some candid information. I have been a regular gadfly on this thread, and I want you both to know that I understand these issues and respect them.

It was suggested that I offer to help with the migration, and believe me, I would if I could. I am, however, a self-taught hacker/programmer; I know how to write PHP, but I get completely lost when I begin to look at any Drupal code. That was why I made my earlier comment.

However, there are a couple of areas I might be able to help with:
First, I have done a little bit with CCK and Views, and although I would be the first to admit I have only the barest beginnings of experience there, I could help determine what CCK fields and what views might be needed and help build those. It's not much, especially since I wouldn't be able to help much with any CSS styling of the results. But I am willing to help there.
Second, I have a small Book Review dataset, and would have motivation to try and figure out how to get my old data into a CCK-based future. Taking into account my serious difficulties with the Drupal Way, I would nevertheless be willing to try my hand out with migration strategies.

Thanks Sunfish,

I think defining the new (abstract rather than SQL) schema is a good start, plus a list of things that we want to be able to do with the Bookreview. Looking at the old schema to see what maps to the new and what doesn't will then give us some information to put out there about any changes we make.

An example is the title field. It's in the code of the 5.x code but IIRC it's commented out, so that it's not possible to have a title for the review separate from the title of the book. This should probably be optional since folks don't want to have their data transferred with blank titles.

There will be differences between the old and the new, but I'd like to run those suggested changes past the community to find out if people are gonna scream about a change.

We should probably also move any discussions of specific design changes outside this particular thread :)

But a great place for you to start would be to come up with that "back of the napkin" level set of fields. Thank you!

I would also need version 6 of this module. I'm not sure if I follow the discussion quite correctly but I would like to say that I use both the body and the review since they fullfill different purposes.

AstaChattare, could you take up your request to keep the body and review in the Book Review Schema thread: #283617: Schema Ideas for D6/CCK Implementation?

Subscribe. Thanks everyone!

Hi,

I made some changes on the 5. version. I very much like to have the 5 version in production before jumping on drupal 6.
Do there have to be done so much things more to get this working on drupal 5?
When a drupal 6 version is in production and a drupal 5 version is lacking, back reengineering is rather difficult I think.
So +1 for drupal 5 1.0 version!

greetings,
Martijn

Martijn,

As far as I know (and from my own limited experience) the version 5 module works. Personally, it doesn't look that great to me, but it does work...

David

In case anyone's interested -- I've documented how to convert Book Review in Drupal 5 to CCK, please see http://drupal.org/node/294309.