30knees

Thanks, but I don't want an exact duplicate. That would give me the same messed up database. I'd like to start with a clean database and just transfer the products.

Hi, I have a TB installation that's a migration from PS. Unfortunately, I think I've messed up quite a bit of the database. I'd like to save some bits and start with a clean TB installation. The only things I'd really like to save are: Product descriptions in two languages Product attributes and their prices and weight, etc. Is there anyway to do this?

I think it's a question of style. IKEA only used informal speech in Germany, and people love it. Banks, on the other hand, are typically very formal. That's why I think having two localization packs is a good idea. Let the merchant decide whether they'd like to use formal or informal speech.

A lot of menus allow menu elements to be ordered, but only on a per element basis. I think an ordering by language would be a great advantage. As an example, if I want the following alphabetic order in English: Apples, Lemons, Pears It wouldn't work for German. We can only hard code the order of each element without regard to the language, meaning that "Lemons" stays in second place, even though in German it would need to swap places with "Pears": Äpfel (Apples), Zitronen (Lemons), Birnen (Pears) We used the following code as a semi fix for an alphabetical ordering of the elements in the iqitmegamenu: $sorttitles = array(); foreach($tabs AS $tabkey => $tabrow) { if ($tabrow['position'] == 1) { $sorttitles[$tabkey] = 'AAAA'; // Force first tab on first position (HOME button!) } else { $sorttitles[$tabkey] = strreplace(array('ä', 'ö', 'ü', 'ß'), array('a', 'o', 'u', 's'), mbstrtolower($tabrow['title'])); } } arraymultisort($sorttitles, SORTASC, $tabs); Perhaps it's useful for some other menu modules, too.

Thanks, just signed up. A question to all: Do we want to translate using "Sie" (formal) or "Du" (informal)? Perhaps it would be best to have one pack with "Sie" and one with "Du". I think the current pack mainly uses "Sie". Could we rename it "German (Sie)" and once it's complete we duplicate it and use that as a basis for "German (Du)"?

I installed the German localization pack and would like to help improve it. What's the best way to work on the localization file itself (so not in the backend of TB)?

@DavidP said in No carriers available error: I did a local hack to the OPC module to select a default region (we have different shipping rates for different regions) within our country based on the % of customers we see overall, for example if you got 70% of your deliveries from a certain area then make that the default. It’s not ideal but it’s better than no carrier available when the customer hits the OPC page. Would you mind sharing the code to the solution? I like the One Page Checkout, but it's just not usable as it is right now.

https://www.prestashopmanager.com/ in v. 2.29.1 is compatible with TB 1.0.1.

An update on this error with a semi-solution. I’ve noticed the “No carriers available” error is only for guests/non-logged in customers on the one-page checkout. This is because the shop doesn’t know what country the guest/non-logged in customer is, which in turn is the case because the carrier selector is before the address input field in the checkout. This can be fixed by not using the one-page checkout.

Something to consider for a (one-page) checkout: The address should always be entered before the carrier selector on a one-page checkout. I've noticed that otherwise the shop gives a "No carriers available" error to guests/non-logged in customers. This is because the shop doesn't know what country the guest/non-logged in customer is. See: https://forum.thirtybees.com/topic/235/no-carriers-available-error

Good question. I'm also wondering about the differences between the different referral programs out there (for PS, but assuming their compatibility for TB).

Oh, wow! That's super kind. I'll send you a chat!

Hi, While installing TB I noticed a message on the account creation page that data will be sent to thirtybees. What data is this all?

Hi, We migrated from PrestaShop 1.6.11 to TB in the hope that the dreaded PS "No carriers available error", as eg mentioned here: https://www.prestashop.com/forums/topic/336775-no-carriers-available/ would be fixed. Unfortunately, we still get the same error message. Does the forum have any ideas on how to fix it beyond the standard PS fixes, which unfortunately didn't work for us?