Many shop issues after new try to upgrade

[Scully]

We run TB 1.0.08 for a long time and it hasn't been updated since this version was set up. This old installation contained a lot of specifis changes and any try up upgrade via core upgrade failed. After many failed attempts I first installed a fresh TB 1.6. and then migrated the database from the old installation. The shop works but still with many issues. I try to ask all questions within this thread instead of opening a new one for everything.

Question 1 / Mails

we don't get any mails with the only exception of the contact form. I could not figure out, where the value for TB_BCC_ALL_MAILS_TO is set.

 

 

Edited 8 hours ago by Scully

[Scully]

Question 2 / Order State

Every new order goes to backorder state. Order State Id 9 (out of stock, paied). My order state table looks like this (taken over from old prestashop, then TB 1.0.8).
This is my order state table.

 

[Scully]

Question 3 / Order cancelled, Stock Quantity remains unchanged.

When cancelling an order, the stock quantity does not revert to its original value. My order_state_id for cancelled is 6. But I guess, the new TB order_state_id for cancelled is 5?

Our state 5 is however 'Order finished'. In regard to this: If we change the order state table to the "new" TB values, we needed to change all historic transactions as well. This is possible but quite an effort.

My question is, how are the default order states set? Is it by id or by template name or by others means?

Edited 7 hours ago by Scully

[Scully]

Question 4 / There are no carriers that deliver to the address you selected.

This message pops up on all front end orders. Howerver, it is possible to proceed to the next step and to place an order.

 

[the.rampage.rado]

First of all. Did you try gradually updating between official major versions and keeping their requirements in check (like dependencies, php version, extensions, etc.)? I would recommend to try this 1.0.8->1.1.0->1.2.0->1.3.0->1.4.0->1.5.0->1.6.0. This would take more time but you will be able to investigate step by step where things break, where you have to check your hosting configuration, etc. 1.0.8->1.6 is quite a big leap, quite a lot things changed for these years, and on top of that when you have some custom work done to the code which could have messed up the database it's get messy quite fast. Also I would recommend on each step to consult with the release notes for every version so you can expect some things that are changed. You can find those here: https://forum.thirtybees.com/forum/2-announcements-about-thirty-bees/

Install Collect logs module when it's visible for you in the modules catalog (I don't know if it supports 1.0.8) and check what is recorded there. Make a test FO registration, make an order, send an email, cancel an order. If everything is OK and there are no records in Collect logs module proceed to the next version of thirty bees. On each step update the files through Core Updated but don't forget to check if there are table updates too - do those or your system will not work as expected.

Now, on to your topics:
1. Did you install a mail transport module when under thirtybees 1.6? This functionality was moved to a module so different methods can be used (the one in PS and thirty bees up until now was unmaintained and obstructed further development of the system). After you install your module and configure it you should also select it for use in Advanced Preferences->Email:

2. If you have migrated your old table to a fresh 1.6 install the order state ids might be different. This is not thirty bees fault, it introduces some default states but this configuration might be modified by each shop and this approach is not recommended when updating. If you use Core Updater this will not be the case.

3. Here is the same - most probably a conflict between your old table records and your new install order state ids. When I cancel an order the stock levels are returned to the previous value.

4. Share your carrier settings, check your zones and your carrier coverage for them. More information would be needed to troubleshoot this.