30knees

What is the difference between uninstalling and disabling modules? Does the former clean out the database while the latter does not?

I am looking for the "From" string before the price, as I would like to change it. Where is it located? I can't find it.

Panda theme: http://panda.sunnytoo.com/ Panda file, French: 01498753541580frpanda170629.bin Panda file, German (Sie): 01498513202353depanda170625 (Sie).gzip Panda file, Latvian: 01498753483974lvpanda170629.bin

@Occam Thanks! I didn't realise there's a standard.

That's a nice hack ... so I guess the save button at the very top saves for all sections? Because each section has its own save button. I'll try it out.

I'm translating a theme in the backend. So many fields are repetitive and need to be translated again and again. Is there any autocomplete tool that would recognise e.g. the field "Shipping address" and then automatically autocomplete with the translation the next time "Shipping address" needs to be translated? I tried two autocomplete plugins for Firefox, but they didn't work.

@Havouza Yep, you're right. It's generally not applicable to clothing.

@Havouza Directives set out the framework, but within that framework everyone has to comply by making their own local law. All EU countries have a unit price obligation. It might vary in the details, but generally it will be the same. That is why in (large) supermarkets throughout the EU you will always find for things like ketchup, etc. the unit price indicated.

Here is the Directive for base/unit prices: http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex:31998L0006 So it should be the same throughout the EU.

@DRMasterChief Take a look at: https://forum.thirtybees.com/topic/447/base-unit-price-unit-price-module @Havouza Yep, it's needed for German compliance, but should be the same throughout the EU.

I followed the instructions here: https://www.prestashopmanager.com/useful-articles/how-to/how-to-export-prestashop-attribute-combinations/ and https://www.prestashopmanager.com/useful-articles/tips-tricks/tips-on-how-to-import-prestashop-attributes/ You first need to input the attributes manually in the new store, so eg Color (red, blue, green). I also entered the categories manually. But after that you can export all the products from the old store and then import them into the new store. Make sure the tax settings are the same, too, if you import with prices.

Was able to do it with this module: https://forum.thirtybees.com/topic/423/store-manager-for-prestashop-v-2-29-1 I exported the products and imported them.

The module available at https://addons.prestashop.com/en/additional-information-product-tab/22127-disable-out-of-stock-unavailable-product-combinations.html disables invalid combinations. Its version 1.1.3 is compatible with TB 1.0.1.

Version 1.7.11 of this module https://addons.prestashop.com/en/sizes-units/5756-basicprice-unit-price.html is compatible with TB 1.0.1. The module calculates the base unit price, e.g. what the 100g price of something is that is sold as a 250g pack.

I understand. Shall we stick with the current formal style, then? It would be the easiest.

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