toplakd

Have uploaded it for test if one could not do the conversion by him self. It's convertet from current GeoLite2 City, dated 2019-01-22. GeoLiteCity.dat Just upload it into /tools/geoip folder, enable geolocation from the backoffice and you are ready to go.

Yeah, geolocation is good and needed if you sell across the globe and you are registered to VAT. As in EU prices for the customers have to be shown with tax included, but tax is not charged in case of shipping outside European Union. So displaying tax included prices for outside visitors is not good, as they would see higher price if not logged and many of them would not even register to see that actual price for them is lover for the % of your countries tax. So in my case we have 22% VAT and EU customer sees 122 EUR (tax incl.) price, but for customer outside EU the 100 EUR price is shown (tax excl.) But If you are not registered to VAT than you don't need geolocation for normal shop operation.

Have just converted the free GeoLite2 City Database to GeoLiteCity.dat and uploaded into live store and it works. Have tested the site on dotcom-tools to see if prices are shown with tax included or tax excluded based on country location, as for EU I display prices with tax, and for other countries without tax.

Just found this: https://github.com/sherpya/geolite2legacy

Hat gambio user alle rechte für thirtybees datenbank?

Migration with this module to 1.0.8 was as easy as it gets. Thank you very much for this module, as it made me finaly switch to TB after few months. Only one error happens during migration where email subject is not added to "Email Template Subject" field. It happens on fresh installed 1.6.1.23 prestashop migration, and as I see it also happens with upgrade from 1.0.7 to 1.0.8 (dont know if migraded), so this might not be the modules issue, but 1.0.8 upgrade procedure issue. But other than that, it just works. After the migration, and TB Updater there was stil some stock modules which were saying: by Prestashop, but this might be because fo the reason they were not installed and therefore not checked by the updater. Good work and thank you very much. Dejan

Its funny. Copying the red formatted text from forum into field gives error, but copying same text from thirtybees other instalation gives green ok. Let me try once again without red formatting. [{shop_name}] {subject} p.s. Exactly. Pasting Red formatted text into field with ctrl+v gives red error, but pasting red formated text with ctrl+shift+v gives no error.

Than you most likely will have to use the default theme that comes with shop instalation.

This error is related to back office "Advanced Parameters / Email" and therefore the "Email subject template field" is left blank, so after migration you have to add [{shop_name}] {subject} into that field and save it.

So i should look for something for accesing all my mails from android and linux.

Im using it mainly to answer customers mail, and is handy on phone. But its true that i never searched for good phone app for mails. But as it seems i will have to, even if its easier to have all at one place.

Above saves the reply-to issue, but unfortunately leads to new issue 🙂 If shop@domain is not alias. gmail starts to stack different customers mails into one thread 🙂 LOL

Have found a way to fix it so its now working again. I have shop mail as shop@domain, and customer service as customer@domain. both mail accounts are forwarded to my gmail account, and both mails are allowed to send mail from gmail. Now, for replying as customer@domain you have to have it added as usual and checked "is alias" but if you are also having shop@domain mail in gmail, it should not be marked as alias, as otherwise you will always end up replying to customer@domain. So, customer@domain is alias and shop@domain is not an alias. That way clicking on reply adds correct sender from reply-to header.

Fresh 1.0.8 tb. This looks like a bug When deleting something with bulk actions, it always throws "An error occurred while deleting this selection. " It happens everywhere, carts, addresses, customer service mail deletion, contacts.

In migration process it can happen that you get at least 1 error, which i also get if i migrate freshly installed Prestashop that was created with Softacolous. This error is related to back office "Advanced Parameters / Email" and therefore the "Email subject template field" is left blank, so after migration you have to add {subject} {shop_name} into that field and save it.

Have now bought one on ps market one that adds support for new free GeoLite2 Free Databases. Support for MaxMind GeoLite2 Databases (MMDB) Module

Since the GeoLite Legacy is discontinued, are there any plans for using GeoLite2 with thirty bees? As it seems, the prestaheroes is stil using Legacy as base.

No, it wont. Going to 1.0.8 is as easy as it gets. But don't forget to create backup first. I always transfer the backup to subdomain and perform migrations or updates on the backup. Than test it, and if everything works fine i move it to live domain. In migration process it can happen that you get at least 1 error, which i also get if i migrate freshly installed Prestashop that was created with Softacolous. This error is related to back office "Advanced Parameters / Email" and therefore the "Email subject template field" is left blank, so after migration you have to add {subject} {shop_name} into that field and save it. But other than that it just works.

You don't want to upgrade to other than 1.0.8.

Have now moved to hosting in Germany as my current provider has no plans to do some upgrades. Now my back office is realy flying compared to before 🙂

PS changelog-1.6.1.21.txt - Bug fix: - #8828: Stop sending a copy of the contact message to the "author" (avoid spam) No problems if i loose it, will modify it again, unless TB applies it to the core 🙂

This is the only change to the core file i've made. That change was already integrated in latest ps versions as ps team removed sending a copy of contact form mail to the customer.

Hope no problems will appear. Have tried to migrate several times during different TB versions, but now at 1.0.8 and migrator and updater it worked as it should. I'm using PS 3.11.4 Paypal module, as i'm not ready to play with TB paypal yet and it's rest api 🙂 And first paypal orders are already through with success on migrated site.

I just migrated from latest 1.6.1.23 PS to TB 1.08 without problems. Have switched to the original TB theme in migration process, disabled all overrides and everything was just working. But got that 500 error few weeks back when i was on 1.6.1.22 and tried to copy over my existing customized theme. Yesterday then tried again with upgraded ps to latest, and than migrated to TB. And now even my customized theme works as it should. Don't totaly know where my problem was few weeks back, but yesterday it just worked and already got through first orders succesfully after migration. But I'm not using official TB Paypal module, as stil using the PS Paypal v3.11.4. Switching to TB is already big step, and don't wanna mess with new paypal module at this time.

Next change: Disabling sending copy of contact form message to the customer: Deleted following from line 234 in ContactController.php