X-Cart forums

[cflsystems]

Now why data is wiped out if module is disabled? The module is still there. Not uninstalled. It is simple not active. So if I have a module run for 6 months and data is save din tables, then I disable it for any reason all this history will be lost? And when I enable it again in a week or so everything starts from the beginning? This doesn't make sense.

Imagine a module which adds additional data to completed orders, like some custom shipping data. Now all this will disappear if I disable the module? This is history of the store operations. It should stay intacked. What if customer asks or wants to know about this data 2 months from now, or it is needed to provide prof of delivery or something...

I understand the module has the way to collect, save and print this data and when it is disabled there is no way of doing it but to wipe out all of the previously recorded data is just not right. Not to mention in many countries it is actually the law to keep these records for minimum of X years... You can't just delete them because of this or that.

I am not sure how you can solve something like this but obviously the way it is right now is not right.

[qualiteam]

Hi Steve,

If you ask why we wipe the data, the answer is "we don't". The data is not deleted intentionally.

We agree that how it works now is not right, and the XC5 dev team will look into this.

[totaltec]

I am so glad that this is being looked into. This has been a source of major frustration for me, not only this time 5.1-5.2 but the previous major upgrade as well.

We need to deal with this. We need a way to include our custom modules outside of the marketplace. I think we all understand that this poses a serious problem for custom development.

[tony_sologubov]

Originally Posted by cflsystems

Now why data is wiped out if module is disabled? The module is still there. Not uninstalled. It is simple not active. So if I have a module run for 6 months and data is save din tables, then I disable it for any reason all this history will be lost? And when I enable it again in a week or so everything starts from the beginning? This doesn't make sense.

Imagine a module which adds additional data to completed orders, like some custom shipping data. Now all this will disappear if I disable the module? This is history of the store operations. It should stay intacked. What if customer asks or wants to know about this data 2 months from now, or it is needed to provide prof of delivery or something...

I understand the module has the way to collect, save and print this data and when it is disabled there is no way of doing it but to wipe out all of the previously recorded data is just not right. Not to mention in many countries it is actually the law to keep these records for minimum of X years... You can't just delete them because of this or that.

I am not sure how you can solve something like this but obviously the way it is right now is not right.

Steve, what you are suggesting is right. I agree that this is not working properly at the moment.

The real problem is we cannot change this right now, because 5.2.2 is designed to be upgraded from 5.1.11 and we cannot ship 5.1.12 that fixes the problem.

I am sorry that this problem is here at the moment.

However, the problem will be fixed in 5.2.x branch and next major upgrade will work smoothly.

Tony

[zychen]

Originally Posted by tony_sologubov

Steve, what you are suggesting is right. I agree that this is not working properly at the moment.

The real problem is we cannot change this right now, because 5.2.2 is designed to be upgraded from 5.1.11 and we cannot ship 5.1.12 that fixes the problem.

I am sorry that this problem is here at the moment.

However, the problem will be fixed in 5.2.x branch and next major upgrade will work smoothly.

Tony

I don't think we expect a fix for 5.1.x but I definitely hope that we don't face similar issues after 5.2.x, be best to note it down in a todo list!

[cflsystems]

As above - I don't think anyone expects you to go back and fix 5.1.x. What everyone is after though is if they are on 5.1.x they can upgrade to 5.2.x without problems. But this is not happening either.

What I understand from your response is that this will be fixed for 5.2.x to 5.3.x. Question - how is the upgrade from 5.1.x to 5.2.x to be done now since there are these major issues?

Unfortunately so far I see the forum full of users which stores either cannot be upgraded or end up broken by the upgrade. I am sure there are some for which everything was ok but it seems the majority of XC5 is sadly just not working...

Hopefully you find a way for 5.1.x to upgrade to 5.2.x as well

[tony_sologubov]

Originally Posted by cflsystems

What I understand from your response is that this will be fixed for 5.2.x to 5.3.x. Question - how is the upgrade from 5.1.x to 5.2.x to be done now since there are these major issues?

As I suggested earlier, you can dump custom parts of the database (new tables and new fields in existing tables) and then transfer the data manually.

I agree, this is a time-consuming approach, but this will work.

Originally Posted by cflsystems

Unfortunately so far I see the forum full of users which stores either cannot be upgraded or end up broken by the upgrade. I am sure there are some for which everything was ok but it seems the majority of XC5 is sadly just not working...

Most of the reports on forum related to the problem with improperly updated modules:
http://blog.x-cart.com/5-2-3-upgrade-issue-fix-for-the-users-running-MySQL-5-6.html

5.2.3 release and newsletter to X-Cart 5 module developers are ways how we are making upgrade from 5.1.x to 5.2.x smoother.