Leaderboard

Found it! In the past I had first used the Eicaptcha module and then I had switched to the Thirty Bees module and disabled Eicaptcha. However, somehow the Eicaptcha override was still present. Now that it is removed things work again.

The approach described by @DRMasterChief will not work on newer versions of thirty bees, intentionally. You can check if your tb_employee table contains column signature - if the column exists, you can't change the email/password in the table manually. You also need to change the value of column signature, but for that you need to know a secret that's not available to mysl. This mechanism exists to prevent attackers to elevate sql injections into complete access. If your store contained SQL-injection vulnerability (often caused by older third party modules), attacker could use it to change admin password, and then log in (basically the same mechanism described above). With the requirement to change signature as well, this no longer works. You can use force-login php script to log into your admin, see this post: You will have to: upload force-login.php file into your admin123xyz directory (every installation have different admin folder name) open url https://your.store/admin123xyz/force-login.php this will logs you in as an admin change password delete force-login.php script

Not over yet 😉

Yes, now drop the spam 🙂

Hello everybody, TB is not dead .. it just smells funny, sorry that I couldn't resist. 😄 “Jazz isn't dead. It just smells funny.” ― Frank Zappa but it's up to us to make something different.. I have not much hope from the TEAM.. but from the community maybe things can go further. I still use and work with TB often, but now it's complicated to promote it to anybody because the lack of presence from the official communication. I still make many modules for some users, it's really fun to make modern modules with super cool looks on something that looks "dated", front and back end. Performances on TB are still the best ^^ php 8 does the job, no need for fancy framework. Best Regards to all of you guys !

Das Modul hat Codex gebaut. Hier die Antwort:

This is the idea of this community.

I'm not entirely sure, but you might be able to change the email address in the database to one that definitely works, and then use the "forgot password" function on the back-office login page. Come on, we're going to end up with a complete guide here 🙂

That module is not php8 compatible. You should probably stop using it, or ask author for a new version, or hire somebody to fix it for you. In this particular case, the fix is very simple. Replace the if ($this->_cookie_path{0} != '/') $this->_cookie_path = '/'.$this->_cookie_path; with if ($this->_cookie_path[0] != '/') $this->_cookie_path = '/'.$this->_cookie_path; But who knows how many other issues that module contains.

@Madhosh i think you should urgently install the module in BO: Mail via phpmailer v.1.1.1 (this is the new module for E-mail transport and you need this)

You need to update your theme and remove dependency on polyfill.io This is how we did it in niara theme: https://github.com/thirtybees/niara/commit/3ab40e7ae52e0c495a2b67f09131996fb6ed65ea For your theme, it will be mostly the same - edit file header.tpl, find line with polyfill.io, and delete it.

I do this manually. The old file is copied and renamed XXXXV2026.0.1BeforFixErrorLog25May2026.php and the new file is named XXXX.php. I maintain a file header in each file that has a running list of changes with the change dates. I know this is cumbersome but I've used it for years and it works for me. When modifying files I use the Open Source tool Winmerge.

I found the cause of the product page crashing when there are a large number of attribute combinations and the “blocklayered” module is installed. In the Product class, within the two methods getAttributesInformationsByProduct() and getAttributesParams(), SQL queries have been added with the following condition: if (Module::isInstalled(‘blocklayered’) && Module::isEnabled(‘blocklayered’)) { And these are the ones generating such a huge number of SQL queries on the product page. Interestingly, after removing these SQL queries from the Product class, the navigation filter block on category pages works correctly 🙂 I would report this on GitHub, but there’s no point, because no one has been handling these issues for almost a year now.

"Transparency is one of the key foundations of every successful open source project. Without knowing the direction and priorities, it's hard to build trust and create a united ecosystem front." This statement was made on LinkedIn by the current owner of Prestashop/Sylius. I my opinion the lack of transparency, direction and priorities is exactly the problem with TB. Why spread the word of subscribe for a paid membership if one doesn't know what they support.

Hello thirtybees community, ours are: - https://www.duvalo.sk - https://www.hudobniny.net We rushed into production, so still tweaking some stuff.

Let's blame it on CORS then 🙂 If you are unable to update to 1.4, you can applie these lines (warning PHP7 syntax used - I know you are working on some PHP5.6 servers, for some reason) https://github.com/thirtybees/thirtybees/blob/81dd5d911a086164146bafc3bf650694786d9a56/controllers/front/TriggerController.php#L38-L44