This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
building [2013/01/07 09:36] cruisefactory [Special Sailing Dates] |
building [2018/08/31 17:26] (current) cruisefactory |
||
---|---|---|---|
Line 179: | Line 179: | ||
FROM | FROM | ||
sailingdates, | sailingdates, | ||
- | factorysailingdates | + | specialsailingdates |
WHERE | WHERE | ||
- | factorysailingdates.`special_id`=1234567 | + | specialsailingdates.`special_id`=1234567 |
- | AND factorysailingdates.`sailingdate_id`=sailingdates.`id` | + | AND specialsailingdates.`sailingdate_id`=sailingdates.`id` |
ORDER BY | ORDER BY | ||
sailingdates.`sailingdate` ASC | sailingdates.`sailingdate` ASC | ||
Line 188: | Line 188: | ||
The above would return all sailing dates available for the special ID 1234567. | The above would return all sailing dates available for the special ID 1234567. | ||
+ | |||
+ | ===== Uploaded PDF Retrieval ===== | ||
+ | To download a PDF attached to your special, you can use the following URL: | ||
+ | http:// | ||
+ | |||
+ | The [SPECIAL ID] being the number corresponding to the special you’re fetching the PDF for. For example: | ||
+ | http:// | ||
+ | would fetch the attached PDF for the special ID 1111111. | ||
+ | |||
+ | |||
+ | |||
+ | ===== eFlyer Retrieval ===== | ||
+ | To download the eFlyer you can use the following URL: | ||
+ | http:// | ||
+ | |||
+ | The [SPECIAL ID] being the number corresponding to the special you’re fetching the eflyer PDF for. For example: | ||
+ | http:// | ||
+ | would fetch the eflyer PDF for the special ID 1111111. | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ===== Autoflyer Retrieval ===== | ||
+ | To download a special auto-flyer use the following URL: | ||
+ | http:// | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ===== Image Archive ===== | ||
+ | Images are archive into gzipped tar files ready for download. They can be rather large in download size and are updated once every week. They are available as follows: | ||
+ | http:// | ||
+ | http:// | ||
+ | http:// | ||
+ | http:// | ||
+ | http:// | ||
+ | |||
+ | ===== Image References ===== | ||
+ | You may link directly to the images on the Cruise Factory server or download them to your own server using a batch script. | ||
+ | |||
+ | Use the URLs below to link the image reference in the XML data to the image on the Cruise Factory server. | ||
+ | |||
+ | An example using the an image reference found in the cruise XML data: | ||
+ | http:// | ||
+ | |||
+ | ==== cruises ==== | ||
+ | http:// | ||
+ | |||
+ | ==== ports ==== | ||
+ | http:// | ||
+ | |||
+ | ==== deck plans ==== | ||
+ | http:// | ||
+ | |||
+ | ==== ships (photos) ==== | ||
+ | http:// | ||
+ | |||
+ | ==== ships (thumbnails) ==== | ||
+ | http:// | ||
+ | |||
+ | ==== ships (large) ==== | ||
+ | http:// | ||
+ | |||
+ | ==== ship cabins ==== | ||
+ | http:// | ||
+ | |||
+ | ==== ships cabin photos ==== | ||
+ | http:// | ||
+ | |||
+ | ==== dining ==== | ||
+ | http:// | ||
+ | |||
+ | ==== kids programs ==== | ||
+ | http:// | ||
+ | |||
+ | ==== destinations ==== | ||
+ | http:// | ||
+ | |||
+ | ===== Incremental feed & images ===== | ||
+ | The incremental XML feed for cruises now updates the row for each cruise that has had its image updated. | ||
+ | |||
+ | We recommend that you include functionality into your import scripts to automatically compare and update these images so that your site is always displaying the most up to date and correct images. | ||
+ | |||
+ | ===== Port latitude & longitude ===== | ||
+ | The latitude and longitude coordinates are now included for each port within the Cruise Factory database. You can [[structure# | ||
+ | |||
+ | To access a coordinate of a port you will need to have both the `ports` and `latlong` tables imported successfully. They will then link together via the `ports.id` and `latlong.port_id` columns. | ||
+ | |||
+ | For example, to retrieve all ports with their corresponding lat/long coordinates you could run a query as such: | ||
+ | |||
+ | <code sql> | ||
+ | SELECT | ||
+ | ports.*, | ||
+ | latlong.lat, | ||
+ | latlong.long | ||
+ | FROM | ||
+ | ports, | ||
+ | latlong | ||
+ | WHERE | ||
+ | ports.id=latlong.port_id | ||
+ | </ | ||
+ | ==== Google maps ==== | ||
+ | As a suggested usage for the new port coordinates we recommend using [[https:// | ||
+ | |||
+ | If you follow the tutorial at the link above you will have an API key to access the Google API for you own site. You will then be able to generate maps that display your selected ports using the Cruise Factory provided latitude/ | ||
+ | |||
+ | <code javascript> | ||
+ | var mapOptions = { | ||
+ | center: new google.maps.LatLng(-34.397, | ||
+ | zoom: 8 | ||
+ | }; | ||
+ | </ | ||
+ | |||
+ | By entering in (dynamically) the lat & long of the port into the above you will find that the map automatically centers on the location of the port in your Google map widget. | ||
+ | |||
+ | Read the [[https:// | ||
+ | |||
+ | ==== Amended Conditions ==== | ||
+ | Cruise lines may require specific conditions and disclaimers for the bookings and pricing. We have a table named '' | ||
+ | |||
+ | As above the required table name is '' | ||
+ | * **'' | ||
+ | * This will link to the current sailing: | ||
+ | * '' | ||
+ | * **'' | ||
+ | * This text must be displayed. Suggested under the pricing. | ||
+ | * **'' | ||
+ | * This text must be displayed. | ||
+ | * Will usually be much longer text and should be displayed under a "Terms & Conditions" |