Jump to content
thirty bees forum

elpatron

Members
  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

elpatron's Achievements

Newbie

Newbie (1/14)

9

Reputation

  1. Force Currency at Checkout v2.1.1 - by idnovate Let your customers visit your store in their local currency but force currency in the checkout one of our clients use this method, works with native checkout or at least one opc module well. what are local dop methods of payment, it would be great to offer localized payment method.
  2. Hi, I have module that allows you to set a different front office default currency than what is set in your back office. I think rather than switch currency at payment (a visitor surprise) that you should only offer currencies that you have payment option for. https://www.prestaheroes.com/en-us/modules/front-office-default-currency build for 1.5/1.6 ps so works perfectly for thirty bees.
  3. Hi thirty bee community, The team at PrestaHeroes is happy to announce our first thirty bee compatible modules. Two of my most popular modules Geo Targeting Pro and PrestaVault are thirty bee compliant. We hope to bring our shipping commander module in near future. See you in the mix. https://www.prestaheroes.com/en-us/modules/thirty-bees happy selling, el
  4. @mediacom87 said in Different domain for each language: Hi, if you want to use multi shop solution with one language by shop, you can test this module : https://www.prestatoolbox.com/multi-store-prestashop/317-block-multi-languages-multi-domains.html Wanting it as opposed to does it add value in current localization methods. No disrespect to you, maybe this was a solution at one time historically but here we have discussion of best methods. I'm not best developer but I count myself in top 5 localization experts on the planet...lol...so engage and inform when posting a solution that does not add to conversation of best practice. I just personally 'tuned' a client shop....there is idea to buy modules for localization but to have entire shop geo tuned by me with passion. priceless geo is most interesting thing about ecommerce. have fun, el
  5. @traumflug said in Different domain for each language: I think it depends a bit on what the goal of this one-domain-per-country strategy is. It can be used to adjust offerings to local needs. To get this, there's multishop. As far as a quick research goes, language settings are for all shops together, but one can always choose browser's default language. Another one might be to deal with customer habits. They're simply used to type "es.myshop.com" over "myshop.es". In that case, multishop comes to the rescue, too, because it allows to set up many URLs for a single shop. They all get redirected to the main URL, then. Third possible choice is to establish a couple of .htaccess rules, redirecting from "es.myshop.com" to "myshop.com/es". https://www.prestaheroes.com/en-us/prestashop-geo-localization-solutions/prestashop-multistore-multishop-pro I originally wrote this for ps 1.4. This back in the day when localizing on a url was all the rage. orginal ps has a very robust by country configuration support which is what originally got me interested in this cms. here is my favorite work in multiplexing one installation by country. https://www.prestaheroes.com/en-us/modules/seo-modules/prestashop-module-seo-friendly-language-url-pro this is even compatible with gsitemap in that your old /en/ would be presented en-us for example. googole LOVES this. The one bit missing with this work new feature is where we alias a language pack so that we could define 'many' languge/country codes from one language.....es-es aliased to es-countrycode.....anyway....that is current 'best practice' to localize by country/region content. Another important factor, choosing a multishop solution when there you do not share 'everythinig' and even then creates a lot of challenges most shop managers struggle with. Remember addon's does not have a 'ps ms compliant' attribute. So if shop is not going to share pretty much everything then having separate installations is much better solution. sure with default theme modules ms functions well enough but through in a 3rd party theme and rich module eco you had better have good support. Fun discussion. Happy Thanksgiving from Kansas City. el
  6. @netamismb said in Different domain for each language: I would want to have a separate domain for each language. I know there is a paid for prestashop, is there any module for thirty bees? I've contact the prestashop module developer but I didn't get any answer. @lesley said in Different domain for each language: You might try this developer, https://www.prestaheroes.com/en-us/prestashop-geo-localization-solutions/prestashop-multistore-multishop-pro Hi everyone, elpatron from PrestaHeroes. Thanks Lesley for referral as this is one of my favorite area's. I do 'not' recommend a domain by language unless there are 'by country' differences in your shop. To create a domain by shop using native Prestashop is a LOT of overhead and you are basically creating duplicate content to manage. Language is not by country unless your the entire visitor language, for example es-es for Spain es-co for Colombia. But this all used to be handled by ccTLD's, i.e. .es / com.co but NO MORE. Check out my advanced language friendly url module...it da shit....lol go check major players, they don't use tricks....check azure.com...that is what I modeled our language friendly url module....bleeding edge, read I only sold few...jajajaja Love geo localization chat....but I do not recommend VODOO, domain by language has no place in a best in class solution. Cheers, from Kansas City peeps...el
×
×
  • Create New...