the.rampage.rado

I hope I have something to show in the recent days.

Yes, by using it you don't have to change your csv format. But of course it skips the whole column and if you need some data from there it becomes a problem.

I'm giving an example with Excel: In this case id 2 and 3 will override the price with 0 and not simply skip the import and leave whatever price there was. Empty cell = ;; You are missing one more separator; you are starting with ID, which is empty in the example and you should have it as ;1;test;;; If your example with only 1 row you can set up your import template to ignore those columns: But of course, this does not work in my example above as you won't import any price for 1, 4 and 5.

Yes, I created a feature proposal. Will update you if I can work out something with Codex. We have to be careful which fields we allow this for. If the whole column is empty, you can simply not import it. You can keep it in the csv that generates it, but you can skip it in the import template. But of course, if the column is partially populated, this does not work, as the fields that have nothing between the separators will also be overwritten.

I assume you have a csv column that is partially populated and you want to keep the data in your db for the rows you have no value in the csv? If so currently, no - you can't do this in the importer. If of course your whole column is empty you can simply not import it but I doubt this is your problem. Created a new issue to track this: https://github.com/thirtybees/thirtybees/issues/2120

Yes, the idea is generally targeted to multistore installations so we can achieve better coherence with FO branding and not use style-neutral templates. But it can also be useful for merchants using various modules from separate developers to track, detect, and unify them in one style. For example, currently my revws emails are quite different from my core ones. Yes, you can do that when using one shop by changing the module email template, but you have to keep a map of the modules that have emails and track this on every module update. Using the module, you will create a module email template override and use it instead of the standard one. Can you give some screenshots of the empty templates you use? The inspiration for this module came from one long forgotten one my theme developer supplied, but it is no longer packed with the theme, I even failed to find it in old backups of the template so no logic is shared at all.

Hi forum, I'm 'working' on a small module that swaps the default email templates with new custom ones that can be configured in BO - for v1 - only colors and email logo, more additions later. It also detects missing email templates during sending, so the merchant can later add them. The idea is to have granular per-shop control over the styling and the theme used. We would have the opportunity to have multiple themes and use them simultaneously for different shops. What current templates do you use? Are you stuck (as I am) to the default ones, or have you created/adapted the code to follow your FO design more closely? Can you add screenshots?

@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?

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

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.

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?

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?

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

Let's keep the discussion polite.

I also have probably under 0.5% cancelations/returns. That's why I don't know (or care) about the exact numbers. How do you envision the validation before the customer/guest clicks on the 'withdraw contract' button? Guest tracking is only for guest orders - if you try to check your customer order, there is a message that shows that guides you to log in to your profile and proceed with tracking there. Withdrawal period could be easily configured from the day 'Delivered' status is set for the order. Let's say your T&C state 30 days returns - you set 30 days and after that the button is automatically hidden. If you have partial deliveries, mark the order Delivered after you have delivered the last item in it. The first ones will have a longer period, but I doubt any business will go bankrupt because of that option. And altogether this button is valid for the whole order, not for part of it, so the customer could choose to receive/keep or cancel/return all items.

I continue to think that your tesis of 'available everywhere' is not needed. The document clearly states - 'make the process not harder than ordering'. For registered customers: They have to register an account -> checkout If they want to make a withdrawal -> log in to your account -> find the order in order history -> click on two buttons -> the process (manual or automatic) is triggered. For guests: they can order with just entering their data (including email) -> checkout If they want to make a withdrawal -> use Guest tracking controller -> enter the order number and email (same level of validation as when ordering) -> use a button on this page with the same effect as if a registered customer. Just expose your Guest tracking controller with link in the footer for all guests and this aspect should sufice. If you just make a new controller and put it in the footer, you will still have to have some sort of validation - you can put only the order reference field there, but I think this would not imrpove the process.

Yes, this is a little bit annoying.

I our local PS FB group, we had a lady merchant who was selling custom wedding lapel pins and other stuff. Her combinations per product were around 30k I think (5-6 dropdowns with many choices per dropdown). Of course, the system would fold... 😄

Currently, there is nothing better in thirty bees. Soon there will be packs with combinations feature. You will be able to create packs where customers will be able to select colors, etc. But you hit another snag - sizing will have to be arranged manually with the merchant as currently there is no option to select 5xS, 5xM, 5xL in a 15x pack. How many colors, sizes do you have? I have products with 11 colors and 10 sizes. If you combine personalization in the attributes, you're doing it wrong.

