Acer

Hi I use Panda for ThirtyBees and I can confirm that the product hover effect works in ThirtyBees. Whether it's now a default thirtybees feature is another story. However, seeing that you're already using Panda, it will probably not be too much of a mission to migrate your site to ThirtyBees. Also, Panda has been patched several times for ThirtyBees, so grabbing the latest version of Panda, plus applying the patch in the directory is advised.

...

Hi So did you try the module from Myprestamodules? And how is it for you?

Hi I'm looking for an excellent Product Import module, that does the following Import from either CSV/XML, Upload, Google Sheets or XML/CSV live URL from Warehouse/Supplier Imports full product attributes, like: Combinations, Features, Manufacturer, Shipping weight/dimensions, everything Hopefully imports all the above in one import, without having to feed different CSV files for attributes, etc Cronjob compatible Is reliable, proven and stable Can be PS 1.6 but TB compatible module Is not StoreManager (too expensive) Is not DataKick Import (sadly no CSV support 😞 ) Has a reasonable price I've been looking but haven't found anything suitable so far. If you guys have any suggestions, that'd be seriously helpful. Thanks

Hi and welcome to ThirtyBees! You can reach out to @Smile

All you need is GoogleShopping Flux and it's free, TB compatible and very good https://github.com/dim00z/gshoppingflux

What I'm suggesting is the mechanism should maybe monitor the 500 errors / log files and fix automatically instead of having to scan the whole module directory. All this is in the context of these errors being fixed automatically.

Or what about a mechanism that monitors the 500 errors? And fixes it as it comes up, file by file, error by error. It can display a message that it's performing a compatibility upgrade and that it may be a step by step process. That way it's less intensive and it's more targeted with less risk of time out. @datakick

Maybe even more insane but can you intercept the module and run it on some sort of compatibility layer at all?

What about the flag idea @datakick?

Thank you @datakick Your work on TB is big time appreciated

Though I agree it's caused by PHP 8, this is actually a TB 1.4 problem and they appear know it. Or at least they're aware of the seriousness of this in terms of module support. To the point of @datakickmentioning that they're working on a mechanism to 'fix' it on 3rd party modules automatically. Even though that task would be complex and hard. The point is that there are very few module developers and theme developers still supporting TB and that number is dropping daily. If this was Presta, with devs supporting it, then different story, sure. But with hardly any 3rd party module devs willing to support TB, stuff like this could lead to a demise of TB or at best push it into even more of a niche system, that becomes less and less attractive for new users to adopt and existing users to keep it around. Leading inevitably, and unfortunately, to its eventual end 😞

Hi there I've seen with a Google shopping feed export (using gflux) , the shop description is "powered by ThirtyBees". Where do I change the shop description in TB? Although I know where to change the shop name, address etc. I haven't found where to change the description...

TB 1.4 breaks modules that play with that class causing them to error out. I've had 2 modules break already. If people just update to 1.4, they could encounter problems. Also, right now I'm running 1.4 (for the benefit of running latest + security patches) on PHP 7.2, but will be running on PHP 7.4 when the site goes Live. Running on PHP 7.4 isn't the issue, TB 1.4 is... well technically PHP 8 is the issue, but I'm sure you get what I'm saying 😉 Maybe TB 1.4 can have a flag to support Attribute instead of ProductAttribute - for those who want to run 1.4 but aren't running PHP 8.0 currently? Perhaps this could help in the meantime while a potentially better solution is being worked on?

Hi @datakick Thought I'd let you know: I encountered another 3rd party module with the Attribute / ProductAttribute issue (CSV Import Products by GloBo). All was working fine in 1.3 until I tried to do a product attribute update in 1.4 edge with the module and then it threw an error. The log file revealed that it was the Attribute/ProductAttribute issue, and the module worked again after I followed your fix instructions. The thing is that most people will think that their 1.3 site upgraded to 1.4 is running fine (mine appeared fine). Until they try to use their 3rd party modules to do something fancy, like updating product combinations/attributes. I'm not sure what the plan is regarding releasing 1.4, but I know that unless it includes the Mechanism that you mentioned that scans and updates affected 3rd party modules, then people will run into issues with 1.4 sooner or later. For those encountering an error with "Attribute Class not found", you can follow DataKick's fix instructions here:

