RSS Feed
Latest Updates
Aug
28
Hi Everyone

We would like to bring urgent notice to you that every entity world wide are now required to upgrade all your Imagine Kiosks to the latest version of kiosk for your current core version by September 28th 2017! This action is required due to the expiry of the Adobe Air Code Signing Certificate for Imagine Kiosk. This happens every 2-3 years and is unavoidable. 

The list of the imagine kiosk upgrades required for each core version is below. Please note that you only need to upgrade to the latest version kiosk of the current core version you have currently dispatched. For example if your  kiosk version is 11.9.189, you only need to upgrade to kiosk version 11.9.205. You do not need to upgrade to another core version.

 

  • Latest 11.9 version - 11.9.205
  • Latest 12.1 version - 12.1.075
  • Latest 12.3 version - 12.3.079
  • Latest 12.4 version - 12.4.109
  • Latest 12.6 version - 12.6.065
  • Latest 12,7 version - 12.7.049
 

 

For your awareness - a Code signing certificates is the method of using a certificate-based digital signature to sign Imagine Kiosk executable and scripts in order to verify the author's identity as truly being Whitech Pty Ltd and ensure that the code has not been changed or corrupted since it was signed by Whitech as a matter of security.

Please take this action seriously and plan accordingly over the next 4 weeks. We have made the new code signing certificate available in older versions to allow for a speedy distribution as they include no app code changes other than the addition of the certificate. 

If the upgrade is not complete by the end of September, you will have kiosks that will no longer be able to auto upgrade. This will likely require manual installation of the next future upgrade pushed out by remote access or having an onsite tech at retailers cost. This should be avoided.

Below are some answers to some questions you may have..........

 

 


 

What will upgrading Imagine Kiosk to the latest version of my current core version accomplish?

Upgrading will effectively upgrade your Imagine Kiosk executables which contain new code signed signatures. When the upgrade is pushed, a silent certificate migration is performed. There will be no other changes added to this latest version push. 

Is it possible to keep Imagine Kiosk versions as they are and upgrade our code signing signature alone?

Unfortunately this is not an option.

What is the deadline to upgrade all my kiosks?

September 28th 2017!

What will happen to my Imagine Kiosks if I do not upgrade in time?

The kiosks will continue operate as per normal however the next time you attempt to push an automatic upgrade from your servers, the process will fail. If this happens, you can still upgrade a stores kiosks (and DCM) however the process will need to be done manually which would be very time consuming and inconvenient to yourself and your retailers. If you need to send a tech out, you will have additional costs as well

I have already upgraded some or all of my Imagine Kiosks to core version 15, do I need to upgrade them again?

No, if you have already upgraded to 15.0, your work for this is already done as the latest 15.0 versions of Imagine Kiosk also have the new code signing certificate already built in :). If you do not have version 15, this is fine, you simply have to upgrade to the latest version of your current distributed core version. See list provided earlier in this email.


If you have any questions or issues which are not addressed above, please open a Fusion ticket and one of our staff will assist you as required.

Thank you and Regards.

~Whitech Support Team

 


Read more »



Mar
16

Forcing users to upgrade will be done, at this stage, by the Whitech Support team.

The Whitech Team, as per normal, will submit the latest version to the app stores and once they have been approved will then publish it accordingly.  The force upgrade will only be done when both iTunes and Google Play approves the apps - meaning that the latest version has been published therefore is avaialble to download and install on a device.  

The main purpose of this is to make sure that all users are not only running the same version of the app but to also make sure that bug fixes and new functions are obtained by customers straight away.  

The force upgrade means that anyone that has the app installed on their device, once they relaunch the app, will automatically get prompted and redirected to the relevant app store to download and install the latest version.  


Read more »



Dec
10
*Urgent Attention Required* - Imagine Kiosk Required Upgrade to 10.1 Notice
Posted by Carlos Gonzalez on 10-12-2015 09:21 PM

 

 

Whitech have completed our 2015 upgrade rollout with the release of 10.1 to all entities world wide. As you would be well aware, our upgrade process will always force the "Online Imagine Website" to the latest released version, however it is possible for your kiosks to continue to run on older legacy versions of Imagine Kiosk.

We would like to bring urgent notice to you that everyone world wide are now required to upgrade all your Imagine Kiosks to a minimum version of 10.1. This action is required due to the expiry of the Imagine Kiosk Code Signing Certificate. This happens every 3 years and is unavoidable.

Code signing certificates are the method of using a certificate-based digital signature to sign Imagine Kiosk executables and scripts in order to verify the author's identity as being Whitech Pty Ltd and ensure that the code has not been changed or corrupted since it was signed by Whitech.

 Any currently installed versions of Imagine Kiosk you may have on the field using version 9.9 or earlier are installed with an old and expired code signing. These kiosks must be upgraded to 10.1 at your earliest convienence.

Below are some answers to some questions you may have..........

 

 


 

What will upgrading Imagine Kiosk to 10.1 accomplish?

Upgrading to 10.1 will effectively upgrade your Imagine Kiosk executables which contain new code signed signatures. When the upgrade is pushed, a silent certificate migration is performed.

Is it possible to keep Imagine Kiosk versions 9.9 or earlier and upgrade our code signing signature alone?

Unfortunately this is not an option.

What is the deadline to upgrade all my kiosks?

