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.

Traumflug

Members
  • Content Count

    1,579
  • Joined

  • Last visited

  • Days Won

    71

Everything posted by Traumflug

  1. If (Front)ProductController would support Ajax: yes, absolutely. Unfortunately it doesn't. One whould have to request the regular page by Ajax, then extract the needed return data from this huge blob of HTML coming back.
  2. I tried as well, it's a very dirty solution. When clicking on 'Add to cart' with a forgotten customization save, it doesn't add the product to the cart, but does this save instead. Along the way it forgets wanted quantity, then reloads the page. This may get rid of unsaved customizations, but also get rid of the entire customer. Getting rid of caching would be a matter of removing server side caching, including Cloudflare. Always a good idea, because saving & adding to the cart as designed uses the exact same pages, so one likely see the same caching issue.
  3. Traumflug

    Lost modules

    Click on 'All' (between 'Favorites' and 'Administration'). Some actions apply additional, invisible filters; such a click should remove them.
  4. Genau. Die 19% von 2019 haben dann eben eine andere interne ID als die 19% von 2021, doch das interessiert bestenfalls Datenbank-Ästheten. Wichtig ist doch, dass der richtige Prozentsatz auf der Rechnung steht.
  5. Wozu soll das gut sein? Macht man keinen neuen Steuersatz, braucht man da auch nichts neu zu assoziieren. Schwierig wird es wirklich nur, wenn man die Preissenkung nicht weitergeben will. Da muss man sämtliche Preise erhöhen. Ein negativer Rabatt wäre da sehr praktisch, doch das geht (noch) nicht.
  6. Das ist kein Fehler, sondern völlig richtig so. Da braucht man auch nichts "reaktivieren". Steigt die Mehrwertsteuer wieder, wird der Steuersatz erneut kopiert, alles ist prima. Keinerlei Grund, in der Datenbank herum zu fummeln.
  7. In controllers/admin/AdminCustomCodeController.php, find the array definition starting with: Configuration::CUSTOMCODE_METAS => [ (probably line 29) To this array definition, add 'maxLines' => 100, This lets this field grow to up to 100 lines. Additional keywords: 'fontSize', 'minLines', 'showPrintMargin', 'enableBasicAutocompletion', 'enableSnippets' and 'enableLiveAutocompletion'. Same applies to the other fields defined in this controller ( = on this page) and to code input fields elsewhere.
  8. Wenn man sieht, wie die da freihändig mit "magischen" SQL-Queries um sich werfen, rollen sich Einem ja die Fussnägel hoch. Ich habe jetzt auch mal ein wenig probiert. Wenn man einen bestehenden Mehrwertsteuersatz ändert, wird da nicht einfach die Prozentzahl geändert, sondern es wird eine Kopie mit dem neuen Satz angelegt. Das heisst, die alten Rechnungen und Bestellungen behalten den vorherigen Steuersatz, die im Shop angezeigten Preise ändern sich. Entsprechend rutscht der Steuersatz auch in der Liste ganz nach hinten, falls den jemand nach der Änderung vermisst. An den Produkten muss man also gar nichts ändern. Einen Haken habe ich dennoch gefunden: der Preis im Block "Beliebt" / "popular" auf der Startseite bleibt beim alten Steuersatz. Also Cache leeren nicht vergessen. Das Problem der Zeitspanne zwischen Bestellung und Auslieferung kann man wie folgt lösen (bei Lieferverzögerungen oder Sonderanfertigungen kann das ja durchaus diverse Tage bis Wochen ausmachen): Die Order anschauen. Ganz unten auf der Seite den Preis des ersten Produkts editieren und einen Cent hochsetzen. Den Preis nochmal editieren und wieder einen Cent runter setzen. Das für jedes bestellte Produkt wiederholen. Sprich, Preisänderungen in einer Bestellung erfolgen nach dem neuen Steuersatz. Aber nur Änderungen, unveränderte Preise bleiben. Wie man den Kunden dann im Dezember erklärt, warum sie für die an Sylvester bestellten Waren im Januar ein paar Prozent nachzahlen sollen, überlasse ich den Händlern. Die können das bestimmt besser.
  9. That's not weird, that's expected. This 'deleted' carrier is needed for older orders, from before the change. Without it, older orders would show the new carrier properties.
  10. The unfortunate truth is, neither PS 1.6 nor thirty bees support transparent images. Actually, implementing such a feature and its sibling, non-square images, in PS 1.6 is the reason why I started developing for PS and eventually joined tb: Getting rid of the white background needs a deep dive into PHP, where these images get resized for the various types a theme wants.
  11. Installed another theme, perhaps? Quite a number of third party themes are broken the way they don't define which modules they want to work with. Accordingly, theme installation follows the (empty) list of declared modules and removes all front office modules declared by the previous theme. To fix this one can edit the file 'config.xml' in the root of the theme. Copy in the list of modules from the default theme: https://github.com/thirtybees/community-theme-default/blob/1.1.x/config.xml#L57-L206 (line 57..206), this should reasonably match. Then switch to another theme and back to the new theme to reset the new theme. Another option is no not mess with config.xml and install all the wanted modules manually. The usual way in back office -> Modules & Services. Which modules? Well, see the list I linked above.
  12. Your "fix" may work for you, and nice to see it does, but is certainly not a general solution. It always picks the first image type defined, which can be any size.
  13. Traumflug

    Rounding

    There are (at least) two ways to format prices. One is the way you used. The other way can be found in back office ->Localization -> Currencies -> (edit currency). There one can turn off 'auto format' to get additional options. And even the ability to show one currency with decimals and another one without.
  14. I'd rename the old installation folder and create a new one for the new installation.
  15. I'd be surprised if regenerating images hurts search engine ranking, because image URLs stay the same. A regenerated image is also identical to the one before, same MD5 sum. Just tested this. If you still want to regenerate only some, just delete them. tb generates missing images on the fly, they'll reappear as soon as a visitor needs them. Still same MD5 sum. To find images of a certain type: find img/p -name \*home_default.jpg Adjust this search until it finds what you want, then delete them by adding '-delete': find img/p -name \*home_default.jpg -delete Just don't delete the original, the image without '-' in it's name, like '1.jpg', '342.jpg'.
  16. Earlier this week I was asked for advice on two vulnerabilities somebody assumed to exist on his site. Lo’ and behold, s/he was right both times. For one of them I wrote a blog post, showing how to detect this vulnerability and also a rough sketch on how to fix the server if needed. The Host Header Injection Booboo Detection is quite easy on the command line. Just run this, with <my host> replaced by your actual host: curl -v -H "Host: evil.com" https://<my host> 2>&1 | grep evil.com If the answer contains something with evil.com, the host is vulnerable. Testing should happen on all hosts in the public and with HTTP as well as HTTPS.
  17. Uhm, one can turn on multishop only for all shops of an installation or for none of them. Did you perhaps duplicate your installation, making a copy of all files and the database? One can do this, but it's not multishop. In this case, both are independent installations. To get a multishop, one has only one installation with one database. There one can add additional domains and URLs for this single installation.
  18. Increasing the size of a table data type can never hurt other than needing slightly more disk space. There is one case where it wants to decrease decimal(21,6) to decimal(20,6), which is safe as well. All prices are stored in decimal(20,6), so having one of many fields with an additional digit makes no distinction.
  19. Traumflug

    New Sellers

    PS 1.6 modules usually need no adaption to tb. Just install it.
  20. Besten Dank für diesen Bericht. Wo der rechtliche Unterschied zwischen einer eigenen Auswertung und einer Auswertung bei Google liegt, erschliesst sich mir jedoch nicht so ganz. Tracking ist Tracking. Vielleicht bin ich deswegen kein Rechtsanwalt geworden 🙂
  21. Klar, das geht. Ist nur nicht gerade "einfach". Alle Dateien kopieren, SEO & URLs verbiegen, DB nicht nur anlegen sondern duplizieren, Zeiger auf die DB in config/settings.inc.php verbiegen.
  22. Agreement on the first part, not so much on the second part. Technically necessary cookies, e.g. to track a login or a filled cart, don't need consent. Describing these in the privacy statement and/or where they get created is sufficient. Matomo is obviously not technically necessary, as one can handle orders without just fine. Accordingly it needs consent. Anyways, it's hard to find clear descriptions and statements about this matter. Take my comment as educated opinion, not as authoritative answer.
  23. Ah, wait, I overlooked the 'go to next page'. Then I indeed get 'no products'. Also another snippet not looking right, page 1 is missing: Regarding the problem, the link behind 2, 3, ... is wrong. It is: https://www.rock4u.eu/camisetas-rock#/page-2 It should be https://www.rock4u.eu/camisetas-rock?p=2 Maybe a typo in the "Friendly URL" of the category, maybe a module messing things up. There's a switch in Advanced Parameters -> Performance to turn all non-thirty-bees modules (edit: and all overrides) off. Always worth a try.
×
×
  • Create New...