Firstly make back ups of the styles XML's // folders just in case.
Typically you'd update xenBase, then Splash. So when updating Splash if you're not using a child of Splash you will lose your customizations when you overwrite Splash. If you're not using a child of Splash you could import this updated Splash as a brand new child of xenbase, then create a child style and port over all your edits to it.
This makes it so future upgrades would be a breeze for you.
@Russ, quick question, probably missing something really obvious. I've added some custom side blocks on to my site, when viewing on an iPhone in portrait they don't show up however if you turn it in to landscape they pop back up...
Something I need to add on the back end somewhere maybe to make them show in portrait?
Just wondered if you (or anyone else) had experienced this?
So the plan originally was to update the styles for 1.2.4 however I think we're going to hold off for our next version of XenBase. 1.2.4 was a minor update which for the most part showing one outdated template which you can use the merge feature to fix.
We have some cool things planned for XenBase 1.3, some of it a re-write to clean up some code. We'll also be organizing and adding some new features.
We're taking a break for the holidays so we'll be back officially after the new year.
I'll still provide sales and support the best I can however please keep in mind we wish to spend time with our families during the holidays.
As I have been mentioning across various threads 1.3 is bringing a rather massive change to the way our style functions. Most of the front end you won't notice a difference aside from a few cosmetic improvements, however we've re-written a good majority of our XenBase.
With this said, if you are a current client of Splash please read carefully.
For anyone with minor customizations it's suggested you treat this upgrading as if you're installing a brand new style....