All Activity

hast du mal einen Screenshot o.ä.? ich verstehe das nicht ganz und konnte auch keinen derartigen Fehler feststellen, auch in anderen Versionen nicht. Hast du das EU-Modul aktiv?

@vir - Because I have some ideas, can you help me with your workflow? How do you plan to proceed with those requests? What you envision is your optimal workflow in BO? Where are you located and what are your local requirements for delivery refunds in such cases?

@DRMasterChief It's a pleasure to contribute to the discussion. Unfortunately, however, I must once again contradict you, since, contrary to what you claim, I have never found any evidence to suggest that the withdrawal function should be accessible even without logging in. Furthermore, the same underlying logic supports my thesis: requesting a withdrawal without logging in (and therefore manually entering order details) is certainly more complex than logging in and pressing a button (without having to manually retrieve any data), and the law, as you yourself pointed out, establishes that "the procedure for requesting withdrawal must not be more complex than the procedure for concluding the purchase contract" (which necessarily requires a login or, in any case, the entry of at least one email address and the generation of a password, to ensure security and privacy during the purchase/payment process).

Danke, nun Anzeigen auf nein, cache löschen und trotz allem ist die MwSt. noch drin. TB 1.6 hat eindeutig mehr Macken als die 1.3. So ist eine Kategorie gegraut. Im Frontend wird sie aber gezeigt. Ich schreibe den inkl. MwSt. in die Beschreibung nur die zzgl MwSt. sticht halt ins Auge.

Thanks for your contribution. I don't want to discuss here whether a particular approach is the right one. Only time will tell, and then the next few weeks when the law is in effect. However, all the statements I've found so far point in this direction: The cancellation function must be accessible even without logging in. We must also not forget that we are viewing this strongly from the perspective of a shop owner... So it wouldn't be as most people here seem to think. It remains a nonsensical approach, and of course, it annoys the shop owner to varying degrees 🙂

@DRMasterChief Hi. I think that the crux of the matter here is "Die Ausübung des Widerrufsrechts soll nicht aufwendiger sein als das Verfahren für den Vertragsabschluss" ("Exercising the right of withdrawal must not be more complicated than the contract conclusion procedure.")...so there is no doubt about the legitimacy of the login, since any buyer, whether a customer or a guest, on any e-commerce platform (thirtybees, woocommerce or other) must register with at least an email address and password (chosen by the buyer or provided by the system) and then log in to the system to conclude the purchase contract (and therefore, since it is no more complicated than the purchase procedure, log in to withdraw from the contract). Therefore, the procedure provided by the module PS I am using is correct and unobjectionable by any lawyer/authority.

@Yabber You don't need to explain it to me; I think all shop owners here know the procedure. But you should understand what's required and implement it—that's just how it is. Whether it makes sense at the moment or not. If you ever get prosecuted for such a violation (e.g. GDPR, Withdrawal button or anything similar), you'll have to explain it to the authorities, and maybe then they'll understand and take notice. Excuse my language, but this isn't getting us any closer to a solution.

No store in the world offers a "nicht registrierte Gastbesteller" option. The "Guest Checkout" option involves the standard registration of a customer account with the store, including all personal and address information. The only difference is that the customer does not have access to their account. Shopping without registration would mean that, during the checkout process, the customer would not provide ANY personal or address information, and a psychic employed by the store would provide all the customer information needed to complete the delivery. Such stores do not yet exist anywhere in the world. Many fraudulent stores mislead customers by labeling this option as "Shopping without registration" or "Shopping without creating an account", when they should provide the correct information: "Shopping without access to your account". Additionally, in this "Guest Checkout" option, everything is in violation of the General Data Protection Regulation (GDPR). In the "Guest Tracking" option, the customer also logs in to view their order. The customer logs in using their Order Reference and Email address.

