wakabayashi

As Petr clearly pointed out: just deactivate the mysql cache. IMO you should anyway not use it... Are you using it? Unfortunately security is still my weakness in coding. I understand, that there is some sql injection possibility. Prestashop seems to believe, that it happens in caching. But the fix does irritate me. There is already pSQL() in use. They just replaced it with another encrypt method.

I guess, this is the plan. But @datakick has to decide it and he has other works to do, that are more important right now (PHP 8).

True, thats a good way to handle it. But when you segment your traffic, you can basically stop to compare your conversion to any conversion rate from any random study/blog post. That's why I prefer to just improve my own conversion rate, than to compare it to other. I basically compare my conversion rate to my conversion rate in the past 🙂

Sure. That can be the case. Either the function was not simple enough or there is just no need for it. If the latter is the case, it's best to remove it. It was just an example 🙂 In general: only you can evaluate the situation of your shop. If your orders are declining it can have many reasons. Some that you can influence, some that you can't...

This is a very complex topic, that doesn't have any simple answers. In general conversion rates numbers are bullshit. I give you my example. We produced some quite helpful content about boardgames. For example when you search "learning chess" on german. We get a lot of clicks. 99.99% of this visitors just read and don't buy anything. The other 0.01% buys something. As this is one of the most visited page on our site it pulls our "global" conversion rate down a lot. Do I care? No, not at all. I prefer to have this few orders, than having a higher conversion rate. How do I know, that guy who just ordered, didn't visit my blog post a few weeks ago with his mobile and is now ordering with his desktop? So all this measuring stuff is very tricky. Still conversion rates are somehow important ofc. They are mainly helpful when you plan to make changes. Then you compare before and after conversion rates. This is much better than comparing conversion rates to other websites... Merchants should focus on customer experience. What can you do, to make life of your customer simpler? Is your mobile version good enough? Does your search deliver good results? Does your site load fast? Do you answer all frequent questions on your site? Compare your site with the best sites in your niche. What do they make better? What do you make better? Then also compare it with the biggest ecommerce site in your country. What can you learn from them? I have a list of about 50 shops called "best practice". I check them regular and learn much. And maybe most important: take your current customer serious. What do they like on your store? What do they don't like? Just ask them 🙂 In my example I learnt, that I need to bring back the wishlist function. In your store that could be something completly different: "Delayed shipping", "Customer support by phone", "Some new brand" or whatever 😏

As far as I know, right now tb is not compatible with php8. But it soon should be 😏

Thanks a lot! If we are lucky this will be in 1.4 together with php8 support. That would be really new heights 😎

The PR is now in, but it will surely take some time and some changes to be good enough for the CORE: https://github.com/thirtybees/thirtybees/pull/1455 Github says 1412 lines are changed, which can give you an impression, how much time and energy I invested into it. Btw we are using it since a few weeks on our live site and it works fine 😏

What does that mean? I don't understand it. Maybe the M2/M3 thing is the thing that my PR does actually solve 😅 No sorry, I won't do that. I doesn't have a lot to do with my PR and I don't even use the layered navigation module from tb. I have my own one...

V.1.1.0 has been released: https://github.com/eschiendorfer/genzo_branch_tester/releases/tag/v.1.1.0 Here is a very quick preview of what the new system is capabale of. If you test it you will find even more options 🙂

I believe, that this can only be fixed in the theme. Niara uses: {$feature.value|escape:'html':'UTF-8'} If we change it simply to: {$feature.value|escape:'UTF-8'}

10 years is a long time... I am happy if the next 10 months are safe for me 😅 In general tb developement seems to be more alive than 1 year ago. At least thats my impression on github. I am here since day zero and I don't plan to switch anywhere. If @Smile does the same and holds @datakick here, the thing goes on. We will see how long old PS theme and modules stay compatible with PHP 8 and so. But to be honest: you have this problem anyway. If you stay on PS 1.6 or switch here.

Amazing 🤩

