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.

Pedalman

Members
  • Content Count

    342
  • Joined

  • Last visited

  • Days Won

    2

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 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?
  2. 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.
  3. 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?
  4. 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', ];
  5. 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.
  6. Pedalman

    robots.txt

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

    robots.txt

    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?
  8. 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.
  9. @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?
  10. 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
  11. If you go to dashboard settings* you see at the bottom the form to add 'additional costs' in Euro. * https://i.imgur.com/HMmEizo.png Well, I can not use that but I could use a setting to enter 'additional costs for marketing'. I bet every other merchant too! For the simplicity I suggest a value in percentage (that is something I can easily gather from my GoogleAnalytics or better Adwords account). Since I assume there is nobody working on these 'core theme' files I am asking if I could get some tips to change it for myself.
  12. Thank you Datakick for the nice advice. Actually yesterday I installed some containers with macvlan and and pretty happy. But in order to get such a nice testing environment running like you suggested I need to learn much more I guess 🙂 Anyhow, I just noticed that GitUpdate.php has been updated and the core updater function in Thirtybees works flawless under Windows and Xampp.
  13. I was looking for information on compatibility of Thirtybees and PHP 7.4 since this is the latest my host Hetzner Europe offers for now. I do not know about Php 7.4 but the information given above might be to be updated. Well, ofcourse the post is a year old. Anyhow on https://github.com/thirtybees/thirtybees you will find: PHP 5.6 - PHP 7.3 with a minimum of 128 MiB RAM
  14. I use a module that makes use of the rosell-dk library and converts none wepb images if into the WebP format directly despite the fact that my Warehouse Iquit theme is not 'tagged as webp compatible'. I think it works and wonder if could set this 'tag' in the database so Thirtybees thinks my theme is compatible. Then the option (I am missing it too) would reappear and I could perhaps deinstall my module.. (## To convert an image, using a stack of converters, use the *WebPConvert::convert* method. It is documented in [docs/api/convert.md](https://github.com/rosell-dk/webp-convert/blob/master/docs/api/convert.md).
  15. Wow, these are great additions, and I am very happy you gave them to us. This makes Chex the perfect checkout module for me. Thank you a lot!
×
×
  • Create New...