Though most all salons currently running the SuperSalon software are on the series 5 and above releases, a few salons are still in the process of converting over from the old version 3. The purpose of this article is to clearly lay out the steps involved in making this great leap in software versions.
It cannot be understated enough that the owner needs to be informed of every possibility involved in this update. One of which is the loss of inventory counts which happens very frequently after this process is complete.
Updates of any version of SuperSalon are not done from Friday to Sunday, except under very special circumstances that requires a conference with the salon owner and the manager on duty.
With ANY update to SuperSalon, be sure to check both the system capabilities of the PC size AND the size of the database. If the database is too large (over 500 MB), and the system specs are sub-par, the update will most likely not be possible on that machine!!
Close SuperSalon
Go to C:\Super Salon\Mysql\Data
Copy the SSPOS folder. Paste into Backup folder on Desktop
Check C:\Super Salon\ for an “Active Charge” or “Pc-Charge” folder
If you find one back it up to the same desktop folder.
https://ioffice.supersalon.com/update/Old_Updates/v5_prepatch.exe
https://ioffice.supersalon.com/update/Old_Updates/SuperSalon-5.5.26.4-18125.exe
https://ioffice.supersalon.com/update/Old_Updates/update_php516.exe
https://ioffice.supersalon.com/update/Old_Updates/firefox2_0_0_3.exe
Run the update_php516.exe update.
Stop Apache and Mysql
Go to C:\SuperSalon\ssproject and run the php516 file.
Start Apache and Mysql.
Go to C:\SuperSalon\Apache\conf and open the httpd.conf file in notepad
Ctrl+F search for ScriptAlias /php/ “c:/SuperSalon/php5/”
Change the line so that it reads ScriptAlias /php/ “c:/SuperSalon/php516/” close and save.
Stop then Start Apache and Mysql.
Check the version by going to http://localhost/scripts/phpinfo.php and verify that the version running is 5.1.6
Run the firefox2-0-0-3.exe file
If all goes well it should ask you if you want to import any settings when you open SuperSalon again. Select No.
It will ask you if you want to make firefox your default browser. Select Yes.
OPEN SS After Every patch to let the scripts run, once complete close SS and run next patch
Run the v5_prepatch.exe
Run the 5.5.26.4 patch and wait for it to complete the update process
Once 5.5.26.4 is up and running, run the 5.6.1.x (or latest) update
Remove install files from desktop
CHANGE ADMIN VERSION AND UPDATE FILE. Seriously, miss this step and Support will not be happy. Back patching is not fun to fix.
Clear the Mozilla cache
Run DB checkers
Re-Register Software / Set Owner Password
There are a lot of changes to the system that come along with v5. Here is a checklist of items you need to work on with the customer.
Tax Setup: The tax system has changed. Make sure the proper settings are entered
Wait time: Old systems(lets face it, you’re updating from v3, you’re using an older system) have a hard time with wait time calcs.
Permissions: Lots of new permissions have been added to the system. Make sure they are set accordingly.
The Padlock: Review with the customer how the password save feature works. Adjust settings to their liking.
Appointments: The Appointment system received a huge overhaul. Train accordingly.
IOffice: Lots of new features will be available to the owner now on ioffice for this store.
If you look in the original error, it had to do with a failed in clause — (psuedo code) SELECT WHERE id IN (1,2,3,4,). The error being the final comma.
With the knowledge of the SuperSalon database, you can see that its querying the sales table (sale, transaction, ticket, etc) and the only field that would contain that type of data would be the other field in the transaction table.
Using the given saleID, query for all transactions in the transaction table with the corresponding id. Then, the offending data can be found and corrected (removed the trailing comma). This or a similar fix can be performed when the error message appears. There is no need to reload the v3 db, correct the data, then re-update.