Here's a statement from the trade association (a specialized lawyer provided information on this). I'm including the German text here so you can use a translation yourself. I think this conveys the information most accurately. I'm really having doubts about the login issue. Durch den Widerrufsbutton soll sichergestellt werden, dass Verbraucher einen Vertrag ebenso leicht widerrufen können, wie sie den Vertrag abschließen konnten. Die Ausübung des Widerrufsrechts soll nicht aufwendiger sein als das Verfahren für den Vertragsabschluss. Der Widerrufsbutton muss für registrierte Kunden und nicht registrierte Gastbesteller bereitgestellt werden. Die Widerrufsfunktion muss grundsätzlich auch ohne Login erreichbar sein. Die gesetzlich vorgeschriebene vierzehntägige Widerrufsfrist läuft jedoch erst ab Erhalt der Ware und somit kundenindividuell. Laut dem Gesetzentwurf reicht es aus, wenn die Widerrufsfunktion ohne Rücksicht auf die individuellen Widerrufsfristen pauschal angezeigt wird. Ist das Widerrufsrecht des Verbrauchers für einen bestimmten Vertragsgegenstand erloschen, wird es durch die Bereitstellung eines Widerrufsbuttons durch den Unternehmer auf seiner Website nicht wieder aktiv. In der Regel wird den Vorgaben dadurch entsprochen, dass der Widerrufsbutton deutlich beschriftet wird, beispielsweise mit „Vertrag widerrufen". Der Button ist optisch hervorzuheben (z. B. Farbwahl, Kontraste) und muss auf der Hauptinternetseite verfügbar sein. Dabei ist er eindeutig von anderen Informationen wie den AGB, dem Impressum oder der Datenschutzerklärung abzugrenzen. Nach dem Klick auf den Button (auf der Hauptseite) ist der Verbraucher zunächst auf eine separate Seite weiterzuleiten, auf der er bestimmte Vertragsinformationen eingeben und dann eine weitere Schaltfläche, z.B. „Widerruf bestätigen“, anklicken muss, um den Widerruf zu erklären. Bei den Vertragsinformationen (damit der Widerruf dem richtigen Vertrag zugeordnet werden kann) ist folgendes abzufragen: Name des Verbrauchers Daten zur Identifizierung des Vertrags (z. B. Bestell-, Auftrags- oder Vertragsnummer) Angaben dazu, wie der Eingang des Widerrufs bestätigt werden soll (in der Regel per automatisierter E-Mail). Der Widerruf ist also samt Inhalt der Widerrufserklärung sowie Datum und Uhrzeit des Eingangs zu bestätigen. Wurden mehrere Verträge abgeschlossen oder umfasst der zu widerrufende Vertrag mehrere Waren oder Dienstleistungen, so muss der zu widerrufende Vertrag oder Vertragsteil vom Verbraucher konkret benannt werden.

Hi, "Länder" > MwSt. anzeigen und seit dem Modul "Europäische Rechtssicherheit" funktioniert doch eigentlich ganz gut?! Mehr Infos bitte... auch wenn die MwSt. enthalten ist musst du ja für Endverbraucher den Hinweis geben. Ich habe im o.g. Modul aber auch eine Anpassung machen müssen, war aber eher optischer Natur fürs Theme. Ist es bei dir ggf. auch fest im Theme inkludiert? Dann kannst du es auch per Übersetzung lösen, aber Warenkorbmodul usw. muss dann auch dazu passen.

Jungens, Wie bekomme ich das zzgl. MwSt. aus dem Frontend /backend? Preise sind alle mit inbegriffener MwSt. also Brutto.

I came across this older discussion and wanted to add that Mailchimp and MailerLite still work fine with PS 1.6 if you sync contacts through a simple bridge script instead of a full module. I've also seen people get good results with Sendy if you host it yourself. Has anyone here tried connecting TB with Mautic lately? I’m curious how smooth the setup is.

Okay, I also think that's an exaggeration just because you haven't seen any activity for x weeks. A project like this isn't so short-lived that it needs an update every week. Many developments certainly require several weeks of work or even longer, especially if you're not doing ThirtyBees programming full-time. The internet and everything connected to it is fast-paced, that's clear. But the rule still applies: if you're in a hurry, go slowly. It's nice to get an update from Acer, even if it doesn't bring anything new.