You fortunately have some time. Please plan to have all your kiosks upgraded to 10.1 by January 22nd, 2016. We recommend giving yourself some time before this deadline to protect any clients that may have had any issues with their installation.

What will happen to my Imagine Kiosks if I do not upgrade in time?

The kiosks will continue operate as per normal however the next time you attempt to push an automatic upgrade from your servers, the process will fail. If this happens, you can still upgrade a stores kiosks (and DCM) however the process will need to be done manually which would be very time consuming and inconvinient.

I have already upgraded some or all of my Imagine Kiosks to 10.1, do I need to upgrade them again?

No, if you have already upgraded to 10.1, your work for this is already done. :)


If you have any questions or issues which are not addressed above, please open a Fusion ticket and one of our staff will assist you as required.

Thank you and Regards.

~Whitech Support Team

 

 


Read more »



Mar
6
Release Notes Version 9
Posted by Diana Parana on 06-03-2015 03:35 PM

[IMA-4029] - Irrelevant message box appears on a normal book when we try to apply borders and that could not be closed – FUSION TICKET 1782

An issue was raised where an irrelevant message box would appear when apply borders on photobooks and users could not close it off and proceed with their creation/order.  

This has been resolved. 

 

[IMA-4180] - Promotions - When promotions are applied, output console crashes job – FUSION TICKET 1655

An issue was raised where output console was not able to create a jobs’ info.xml therefore making it crash when a promotion is being applied.  

This has been resolved.

 

[IMA-4355] - Digital Prints Navigation - Group level issue & [IMA-4406] - FFUK R8.1 Trial Site Kiosk Issues: Pre-loader stuck when navigating forward and back between print size selection screen – FUSION TICKET 1821

An issue was raised where frontend will display products not assigned in a group level when navigating back and forth.  

This has been resolved.

 

[IMA-4381] - FFAU Guest ID in XML data instead of CUSTOMER ID – FUSION TICKET 1773

An issue was raised where image links identified in the job xml was using a guest customer id and caused.  This situation seems to only occur where users would initially start off as a guest user, loads images then decides to log onto their existing imagine account.

This has now been resolved.

 

[IMA-4392] - Add photos - Text to display no pictures selected needs rewording. – FUSION TICKET 1857

The wording seen on the Add Photos screen has been amended to read as follows

 No pictures selected. 

To select pictures, choose an album and click on the pictures you wish to use.

 

[IMA-4409] - Trying to apply auto correct to imagine will result in error message "Issue has been encountered while generating a preview of the auto correct filter" – FUSION TICKET 1825

An issue was raised where an error message would appear when apply auto correct to an image.  

This has now been resolved.

 

[IMA-4412] - Borders are not saved for some photos in photo book – FUSION TICKET 1797 & 1826

An issue was raised where borders that were being applied on photobooks were not being saved at all.

This has now been resolved.

 

[IMA-4346] - Add pickup time to receipt xml for Just Photos – FUSION TICKET 1572

A request was forwarded to add the pickup time field to receipts.

This has been completed.

 

[IMA-3487] - Retailer is receiving guest mobile emails. – FUSION TICKET 1228

An issue was raised where retailers would receive the guest mobile email each time a customer registers as an imagine customer.

This has been resolved.

 

[IMA-3920] - Phaser - Unable to print for more than 1 card – FUSION TICKET 1437

Using a Phaser Printer Link, users will now be able to print jobs where the set quantity is more than 1.

 

[IMA-4184] - Admin Tool Time out when pushing updates to ASDA – FUSION TICKET 1562

An issue was raised where Admintool times out when pushing through all service updates against all stores.

This has been resolved.

 

[IMA-4335] - Session timeout when trying to log in and save phone number on kiosk – FUSION TICKET 1711

An issue was raised where a user’s session would time out when updating their details – specifically their phone number – on a kiosk after logging into their account.

This has been resolved.

 

[IMA-4363] - Some kiosks fail to read certain SD cards in Denmark – FUSION TICKET 1758

An issue was raised where some kiosks failed to read certain SD cards

This has been resolved.

 

[IMA-4417] - Random images appear in the "Sample Images"- FUSION TICKET 1833

As issue was raised where random images would appear on the sample images page

This has been resolved.

 

[IMA-4424] - Freezing in Express mode when using large amounts of images – FUSION TICKET 1866

An issue was raised where the IK would freeze when switching on the express prints mode on a kiosk profile.

This has been resolved.

 

[IMA-4425] - Eway Payment changing prices causing mass problems at Photocreate

An issue was raised where Eway payments where incorrect after promotions were applied against orders.

This has been resolved.

 

[IMA-4431] - Calendar Grid value <grid_background_alpha> is NaN and not crashing on OC – FUSION TICKET 1799

An issue was raised where some calendar jobs would obtain a white grid during output

This has been resolved.

 

[IMA-4435] - FrontEnd Kiosk freeze when upgrading to 8.1.073 – FUSION TICKET 1870

An issue was raised where frontend Kiosk would freeze during an upgrade.

This has been resolved.

 

[IMA-4437] - Password Request Email by code: Not using correct user group name in email body – FUSION TICKET 1791

An issue was raised where the incorrect email was being sent when tyring to retrieve a password recovery.

This has been resolved.

 

[IMA-4476] - Yearly calendar is asking for the starting month – FUSION TICKET 1879

An issue was raised where users were being prompted to select a starting month when creating a yearly calendar.

This has been resolved.


Read more »