Bookings API: Drupal 7 Upgrade

Hi tirsales, any updates or estimates on when a D7 release might be available?

Thanks tirsales,

After having a look at the module and processing through coder, it looks like the main fixes will be:

Removing/Changing dependancies on content and content_copy
Updating node_reference related code to D7 References project
Database API changes to the D7 database API

Unfortunately I don't have the time either to learn and make the D7 database API changes, but I would be happy to contribute via chipin to get this and Event Bookings upgraded asap if anyone is interested?

Thanks Dru-p, I am happy to match the $100US and offer another $100 if we can get the sub-module Event Bookings ported too. However, I need them done within two weeks due to time contraints. Both are fantastic modules and I really need them for my new site.

tirsales, you are probably best placed to do the port (knowing the code) but totally understand if you are still too busy. Are you open to me posting the above bounty in the forums?

After looking at this for an hour or so, I'd say it's not going to be a trivial upgrade. There are two primary reasons for this. First, the module as written is pretty MySQL specific. For example, there are a lot of datetime column types in the hook_schema calls, which are no longer valid in D7 (see http://drupal.org/node/866340 for more info). The simple solution is to change these columns to 'mysql_type' instead of 'type', which might be ok for a dev snapshot or alpha but is definitely going to need to be fixed for any official release, which will mean reworking module code to remove dependencies on the db returning MySQL datetime formatted data. Not rocket science, but it will take some time.

The second issue is more complex. The 3.x branch has a deep integration with CCK and nodereference in particular. Reworking a lot of the CCK-specific code to work with Fields will be tedious but doable, but the nodereference issues are more problematic, since there's no clear nodereference.module replacement in D7. The Relation module (http://drupal.org/project/relation) will probably be the "winner", but choosing that over Reference, for example, is an architectural decision that will need to be made before moving forward, since it will necessitate a significant dependency. Also to Dru-p's comment above, I can see plenty of use cases for making users or even terms "bookable" so I think taking a more generic entity-based approach might make more sense in the long run.

Not to say that an upgrade shouldn't happen or can't be one - just that it's probably going to be a significant amount of work and possibly a departure from the current design in several ways, which means it might not be feasible in two weeks. I'll keep an eye on this issue and if some direction evolves about where to go next, I'll try to jump in and help with some of the code.

Thanks for looking into this Chris. Regarding the node reference module, would http://drupal.org/project/references be an option? I am using this as a direct replacement for node reference in my current D7 site.

From the project/references page:

References will most probably be deprecated in the near future in favor of Entity Reference, which should probably be considered first on fresh D7 projects. Another, more radical, alternative would be the Relation module

I'd love to see help with this, but I don't have the time to port it myself :-/

.