the.rampage.rado

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.

Last thing I can think of is clicking on the double arrows. Does it clear this page's cache and does it show correct information afterwards. It's very hard to replicate such edge cases as this is probably some server related issue as many users are already on 1.5 and post 1.5 and they don't report such issues as of now.

Regarding the initial post, it's obiously some bug. I did replicate it just now. Tracking here. Regarding the second one, I'm not sure what you mean. Could you post little bit more details, like if any of the rules were previously saved, or whatever?

Not able to replicate the operators not supported issue. What exactly did you do so we can replicate it? Post screenshots of your discount, if possible so I can try and replicate. Also, could you post the second part of the error log as it's very helpful too? Thanks! The email 'issue' is not an issue or a bug, it's a feature change that enables smoother progression.

Nice widget but nginx is definetly not default configuration on most cpanels. @selwynorren, did you try different browser?

And no bueno? Sometimes this happens and it's cache related issue, either the thirtybees cache is not working correctly or the browser cache is fuzzy...

Did you try clearing your caches?

With this information I managed to reproduce it on my test site just now. Tracked here: https://github.com/thirtybees/thirtybees/issues/1745 EDIT: It is generally good idea to have Standard setting there as it's more user-friendly.

Unfortunately I'm unable to duplicate this issue in any of my setups. 😞 Tried playing with many settings but failed to replicate it. Any specific settings in this demo store?

On 3/20/2023 at 2:24 PM, datakick said: That's strange. Try to manually edit settings.inc.php and change value of _TB_BUILDPHP to 7.4 Then go to core updater and try update. It will probably display something funny (manual modifications warnings, etc), but you can ignore these and perform the update. What happens when you apply this manual fix? As I said the tbmigrator can't update straight to more modern version of thirtybees as those don't work on php5.6 and your PS1.6.1.xx was very unhappy on everything newer than php7 if I remember correctly. The way to update to latest TB is with little patience and core updater will do its job step by step.

First check what version does it say inside. If it's not 7.4 make it be. If it does not work you can try 755, but it should be 644 And as you're inside settings.inc.php check if you have a populated _PHP_ENCRYPTION_KEY_ as it's another nagging bug from past times. (if you have it, don't share it with us 😛 )

Probably you have this error with writing to settings.inc.php

What do you have here: Core updater -> Settings ? It always has to be 'Server PHP version' (if you are not trying to downgrade php or thirtybees.

OK, Could you press F12 in your browser and tell what errors pop there when uploading the picture?

This error might be caused by many factors. Did you make any changes to the core (overrides, etc.)? Is it actually uploading it under this error or not at all?

That's because Core updater is made to guard you against updating TB to version that does not support your current php version. Minimum for 1.5.1 is php7.4 So first update to TB1.4 and php7.3, then switch to php7.4, update to TB1.5.1 and iron out any issues, bugs, warnings, errors with your modules and theme. After that update to php 8.0 - check once again for bugs, if none, update to 8.1 and you're super fast, secure (TB1.5.1 come with many bugfixes and security fixes) and happy.