All Activity

Bro you are not a normal thirtybees user, you are a module seller 🤷‍♂️

So now you have domain.com/admin/index.php and domain.com/index.php - and this is working but with domain.com/ and domain.com/admin/ it is not working? Then you do not have mod_rewrite active on the server, and you can't use 'pretty URLs' or Friendly URL as it's known in BO.

I added the name files name: index.php, into the URL, Sorry if I was that unclear. Anyway the greyed not found issue is still present. 1.5 and 1.6 are displaying a similar behavior.

@Yabber Just look at the screenshots I posted to understand how the module I'm using works. The withdrawal function is so simple: just click the "orange button" in the order detail and confirm with a second click (red button in the confirm page). No form, no data entry, everything is automatic, exactly as required by the directive. I invite you to reread it again, perhaps with the assistance of one of the many feared German lawyers. Sorry to repeat myself, but in this post you're just continuing to create unnecessary confusion. P.S. I apologize for the quality of the images, but I'm not a graphic designer or a technician. I'm just a thirtybees user.

You should always have index.php in every folder. This is not a fix. Something is breaking the installer. Did you have a running install on this setup before?

I used now TB 1.5 and adding the index.php to the admin folders name did reveal the login page. With TB1.6 that did not work.

Both experiments came to the same end. Page not shown on, 1st Intend the clean download, uploaded to a folder and installing to a brand new database as 2 other DB where not found, or not good enough. Result: a greyed out filed with Admin page not found, Meaning instead of the admin login, a greyed out area saying page not found. Shop Url Page not found. Similar result. After deleting everything I tried a Softaculus approach, with the exact same results.

What do you mean by 'installed to a brand new database'? If you run the installer, it should always be in new db. Sounds like the installer choked somewhere and did not complete the install. Did you use Softaculus or a clean download from the site? Did you try the other option?

I just uploaded a recent download TB1.6. It only installed to a brand new DataBase not a renamed one or even an empty one. Upon install I get a page not found and no admin, Shop is the same picture. Shop is in German, no Demo Pictures, Php is se t to 8. I've disabled webservice no changes, Anyone has an idea?

Currently, the returns feature only works for orders with the statuses “Shipped” and “Delivered,” which makes sense, since it would be difficult for a customer to return products they haven't received. Therefore, adding the ability to cancel orders to the returns feature would require a major overhaul of that functionality.

Database, PREFIX_employee table, campaign_disabled field. Set the date 100 years in the future.

Click on the x and then on the last entry on the new page that shows. This will mute the banner for 1 month.

great, care to share the location (s)?

3.8.3 - 03/24/2026 Fixed HTML content displayed as raw code in the front-office form (form text and confirmation message) Fixed hardcoded 'classic' theme fallback, now uses the configured theme Removed unused images and dead code

I don't know the regulation and I am not affected by it. But in general I agree with @Yabber how it should be handled. A clean/standardized process, that is triggred by a button. Afterwards I would check if the order involves multiple products. If yes, I would ask the customer, if he wants to cancel the whole order or only some products. A contact form might work as the oldfashioned solution, but imo it has only drawbacks (for merchant and customer). I would only disagree with @Yabber, that cancellation and refund are totally different things. From a coding perspective, they are pretty strongly related. In both processes you have questions like: Needs the current_state (order) be changed? Is there a money refund involved? Is the whole order involved or only some products? In both cases restock might be needed. So in short I would say, cancellation is a simple case of returns.

Let's keep the discussion polite.

@DRMasterChief Whether a customer sends an email via the contact form or through an email client, it’s always just sending emails with no integration with the store’s functionality. This doesn’t automate any operations in the store and requires labor-intensive handling by store staff. There are industries where the return rate reaches as high as 40%. At a company like Zalando, they have to process thousands of returns every day. So the number of canceled orders will also be enormous.

Oh dear, good grief! There's no need to send an email to the shop using an email program. The regulation specifies a button that may link to a form. The form can be pre-filled or not; there are no further regulations regarding this. And yes, when the "confirm cancellation" button is clicked, the shop receives a notification in the background. The regulation, effective from June, simply aims to prevent customers from having to use an email program, a letter, a fax, or even a carrier pigeon. That's the basic idea. The customer simply fills out a form or checks a box, and then submits the declaration that they wish to cancel the order. Why is so much more being read into the regulation than it actually stipulates? Thanks @vir for your post before.

@vir The module you're promoting includes the following description: “This module adds a withdrawal request button to the order detail page in the customer account.” So I assume that the customer must be logged in to submit a request to cancel an order. There isn't a demo of the module, so it's hard to say much more about how it works. I provided the WooCommerce and Shopware examples to show that in every e-commerce application, the customer must be logged in to manage their orders. Without logging in, the only option is to send emails to the store.

@Yabber Sorry if I say this but you're just creating confusion and confusing whoever reads this post. Your screenshot shows a section where the customer can access after logging in, correct?...I also remind you that this forum should only refer to Thirtybees, not WooCommerce..... So we have a login and a much more complex procedure than the one provided for by the module I'm using, which simply requires clicking a button (a button expressly required by the directive). Sorry to insist, but I'd like this to be clear for everyone....

@vir When processing a return, the customer simply selects the items to be returned and, if necessary, adjusts the quantity (they don’t have to return all the items). What is difficult about this interface, and what could be simplified? What aspect of this procedure is inconsistent with EU directives? Is it true that, under EU directives, a customer can cancel an order at any time (even 10 years after purchase), the store must refund 100% of the payment, and the customer does not have to return any products?

I have to disagree with you Yabber. The procedure you described is too complicated and violates the EU Directive. Without the module https://psitsolution.com/tools/en/thirtybees-ps-mandatory-withdrawal-button-module (or a modification to the current Thirtybees core), you cannot comply with the directive. The module does what it needs to do and costs less than 30 euros. Lifetime license and updates, so, if there are any future changes or adjustments to be made, they will certainly be implemented by the developer.....This is my experience and my choice. I'm very satisfied and just want to share. Feel free to do as you wish, but be careful with German lawyers! ;)

@DRMasterChief You are confusing two completely different procedures: "Order Cancellation" and "Order Return". If the order has not yet been shipped, the customer can cancel the order, and the store will issue a 100% refund for the order. If the store has already shipped the order, there can be no question of canceling it. In that case, the "Return" procedure is followed. The customer sends the products back to the store, the store checks whether the products are damaged or used, and only then issues a refund for the order, minus the shipping costs incurred by the store. In Thirtybees, the order return functionality is very well implemented. We configure the timeframe allowed for order returns; the minimum period required by law is 14 days, but many stores set it to 30 days or even 60. Thirtybees automatically monitors the timeframe allowed for returns. Of course, both procedures must be described in the store’s terms and conditions.

I've also come to the conclusion that we're talking about different things. On the one hand, there's the simple cancellation "I don't want the goods / I want to return them," and on the other hand, there's an automated process with a possible automatic refund. These are indeed different things, and the EU regulation doesn't require any refund function. The conditions for a refund are fully and clearly regulated elsewhere, and have been for a long time; there won't be any changes to that in June 2026. And we certainly don't use a shop system for this, but rather an inventory management system, which undoubtedly operates on a different level. But thank you for the hint to keep our business going. Now nothing can go wrong. 🤙 🤠

German Shopware store app. Extension: "Order Revocation for Customers", a legally compliant implementation in accordance with EU Directive 2023/2673. The customer LOGS IN to their order dashboard and sees a “Revoke” button for the relevant order.