Are you able to notify eShop users when an upgrade is implemented and when the next one is scheduled?
Notes appertaining to each upgrade would also be very helpful as new tweeks which may be of use could exist without subscribers being aware of them.
Also, is there a way of identifying which version is currently operating?
Bertie
Hi Bertie, thanks for your ideas. Firstly we are in complete agreement, as I'm sure you know we a re constantly developing the eShop platform to improve performance and usability as well as adding new functionality and 3rd party extensions. We are currently evaluating how best to make this information available to our customers and will be able to update you shortly. Regarding the version we are currently at eShop v6 which you can find more information about here: http://btbusiness.custhelp.com/app/answers/detail/a_id/85/c/1995,1999,2032
Hello eShop Team
Thanks for your reply.
There are 'sub' versions to version 6, for example 6.0.7 which has already been released by epages. These sub versions often contain bug fixes and enhancements which can make quite a difference to the site performance and usability.
It is this information which is required - see http://www.epages.com/en/products/knownbugs/.
Can you say which sub version BT is currently operating?
Regards
Hi Bertie,
The BT eShop is currently running at version 6.0.6.5 which is the latest production ready release, 6.0.7 is currently an internal release and is not yet ready for live rollout. We expect to move directly to 6.0.8 early in the new year once the upgrade has been finalised and production tested.
Many thanks.
Can you put a sticky posting on the forum when the release is active, and post a list of the amendments please?
Regards
Hi Bertie,
That is exactly what we will do, today we have created a seperate forum dedicated to eShop and as soon as we can provide an update it will be a sticky thread there.
As 6.0.9 has now been released by epages which appears to improve the canonical tag and ssl situation, can you say when we will be moving onto this version from the 6.0.6.5 release which I believe, based on your reply last November, that we are all still on?