Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Is planed a upgrade to D8?
Regards,
Giuseppe
Is planed a upgrade to D8?
Regards,
Giuseppe
Comments
Comment #2
fietserwinNo, not for the moment and depending on the state of Rooms in D8 it might never come. The plans for Rooms 2 look promising, and if they are indeed realized it might be better to convert to that.
Comment #3
giupenni CreditAttribution: giupenni commentedThank you fo reply.
Is Rooms for real estate/apartments too?
How I can read the plans for Rooms 2?
Comment #4
fietserwinSee e.g.:
- https://www.drupal.org/project/bat
- http://drupal.org/project/rooms
- http://www.bluespark.com/blog/rooms-10-released-and-roadmap
- https://roomify.us/
Comment #5
giupenni CreditAttribution: giupenni commentedThank you
Comment #6
SkinAny news? It woud be nice to have a D8 port.
Comment #7
fietserwinI'm currently in the process of migrating our own site from D7 to D8. I am thinking about replacing the features of Availability Calendars by the BEE module. The major drawback of A.C. is that it does not store information about separate bookings. E.g. the recently added iCal import integration cannot process annulations as it can't store the UUID of blocked periods that it imports.
For ourselves, I want to move to a real booking system that we can access online, thereby making our spreadsheets [yes, internally we are stil working with a spreadsheet to store booking info :(] and this module superfluous.
The basics of the migration I have handled, so I am about to start looking into if BEE is indeed the right module for us and, if so, how to import our existing data. As you can understand from the remark above, I will import form that spreadsheet not migrate the A.C. data. However, as this migration is also a learning process for me, I will also look into migrating A.C. data to BEE and release any results as a D8 contrib module.
You can expert more info within a month.
Comment #8
SkinGreat news, thanks for your reply.
BEE to me seems just a very nice demo, but don't think it is ready for production: for example from a point of view of User eXperience and User Interface it seems almost unusable without redoing the calendar and reviewing the way in which a user must book, there are also zero mobile optimizations, but since it is based on BAT in the hands of a developer it has really a great potential.
Comment #9
fietserwinThanks for the warning, so far I indeed have only watched the demo which told me that the basics are there but that all screens seem indeed a bit shallow.
So I now start with finding out what is needed to make it usable in our situation. If that means I have to add some field widgets or entity/field formatters, I'm not afraid to do so and contribute it back to the project or a stand-alone module.
Comment #10
SkinIf you need someone to translate from english to italian I`m here, I`m also good with css so if you need someone to work on the design I`ll be happy to contribute.
Comment #11
fietserwinThanks for the offer, I'll keep it in mind and contact you when needed.
Comment #12
igonzalez CreditAttribution: igonzalez commentedGood morning, sir,
If someday we want to build a web of reserves in drupal 8 with BAT we need to migrate this module.
Someone sees it as possible
Greetings
Comment #13
fietserwinI tested the BEE module a bit and it is indeed a no-go, so any replacement should be built on top of BAT. but more generic than BEE (BEE with about all feature requests in the issue queue implemented and then some more). Not using BAT or not integrating with Commerce will make any replacement module a LOT more work. So, even though I have my doubts about the storage defined by BAT (hard to plug into SQL based (faceted) search modules, any D8 module should use BAT.
However, the rest of this year I don't have time to do anything with this or even for the migration of my own site (see comment #7).
Some ideas:
- If you would write a new booking module or convert this module to D8, you will probably want a migration. I think I would do so using iCal, the current version of this module supports it, so the D8 module should be able to import iCal as of its 1st version and you have migration of data without having spent time on functionality usable during migration only.
- The idea of BEE of linking BAT entities to other entities is a good start. Though managing units directly on the edit form of the other entity is IMO not so good, see some issues on PHP warnings, not supporting layouts, etc.
- The dependency on office hours,also for day based availability is also not well thought out.
Comment #14
Nchase CreditAttribution: Nchase as a volunteer commentedI was looking at BAT and from my perspective it is far too difficult. The requirements of modules to be activated to just get a booking going is enormous. BAT is tailored for multi purpose needs, hotels, guest houses with multiple bookable rooms, multiple conference rooms, etc. but not for simple things like one room, or one house.