DRMasterChief

Hello, first of all very bad news, even when it is partially understandable from datakicks side... My idea was always to set tb on a other business model. I dont think supporters models will work: MOST of the supporters will go away after shortest time when shopsystem is working, they are all merchants and have no time or effort for such things, what we need is a good and stable shopsystem with the possibility to have extra features or modules and support if needed, but 99.999% of all merchants are no hobby developers with time and effort to have a look at a forum each week or so. You have to ensure a permanent monthly income for a shopsystem like tb (even when it is a great thing to have it free), so it should be a monthly subscription for the shopsystem will all main modules, maybe in 2 or 3 steps with price increasing. Basis can be 5 USD /month for tb shop with main modules, then 2 upgrades or similar maybe with support included (but the better way is to have support in separate booking and this is also the prefered way to make developers happy 🙂 ) OK, this is not a new idea and most of the other 'professional' shopsystems do so, but it is the only useful way for both sides, merchant and tb. Price just have to be very good compared to other shopsystems and developer should have two open ears for the needs of merchants, thats it.

Hi Sigi, just create an zone with only 'country A' and then you have all possibilities for this zone, e.g. free shipping with amounts....

Hi, you can use this module, works with tb: http://greenmousestudio.com/en/numeric-reference/

Hi, can someone please tell me if the 'optional suffix' (-1234) is common for US citizens? We have some orders from USA and no one give this at the order. We have to search this manually each time, as it is very important for the shipment abroad.... I think the validation of both formats is useful, maybe the customers can/should be forced in any way to give the suffix voluntarily 🙂 thank you

Thank you, will try then. my tb 1.0.8 generates the following: AddType application/vnd.ms-fontobject .eot AddType font/ttf .ttf AddType font/otf .otf AddType application/font-woff .woff AddType application/font-woff2 .woff2

Yes, i have also done this in BO to make sure the .htaccess is up to date after the migration, and it shows this also! I will check the old and the new .htaccess and compare. At the moment i can not share the Domain, pls. understand. The hoster make a migration to an Apache Server, at the moment it was LiteSpeed server and i thought this could be a part of the problem.... I will be back here soon when migratin is done.

Dont get me wrong, i also think that there is no problem with tb 🙂 The hoster will give me an account on an Apache server, i will install and test my migration then and hope the best!

Hello, i have contacted the support from hoster. They told me, that in .htaccess the data is already included: ... AddType application/font-woff .woff AddType application/font-woff2 .woff2 ... but no success, also not with the fresh clean install of tb.

Have done a new picture, please have a look at this (from old / current hosting), woff would be 'enough' for the symbols, but there is also a woff2 which is loaded and seems to be correct on the old hosting. On the 'new' hosting, the Open Sans font is not be loaded at all, wtf ?

Hello @datakick thank you for your idea and reply, glad about this. But... please see my posting from Tuesday at 10:38 PM and the picture. The 'old' hosting shows the same in Chrome and this works without these problems. Please give me some minutes, at the moment i will do a fresh installation of tb in the same hosting in a separate folder and database, lets see how this is then. Maybe i have to contact the hoster then again, with informaiton about your link for mime type.

Hi, still no success here. I do a backup with MySQLDumper, which usually is flawless, then import this into the new hosting. Still the same. Also checked the collations and tried different. Think i have to install tb from ground, then install Theme too. But i have a lot of customized files (Frontend and translations), how to find and copy them?

Hello @toplakd , i have checked this in CPanel and it is correct (same as your picture). Could this error caused by anything in DB and utf-8 (or wrong settings for utf-8 when DB was transfered)? edit: now i have rechecked all DB tables, some of them are utf8_generel_ci , most are utf8mb4_unicode_ci . I have set all tables in the new hosting to the same as old hosting, but no success 😩

Hello, now i have checked with 'old' hosting (there are no such problems there). The Chrome dev tools give the same content type and this tb site works fine. So now ?!?

Server is Litespeed . I can set Apache Handle in CPanel control panel, is this correct or useful for this?

and this is from startpage, there is no content-type showing !!

uff, this is all i get from my Chrome. The fonts should be loaded from local hosting source, not via online / webservice !

and here another site with 3 fonts:

it seems to be font: (but preview is weired, not sure if this is normal for this type of file)

When i type in the direct path into the browser, then the files are been downloaded. Could there be something in the .htaccess which goes wrong (AddFile e.g.)?

nothing, no error, no warning 😰

