| ||||||||||
Shopping cart software Solutions for online shops and malls | ||||||||||
|
X-Cart Home | FAQ | Forum rules | Calendar | User manuals | Login |
Changing Versions for Custom Modules | ||||
|
|
Thread Tools | Search this Thread |
#11
|
|||||||||
|
|||||||||
Re: Changing Versions for Custom Modules
Quote:
I always get an error on the Update Schema step in the redeployment. It would say that it is unable to execute the MySQL query because it would truncate data from the additional fields. Even a minor edit like increasing the SKU to varchar(40) instead of varchar(32) in the custom module causes the same error.
__________________
X-Cart 5.1.10 X-Cart Next 5.2.1 Beta |
|||||||||
#12
|
|||||||||
|
|||||||||
Re: Changing Versions for Custom Modules
Quote:
I've sent your message to the XC5 dev team so that they could check why it is so.
__________________
Alex Solovev, Qualiteam --- User manual Video tutorials X-Cart FAQ You are welcome to press "Thanks" button if you find this post useful Click here to learn how to apply patches X-Cart Extensions |
|||||||||
|
#13
|
|||||||||
|
|||||||||
Re: Changing Versions for Custom Modules
Quote:
Could you please let me know what exactly MySQL error message did you get? Thank you.
__________________
Found a bug in X-Cart? Post it to our bug tracker! Know how to make X-Cart better? Suggest an idea! |
|||||||||
#14
|
|||||||||
|
|||||||||
Re: Changing Versions for Custom Modules
Hey Tony,
Quote:
Here's the error log when I disable my custom module. Quote:
The error happens at: Quote:
-Niboon
__________________
X-Cart 5.1.10 X-Cart Next 5.2.1 Beta |
|||||||||
#15
|
|||||||||
|
|||||||||
Re: Changing Versions for Custom Modules
Do I understand correctly that your module changes length of SKU field?
Just need to make sure before I suggest some solution.
__________________
Found a bug in X-Cart? Post it to our bug tracker! Know how to make X-Cart better? Suggest an idea! |
|||||||||
#16
|
|||||||||
|
|||||||||
Re: Changing Versions for Custom Modules
That's correct Tony,
It changes the length of SKU field, and also adds the fields packSize, POQty, available and techData. All of which have data in the tables already. -Niboon
__________________
X-Cart 5.1.10 X-Cart Next 5.2.1 Beta |
|||||||||
#17
|
|||||||||
|
|||||||||
Re: Changing Versions for Custom Modules
Hi Niboon,
Thank you for clarifications. I will talk to our developers and will get back to you with the results within a day or two. Tony
__________________
Found a bug in X-Cart? Post it to our bug tracker! Know how to make X-Cart better? Suggest an idea! |
|||||||||
#18
|
|||||||||
|
|||||||||
Re: Changing Versions for Custom Modules
Hello Niboon,
I just talked to developers and unfortunately there is no automatic way to transfer your custom module through upgrade. You need to manually save data that is used by your custom module. Then upgrade the store, then upgrade the module and finally upload the data back. I agree, this is a bad approach and it must be improved in the future. We have already planned changes to major upgrade procedure, so you would not have to repeat the same in the future. Tony
__________________
Found a bug in X-Cart? Post it to our bug tracker! Know how to make X-Cart better? Suggest an idea! |
|||||||||
#19
|
|||||||||
|
|||||||||
Re: Changing Versions for Custom Modules
Tony is it to understand if a module is on the market place the changes and data added to database will remain with the upgrade? And if the module is not on the market place these changes and data will be lost with the upgrade?
Or they will be lost either way? This really puts XC5 upgrades on a lower level below upgrades of XC4.... It is a major overlook. What if modules use pre- and post- upgrade hooks to export data first and then import it back once upgrade is done? But this assumes module in question doe snot have to be disabled in the first place right?
__________________
Steve Stoyanov CFLSystems.com Web Development |
|||||||||
#20
|
|||||||||
|
|||||||||
Re: Changing Versions for Custom Modules
Yes, if a module is in the marketplace, then data and changes will remain during upgrade.
If a module is not in the marketplace, you have to disable module during upgrade and this forces you to lose the data. All above is true only in case of major upgrade (e.g. 5.1.11 > 5.2.3). In case of minor upgrade (e.g. 5.1.10 > 5.1.11), modules always keep the data. I agree, this is an overlook and by next major upgrade we will come to the solution.
__________________
Found a bug in X-Cart? Post it to our bug tracker! Know how to make X-Cart better? Suggest an idea! |
|||||||||
|
|||
X-Cart forums © 2001-2020
|