Showing posts with label issues. Show all posts
Showing posts with label issues. Show all posts

Wednesday, 20 January 2010

A great first week (with a few minor niggles)

We have had a great response to version 3.2, so a big thanks to everyone who has purchased the new version of the application this week - we have had our best week of sales since the project started.

A few minor issues have shown up however, mainly in regard to the built in esellerate purchase/licensing mechanism. Some users have reported being unable to register the product from the built-in esellerate store, and a number of users who had previously downloaded earlier versions of the application have been unable to get the new version up and running, seeing a 'Your Trial has now expired' dialogue.

As always we are working on fixing these few niggles, and will have an update available before too long.

Thanks again for the great response.

Monday, 16 March 2009

Safari 4 Beta & Esellerate update

We are still have problems with Esellerate when the Safari 4 Beta is installed. Currently it is not possible to activate, de-activate or purchase a license from within the application when Safari 4 Beta has been installed. The official response from Esellerate is as follows;

'Unfortunately, at this time we have not completely tested the eSellerate SDKs with Safari 4.0 since there hasn't yet been an official release and the product is still in beta. It's possible there might be problems with the Webkit components that could have issues with the eSellerate SDK, but which either Apple might correct or else perhaps we might have to adjust the SDK for in the future, when Safari 4.0 is released.'

Therefore, for the time being, to activate Frameline, it will be necessary to un-install the Safari 4 Beta. We will keep you posted when we have some more information on this issue.

Friday, 27 February 2009

Safari 4 Beta issues

Unfortunately, our implementation of the esellerate API that we use in Frameline is not compatible with the new Safari 4 Beta (due to an updated webkit) This causes the application to crash on startup. We are now working to get this fixed, and will incorporate the fix into the imminent 3.1 update.