the.rampage.rado

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.

Is it possible for this module to emit the following items: - current year - would be wonderful if we can activate the module in the footer of our theme or CMS page - shop name - if we have multistore and our CMS pages are the same, but we only want to switch the shop names - shop URL - same - contact email - point to our shop email in Shop Contacts, again useful in CMS pages I know that the module currently does not support CMS pages but for future release,s I think it could be interesting proposal.

Could you give me access to your shop to check on this issue?

What is the reason for this switch?

Merchants can always upload 1px transparent blank images if they only want graphics for only some of the categories.

The team is working on a surprise. When they are ready, it will be revealed. 🙂

Did you follow the guide from page 1? All entities set correctly? Here is an example from Warehouse: Have you regenerated all thumbnails with the new settings down the page: Did you regenerate your htaccess and does it include the images as: .... RewriteRule ^categories/([0-9]+)(\-[_a-zA-Z0-9\s-]*)?/.+?([2-4]x)?\.(avif|gif|jpeg|jpg|png|webp)$ %{ENV:REWRITEBASE}img/c/$1$2$3.$4 [L] .... RewriteRule ^products/([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?/.+?([2-4]x)?\.(avif|gif|jpeg|jpg|png|webp)$ %{ENV:REWRITEBASE}img/p/$1/$2/$1$2$3$4.$5 [L] and so on...

Configure the entities first and after that if you're using custom theme it might be coded to use hardcoded links to the images, not the one supplied by the core. After the image rewrite the links are different.

In 1.6 there was a rewrite of the whole images section thanks to @wakabayashi and @datakick. In order to update to 1.6 and later you have to follow this guide in the BO -> Images:

What is your experience with it? Did it sink your shops or you get lucky and win? My shops experienced vast volatility during 11-14th and right after that a huge swing down. Now I'm like, at least 50% down in impressions. All my vital keyword niches are messed up. It promoted shops that don't sell sporting goods but have a huge market in toys and junk items, it also boosted small, unknown sites that don't look professional at all. Since 1st of January I don't see any further volatility, but I'm stuck on those lower impression levels. "Luckily," January is always a low point for me during the year and I'm hoping a small update will pass around the end of the month. Of course - no blackhat stuff, all links are natural, nothing bad is made SEO wise. Simply a low number of external links and Google thinks you no longer need this first place and moves you to 38th position. What is your experience with it?

If you build your install for 8.1 and any third party modules are running on it it's not big trouble. thirty bees is stable on 8.1 since years.

Here is my config on php 8.1 and litespeed:

You have to run pdo_mysql. In order to quickly view if you do access AdminInformation controller in BO and append "&display=phpinfo" (no quotes), this will launch phpinfo where you can check if it's running. If not - turn it on and check again.

It's active. Go through the branches and see what is cooking underneath. 🙂 And there are other BIG projects that are not on github but they took long time to develop.

There is a bug in thirty bees or the core updater that not every time the update runs define('_TB_BUILD_PHP_', '8.1'); in settings.inc.php is updated. It is not critical and you can manually edit this if you're sure the update propagated and your shop is running OK. This isssue was spotted a while back and @datakick advised that it can be fixed that way but nobody tracked down the issue so it's still present for some users in some scenarios.