Jump to content

Welcome, Guest!

By registering with us, you'll be able to discuss, share and private message with other members of our community.


  • Content Count

  • Joined

  • Last visited

  • Days Won


Pedalman last won the day on July 1

Pedalman had the most liked content!

Community Reputation

57 Excellent

Recent Profile Visitors

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

  1. I am still hoping that I can get help on this topic. The module runs fine with PS1.6 but not with TB 1.1. bleeding edge.
  2. " yes, ideal scenario would be if there is a check if source image has a right size for example 1600px, then skip that one if possible (depends on compression format) " That is an important option a nice shop system should have nowadays. And of course for each image type. In my case I like to use webp. But best would be to skip webp or any compression for small image dimensions. My workflow is to shoot in high quality, to resize product image to 2024x2024 (I like the dimension 😉 ), and to export it to jpg via my photoedit tool in quality setting 100% ! Then I use a compression tool called Riot on Windows and compress files to 50-65 % .... mostly 65%. Finally I upload them. I did not notice during my last tests that Thirtybees with compression setting 100 compresses files but if so we really need an override that skips this until the option for image in Thirtybees are honed. I mean, look how many threads only in this forum exist about that and how many answeres came...despite the fact that this is extremely important I think. And moreover, the original image should never be touched.
  3. Vorraussetzung, dass es funktioniert ist, dass JavaScript ans Ende verschieben DEAKTIVIERT ist. So ist es leider bei mir. Außerdem habe ich noch Schwierigkeiten meinen GTManager (Modul) richtig einzubinden. Es gibt eine Anleitung bei usercentrics für den GTM, allerdings brauch man dann glaube ich ein Konto bei Usercentrics. Alleine mit PRIVE scheint es nicht zu funktionieren 😞 Wenn ich bei UC ein Konto erstelle, dann kann ich es nicht mit der ID von Prive verbinden. Alles nicht sehr nutzerfreundlich (Händlerfreundlich) und mehr als kompliziert. Ich habe zwischenzeitlich eine Anleitung bei cookieBot für GTM entdeckt, allerdings müsste ich wahrscheinlich auch hier ein Bezahlkonto aufmachen. Also mal wieder einen Dienst mehr bezahlen. Bei Euch läuft es?
  4. We use the payment provider Mollie. This is Prestashop V1.6.x compatible. But there is something wrong with Thirtybees. When we install the latest Mollie module V4.0.7 all order get the sum 1 EUR. total_order is wrong. Our shop is dependent on the Mollie payment options. It runs since early 2020 with Mollie V3.5.5 but this is rather old and we need to update to the latest V4.0.7. I tested the module on a clean Thirtybees install (after upgrading core to latest bleeding edge) and total_order is always wrong 😞 I did the same test with Prestashop 1.6.24 and all is fine! I really hope that some one can have a look at it and dig what the problem causes. Thank you
  5. Hi @datakick perhaps I missed something but today I struggled to translate some 'strings' from fields I use in Chex. First one is in new account creation field and second one in confirmation fields. Both refer to the Revws module. In English is the sting: "I agree to receive review requests for purchased products" I could not translate it via back office. I had to change the L s=" ... " in \revws-thirtybees-2.2.2\revws\classes\integration\chex.php \revws-thirtybees-2.2.2\revws\views\templates\hook\subscription-account.tpl Also if you find the time to add those "Fields" to the translations perhaps you can think about a way to make those fields positions moveable in Chex options.
  6. I had the same question in the past. I stumbled also about shops that had non-white product image backgrounds and if they choose to have a gray background it looked attractive to me. At this time I thought to know that Google and also Amazon had the "prerequisite" that product images have white background. Today I think it might be ok if it is consistent. As Petr and Oliver said you will need png images with 'transparent' background. Then you can make product image background in any color you like via css (theme settings). Right? But now I am interested in two points: 1.) I want to go in near future with webp images. Does thirtybees create these 'after' product image background for png was rendered? So, if I have product image with transparent background and choose a gray backfground via css does the webp then have a grey background or something else? 2.) I assume that if I have png product images with transparent background and I export my products via feed to Google (Shopping feed), Amazon etc. I would have no problems since they gather the png with transparency and add the background they like?
  7. Ich habe noch den Preis für meine Spediteure angepasst. Ich nutze einen Pauschalpreis für den Versand und wollte den alten beibehalten. Also prüft, ob ihr mit den Preisen für den Versand nach Umstellung auf 16% MwSt. im Backoffice zufrieden seid.
  8. I hit the fix button for all the hundreds of critical recommendations in the hope all will be more fine than it was. But one table is resistent to auto fix 🙂 Different unique key `id_product_2` in table ps_specific_price What is the recommendation how to deal with that one?
  9. I want to exclude tables from database export (through backoffice) in order to get a smaller export sql file. For example I want exclude: _DB_PREFIX_.'ps_site_defender', _DB_PREFIX_.'ps_smarty_cache' I tried the following in PrestaShopBackup.php but all following tables are being skipped... not I want: public function add() { if (!$this->psBackupAll) { $ignoreInsertTable = [ _DB_PREFIX_.'connections', _DB_PREFIX_.'connections_page', _DB_PREFIX_.'connections_source', _DB_PREFIX_.'guest', _DB_PREFIX_.'statssearch', ]; } else { $ignoreInsertTable = []; } // pedalman $ignoreInsertTable = [ _DB_PREFIX_.'ps_site_defender', _DB_PREFIX_.'ps_smarty_cache', ];
  10. Vielleicht brauchen wir Händler, die maximal mit CSV umgehen können, ein Tutorial wie wir unseren Shop 'virtualisiern' bzw. clonen in eine Arbeitsumgebung, die einfache vor-/zurück Schritte (snapshots) erlaubt zum Testen. Es gibt zum Beispiel Virtuelle Maschienen für VirtualBox/Vmware/Bitnami mit Prestashop und vielleicht auch Thirtybees? Es gibt auch docker container mit selbigen vermutlich? Schön wäre es relativ einfach und zuverlässig seinen 'live shop' so zu kopieren, um diese Versuche schnell und zuverlässig ausführen zu können. Und nebenbei: Vielen Dank für den Hinweis mit den Rechnungen! Denn ich glaube mich zu erinnern, dass in der Vergangenheit bei Presta genau dieses Problem vorlag. Ich werde es mal testen, nächste Woche und hoffe, wir finden hier einen guten Weg für alle.
  11. Pedalman


    Thanks, I will have a look at Google Webmaster. Two years ago a SEO expert told me to add these lines ?! 😞
  12. Pedalman


    I just generated the robots.txt via Thirtybees backoffice and noticed that my old robots.txt had these lines at the top that are missing in the new one: User-agent: * Disallow: User-agent: Googlebot Disallow: User-agent: Googlebot-image Disallow: # Allow Directives The new one looks like this: User-agent: * # Allow Directives Should I bother? Do they mean the same or does the new one generated via Thirtybees block the google image bot?
  13. Es wäre aber trotzdem schön, wenn es eine genaue Anleitung zur Einrrichtung gäbe. Ich bin auch nur ein Händler und habe Schwierigkeiten mit dem cookie addon. Ich gehe mal davon aus, dass die beiden die mit Thirtybees kommen nicht mehr rechtsicher sind.
  14. @datakick Do you still have this on your list? As already discussed in Germany we have this law that requires the cart summary (plus addtional product features) directly above the confirmation/buy button. Perhaps you could add the option in modules settings to show this redundant information for merchants who think they need it. But may be this is not really required by law? If a customer chooses to buy via Klarna and checksout via 'buy now' button he is redirected to Klarna confirmation page that looks pretty familiar to Chex as it is. See attachment please Second, I was irrated to notice that saw the forms to enter adress information after I entered my email adress while doing a test buy. My email adress is already registered and I assumed that my adresses would be shown but instead of that Chex showed me forms to enter new adress if wanted and the more or less 'hidden' link to uses already registered adress. I think the other way round would be more UX friendly?
  15. Hi it is June 2020 and the module is being actively developed by an agency. At the moment V4.x is the actual one but I have problems to make the payment options show in cart and perhaps there are other issues. But I like to believe that V4.x is running fine with Thirtybees. I am running at the moment Mollie module V3.5.5 for Prestashop on Thirtybees V1.1.x and I am using the fine checkout module CHEX by Datakick. As said even after a deinstall of V3.5x and a fresh install of V4.x I can not make the module show the payment options. Perhaps somebody else here has the new Mollie V4.x running and can give tips? PS: There is to be found a patch of the latest Mollie module by Waschier design https://github.com/waschier-design/PrestaShop/blob/eec24352b982397e0f68b819b634faddfa81e618/mollie.php Problem is though hooks looked fine I did a test buy via one of my payment options (invoice payment) that is not related to Mollie and I got a Error500 So, I went back to V3.5.5 and I hope all is more or less fine and customers can buy
  • Create New...