datakick

Simply go to https://github.com/thirtybees/thirtybees/issues and file new issue. I'm afraid this one will have low priority, though. There aren't many merchants having more than 50 cms pages in sub-categories

The problem was found. There's a new configuration option named Maximum level depth When you install this module from scratch, it is initialized to value 2. But when you upgrade from previous version it has value 0, thus displaying only top-level entries. When you add non-zero value it works as expected.

Weird. If you PM me access to your back office I can have a look

cache?

There's a bug in in beesblog module - it emits invalid metadata to the page. To fix this, you will need to modify templates and apply this fix

Configuration::updateValueRaw method exists in core. If your server claims it doesn't exists, it's probably caused by badly-written override, or some manual modification to configuration.php file.

I'm not really familiar with the iquitcontenteditor module, but it looks like it doesn't allows you to pass any custom parameters to display hook. And you really need to pass review id. So I'm afraid this module will not work with this revws hook

Thanks for the confirmation. My test also suggests that all issues are solved, so I've officially released 3.0.4. Hopefully not many people upgraded to faulty 3.0.3 yet.

@cprats could you please test this new version of the module fixes the problems? Thanks blocktopmenu-3.0.4-pre.zip

Indeed, the new version of blocktopmenu doesn't work correctly. You should downgrade to version 3.0.2

Did anyone had a chance to test the release preview version?

Both methods must work. If you could test both module upgrade, and fresh installation, that would be great.

New version (release candidate): SCA support Here's a pre-release candidate of stripe module that implements support for SCA - new European regulation coming into effect on September 14, 2019. If you are collecting payments from EU customers, you will need to upgrade stripe module, otherwise you will see a huge increase in card declines. The changes to the module are substantial -- 3 core checkout flows had to be rewritten from scratch using new Payment Intent API. Therefore, before I release this version officially, I would like to ask you all to test it thoroughly. If you find any bug or problem, please report to this thread. Download: stripe-v1.7.0.zip

Ohh, you are right. This package contains constant (currency id) that is specific to my setup only. I will need to come up with some better package installation process -- ask user for information and use it to replace hardcoded values. Meanwhile, I've uploaded new version of this particular package that depends on currency with id 1. That one is more likely to exist that currency with id 3.

Yes, it's possible.The trigger part is tricky one -- since this changes with time, the only way to implement this is using measure - for every product in your specific category track if it is available or not. This is sql to define such measure: SELECT ps.id_product, 1 AS is_available FROM tb_product_shop ps INNER join tb_category_product pc ON (ps.id_product = pc.id_product) WHERE pc.id_category = 5555 AND now() > ps.available_date This will return list of every available product in category with id 5555 With this measure in place, you can use trigger Measure value changed that will react when the result of that sql changes. When some product in category 5555 becomes available, sql result will include this product, and rule will be triggered. You can now do whatever you want. To remove product from category, you will have to use custom sql action and execute this sql: DELETE FROM tb_category_product WHERE id_product = {id} AND id_category = 5555 Where {id} is a placeholder. You will need to bind this to product ID: You can have a look at my demo account, I've create this rule there (for category 2, not 5555)

@x97wehner what tb version are you using? Is it bleeding edge? Please confirm

More and more users blocks google analytics nowadays. With self-hosted tracking tool the situation is much better as it's hard(er) for blockers to detect and block it. So, I'd say that self-hosted Matomo will give you more precise data. Still not 100% accurate, but better than GA. But it's not really that important. We are not using these tools to look at transactional data, we are using it to look at aggregated data. And from this point of view, data collected by GA will have very similar characteristics as data collected by Matomo. For me, the real question is which solution offers better tools to analyze collected datasets.

You should look what is in ajax response -- open browser javascript console, switch to network tab, and find the request that loads the rule. On related note: I can see something strange on your frontoffice: Those rnrnrnrn characters shouldn't be there. They probably meant to be \r\n characters -- linebreak. You should find the source of this unwanted output and fix it. It is quite likely that this will fix your conseqs issue as well (but maybe not)

With new version of tb there comes new version of smarty, which changes how things works sometimes. In old version of smarty, $carrier variable would hold value of last item after the {foreach} cycle has ended. So the original template code worked, but it just Delivery time for the last carrier in the list only. New version of smarty works the same, *unless* $carrier variable is defined before the {foreach} cycle starts. If $carrier variable already existed in global scope, then after {foreach} cycle ends, the original value is recovered. With this changed semantics the template no longer works. I'm not sure what the intention of this code in this template was. But it looks very likely that @yaniv14 is right, and that author really meant to do show delivery time for all carries. So to fix this particular case, we can use yaniv's proposed fix - this would change template output, but that's probably correct rename iteration variable from $carrier to something else. This would keep the template output the same I vote for #1

This kind of error happens when ajax response contains some extra text. This is often the case when you have enabled debug mode, and there is some php warning or notice. I have retested this on my server, and I don't have the same problem. So it's probably some issue on your server

Revws module expected image type home to exists. If it does, it should work, even for legacy mode. Anyway, this is the code that would need to be updated

Great to have some SysAdmin aboard, that's another group of problems this forum can help with now!

I've just released new version 0.4.0 PACKAGE REPOSITORY There are some automations that almost every merchant using my module created. For example, everyone created their own version of reward for review rule. Even though rule creation process is very simple and easy to understand, this repetition seems unnecessary. So I decided to come up with list of prepared solutions that you can simply import to your store and modify. You will find new tab named Packages that will let you browse through packages stored on central repository. At the moment there are only few packages, but I'll add more. Also, if you create some cool automation, please export it, and send it to me. After careful validation and verification, I will add it to the repository. This needs to be manual process to prevent any hacking attempt NEW CONDITIONS There are two new conditions you can use to build your rules starts with - evaluates to true if text starts with specific prefix ends with - evaluates to true if text ends with specific suffix

Nobody is abandoning this module. If there's something broken in the module, it will be fixed. In the same way bugs are fixed in other modules. But that doesn't necessarily mean that new functionality will be implemented. For example, support for newer version of ES server. It would be nice to have, of course, but there's just no free capacity to do that. Now, what is wrong with the module that needs to be fixed? I haven't seen any new bug reports. If you did encounter any, please file github issue. Make sure you include reprosteps so we can reproduce the problem.

I'm not sure if this module is worth the trouble. I mean, it can be extremely useful for anyone with huge amount of products, but it's not for an ordinary merchants. I believe there is less than 5% of the tb community that actually have needs for it. And these merchants can usually afford to purchase some commercial alternative, one that comes with support. Or they can hire developer to set this module for them. I'm not against another crowdfunding project, but it would be better if it was something useful for entire community. Maybe some advanced order editing module, dran'n'drop cms page builder, shortcode system to use in html editor, or whatnot.