datakick

They are (the dangerous ones). Thirty bees server does not allows you to update to bleeding edge, it simply does not offer this target for selection.

The new version of core updater is not yet released, it's currently under testing. There were a lot of changes, both in server api and module, so I want to be sure this works correctly before we release it officially. Wouldn't want to destroy your stores during update 🙂 Good idea, will look into it. Although I don't think many merchants would notice this -- does anyone actually read the news stream on dashboard?

How many spams do you get? I personally have one spammer as well, but I'm almost sure it's not automated script. From access logs it looks like somebody do this manually. And there's not much I can do about that. I have set up Conseqs module rule to block sending contact_form email to customers, so this spam attempts do not bother me much, as I'm the only one who actually receive the spam emails.

You need to look into server's error logs to figure out what the error is about.

This issue is fixed in bleeding edge: https://github.com/thirtybees/thirtybees/issues/1242

These are only notices, not errors. You don't have to worry about them much. What happens here is that module is registering hook (telling thirty bees core to call back when something happens) but it does not implement code handler. Without the handler core have no way to actually call back the module. It's like asking somebody to call you but forgetting to provide your phone number. Thirtybees simply detects this situation, and emits notice into system log with hope that somebody will contact module author and ask them to fix this issue. Usually the fix is pretty simply, just delete hook registration from module.

It should work without major problems. I'm personally using 8.0.23 for development, and so far encountered only single issue regarding complex queries of information schema -- this affects core updater, but is already fixed in new version.

Don't worry about this, it's harmless. This happens when your customer visits your site after they placed order. The cookie still reference the old cart that has been converted to order already. Thirtybees / ps16 detects this, and create a new cart. And in ps16 this 'notice' is generated. Not in thirtybees, though.

I tested the functionality on my local environment and it works fine. Please ensure you have latest version of niara theme, and that you don't have any core modifications and/or overrides

There is not much that can be done. This would require massive rewrite of the js app, there's not a simple solution

This is just a short FYI: We are currently integrating various features to main branch (aka bleeding edge) in preparation for release of thirty bees version 1.3.0. Some of these features require special initialisation, for example creating entries in database tables, new menu items, etc. Unfortunately, current version of Core updater do not support this functionality - only code is updated, and potentially database schema is fixed. But no data fixtures can be inserted into the database as part of update. This is serious limitation that prevents us to roll out of new features. Therefore, we have decided to extend Core Updater and implement this functionality. New version will be released soon. This new version allows us to introduce new core code together with all data fixtures it needs, nicely wrapped together. New functionality in 1.3.0/bleeding edge already depends on this new core updater functionality. Unfortunately, this also means that in order to update to upcoming version 1.3.0 (or current bleeding edge), you will have to first update your Core Updater module. Current version of core updater CAN NOT be used to update to this new version, because the system database would end up in inconsistent state. You can still use current version to update to 1.2.0, but not to main (bleeding edge). This is wanted behaviour. Once new version of core updater is released (hopefully this week) and you update to it, you will once again be able to update to bleeding edge and/or 1.3.0.

Nobody can answer that based on your description. Something must have changed - new module, updated php version, implemented caching system, antivirus, hacked server, etc. Computer programs rarely stop working without external input. Did you look into server logs? What does browser console says?

I see. Unfortunately no, it's not possible from within the module itself. You can delete it directly in db, using query like this: delete from tb_revws_review_image where id_review = 12345; Just replace id_review with correct value

It's not possible. The email address is required to distinguish between returning and new customers. Flow for different kind of customers are very different. For example, with returning customers you can choose between existing addresses, you don't have to enter account related information again, etc.

Hi everyone, Sorry for the trouble. This seems to be related to server plesk software update -- the configuration of extra PHP environment property was lost during the update, and the api server stopped working. The server is up and running again.

Hi Andy, I don't understand the question. Could you please explain a bit more?

Thirtybees requires InnoDB database engine. Your mysql server does not support this. You need to contact your hosting provider and ask them to enable it

that's indeed a very good idea, as it offers much better protection than the IP address check. It also ensures that the employee context is properly initialized -- that's important for logging, error handling, etc. And since you extract the logic to the admin controller, you can also wrap it all into a small useful module and offer it to the community 🙂

Because server responded with error code 500, you need to look into server errors log for further information

The module contains js library to determine screen resolution, and use it to determine if the floating cart is supported or not. On small displays it's automatically disabled. I guess there is some bug in the library itself, or in the browser on the devices, that reports wrong screen size sometimes. The size detection seems to be working correctly when testing on desktop browser in mobile mode. It will be hard to fix, as debugging in mobile is very limited, ... and I don't have such device that is affected by this problem. I could implement a feature that would force-disable cart floating on specific device(s), based navigator.userAgent browser property

And what does it say in javascript console?

There will be some screen resolution glitch. It's hard to investigate if it's reproducible on this device only, and I don't have it. Anyway, you can disable floating cart in the module settings, that should help mitigate the problem.

The fix should be in 'main' branch, not in 1.2.x

Regarding PHP compatibility: 1.3.0 will still be supported on PHP5.6 ... PHP7.4 There is an ongoing effort to make it work on PHP8. This is not a small feat because PHP8 introduced standard class 'Attribute' that clashes with thirty bees core class. To fix it we need to rename our class, respective move it to different namespace (in core and all native modules). While this is quite simple to do, it of course introduces compatibility issues with any third party modules. To overcome this issue, thirty bees will contain mechanism that will parse and 'patch' third party modules PHP files. When you install new module, it's php files will be processed anda all references to Attribute class will be adjusted. For this we will use third party library. Unfortunately that lib does not support PHP5.6, which is one of the reasons why we are deprecating PHP5.6 and will not support it in the future. At this moment there is still no need to actually remove support for PHP5.6, but once we integrate the support for PHP8 to mainline, we will be forced to do it.

Look into database. table <prefix>_configuration and check value of configuration key PS_OS_PAYMENT select name, value from tb_configuration where name = 'PS_OS_PAYMENT'; +---------------+-------+ | name | value | +---------------+-------+ | PS_OS_PAYMENT | 1 | +---------------+-------+ The value contains ID of order status that will be used when paypay module process the payment. You can compare it with the value in table <prefix>_order_state_lang select id_order_state, name from tb_order_state_lang where id_lang = 1; +----------------+--------------------------------------+ | id_order_state | name | +----------------+--------------------------------------+ | 1 | Payment accepted | | 2 | Processing in progress | | 3 | Shipped | | 4 | Delivered | | 5 | Canceled | | 6 | Refunded | | 7 | Payment error | | 8 | On backorder (paid) | | 9 | Awaiting bank wire payment | | 10 | Awaiting PayPal payment | | 11 | Remote payment accepted | | 12 | On backorder (not paid) | | 13 | Awaiting Cash On Delivery validation | | 20 | Awaiting Bitcoin Payment | | 21 | Waiting for 2 Confirmations | | 22 | Bitcoin Payment Confirmed | +----------------+--------------------------------------+ In my case, it matches the Payment accepted order state. I bet in your store this configuration option will point to different state. If that's the case, then update the configuration value to point to expected order state.