datakick

This is a bug in 1.4, already fixed in bleeding edge: https://github.com/thirtybees/thirtybees/commit/6a4f9d59a6af67b79546aca8d8af8aebf589ae81

Indeed, looks like a bug

I can implement this for the next version.

The module is not compatible with stripe api version 2022-08-01 or newer.

Works fine for me. Do you have any error message in your error logs?

First, you need to know exactly what hooks you want to trigger. There are a lot of them, actually. For product modification, these can be called (and that's only a subset of them) actionObjectAddBefore actionObjectProductAddBefore actionObjectAddAfter actionObjectProductAddAfter actionObjectUpdateBefore actionObjectProductUpdateBefore actionAdminUpdateAfter actionObjectProductUpdateAfter actionAdminProductControllerAddBefore actionAdminAddBefore actionAdminProductControllerUpdateBefore actionAdminUpdateBefore actionProductUpdate ... Once you know which hook(s) to trigger, you need to find the place in the core that is calling them, and figure out what parameters are send. Each hook sends different parameter. For example, hookObjectProductUpdateAfter https://github.com/thirtybees/thirtybees/blob/82b3102a421ce53347c4a660966048439e4f759b/classes/ObjectModel.php#L857-L858 Expects single parameter 'object' that is instance of Product class. You can trigger it as this one (for product 123): Hook::exec('hookObjectProductUpdateAfter', ['object' => new Product(123)]); Note that this can actually cause you more troubles. Modules can expect that the hooks are triggered in some sequence. For example, I have a module that create create audit logs of all changes. This module expects that first 'hookObjectProductUpdateBefore' is called -- at that point I retrieve data from database. Then when 'hookObjectProductUpdateAfter' is called, I once again retrieve data from db, and compare these two datasets to find out what has changed. If you just trigger hookObjectProductUpdateAfter, my module would be quite confused 🙂 And I'm sure there will be other modules that depends on things like these (sequence, context, controllers, GET / POST parameters, etc). So be aware

/config/settings.inc.php define('_COOKIE_KEY_', '********'); define('_COOKIE_IV_', '********'); Make sure your new server has the same values as the old server. This information was used to salt md5 passwords.

You should first look into source database ps_customer table and compare data with target db. SELECT id_customer, passwd FROM ps_customer ORDER BY id_customer LIMIT 10 Verify few customers. If the data are different, you can keep this conversation here, as it's a bug in the copy tool. If the data are the same, though, then the issue is somewhere else. You either didn't copied the _COOKIE_KEY_ and_COOKIE_IV_ settings from source to target server. Or maybe you used some sort of custom login functionality in your original server in the first place (maybe some auth module, or whatnot)

Of course you can. You just have to first update your thirty bees using coreupdater to PHP 7.4 build. There would be compile/syntax errors if you tried to run code that is using PHP8 syntax on PHP7. It's been discussed on this forum already. Try search.

This module is not PHP8 ready. https://github.com/thirtybees/nocaptcharecaptcha/issues/12

Update module to new version 2.2.4.

Did you check /themes/<theme>/modules/homeslider/homeslider.tpl override inside your theme, as described in one of the posts above?

Most likely caused by password column size -- it should be 60 chars long. You can use core updater database schema verification to find all database differences, and fix them.

Chex does not impact standard order flow. If module is enabled, it simply replace it. Since this is bug in standard OPC flow, I doubt that it has anything to do with the module.

This is how dashboard_zone_one.tpl looks in version module version 1.3.0: https://github.com/thirtybees/dashactivity/blob/master/views/templates/hook/dashboard_zone_one.tpl There is no reference to $allow_push. Please double check module version. If it's indeed 1.3.0, and the file looks the same as in the link, than it will be caching issue.

Looks like the same problem as @musicmasterencountered here: The problem will be with some module calling Link::getAdminLink with invalid paramter. I have added new check to the code: https://github.com/thirtybees/thirtybees/commit/125bc3039f5e4d6cb490288e073a751c50e29f9a If the method Link::getAdminLink is called with invalid parameter, system will raise warning instead of error. You can update to bleeding edge, the fix is already there. Note that you still have to fix the module, as in the future this will throw an error again.

can you show the stacktrace as well?

This does not look like an issue with chex. Once you enable chex, the order page is skipped, and user is redirected to module controller. This error comes from standard order controller.

Update dashactivity module to the latest version 1.3.0

That is not a fix, that's just code location that needs to be fixed.

your /img/ directory is probably not writeable, so module failed to create subdirectory homeslider inside it. You might need to create this subdirectory manually (via ftp, for example), and set correct permission for it

Did you update the module manually, or automatically? If automatically, all your existing images were wiped out. You will have to re-upload them, and they should be stored inside /img/homeslider directory (if it's writeable)

Known issue: https://github.com/thirtybees/thirtybees/issues/1292

I googled a little bit and it looks like the php8 version is more strict regarding email standards. Something about email sections being delimited by \r\n characters, but switftmailer library we are using for sending emails use \n as a delimiter. Or something like that. Unfortunately, we can't update switftmailer library, as it is no longer maintained. We have to migrate to new email sending library soon (swiftmailer is not PHP8.2 ready anyway), so this problem will be fixed together with it. Meanwhile you will have to use smtp transport if you are on PHP8

To determine locally modified files, core updater asks API sever for a list of files for some revision and PHP version. Unfortunately, previous versions of core updater did not remember PHP version the code base was build for, and always asked for PHP version currently in use. When you switched the PHP version to 8.1, core updater asked api server to send him list of files for revision 05affeeeb438431cc5582d671785b9ce3b9ca0a3 and php version 8.1. Unfortunately, this combination does not exist, because this revision was only build for php7.4 and lower (that version does not officially supports PHP8). There are multiple fixes. 1) downgrade your php version to 7.4 (or whatever you were using before), and then update to bleeding edge. Then you can upgrade php version to 8.1 and update again. 2) alternatively, you can edit your settings.inc.php file, and add entry define('_TB_BUILD_PHP_', '7.4'); This will tell core updater that he should ask for combination 05affeeeb438431cc5582d671785b9ce3b9ca0a3 and php 7.4 Note that new versions of core updater saves information about PHP version the code base was designed for during update, so this problem will not occur in the future. Once you update, this _TB_BUILD_PHP_ constant in settings.inc.php will be created/updated by core updater automatically.