Since there had been absolutely no activity on GitHub for over six months, I assumed the project had been abandoned and stopped submitting pull requests, considering it a waste of time.

Your drive for more founding is clearly visible in the 1.6 Version. Annoying is the least. How about a founding round and invite some active investors?

Hi @led24ee @led24ee No, the project is not dead. And Petr is still around - he's just working on things that are not currently committed to GitHub, but will be in the future. Yes, we only have 1 core developer, and the concerns you have, imo, are valid - which is something we've been wanting to change for a long while. We've been trying to drive "support Thirtybees" campaigns, so we can boost funds and hire more developers and hire some of us full time. Which will result in a massive injection of energy and improvements and new life for ThirtyBees. Unfortunately, it's been a bit of a struggle as I'm sure you've seen with our reminder posts or mentions on the topic from time to time. Chicken and egg scenario, and that is the truth. That being said, there is movement albeit slow, and there are plans, and eventually (hopefully soon), you will see more movement and obvious progress. But yes, more support will be beneficial for ThirtyBees. Don't give up on us yet - see what you can do to help, and hopefully we can all see an improvement soon. Thank you You can DM me directly if you need an email answered - I will share Smile's email address.

Sure I did understand, just there more than one channel. Who did you try to contact?

I use option BCC when sending e-mail, so I can see what I'm sending. Of course this depend how heavy outgoing traffic is. I suggest for better result there is possibility to use shop logo when product picture is not available (what ever this reason may be) or at least this looks better for me.

I have this issue also but i haven't noticed it until now, i simply forgot we are sending the images too.

Hi Will try, because this may be the reason. But in this case I'm the only one who run this format ? I haven't seen that someone else is having this problem and I highly doubt that I'm only one using this module. Thank You

I checked the code, and revws module only supports jpg files. Which was ok in the past, but now when you can have your product images in webp or other formats, it can cause troubles. If your store uses webp images, edit file modules/revws/controllers/front/EmailAction.php and change lines private function getImage(RevwsEmail $email) { $email->markOpened(); $imageId = (int)$this->getValueOrThrow('image-id'); $type = $this->getImageType(); $file = _PS_PROD_IMG_DIR_ . Image::getImgFolderStatic($imageId) . $imageId . $type . ".jpg"; if (!file_exists($file)) { $file = _PS_PROD_IMG_DIR_ . Image::getImgFolderStatic($imageId) . $imageId . ".jpg"; } to private function getImage(RevwsEmail $email) { $email->markOpened(); $imageId = (int)$this->getValueOrThrow('image-id'); $type = $this->getImageType(); $file = _PS_PROD_IMG_DIR_ . Image::getImgFolderStatic($imageId) . $imageId . $type . ".webp"; if (!file_exists($file)) { $file = _PS_PROD_IMG_DIR_ . Image::getImgFolderStatic($imageId) . $imageId . ".webp"; } I will fix this in next version of module

I have this module. Somehow there is error. When client get this email there is only language relates flag picture instead of product picture. Can someone point me in correct direction to find out why is this ? I haven't changed anything in system. So I have no idea what can be the cause. Thank You

Maybe You don't understand this. I pay for this. They can at least answer. Even negative answer is better than nothing. But now some ... is saying that go look for some other ways. I spend about 3 month last year to try to BUY some extra things. They answered once a week. I offered extra payment but they couldn't understand or maybe they had already too much money. Result was zero. Now after about half a year later I renew my subscription. And now they even wouldn't answer. I wouldn't be moaning if I was some random jerk in forum. So yes this project is dead. Maybe there will be resurrection, but I doubt. I have no idea how long this current version will run. github shows almost zero activity.

It is not dead, if you need something done you have several channels. Not everything needs to be handles by staff. What do you need? TB has one of the most helpful people in the forum. Developers read here too something other forums won't have. It is a self help shop system. It has hints in some of the files to explain what else is connected. Something I have not seen elsewhere. It runs on php8.3 and most likely on 8.4 too.

This project is dead. Even if You are paying, there will be even no answer to email.