Working now, thank you. I appreciate it 👍

Awesome, thanks for the explanation and solution. I will implement accordingly. Bytw, I particularly like your idea of the mechanism to fix 3rd party modules automagically. But I can appreciate the complexity and hornet's nest involved in that one. Also just last question for now @datakickWhen I started building this site, PHP 7.2 was kinda still fine with 7.3 recommended, with the dev site running 7.2. Assuming that Panda and other third party modules will still work, which PHP version do you recommend for the live site? Should I go for 7.4?

So I've just purchased this module https://addons.prestashop.com/en/sizes-units/24128-product-combination-attribute-dimensions.html#specifications But I'm getting the following error (Running TB 1.4 on PS 7.2): ThirtyBeesException Class 'Attribute' not found in file modules/combinationdimensions/classes/AttributeDimension.php at line 85 Source file: modules/combinationdimensions/classes/AttributeDimension.php 66: 67: /** 68: * Get saved attributes from DB 69: * @return array 70: */ 71: public static function getSavedAttributes() 72: { 73: return Db::getInstance()->executeS('SELECT * FROM '._DB_PREFIX_.'cd_attribute_dimensions'); 74: } 75: 76: /** 77: * Method to modify saved attributes for helper list 78: * @return array 79: */ 80: public static function getListAttributes() 81: { 82: $attributes = AttributeDimension::getSavedAttributes(); 83: 84: foreach ($attributes as &$attribute) { 85: $att = new Attribute($attribute['id_attribute']); 86: $attribute['attribute_value'] = $att->name[Context::getContext()->language->id]; 87: $attribute['height'] = (float) $attribute['height']; 88: $attribute['width'] = (float) $attribute['width']; 89: $attribute['depth'] = (float) $attribute['depth']; 90: } 91: 92: return $attributes; 93: } 94: 95: /** Is there something I need to change in the code here, please @datakick ?

Ok found it. The folder name is update1.5.5 Unzip the installation, then copy the contents of the update folder into the Panda installation folder, then install Panda.

It's a folder within the Panda zip. I think it's called 1.15 or something. Will probably check tomorrow. But you'll recognise it immediately when you see it. Got a bunch of folders in it.

Enable debug mode. Advanced Perimeters -> Performance - > debug. Try again and see. You can also check out the log file in the site logs directory

Another way is to include the Google analytics or tag manager code in the theme directly, which is what I've done. Find the header or footer template file for the theme that is being used then paste the code in a literal container tag. Like so {literal} Google script here {/literal} You'll need to clear the site cache afterwards ofc. Advanced Perimeters -> Performance - > Clear cache

From what I recall the Panda patch could've fixed something with the config file and hooks. It was a while back when dk made some changes to the way the themes read that xml or something then Sunny had to patch Panda. The installation folder contains the patch. Unzip the installation and copy the patch into it, then use this new folder for the theme install. Let us know if you came right please. I'm curious to see what the problem was and how it was fixed and if the patch helped. Also if it works on a fresh TB with patched Panda, then you know it's likely something to do with the old site migrate and not the theme.

More monetary support and more paid support work will help TB grow so we can get more devs. Obviously there are things that TB management needs to do to bring in more users / theme devs. But that's another story. Right, Chiel? @Smile Right now TB needs our support. Both for their sakes and ours. We like running one of the best opensource eCommerce platforms out there and want it to continue and get better, right?

Also if you need any help and it's small enough not for paid support, you can always ask here in the forums and include Datakick. Thanks to @datakick, @Smile and the supporters who have kept TB alive. There's more to be done and room for improvement ofc, but at least it's alive and active.