the.rampage.rado

Thank you for looking into that! I'm not even sure if I can process card payment and not apply VAT currently as here we are obliged to issue a fiscal receipt and my machine is not configured to issue 0% VAT. What about if we limit the vouchers to the country of purchase - we detect the invoice country and pass this information on the voucher creation logic. Not that it solves anything else other than the possible difference in VATs. When I purchase a voucher in Bulgaria they issue me with receipt as a normal purchase and apply VAT at this moment. I'll have to look into that.

The bots crawl and look for exploits, they don't care if your module is called XYZ or ZYX. If your module has the same code in it the name does not matter. In some cases the module names is even not visible.

Here is a tiny module that is s till in alpha stage so please test and use with care. You want to offer virtual gift vouchers to your customers? OK then! Virtual Vouchers Generator How to use this module: 1. Create your voucher products - set those as Virtual so they don't incur delivery if ordered alone. The value of those products will be picked as voucher value. If multiple products are ordered at once the value will be combined into one voucher. 2. Specify the Product IDs for those products in Virtual Voucher Product IDs. 3. Specify the proper statuses when the virtual voucher order is considered paid in Paid Order States (IDs). 4. Configure the rest of the options to your liking. 5. Copy the cron URL and run it at proper intervals (recommended 5-10 mins). Configuration page: Email sent after order validated as paid: Check voucher page (in Niara - adjust module css to your liking!): As I'm still learning, so please keep in mind this module could (and most probably will) have some bugs. And still the lookback logic for validating the orders is not so cleared out. If in future somebody want to take over development would be more than happy. Changelog: 0.7.3 alpha (12/1/2024) - Fixed bugs with translation strings, new email template (single column, mobile-friendly), fixed bug with cron link not including https. 0.7.2 alpha - Minor bugfixes with multistore reCAPTCHA settings, voucher check page, and controller name. 0.7.1 alpha - Introduction of 'Check voucher' page where the customer can see how much funds are left into their multi-use voucher. Integrated with Thirty Bees' reCAPTCHA module (if it's installed, enabled, and configured the reCAPTCHA will be shown here too) - the customer has to enter the validity date of the voucher as a safety measure. The page's friendly URL should be configured in SEO & URLs (or if you don't use SEO URLs, access from here: /index.php?fc=module&module=tbvirtualvouchers&controller=vouchercheck). 0.7.0 alpha - Option to limit the voucher country based on where it was ordered (from invoice address), email tweaks and fixes, new logo with attribution. 0.6.0 alpha - New email template, Bulgarian email language. 0.5.0 alpha - Initial release. To do: further voucher settings add T&C section to configuration so those are attached to the email. pass conditional information to email for country restriction (if available). introduce changelog in the module. tbvirtualvouchers-0.7.2.zip tbvirtualvouchers-0.7.3.zip

Very strange 🙂 @datakick would assist then.

If they opt out this is a normal behavior. It's the same for me with Analytics.

If you have added some js yes. But based on the files you changed you probably removed a polyfil dependency - if this is the only change this will not affect this functionality.

If you have many third party modules - try disabling them one by one. It might be a module conflict, yes.

Right button anywhere on the page -> Inspect and this icon:

Do you have some custom js code? The issue is not only on mobile browsers but if you click on mobile view in your desktop browser too. So something is acting funny. In my test instance I just switched to Niara and I'm able to add to cart from this list. You also have 2 console errors - piwik is failing to load - temporarily disable it (very little chance it is causing the issue) and one more error with front.js that I'm unable to figure out.

Can you post a link?

I doubt the issue is the age of the OS. By any chance the js is disabled on this mobile browser?

For me it's working fine on my test install. "Add to cart" works.

Also give more details what hosting do you use - shared, dedicated, virtual server, etc. So we can tell you how to fix this. In general you have to create mysql user and associate your table with this user with all privileges.

You can edit/add/remove CMS pages at Preferences->CMS and you can control which ones to display in the footer at Modules->Block CMS

Preferences->Themes->Advanced Options button (bottom right) You can select on which pages you want which columns. Clear the cache after this change.

What did the module developer said? My module works as expected without any modifications.

