This article lists the new features and changes in Moxie version 7.09. It is intended for anyone planning to upgrade their installation of Moxie 7.08. All Moxie components, including Data Server, Player, Studio and services must be upgraded to 7.09 to ensure compatibility.
This article lists the new features and changes in Moxie version 7.07. It is intended for anyone planning to upgrade their installation of Moxie 7.06. All Moxie components, including Data Server, Player, Studio and services must be upgraded to 7.07 to ensure compatibility.
One of the many performance improvements implemented in Moxie version 7.05 was the use of a relative path to reference files in the Moxie cache.
While this change typically doesn't affect an installation, in the case that:
This article lists the new features and changes in Moxie version 7.05. It is intended for anyone planning to upgrade their installation of Moxie 7.04. All Moxie components, including Data Server, Player, Studio and services must be upgraded to 7.05 to ensure compatibility.
When performing a remote Player upgrade from Moxie Studio, one or more Moxie Player upgrades fail with the following error message "Not a valid Omnivex signed upgrade file"
When a remote Player upgrade is initiated, the upgrade file is sent over to the Player PC and its signature is verified to ensure the file is not corrupted. Sometimes, due to certain security reasons if the Player PC can not verify the file's certificate, it aborts executing the installation file.
Remotely upgrading a 32-bit Moxie Player to a 64-bit Moxie Player fails, and the original 32-bit Player is uninstalled. The Player still consumes a license and shows up in the Player Manager and System Manager module in Moxie Studio.
In previous versions of Moxie:
The following is the recommended path for upgrading your Moxie installation.