No idea, why this additional weren't implemented multistore ready. Makes not a lot of sense to me. Probably it just got forgotten. When the coder don't work on multistore you can easily forget. I don't have time to fix it, but I can give you a simple (dirty) solution: Open header.tpl in your theme Search for the "</head>" tag. Just before add your code in this schema {if $cart->id_shop==1}/* Your Code for shop with id 1 */{/if} {if $cart->id_shop==2}/* Your Code for shop with id 2 */{/if} {if $cart->id_shop==3}/* Your Code for shop with id 3 */{/if} That was the way I started coding 5 years ago ^^

Thanks a lot Petr! Very interesting, cause when I tested it like 5 minutes on the core before releasing the module. I noticed this issue too. But I don't have it on my live site. I will check it. Cause my intention was also to allow "<br>". The other schema values I will implement as well ☺️ Are you on a clean installation? What I notice on my clean installation. The closing "x" of chosen is not showing up. But I guess it has nothing to do with my work...

I have worked for weeks now, to improve the multiple feature system: Possibility to use displayble (Show a different value from filter value) Usage of chosen plugin in BO Product Form Possibility to add feature values in BO Product Form Possibility to sort feature values and use custom seperators Drop of custom feature values Now it's time to test. PLEASE ONLY DO THIS ON A TEST ENVIRONMENT. The steps: Update your test store with core update to bleeding edge. Install genzo_branch_tester module and click "update". Don't worry: this module won't be needed in the future. It's just for override files and adding an sql table. Go to core updater module and fix the database. Now you should be good to go. Try to play around. Check if it works out with your filter module. With this new version, you can improve the usage of every filter module. How do you like it?

With this informations it's almost impossible to evaluate the issue. Which module are you using? What is the url?

Hard to say. I just turn on the debug mode in BO and it throw out a logical error (for coders). It tries to delete tables that might not be there. That's why I check, if these modules are installed or not... The rest I just wondered: why is this module again needed? Is it about the frontOffice functionality, cause we have a delete button on customers in BO. But I guess it will just delete the core object customer and not any related table.

I dunno, but I get clear error messages when turning on debug mode. Have you used mailalerts/productcomments module before and uninstalled them? This seems to be an issue. The module is in general well structured and the code looks solid. But I think this is necessary: if (Module::isInstalled('mailalerts')) { $queries[] = "DELETE FROM `" . _DB_PREFIX_ . "mailalert_customer_oos` WHERE id_customer = " . (int)$customer->id; } if (Module::isInstalled('productcomments')) { // delete customer from productcomment module $queries[] = "DELETE FROM `"._DB_PREFIX_."product_comment` WHERE id_customer = ".(int)$customer->id; // clean productcomment module $queries[] = "DELETE FROM `"._DB_PREFIX_."product_comment_grade` WHERE `id_product_comment` NOT IN (SELECT `id_product_comment` FROM `"._DB_PREFIX_."product_comment`)"; $queries[] = "DELETE FROM `"._DB_PREFIX_."product_comment_report` WHERE `id_product_comment` NOT IN (SELECT `id_product_comment` FROM `"._DB_PREFIX_."product_comment`)"; $queries[] = "DELETE FROM `"._DB_PREFIX_."product_comment_usefulness` WHERE `id_product_comment` NOT IN (SELECT `id_product_comment` FROM `"._DB_PREFIX_."product_comment`)"; } I added the two if (Module::isInstalled...) in deleteDataFromPrestashop function.

I guess it's allowed then. I can take a short look and see what might cause the problem. But I am still a bit sceptical about deleting customer. What does it mean? addresses? orders? module data? Should this all be deleted? 😊 I doubt that every merchant want the same...

Wow you have even done a video! That's amazing!! Thanks a lot 😍 I did add a link to the first post in my modules thread. Love this kind of "teamwork" 👏

It's correct. If you use the custom hook, you can place it direct at the "category block". Do you know a hook that is this category block? I believe there is just no hook, that does it. That's why I took the footer...

Sure! I would like that 😎 Thanks a lot for your work 🤩

I could convince thirty bees team to add the "discussion" tab on github: https://github.com/thirtybees/thirtybees/discussions I invite all devs to take part, to advanced talks about technical stuff. Note: this should by no way replace the forum. It's just the right place, to discuss advanced technical topics.

I have rewritten this module. Version 2.0.0 is out. It works now out of the box. Download is now available for everyone: https://github.com/eschiendorfer/genzo_category/releases/tag/v.2.0.0