the.rampage.rado

Remove the last comma on line 5579 in classes/Product.php then continue with the DB update aswell: $depthImpact = null, should become: $depthImpact = null

In order to update php versions you have to follow "strict" procedure which is described here: This applies for vanilla thirty bees and Niara or Community theme. If you use another 3rd party theme (ones inherited from PS) they WILL not work on php8 straight out the box. 99.99% theme has issue with block cart override in the theme itself which leads to Error 500. You have to run your shop on 7.4, fix all notices for such issues then update to 8.0. Again fix all notices and warnings and then update to 8.1, etc. The update procedure is not vicious its strict and it's made that way because thirty bees dependencies sometimes work on 7.4 but not on 8+ and vice versa.

Thank you Daresh! I would like to have this information as a tab.

Did you update your DB too after the files were updated?

Do you have backoffice access? The code you have given is not very descriptive. Put the information from Collect logs module where you can see the error.

Thank you for supporting thirty bees community Daresh! In your demo site the information is visible in two places - once at the tabs and once under all the product page information. Is this configurable if we want to display this info only in a tab?

There is no such feature. But you can make a custom query in the SQL manager in BO and pull this list: (adjust the table prefix to your needs) In general - if you want certain list to be created and it's still not a part of thirty bees you can do so with ChatGPT and save it in the SQL manager to use from BO. SELECT email, COUNT(id_customer) AS customer_count, GROUP_CONCAT(id_customer ORDER BY id_customer) AS customer_ids FROM ps_customer GROUP BY email HAVING customer_count > 1;

Thanks! Tomorrow I can make PRs for the modules that have the same 'issue'.

If you are in the guest profile you should merge into the customer profile. Just check which is which.

The error message 'Your email address is blocked from sending messages through contact form. Please send email to xxx instead.' is currently not translatable. I'll split this offtopic later.

Of course... 😄 The rule is working as expected!

I don't want to register such account. 😄 Thank you!

Thank you! Will those filters work or I did not set them correctly?

I don't see the second module that was mentioned with the 1.6 release, I only have Contact Form IP address blocker.

@DRMasterChief if you are on 1.6 the first two rows are already implemented in the core (one as buttons in the Carts section and one as automated maintenance task), we can make something similar for the other two rows.

In general you use CMS similarly as a blog - why don't you simply use thirty bees blog and share those posts?

Do you have the error?

So now the images are visible in BO?

Thanks, will use lowercase in the next version!

New feature - check voucher page in FO and one question... Why in 2 separate installations the module works with a controller named VoucherCheck.php and on another install it does not work and looks for vouchercheck.php (all updated to edge)?

Try the following: 1. Regenerate your htaccess file. 2. Clear status and regenerate your thumbnails. 3. Check if the source image is in the appropriate folder. (it might be corrupted or missing altogether)

The module is not updated up until now as this bug was not detected. This module is not very popular.

Preferences -> Themes and upload the appropriate format for the appropriate place.

By any chance your source images are smaller than 870x217 because now you have this image with large transparent background?

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.