Click the last option and you wont see those for a month. I would not call them 'nag boxes' more like 'an open source project that probably makes you a decent amount of money needs your support' boxes. Do you like the facelift of BO that came with this change?

The values on the installation I was testing my code were not ordered...

Just a quick question - if you add your attributes in random order in BO so they look like this in Product->Attributes: You see them in FO ordered, right? EDIT: just tested a brand new install - yes, they are ordering in FO.

Thanks. I'll have to dig and find what have I done to mess this up.

Thanks for your reply! It does not sort them. They are displayed in the order I have added them to the product: I was under the impression that the drop-down is also sorted but no, when I add them assorted in BO, they appear assorted in FO.

Something that I think is working, of course not perfect as some things are done in js and not at backend but... Warehouse's product.tpl {elseif ($group.group_type == 'radio')} <div id="product-options"> {foreach from=$group.attributes key=id_attribute item=group_attribute} <input type="radio" id="attribute_{$id_attribute}" class="attribute_radio" name="{$groupName|escape:'html':'UTF-8'}" value="{$id_attribute}" {if ($group.default == $id_attribute)} checked="checked"{/if} hidden /> <label for="attribute_{$id_attribute}" class="btn {if $group.default == $id_attribute}active{/if}"> <span class="label-text">{$group_attribute|escape:'html':'UTF-8'}</span> </label> {/foreach} </div> {/if} css: /* Warehouse buttons css START */ /* Ensure buttons behave like inline blocks and center content */ #product-options .btn { display: inline-block; padding-left: 10px !important; padding-right: 10px !important; text-align: center; border: 1px solid #ccc; border-color: #ccc; background-color: white; color: #333; font-weight: normal; margin: 3px; min-width: 65px; white-space: nowrap; transition: background-color 0.3s ease; outline: none; box-shadow: none !important; } /* Style for the selected state (checked radio button) */ #product-options .btn.active { background-color: #55c65e; color: white; } /* Hover effect for inactive buttons */ #product-options .btn:hover { background-color: #d3d3d3; } /* Style the radio button (which is hidden) */ #product-options input[type="radio"] { position: absolute; opacity: 0; } /* Ensure uniform text size */ #product-options .btn .label-text { display: inline-block; width: 100%; text-align: center; } /* Warehouse buttons css END */ js: $(document).ready(function () { // Handling click events for selecting attributes $('#product-options .btn').on('click', function () { $(this).siblings('.btn').removeClass('active'); $(this).addClass('active'); $(this).prev('input[type="radio"]').prop('checked', true).trigger('change'); // Trigger PrestaShop's findCombination to update the combination details findCombination(); }); }); I would like to move the sorting to BO but for now it is what it is. EDIT: Corrected code as there was no need to reorder using js.

I asked if you have checked for core changes against 1.1 in core updater, i don't see if you did try to check that. Don't update, just check for changes.

