the.rampage.rado

If a merchant is trying to be serious about their shop I don't see any other alternative rather to hire the best person they can find to work on their shop. In our case it's very easy as we know him. 🙂

As somebody said - most of those 'issues' are fixed very quickly as they are trivial syntax change. Of course for me this is not the case as I'm a code noob. If you also don't feel secure you can hire a php developer and they will help you out. I even know a very very good one - datakick. As a bonus - you will work with the project's mantainer, currently there is nobody more experienced with thirty bees' code and inner workings. And of course by hiring a developer fixing your shop they can find some bug and help develop the platform for everybody else! 😉

7.4 is not supported version of php (by php developers, not by thirty bees - it supports it!) anymore but you should use it as a stepping stone to update your modules, fix any bugs that are present on 7.4 with your modules and theme and then follow the steps from above. If your site is not working on php8 it wont magically start working on 8.3 as there even more things that change between those two versions. You (or your developer) should work to iron out the issues with modules/external theme. Thirty bees does not have control and is not to blame if they don't work on 8 or later. My sites are also on 7.4 but I plan on migrating slowly to later versions in 2025 but for this to be done a developer should make my old theme work first. And this is nothing to do with thirty bees - natively it works on 8.2 (or even 8.3).

So you have some modules that don't play nicely with php8 too. Install thirty bees' Collect logs module and look what it gives you as info on 7.4, fix some of those and try again. The update method is as follows: 1. You are on 7.4 and your site runs without notices, errors, warnings, exceptions, etc. 2. You update using Core updater by pointing it to target version. 3. Your site is now broken because some dependecies don't work on php 8 4. Your switch your server to php8 5. Your site is working again because at step 1 you fixed all stuff that thirty bees has no control over (external theme and modules). If you want to proceed updating to php8.1: 1. You are on php8 and your site runs without notices, errors, warnings, exceptions, etc. - THERE WILL BE NEW ISSUES in Collect log module 100%. .... proceed according to the list above. If you want to downgrade and not use a backup and your BO works after the update of php version (not your case obviously): 1. You are on php 8.x. and your site works 2. In Core updater you put target version 7.4. 3. Update dependencies with Core updater 4. Your site is broken. 5. Downgrade php on your server to 7.4 6. Your site works if it was working before on php 8.x

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)