the.rampage.rado

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

Good work! Sharing is caring! 🙂

I see that you use Rocket loader. Do you notice any issues with it?

Advanced parameters--> Logs --> and decript the long string.

The man is VERY busy. Unfortunatelly when the project relies on small number of people delays can happen, message chains could be forgotten, etc. Highly doubt you will even speak to a human with Shopify... 😉

There is no sync script already baked in the platform. You would have to go and manually change those. In general if certain product has no option to change certain parameter - use features. If it can be changed - use attributes. Later in Layered Navigation module you can apply filtering both by features and attributes if you need.

With your current working installation, decode the error message which can be found in var data = ' ...... ' And you will see what is causing the issue.

Good for the previous owner - they squeezed whatever they can and sold a shell...

Good for them...

Don't you consider this a vital secret for your shop? Aren't you afraid of competition tracing your business? I think it's a big issue bug in the current code where it is leacked in FO urls.