We would need to have the workflow working with rooms_unit entity (publish/unpublish states, scheduler module in place etc.). As far as I understand this is not possible to do current Entity Api, so as a solution could be convert rooms_unit entity to node? Could someone give some guides on how to do that, would really appreciate your support.

Comments

ronald_istos’s picture

Bookable Units as nodes is something we specifically don't want to do right now although I am happy to have a discussion about it and maybe be convinced. Maybe we can start with a detailed breakdown of the types of things that you would like to do and cannot do now and then we can see if there are entity-level modules that would allow you to do these stuff or whether it is a feature that Rooms should directly support.

evave’s picture

The only missing feature is having published/unpublished states for each rooms unit. It would be nice if the owners of the rooms or rentals could be able to manage these states through Scheduler and Workflow modules. Hope this would be possible when Entity API will support revisions, or is there any other solution already without hacking the code so much.

On the other hand this looks very promising, hope this feature will be supported soon.

joecanti’s picture

I would also be interested in this feature - but I understand it would probably add a lot of work to the module.

It would be nice to be able to manage the rooms as nodes so that descriptions / photos can be added, and the rooms can be categorized using taxonomy - but this is perhaps not necessary for the majority of the use cases.

My use case is a little different. I am trying to create an advertising system, and if I used 'rooms' I could have a set number of ad blocks, and rent the blocks out on a per month basis. I like very much the integration with commerce and the front-end booking - it would be a great solution for me...

But the problem for me is how to create a system whereby users can enter their advert text - and how this can be displayed and rotated - something the traditional ad modules might do much better.

I'm looking all over for different solutions.

Good job the rooms mod - it has many possible applications. Cheers, Joe

acrollet’s picture

Status: Active » Postponed

Setting status, as this is unlikely to be a priority in the near future. For anyone who is interested in doing the work to get this in, the steps would look like:

1. Find a solid module that provides a workflow that works with revisioned entities.
2. Document what would need to be added to Rooms for compatibility.

At this point, we could discuss the level of effort required and determine next steps.

acrollet’s picture

Priority: Major » Minor
eebanos’s picture

My use case is quite odd, i have different Booking Unit types for example: Chalets, Mansions, Country houses.... i define the bookable units type and create different bookable units but my country houses aren´t the same, my chalet´s aren´t the same and i´m only can attach a unit description into a bookable unit type, and i need a different unit description available per unit, how i do that? Perhaps if every Room Unit is a node i can solve that.

ziomizar’s picture

Hi all,

I'm writing a small module (in sandbox) that adds this feature to node with some other extra.
You can found the first version at this url : https://drupal.org/sandbox/ziomizar/2086255

Let me know..

jwilson3’s picture

Issue summary: View changes

You can easily add custom fields (from Field API) to a Rooms Unit. All Units from the same Unit Type share fields, thus the UI for adding fields to Units is located at:

Admin > Rooms > Units > Unit Types then click on the "manage fields" link for a given Unit Type.

This throws many people off as being unintuitive, but if you think about it, it works the same way as nodes: The field administration is on the Content Type edit page, not the Node edit page.

Once you have your fields on a room, you can easily use rules to do just about anything you need to manipulate room units during booking or checkout processes.