I've been playing around with this idea for 2 days. Up until now I've always used dropdowns for my size selections but I would like to make them buttons. Of course thirty bees does not offer such thing currently. I tried editing the radio button case in product.tpl to display bootstrap buttons and hide the circle. Some js, some css and it works for Niara: Product.tpl changes: {elseif ($group.group_type == 'radio')} <div id="product-options" class="btn-group" data-toggle="buttons"> {foreach from=$group.attributes key=id_attribute item=group_attribute} <label class="btn btn-outline-primary {if ($group.default == $id_attribute)} active{/if}" for="group_{$id_attribute}"> <input type="radio" id="group_{$id_attribute}" class="d-none" name="{$groupName|escape:'html':'UTF-8'}" value="{$id_attribute}" {if ($group.default == $id_attribute)} checked="checked"{/if} autocomplete="off"> {$group_attribute|escape:'html':'UTF-8'} </label> {/foreach} </div> {/if} Additional css in my example to make them 'table-like' (when I have mutliple sizes): /* Ensure buttons behave like inline blocks and center content */ #product-options .btn { display: inline-block; /* Inline block to align buttons horizontally */ padding-left: 10px !important; padding-right: 10px !important;/* Adjust padding as needed */ text-align: center; /* Center text horizontally */ border: 1px solid #ccc; /* Border style */ background-color: white; /* Background color */ color: #333; /* Text color */ border-radius: 3px; /* Rounded corners */ margin: 3px; /* Space between buttons */ min-width: 65px; /* Ensure minimum button width */ white-space: nowrap; /* Prevent text wrapping */ transition: background-color 0.3s ease; /* Smooth background transitions */ outline: none; /* Remove focus outline */ box-shadow: none !important; /* Remove any shadow */ } /* Style for the selected state (checked radio button) */ #product-options .btn.active { background-color: #43b775; /* Green background for active buttons */ color: white; /* White text for active buttons */ border-color: #ccc; /* Keep the border color unchanged */ box-shadow: none !important; /* Remove any box-shadow on active buttons */ } /* Hover effect for inactive buttons */ #product-options .btn:hover { background-color: #d3d3d3; /* Light grey background on hover */ color: #333; /* Keep the original text color on hover */ border-color: #ccc; /* Keep the same border color as unselected buttons */ box-shadow: none !important; /* Remove any box-shadow on hover */ } /* Remove the black frame (focus outline) */ #product-options .btn:focus, #product-options .btn:active { outline: none; /* Remove the black focus/active border */ box-shadow: none !important; /* Remove any shadow effect */ } /* Style the radio button (which is hidden) */ #product-options input[type="radio"] { position: absolute; opacity: 0; } /* Ensure uniform text size */ #product-options .btn .label-text { font-weight: bold; /* Bold text */ display: inline-block; width: 100%; text-align: center; } Additinal js to assign the selected button to the radio buttons and sort the buttons alphabetically (as they appear in the order they are created in BO, unlike with dropdown where it sorts them): document.addEventListener('DOMContentLoaded', function() { const productOptionsContainer = document.querySelector('#product-options'); if (productOptionsContainer) { const buttons = productOptionsContainer.querySelectorAll('.btn'); buttons.forEach(function(button) { button.addEventListener('click', function() { buttons.forEach(function(btn) { btn.classList.remove('active'); }); button.classList.add('active'); const radioInput = button.querySelector('input[type="radio"]'); if (radioInput) { radioInput.checked = true; // Manually trigger the combination update in Thirty Bees if (typeof findCombination === "function") { findCombination(); } } }); }); } }); document.addEventListener('DOMContentLoaded', function() { const productOptionsContainer = document.querySelector('#product-options'); if (productOptionsContainer) { const buttons = Array.from(productOptionsContainer.querySelectorAll('.btn')); // Get all buttons // Extract the text values and sort them numerically or alphabetically buttons.sort((a, b) => { let valueA = a.textContent.trim(); let valueB = b.textContent.trim(); // Convert to numbers if possible, else compare as strings if (!isNaN(valueA) && !isNaN(valueB)) { return parseFloat(valueA) - parseFloat(valueB); } else { return valueA.localeCompare(valueB); } }); // Clear the container and re-append sorted buttons productOptionsContainer.innerHTML = ''; buttons.forEach(button => productOptionsContainer.appendChild(button)); } }); The issue is that this change does not work with Warehouse theme, I'm unable to make the button change the active combination, also the sorting does not work. My questions are: 1. Which functions were changed for detecting the combinations in this section? Currently Warehouse's implementation only adds to the cart the default combination so the js I have here does not work. 2. Can we move the sorting in the core for radio buttons? Currently it's done with a js during the output. 3. Is somebody else interested in such development and migration of the community themes? Are there people that use radio buttons in their pages in 2024? If we implement something similar for FO, the BO should still refer to them as 'radio buttons' as this is interwoven in many many parts of the system. 4. Can this be pulled into a module that replaces this part of the theme so this module could be theme-agnostic? Something similar to https://addons.prestashop.com/it/combinazioni-personalizzazione/49820-product-combination-images-swatch-attributes.html but for the buttons. 5. Shopify has a nice functionality - Swatch King - if we can implement something similar it will be nice - https://apps.shopify.com/variant-swatch-king The PS module and this also implement color swatches for combinations. The color swatches per combination is also a nice feature to have.

The first module looks very promising. I see it is a Romanian developer. Do you know his/her name or company?