Hello, i have a strange thing with FontAwesome - this is not loading since we have moved to an other faster hosting plan. It only shows weired signs in the Frontoffice, e.g. at button cart, contact and so on. Pls. refer to the picture. The 'old' hosting plan was with Apache and MySQL, the new is with nginx and MariaDB on SSD drives. Not sure if this can be a reason? The move was directly with copying all files and import DB via phpMyAdmin. We are not using the standard theme, but when i change the frontend theme to default, the FontAwesome will NOT be loaded either. I have checked path and files again and again and the files are stored correctly, i also have tried various permissions, without any effect. In global.css there is the following call: src: url ("../ fonts / font-awesome / fontawesome-webfont.eot? v = 4.6.3"); src: url ("../ fonts / font-awesome / fontawesome-webfont.eot? # iefix & v = 4.6.3") format ("embedded-opentype"), url ("../ fonts / font-awesome / fontawesome -webfont.woff2? v = 4.6.3 ") format (" woff2 "), url (" ../ fonts / font-awesome / fontawesome-webfont.woff? v = 4.6.3 ") format (" woff ") , url ("../ fonts / font-awesome / fontawesome-webfont.ttf? v = 4.6.3") format ("truetype"), url ("../ fonts / font-awesome / fontawesome-webfont.svg ? v = 4.6.3 # fontawesomeregular ") format (" svg "); and the direct path on server is: /public_html/shop/themes/community-theme-default/fonts/font-awesome So this file is also offered for download when called up in the browser and is therefore found (the other file extensions too): mydomain.xyz/themes/community-theme-default/fonts/font-awesome/fontawesome-webfont.eot mydomain.xyz/themes/community-theme-default/fonts/font-awesome/fontawesome-webfont.woff2 etc. We have deleted or emptied the .htaccess too, but with no success or other result. Do you have any idea or solution?! thank you

Hello, do you have set the carrier by 'weight'? This problem is shown when weight is out of range or something like that. Also, check your zones for shipping/pick up and also the states of countries!

I think some more variable shipping options are a good thing. We are also looking for a combination for 'small lightweight items' with additional 'very heavy items' and shipping costs will increase when such a heavy item is in cart and/or there should be no free shipping then.

Ja, am besten die Tabellen die eindeutig sind erstmal machen, dann nach und nach, immer einzeln (geht ja schnell) und notieren, wenn ein Fehler auftaucht kann man so immer gleich wieder zurück. Und ausserdem kann man so dann eine Anleitung hier schreiben 😎

Hallo, meine daß es auch einfacher geht, Gedanken dazu, keine Sicherheit ob das läuft: Du brauchst "phpMyAdmin" (sollte irgendwo im Webhosting-Zugang / Providermenü mit dabei sein), da schaust du mal die Tabellen durch. Die Bezeichnung ist eigtl. selbsterklärend oder man kann vieles dazu googlen. Das hier ist für PS, aber schonmal eine gute Hilfe und nahezu identisch für tb: https://www.prestashop.com/de/ressourcen/dokumentation und https://devdocs.prestashop.com/1.7/development/database/ Die Inhalte der Tabellen sind in "phpMyAdmin" sichtbar wenn du draufklickst, da kann man auch sehen für was die jeweilige Tabelle sein soll (im rechten Fenster siehst du dann die Einträge wie Kundenadressen usw.). Dann mach eine Sicherung der alten DB mit "phpMyAdmin" (Export), dabei die Kollation beachten, sollte utf-8 sein. Neuen Shop installieren etc. ist klar (du wirst deine "alten" Daten nicht einfach kopieren wollen da sie fehlerhaft sind - oder? daher willst du neu installieren?). Artikel kannst du per CSV-Datei importieren, das geht eigtl. problemlos und ich würde kein Modul dafür nehmen. Im neuen Webhostingaccount hast du auch wieder "phpMyAdmin", damit kannst du nun die alte DB importieren, und zwar ggf. nicht komplett, sondern Tabelle für Tabelle wie z.B. Kunden und Bestellungen etc. Das BO läuft wie oben schon genannt auch ohne dem ganzen. Welche Tabellen der DB genau du brauchst kann ich nicht sagen, google mal nach PS 1.6 Lösungen denn die passen auch für tb, ansonsten ist es eine Fleißaufgabe und du musst Dir die einzelnen Tabellen ansehen was es ist und was drinsteht, ich meine aber daß man damit schon entscheiden kann ob man sie braucht oder nicht. Es gibt jedoch ein paar Abhängigkeiten für Bestellungen usw., das spinnt ggf. wenn die DB nicht passt.