| ||||||||||
![]() |
Shopping cart software Solutions for online shops and malls | |||||||||
![]() |
![]() |
|
X-Cart Home | ![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
X-Cart 5.3.4: AMP, Onboarding Wizard, Progressive JPEG, Bug Fixes | ||||
![]() |
|
|
Thread Tools |
#1
|
|||||||||
|
|||||||||
![]() Hi friends,
Today we’ve released X-Cart 5.3.4. Its main purpose is the integration of an Onboarding Wizard to make it maximum easy for newcomers to set up their store. However, it also comes with several useful features, like AMP skin, automatic currency selection, and more. View details in our blog https://www.x-cart.com/blog/x-cart-5-3-4-amp-onboarding-wizard-progressive-jpeg-bug-fixes.html
__________________
X-Cart team |
|||||||||
#2
|
|||||||
|
|||||||
![]() Quote:
![]() Presumably? The upgrade to X-Cart 5.3.3 5 will be required in advance of upgrading to X-Cart 5.3.4.0 which makes good sense and also gives more time to XC and us paying end-users / XC customers, to double check everything carefully first, before moving up to the next branch. Quote:
![]() Our own 'cautious' approach, will be to run the X-Cart 5.3.3.5 upgrade process in a dev store and then in a live store (once it's available at Merchant Wave status) and then evaluate X-Cart 5.3.4.0 in detail, in a dev store again, before taking that live. Looking forward to the improvements ![]()
__________________
Dev Store & Live Store XC Business 5.4.1.35 Server; Ubuntu 22.04.2 LTS (HWE 6.2.0.26.26 Kernel)) / Plesk Obsidian Nginx 1.20.4 / Apache 2.4.52 (Ubuntu Backported) / MariaDB 10.11.4 / PHP 7.4.33 |
|||||||
#3
|
|||||||
|
|||||||
![]() It's true. We investigated the AMP area and that time decided that it is not applicable for e-commerce.
However, Google pushes this technology, so we investigated it more detailed and decided to implement amp pages as landing pages and then redirect visitors to the dynamic website.
__________________
Sincerely yours, Max Vydrin |
|||||||
|
#4
|
|||||||
|
|||||||
![]() XC 5.3.4.0.* has already progressed to XC 5.3.4.1 with a changelog that shows many fixes as well as one improvement. We're guessing these observations came from developer access level users, so at least that appears to be working well. However, the not mentioned in the blog but still shown clearly on the changelog XC 5.3.3.5 release, which we're assuming will be separate and required before progressing to XC 5.3.4.* we still can't see (at merchant level) in any store. This was released on 31st October which is 10 days ago now. 10 days is around the usual time previous upgrades have moved from dev to merchant access level status. We're actively chasing bug-fix releases... Is the XC 5.3.3.5 imminent?
![]()
__________________
Dev Store & Live Store XC Business 5.4.1.35 Server; Ubuntu 22.04.2 LTS (HWE 6.2.0.26.26 Kernel)) / Plesk Obsidian Nginx 1.20.4 / Apache 2.4.52 (Ubuntu Backported) / MariaDB 10.11.4 / PHP 7.4.33 |
|||||||
#5
|
|||||||
|
|||||||
![]() 5335 is still in the developer wave, at the moment there are a few stores who upgraded to this version. Still testing.
__________________
Sincerely yours, Max Vydrin |
|||||||
|
#6
|
|||||||||
|
|||||||||
![]() Quote:
10 days is not enough time at all for any 3rd party dev to adapt and test their modules to the new release. What happens in this case is the new release will not have 3rd party modules ready or if they say they are ready they won't be fully tested...
__________________
Steve Stoyanov CFLSystems.com Web Development |
|||||||||
#7
|
|||||||
|
|||||||
![]() Quote:
![]() However, being parochial for a moment, we (currently) don't use any other modules, apart from XC official modules, which should have been tested / verified / signed off BEFORE this latest upgrade ![]() We no longer get involved in taking developer level upgrades, because merchant level releases should be a better solution for us and our setup
__________________
Dev Store & Live Store XC Business 5.4.1.35 Server; Ubuntu 22.04.2 LTS (HWE 6.2.0.26.26 Kernel)) / Plesk Obsidian Nginx 1.20.4 / Apache 2.4.52 (Ubuntu Backported) / MariaDB 10.11.4 / PHP 7.4.33 |
|||||||
#8
|
|||||||||
|
|||||||||
![]() 5.3.3.4 clean install, upgraded to 5.3.3.5 and 5.3.4.x - they all complain on Environment page about "MySQL cache". The server is on MySQL 5.7.20 and according to MySQL "The query cache is deprecated as of MySQL 5.7.20, and is removed in MySQL 8.0." - https://dev.mysql.com/doc/refman/5.7/en/query-cache-configuration.html
Why is XC5 listing this as one of the "non-critical requirements" since this is deprecated in the MySQL version used and it's being removed from future MySQL versions? If the cart is checking for it it should check for the MySQL version installed and act accordingly. It is annoying not to mention for a normal non-technical person it will probably trigger "Oh my God what do I do now?" kind of reaction. And I suspect the code relies on MySQL cache and it has not been adjusted to not use it. This should have been removed from XC5 code by now especially in 5.3.4.x. I posted about this 2 months ago - https://forum.x-cart.com/showpost.php?p=404968&postcount=11
__________________
Steve Stoyanov CFLSystems.com Web Development |
|||||||||
|
#9
|
|||||||
|
|||||||
![]() Quote:
![]() We haven't seen XC 5.3.3.5 at Merchant Level release yet, but XC 5.3.3.6 with additional bug fixes has now been released anyway. Same situation with XC 5.3.4.0 We haven't seen that at a Merchant Level release yet either, but first XC 5.3.4.1 and now XC 5.3.4.2 have both been released meantime. We'll still run the X-Cart 5.3.3.5 / XC 5.3.3.6 upgrade process first and examine the results, whilst evaluating X-Cart 5.3.4.* separately (all in dev stores) before taking any of these live. Looking forward to all the bug fixes first and any improvements second, as soon as these are all released at Merchant Level
__________________
Dev Store & Live Store XC Business 5.4.1.35 Server; Ubuntu 22.04.2 LTS (HWE 6.2.0.26.26 Kernel)) / Plesk Obsidian Nginx 1.20.4 / Apache 2.4.52 (Ubuntu Backported) / MariaDB 10.11.4 / PHP 7.4.33 |
|||||||
#10
|
|||||||||
|
|||||||||
![]() Not sure when this was included with stock cart. I don't think it was with the newest release.
There is a field in products table PHP Code:
which controls if specification tab shows as a separate tab (true value) or its content shows under description tab (false value). There is no way to control this behavior from admin - at least I did not find it anywhere. This field and its value can be changed with import or directly in database only. However it has been argued few times already that attributes showing under description - weight, upc, sku - should not be there to begin with. None of these 3 fields is part of the description. If they show at all they should be under Specifications tab. So here we are with completely reversed behavior - instead of moving these fields under Spects tab XC decided to move Spects info under Description tab.... Why? It makes no sense at all... And why there is no control in admin for this field?
__________________
Steve Stoyanov CFLSystems.com Web Development |
|||||||||
![]() |
|
Thread Tools | |
|
|
|
|||
X-Cart forums © 2001-2020
|