the.rampage.rado

The target setting in Core updaters points the module to which PHP version of the core files you want to update next, not what version you're currently running on your server at the moment. This is VERY useful you are debugging modules errors moving forward with PHP and you need to roll back to php7.4. You should always set this to 'Server PHP version' if you don't do some changes (updates of the core or testing newer php version). As datakick advised: 1.4 is compatible with php 7.4 1.5 is compatible with php8+ but many modules will not be. It runs on 7.4 also. So first install collectlogs module (or regularly read you error_log manually), roll to php7.4. If you have any issues with your module (errors, warnings, etc - fix them now!). Roll to 1.4 if you're using an older version - fix errors and warnings on php7.4. Make db changes and fixes in Core module. Roll to 1.5, remove tbupdater module (NOT Core updater module, they are different), update all native modules (if update is available), choose, install and configure email transport module (1.5 will not send emails out if this is not done, 3 minutes), install minification module (this was in the core, but was moved to a module for compatibility reasons, check if your code minification settings are proper in the old place where they were before, 1 minute). Make db changes and fixes in Core updater module. Look for new errors with your modules in Collectlogs module (core and native modules should work perfectly on php7.4). Then update to php8.0 - again look for errors, if any - fix them. And proceed to the latest php8 version you wish to use in the same manner. DO NOT UPDATE directly from 7.3 to 8.2 - your shop will crash 99% (99% because of installed 3rd party modules). At each step - make a USEFULL backup of your DB and file system.

This is my config. v.1.4.1 (I used 1.4 for quite a long time and also had no issues (I could find) with my setup). Could you share yours? I use Warehouse and I have no separate mobile view.

Me, it's running much faster. Adding the cache module it's even faster. Can send you a link to test.

IMHO - price matching is the most toxic way of making business. If you can't offer constant lower price try to attract customers in a different way. The module - 10/10 - statistics that every merchant needs but if you don't use external system you were stuck up until now. A feature proposal I have is if we can add global catalogue statistics in the module: 1. Global average and median values for the catalogue. 2. A list of products without available statistics, so in general without added wholesale price - this will make the adoption for the module lot quicker for sites that did not enter this valuable metric per product up until now. (as my old shop, where all profit calculations were done outside the shop).

You probably downloaded this moded version. https://store.thirtybees.com/shop-modules/statistics/dash-activity-v6

@SLiCK_303

That's very strange. Do you have B2B option turned on?

Install Collect PHP Logs and see what is causing the problems.

My post is not directed to you by any means.

Should we delete it? 😄

As it was mentioned in the first post email transport was moved to a module. You can choose one of 2 methods as of now and configure them as before. It's like 5 minute job, including testing. This was done for more flexibility as the lib that was shipping with TB up to 1.5 was outdated. Now everybody can write external email transport using different methods. (you need just one installed module at once but you might install few and simply change them in the dropdown you showed)

Do you mean VAT per sale or the monthly VAT?

How was the product list in PS? I guess exactly the same if I remember correctly?

If they don't cause your site to reach it's limits and don't make a mess in your BO (like making carts, spamming, etc) I would suggest to simply clear the connections table regularly. This will also speed up your site if the table is very big.

Your hosting is probably doing some changes.

Don't take it as a subscription or paid service. Take it as a gift from the maintainers to the community of supporters that help fund (at least for now) VERY SMALL part of the expenses behind this project. If you don't want to subscribe you can still use every other part of this software for free and I have not seen any announcements regarding changes in this area.

This module does not support php8. If you already rolled back to your backup set your php version to 7.4, update TB core to 7.4, install Collectlogs module and observe the warnings that this module will rise. Fix the all the issues that are generating during 7.4 and then BACKUP again and try an update to php8.

Should we make any changes to our DB?

You have to install one of the two included email transport modules (find them in the modules catalog) and configure them. Then you can test in Advanced Parameters - Email if the system sends out emails, right at the bottom of the page. This was moved out of core in 1.5 as the library that was used was outdated.

Can you post some link as I'm unable to find it?

Working for me also. It was most probably some local caching issue with your browser. Please, note - don't use the full page cache in Performance as it could bring such issues. You can set up Redis server or apcu caching and use the other 2 types of caches.

You can use Block Contact Infos

Custom JS Code in Preferences -> Custom Code

1. Does it keep track of pack sales also? If I sell 10x of certain product but the product pack has no set supplier as it relies on products with set suppliers does it calculate those sales? If it does not track them what happens if the products in the pack come from different suppliers? 2. Could we have in future supplier MOQ and Minimal stock levels settings? Lets say we have a discount for full box of certain item and we wish to order only per said quantity but by piece for other items from that supplier. Minimal stock levels should be set by the merchant (per product/reference) and if the quantity on hand drops lower than the said number, the difference should be suggested always even if the calculation does not offer it. 3. Can you describe this setting? Why the default was only Canceled? And should we keep it that way? 4. I assume that all settings for costs in the module Settings take into account the default currency and not the supplier default currencies? 5. When adding a supplier and then supplier references could we automatically pick the currency based on the selected supplier default currency? Currently the drop down shows the default shop currency and we have to fix this every time if both are different. 6. What do Safe stock and Reorder point mean?

If I purchase the paid version and install it will I keep my reviews from the free version? I would like to start sending out review emails. And one quick bug report - page revws - AllReviews displays reviews even for disabled products.