the.rampage.rado

Link to Core Updater 1.6.6 - https://github.com/thirtybees/coreupdater/releases/download/1.6.6/coreupdater-v1.6.6.zip What do you mean by not working? Give us more information. thirtybees version at the moment, error that the module gives, etc. With only 'not working' it's very hard to guess what's going on. If you are on thirtybees 1.5 or later tbupdater is not needed as its functionality is moved in the core of thirtybees and the module should be uninstalled and deleted from your server. For versions before 1.5 it should be kept as it's used to update the other modules.

You moved servers - look into that. Configuration of the new server, especially https settings on it as it says that the connection is not secure. Also those messages in the console are coming from Chrome, not your site. They will ban all third-party cookies soon (https://developers.google.com/privacy-sandbox/3pcd) and your checkout does not care for tracking, etc cookies at this point.

Did you consider that overall customers spend far less in January compared to December? For me the sales and conversions are probably less than 30% of December numbers.

Regarding the listespeed module check here: https://github.com/litespeedtech/lscache_prestashop/issues/57 With those fixes those deprecations are no more but there are 2 more errors under php8 for me.

Uninstall it. It's no longer needed if you're on thirtybees 1.5 or later. tbupdater, not core updater, they are 2 completely different modules, doing different things. Core updater should be kept installed.

You should see your Core updater module in your modules list (under All or Administration tabs). Current version is 1.6.6. Those notices should not affect your shop's functionality in any way but they will populate in your error_log and it will grow slowly over time. If you can I would advise to roll back to php 8.0 or 8.1 and they should stop showing. In future they will be fixed for your current version. If you can't roll back your php version I would advise to check if your order process is affected, or you see any issues and if no such concerns are present I would proceed with them. Yes, they are little annoying but they should not be a showstoppers. I'll investigate and file a github issue if I manage to preproduce them. If possible could you share what you see here (Advanced->Configuration information), please hide the confidantial information on the left of the page!!! :

All of those are notices. As such those don't pose a DIRECT issue to your site - it should be working and accepting orders normally. If you need help you have to be little more respectful that this is a free community and nobody here is paid to support such issues. We can assist but in our free time and in our own capabilities. Now I'll close this thread and let continue in the other.

You will find some interesting things inside (if you have enough ram and notepad++) 😄 Download it, delete it from the server and wait couple of days, then open the new error_log and see what is pumping lines. Also a useful module to see those (and many more) in backoffice is "Collect PHP Logs" module. You can find it your list, install and keep it installed. I bet you switched php versions recently (or your hosting did and you don't know about it).

It turned out that the appropriate categories permissions were not set by the migration module so the visitor was forbidden from viewing certain products.

Through the contact form or direct spam in your email?

Theme editor->Top bar ->

Send me a link so I can check something? PM

I'm no beekeeper per se but it appears that the ones on the top are not very keen to get in the hive and call themselves part of the thirtybees crew. 😄 😄 😄

The community is sill very small. Custom work is hard but you could succeed if you try to search for experienced PS1.6 dev. Not many things are changed in themes since the beginning.

This is not problem of the system but your browser's cache. Probably you have some caches in thirtybees that are misconfigured and your browser is following those rules and keeping things for too long.

Did you try the fix that was given by datakick and did it solve your issue?

@horia, the issue is fixed in edge channel by datakick. You can update to edge or manually revert the changes in controllers/front/AuthController.php https://github.com/thirtybees/thirtybees/commit/f7abd964a67446a04bb0416d2619db84cd75c80d

@bhtoys just letting you know that datakick just fixed the bug in the edge channel. You can update to edge (if you run thirtybees 1.5 or 1.5.1 the process should be very quick). Or you can manually apply the changes in classes/SpecificPriceRule.php https://github.com/thirtybees/thirtybees/commit/7093aee9d1f849a43b47cb2cb15b220f89a2e934 For me this exception is not showing in my test setup running latest edge.

Could you PM me your domain?

Just checked on stock demo site of mine and it appears to work as expected. Is this some custom theme? And are there any notices in browser's developer console when you click? But I get a notice when setting up those pages in BO. Will investigate further now. EDIT: Issue here

Could you give a screenshot of the issue, I'm stull lost on exactly where is this text. Are you referring to the Advanced EU Compliance module and the texts it is adding?

You should keep it installed and monitor from time to time. You will find interesting information that otherwise gets missed.

If you switch between php versions in your cpanel you should make sure that php loads all needed extensions for thirtybees. Most probably you have 500 on php7.3 because you have never used it before and your pdo_mysql is not turned on by default. Either this or some other requirement is not on. I rolled thirtybees on 7.3 for ages before moving to 7.4 and now I'm debugging final notices and errors to finally move to php8 and later. There are numerous posts in the forum regarding updating to thirtybees 1.5 (and then 1.5.1 or edge), the benefits of doing so and of course the right approach in order to achieve this without problems. For example: Just a hint: when you have a running shop it's strongly advised to use your core updater module that will take care of your vendor folder (and all other files that must be synced for your special thirtybees/php combination). Do not manually load folders from any distribution as they will more likely be overwritten by core updater once you run it's updates. It will also migrate and fix your db, etc. So no need for manual file transfers (other than manually backing up which is strongly advised of course! 😉 )

In order to debug the most of your shop you will always need to have installed this module: It collects and displays in a userfriendly manner nearly all errors (notices and warnings also, depending of it's configuration) and you will have a handy tool to debug and fix most of your issues. If it shows nothing next time when you encounter this issue it might be helpful to turn (temporarily!!!) the debug mode: Advanced->Performance and turn ON 'Debug Mode' and you can have 'Display deprecation warnings' always ON. Then go to your problematic page and it should show vital error information. (which should also be populated in your error_log in your root folder (accessible by ftp)). Most probably you have some module that hooks in there and is not compatible with your current php version.

- "no sense from the use case point of view" - tons of bug and SECURITY fixes?! Not interested? New features and new php versions support?! Not interested? OK... - "newer shops use more energy, weight usually more' - code was optimized, refactored and improved. Not interested? OK... - "and you won't find modules for it." - no backwards compatibility changes in newest release, meaning ALL current modules will work with core (of course if they are compatible with the php version you want to rock!!!). Not interested? OK... @SLiCK_303 I believe this issue is caused by the new analytics implementation. I believe UA is slowly turning off all their apis and we will have to move to GA4. For me it also does not display the totals but the sources underneath are shown.