datakick

What module is causing you trouble? Who is the module author? Did you report this issue, are developers aware of the problem? Are they still actively supporting/developing this module? If you are talking about this problem: then it's not a module issue, but theme one. You are using outdated community-theme version. You should update to new version. Core updater can help you with this, unless you modified the theme yourself. This particular problem was fixed by this commit back in September 2020: https://github.com/thirtybees/community-theme-default/commit/e8aaf3632640d8df85e6ca1074878d4b80d008a0

What module is causing you trouble? Who is the module author? Did you report this issue, are developers aware of the problem? Are they still actively supporting/developing this module?

Go to Core Updater settings page (either click on Configure from Module list, or open core updater and click on Settings in upper right corner), and in distribution channel choose Bleeding Edge.

Yes. Fix is in both bleeding edge, and 1.4.x (bleeding edge for upcoming 1.4.1 bufix release)

Instead of deleting/overwriting existing theme, I would recommend to create new file, for example: /admin/themes/default/css/schemes/admin-theme-dark.css You can then select and use this new theme in Employee settings page.

Yes, it's normal, unfortunately. While thirty bees core is PHP8 compatible, many third party modules are not. New major versions of PHP bring breaking changes, which means that PHP code have to be updated. Users are warned about these breaking changes in advance by PHP deprecation warnings (while you are still running on lower versions of PHP). Unfortunately, not so many people looks inside their server's error log. I recommend this flow: update your store to thirty bees 1.4 still use PHP 7.4 install collectlogs module use your store for few days/weeks continuously watch Advanced Parameters > Error Logs. You should fix every Error/Warning/Deprecation. You can ignore notices, for the time being. once you fixed all issues, and no new warning was found for a few days, you can switch to PHP 8.0 watch error logs for few days, if everything is ok, upgrade to PHP8.1 do NOT update to PHP8.2 yet, as it is not supported by tb 1.4. Support will be added in 1.5

Hi, xml backup file generated by module can be imported using datakick export/import module, as it supports reviews data. Alternatively, you can open this xml data in excel, and transform it to csv format. Or dump tb_revws* database table and import them using phpmysql tool. Note that in all scenarios you will have to make sure your product ids and author ids matches in both systems, or map them manually.

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.