Wouldn't it be great if there was an option to choose a booking engine version that only receives security fixes but stays stable, including all functionality and assets(.jss,.css,...)?
Here are some of the things I did for last year's season,
- * Add css styling.
- I added a responsive solution of my own for mobiles and tablets
- Integration with the main page
* Added js to fix broken translations
* Added google analytics scripts with parcial Enhanced Ecommerce support
* Added js to create responsive iframe - The only thing that hasn't broken so far
* Custom confirmation page and email
* And some things more
- * Css
- It was broken this early this year even though support said I could roll back to the previous version. Where the hell did booking3.css come from then?
- Beds24's non-responsive view had definitely changed. It completely broke my booking engine.
* Last year I helped to fix the Spanish translation of the booking engine. Some of the proposed changes were never applied, for which I created my own fixes
- But surprisingly some of the translations that were OK have changed to worse.
* Template variables recently broke. I don't know why the decimal separator changed from a point to a comma breaking my JS code.
* Some other small nuisances
I have a script that checks every 6 hours for changes in the pages and assets and when that happens it sends me a notification. However it doesn't detect everything, like it was the case with template variables and even if it does it can take a day or a few days to create a workaround. Emulating a full browser user experience and testing each and every possible case is beyond my capabilities.
Finally a non related topic. I was browsing the wiki and in my experience the instructions about using iFrame Resizer can lead to problems. If the clients have antivirus addons installed in their browsers, a warning about a cross-site scripting attack will appear. They are going to put the credit cards there so they'll freak out. Solving it was hard, you have to create a proxy in a virtual directory of your own main domain, for example if you choose mydomain.com/booking/ as the virtual directory, mydomain.com/booking/booking2.php?params should proxy the page beds24.com/booking2.php?params
Doing it right isn't easy, it requires configuration on your webserver. Using a subdomain(i.e. booking.mydomain.com) doesn't get rid of the warning.