tomek

I got the same error after I updated today. The update tells me I have the latest version, but if switch to database tab, I get the same error. BO seems to work, but the Front office is 500 error. When I open TB logs I have just some info about admin login. Ok, I just found the fix - I hope so. I switched the PHP version from 7.4 to 8.1 on server side and in the CoreUpdater settings. Then fixed all the errors in the Database tab. Then tried to update the store which gave me an error about broken installation, but after another update of the store it seems to work.

I created a new shop and I DID NOT login into the BO, but first changed the values. I got no clue what's the difference but then I was able to log into the new shop.

Sorry, I am a bit lost ;) When I create a new shop, the COOKIE_KEY and COOKIE_IV are different from the old one. When I change it to the old COOKIE_*, then I cannot login. I cannot change the COOKIE_* things before running the shop installation (but after copying the TB data to my ftp). Doing it afetr installation results in failure of login into a new shop.

datakick, when I copy those to a new shop I cannot even login to it - it says something like that: The user does not exists or password is invalid

Ok, now I think I know what is going on - I restored an old backup and there is something wrong with the old database - there is the same problem. I don't know why as my clients could log in without a problem in the old shop

Does it matter if I change the database prefix (the old one was ps_ and the new one is tb_ ) ?

What do you mean by that? I have to admit I did not do such thing as I couldn't see anything like that in the copy_shopdata_config.php file

Ok, I set up a new shop. After every change I logged on an old account to check whether everything is ok. When I copied all the clients with copy_shopdata (the latest one) I still have the same problem with Authentication failed. Changing password for any account gives nothing - still the same problem and none of the older shop clients can log in into my shop. I checked consistency of the tables with core updater and it said everything is ok.

Thanks, datakick. But when can we expect the module to work on PHP 8?

Really sad as I cannot come back to 7.4 due to: Fatal error: Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 8.1.0". You are running 7.4.20. in (blahblah)/public_html/vendor/composer/platform_check.php on line 24

I installed the module and filled all the required data in, but cannot save it, because I get a "Server Error" message. I looked into the logs and I got the following: Fatal Error Cannot use "parent" when current class scope has no parent in file (blahblahblah)/public_html/modules/nocaptcharecaptcha/nocaptcharecaptcha.php(2741) : eval()'d code at line 26 Stack trace 2. modules/nocaptcharecaptcha/nocaptcharecaptcha.php(2741) : eval()'d code:26 () PHP version: unknown. Code revision: unknown build for PHP unknown TB 1.4, PHP 8.1

Can I change the following parameter: $numtables = 9999; to a bigger one? I am not sure what is the number of tables and if it makes any sense to increase the number..

I upgraded the store to 1.5 (bleeding edge) and despite having the homslider.tpl file replaced the problem appeared again. Edit: I found that hte images were spoiled - changing the images solved the problem.

I get the following: Error Class "BeesBlogModule\BeesBlogPost" not found in file (beeeep)/public_html/modules/beesblogrecentposts/beesblogrecentposts.php at line 123 Source file: (beeeep)/public_html/modules/beesblogrecentposts/beesblogrecentposts.php : 104: return $this->hookDisplayLeftColumn(); 105: } 106: 107: /** 108: * Display in home page 109: * 110: * @return string 111: * 112: * @throws PrestaShopException 113: * @throws SmartyException 114: * @since 1.0.3 115: */ 116: public function hookDisplayHome() 117: { 118: if (!Module::isEnabled('beesblog')) { 119: return ''; 120: } 121: 122: $this->context->smarty->assign([ 123: 'beesblogRecentPostsPosts' => BeesBlogPost::getPosts($this->context->language->id, 0, 4), 124: 'beesblogRecentPostsBlogUrl' => BeesBlog::getBeesBlogLink(), 125: ]); 126: 127: return $this->display(__FILE__, 'views/templates/hooks/home.tpl'); 128: } 129: 130: /** 131: * Display in product page 132: * 133: * @return string Stack trace: 1. classes/Hook.php:744 source BeesBlogRecentPosts->hookDisplayHome(arguments) 2. classes/Hook.php:458 source HookCore::coreCallHook(arguments) 3. classes/Hook.php:282 source HookCore::execWithoutCache(arguments) 4. controllers/front/IndexController.php:54 source HookCore::exec(arguments) 5. classes/controller/Controller.php:202 source IndexControllerCore->initContent() 6. classes/controller/FrontController.php:243 source ControllerCore->run() 7. classes/Dispatcher.php:851 source FrontControllerCore->run() 8. ./index.php:33 source DispatcherCore->dispatch() And there is a message about: PHP version: unknown. Code revision: unknown build for PHP unknown The PHP ver. is 8.1 I also forgot to mention that when a client succeded to create a new account and tried to place an order, he got a message that the items he ordered are out of stock, while there was over 15 items in stock left.

I have done it and the 500 Error seems to be a Bees Blog module problem. I don't know whether both problems (client's authentication error and 500 error) are related, but I made a backup and will try to reproduce the error.

I don't know, but I verified the database with updater and it did not find anything. I updated the store to bleeding edge, updated all the modules. Then run the database check again and it found something about "word search" or something. Unfortunately I cannot reproduce the error now as I deleted the account that I had a problem and created a new one but I am stuck at the following:

I managed to find some details. When activated Debugging mode I found that the module Bees Blog Recent posts had some problems: Class "BeesBlogModule\BeesBlogPost" not found in modules/beesblogrecentposts/beesblogrecentposts.php at line 130 When I deactivated the module, the "500 Server Error" paged disapeared but the shop is missing the menus - e.g. there is no main menu, no other links, footer gone - just the Home slider left. Deactivating Home slider module does not help anyway.

Yes, all the keys were copied.

When a client logs into my shop, can see "My account" page, can change all personal data, but cannot go to the Home Page because of "500 Server Error". When the web browser cache is cleared then pages of my shop load normally. When logging in again, the problem comes back. TB 1.4, PHP 8.1 (the problem exists also with PHP 7.4).

I confirm that changing the PHP version to 7.4 solved the problem with encoding

I copied shop data from TB 1.01 to another shop (kind of customers backup), created a new shop (TB 1.4, PHP 7.4) on my main domain and copied the data back to a new shop and all my customers cannot log in to my new shop. When they try to change their passwords, they got an error message Authentication failed. Even when I change their passwords in BackOffice, they got the same error and cannot log in. Any idea what I might have done wrong? :(

Ok, so I think that the problem is on the server side - maybe the PHP mail() function. I managed to successfully set up the smtp and the emails started to look "normally" ;) So yo think I shall contact my server administrator?

But I edited them in the TB Background Office Translation menu :| I've tried to send a test message from a test-shop on my secondary domain, where I had not changed/edited any notification and still the same problem.

I have a TB 1.4 with use of PHP mail() function and my customers get messages with (polish) characters completely messud up. Is there any option in TB to set encoding or is it purely PHP server related? Example for a test message: SHOULD BE: "To wiadomość testowa" IS: "To wiadomo=C5=9B=C4=87 testowa" Just imagine how messed up might be a message for/from a client when it's full of polish characters ;)

Thank you, datakick! I've deleted the file from /themes/niara/modules/homeslider and it started to work again. But I downloaded your version of homeslider.tpl and uploaded to the destination - just in case ;)