Could you describe your process/idea?

For sure, I'm not the first to come up with this idea, and precisely because of what nickz said (code quality) I will never release any of those as a paid module. Saying that, if anybody wants to further develop/maintain some of those modules or a later version is worthy of becoming a thirty bees free community module, I'm more than happy to assist.

NOT A MAINTAINER, JUST SPAM MODERATOR HERE. Yesterday I started testing it. After two PRs in code I have used 50% of my session quota. No matter how better is than GPT if I can use it only when they want I will not use it. (I'm on the first paid plan, that have 'normal' usage quotas)

OK, let stick to topic here and I will split it later tonight.\ EDIT - better late than ever... Let's discuss community modules and core additions made with AI here. Vibe coders - unite! My entries: antifraud module - sits in BO Orders and displays account info (number of orders, account age), device info (ip, location (based on external database), device, osint tools (sometimes it's usefull to check the customer email, phone in google if some order smells fishy - if they are present - most probably the order is OK). Also - 'soft ban' function - If I want to ban some customers and not fulfill their orders I can ban the account, the module tries to search for similar later registrations and notify me if it detects similar fingerprints. Also global account note - if I want to say something for later orders in this account it can be saved here. control center - offers a dragNdrop dashboard for merchants that want to see the high-level information - order by status, order profit by period, other KPIs, template export/import, etc My vision is when I 'become big' I will have this in my office on an LCD on the wall and only drink my Caipirinhas while looking at the numbers.... 🙂 dual currency display for our EUR adoption - similar to Croatia we have to display prices in both currencies for a period - in FO and emails, not a complete solution but works. Dynamic llms.txt per shop - set up a dynamic llms.txt file per shop in multistore IndexNow Integration - update search providers that support it. thirty bees File Integrity - most recent and still unfinished - goes through each file on the root and tracks edits, deletions, or new files. Using SQLlite it gives a quick note on what is changed on the server in all folders - useful to find malicious files on the server if they are placed, let's say in img where they are extremely hard to find manually Dynamic Robots - serves a dynamic robots.txt file in a multistore environment. And of course many attempts on core changes - visible in github.

I like your approach for the guest customers. But here is what I think this law makes the waters very murky - I don't think it specifies certan cases of which statuses should be excluded from this option. I think it applies to all orders (probably even non considering download/digital products) - i believe it just upgrades the standard RMA and has to stay on top of it. So if you're using RMA, this button simply triggers the proces so you don't force your customers to manuall fill forms, send emails, etc. The moment where the customer would like to return (cancel/withdrawal) only part of the order is easily achievable by a table with all order products on the confirmation page and preselected checkboxes next to them. If they want to cancel the whole order, they simply have to click confirm. If they want only part of it - make the appropriate selection. But of course, this after that has to be wired to the current RMA process. How hard would it be - I don't know because I currently don't use it. IMHO the button should not be in the footer - it has to be in the profile of registered customers or as Yabber said in their guest tracking so there is at least some level of authentication. If the customer made a registration it is just as simple to cancel their order in their profile and this is the purpose of the law - 'order with one button' and 'cancel with one button'. Same with guest customers.

Hi @DRMasterChief, Can you describe what you want to achieve? I reviewed few online articles and the information I get is: we need to have a withdrawal button next to each order for the specified withdrawal period (by law or if extended by our policies) we should lead the customer to another page where they can confirm the request of withdrawal we should send them email with the details of the withdrawal request I think the best implementation would be in BO: In Preferences->Orders - a value in days to specify the withdrawal period and a switch to display or hide the withdrawal button in FO-> order history In FO: In My Account-> Order history right after the current buttons we place new column with the withdrawal button, after that we take the customer to a confirmation page and after confirmation we send out a withdrawal confirmation email. After the request is recieved it gets little bit messy. Probably we will have to track those requests in separate BO controller and process them there. Or we simply receive a message with the order ID and we apply appropriate actions depending on it's current status (we contact the customer to return the products, cancel the order if not shipped, refund money, etc.). But then what happens with their personal data? Should we also obfuscate it as part of the process? Sources: https://www.heuking.de/en/news-events/newsletter-articles/detail/new-cancellation-button-what-companies-must-implement-by-june-19-2026.html https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ:L_202302673