X-Cart forums

[Anna_Shvetsova]

Hi friends,

Today we've released X-Cart 5.2.15. It includes some bug-fixes. View details in our blog http://blog.x-cart.com/5-2-15-released.html

[kevinrm]

The upgrade from 5.2.14 to 5.2.15 on my development copy went smoothly. There is still a bug in the flyout menu product count however, it is counting disabled products.

[Jeff Spicer]

I completed the upgrade this morning. So far I have experienced no noticeable issues.

[More-Japan]

There were no errors during the update process, and the backend worked fine but the main storefront gave me an error:

ERROR: "Includes\ErrorHandler::FATAL_ERROR" (code 2)

Call to a member function getName() on a non-object

And the storefront cannot be accessed. I will be rolling back to a backup of the previous version.

[Jeff Spicer]

Now it appears that the numbers in the categories are not updating when new items are added.

[kevinrm]

I went from 5.2.13 to 5.2.15 on the live store, the whole thing went smoothly with no problems on the storefront either. This involved 30+ module upgrades so I went into advanced mode, did the core alone first, then upgraded the rest in groups of 5 so as to not overload the server. No problems...

[qualiteam]

Originally Posted by More-Japan

There were no errors during the update process, and the backend worked fine but the main storefront gave me an error:
ERROR: "Includes\ErrorHandler::FATAL_ERROR" (code 2)
Call to a member function getName() on a non-object

+

Originally Posted by Jeff Spicer

Now it appears that the numbers in the categories are not updating when new items are added.

These seem to be caused by your custom modules/themes incompatible with this change:
https://forum.x-cart.com/showthread.php?t=73961

[Triple A Racing]

Originally Posted by Anna_Shvetsova

Today we've released X-Cart 5.2.15. It includes some bug-fixes

We are going slowly and patiently with this on our dev store.
It's hot yes but not a fix for us anyway. It's the opposite really...

The main issues so far are (core / modules):

The mobile site view is altered and the end result is unacceptable. We think (guessing at this stage) this is down to combination of Core CSS / Simple CMS module changes. Updates soon.

A custom modification that we had done and has worked perfectly from 5.2.6 > 5.2.13 now has serious errors. A failed card transaction is recorded and appropriate messages sent, when in actual fact, the transaction is successful (as verified within our payment company test account and independently by their operatives). It's very tedious that a core / module update process trashes a paid-for and previously excellent custom modification. Updates soon.

The 5.2.13 > 5.2.14 > 5.2.15 upgrade process is 'very tetchy' It's prone to errors not seen on previous upgrades plus new 'logic rules' particularly around the some changes in 5.2.14. Hers's one existing thread: https://forum.x-cart.com/showthread.php?t=73961 plus an earlier message in this thread posted by @More-Japan which is linked to it. There are others...

There appears to be some incompatibility between existing, established, tried and tested setups and these latest upgrades. That's not ideal for many users if this is correct

[kevinrm]

Was your custom mods done by Qualteam?

I've got about 5 mods done by Qualteam and 5.2.15 is working flawlessly for us now, every module. I still keep my fingers crossed and hold my breath whenever I do any update or module addition but lately it's been updating problem free. Had zero issues 5.2.13 > 5.2.14 > 5.2.15 upgrade process on our end.

[Triple A Racing]

Originally Posted by kevinrm

Was your custom mods done by Qualteam.

Yes and it is (or was) excellent. Our experience appears to be the opposite of yours (time-wise that is and for whatever technical reasons)

We think we have a much simpler site/setup than your own, so maybe this is what's not gone in our favour on this series of upgrades v the existing custom modification?