Posted by webmestre on January 19, 2011 at 6:23pm
Hello,
I would like to use the Ubercart module to propose holidays stays.
1 stay = 1 description (text, pictures...) + diferent periods in the year
The period is defined by the travel agency, not by the customer. Ex. : visiti Paris from 02/10/2011 to 02/15/2011 or 02/16/2011-02/21/2011 etc...
The customer is not allowed to split the period, to go before or go back after the previously definesd dates.
Do you have an idea to do that ?
Comments
Use Ubercart to make a new
Use Ubercart to make a new product class called (eg) Holiday Package
Use date module to add CCK fields for the date ranges to that content type.
You can then use Views to make the search interface.
OK, larowlan and thanks. But
OK, larowlan and thanks.
But how will it be possible for a customer to book for THE week he choiced and admin knows that ?
Another pb : how to have diferent prices acording to the week : high season, mid season, low season ? The product is the same, the price changes...
I thought you said the dates
I thought you said the dates were fixed.
If you need to use the customer nominated dates, you can use uc_hotel module w/ sub module hotel_discounts to set rates per season. You can change the nomenclature using the locale module to suit.
If you have fixed dates (ie not customer nominated) create a node for each available date range.
1) hotel_discounts : I didn't
1) hotel_discounts : I didn't know the hotel_discounts module of uc_hotel module. Thanks, I'll study this solution.
2) 1 node per date rage : If a tour is proposed 45 times a year, it's not a good idea to create 45 nodes for exactly the same information just diferent in the dates and sometimes in the price.
2) there is no problem with
2) there is no problem with this, just hide the nodes as a page on their own but make them listed on a master node using uc_subproduct
I think you really know UC,
I think you really know UC, that's nice.
I'm just trying to reduce the time of producing : if I can collapse 45 nodes in just 1, OK.
But I'll have to produce 45 nodes per tour x 75 tours in the catalog + number of editions when something changes (pictures, texts, conditions...).
The idea would be to produce 1 main node (general information + pictures...) + 45 dates with a price for each.
I thought date attribute could be a solution. But it's not.
Do you know a solution ?
You can use node_import or
You can use node_import or feeds to load your data from a spreadsheet (csv).
You can use uc_attributes (core uc module) and set each date as an attribute.
But there is a lot of admin work required there too (and not sure if you can bulk import).
Thanks to you, a general
Thanks to you, a general strategy for building the travel company website is growing...
Ex. :
Travel #1 - Easter Tour in Paris
dates : from 04/01/2011 to 04/05/2011 : 324$ - from 04/06/2011 to 04/10/2011 : 350$ - from 04/11/2011 to 04/15/2011 : 324$
Travel #2 - Barcelona
date : from 06/01/2011 to 06/05/2011 : 400$ - from 04/06/2011 to 06/10/2011 : 500$ - from 06/11/2011 to 06/15/2011 : 600$
etc...
Travel 1,2 etc... are products or nodes or both ?
sequences of dates for each travel are attributes ? options ?
I'm not sure but, this is what I tried to organise :
For each travel, I create an attribute for called ie "Paris Easter dates" with the following options "from 04/01/2011 to 04/05/2011 : 324$ - from 04/06/2011 to 04/10/2011 : 350$ - from 04/11/2011 to 04/15/2011 : 324$"
What do you think about that ?