Acer

This is an old post, but seeing that people are still viewing it, I thought an update is in order. I've managed to use and utilise the native TB CSV import functionality extensively. I've imported products and done bulk updates to every column without issues (price, name, categories, url rewrite, images, meta, accessories, tags, etc. etc). So far my experience has been pretty good, apart from the occasional cryptic error messages (normally a silly mistake on my side) - everything imports and updates successfully. My main use case for the CSV Import is initial Product Import and then bulk updates after - all good so far and working as expected. So at the moment no need for 3rd party bulk import / update tool. The only problem I encountered is that if you update the category, it doesn't make the category you specified the "default / or main" category. There is a fix for this if you need it. https://forum.thirtybees.com/topic/3478-solved-issue-request-created-please-help-csv-product-import-problem-moving-category-issue-product-breadcrumb-not-updating-default-category-issue/?do=findComment&comment=30475

@rubben1985 gave me access to his back office, so I had a look at the issue. Indeed there was some weird stuff going on. For example, cache was not flushed when you clicked on Clear cache in Performance tab. My investigation showed that this problem was caused by missing /cache/smarty/cache directory. Recreating this directory using ftp seems to fix the issue (pending confirmation from @rubben1985) Thirtybees codebase never checked existence of this directory, so this issue is hardly 1.1.x injection. But it's an issue nevertheless -- the system should recover from this situation. The fix is already committed in bleeding edge Thanks @datakick for taking the time and effort to investigate this and for finding the cause of the problem (at least where the problem was occurring) and implementing a fix in Core. Your actions here are reassuring and promotes confidence in the project and the ability and willingness from the team to resolve issues. It is appreciated. Thanks again 😀

@datakick he's probably referring to Advanced Search 4. In which case @rubben1985 will need to give you the version number he is on. https://addons.prestashop.com/en/search-filters/2778-advanced-search-4.html I'm running on Advanced Search v4.12.5 on TB 1.1.0. On a local environment though as we're in development phase still. So not playing with cache at the moment. My setup: TB 1.1.0 + AS 4 + Panda. Bytw, have you given the below any thought? The complimentary copy of Panda for local testing? We can request one from @Jonny if you'd like?

Hi @datakick If you'd like, we can reach out to @Jonny and try to organise a complementary copy of Panda for you so you can maybe run it on a bleeding edge test site on local? That way you can connect the debugger and test to your heart's content. Let us know

Hi Just a quicky: To move the Customised text below the Add2cart: In theme directory (probably niara): theme\niaria\product.tpl Go to line 629 or find the text: {if isset($product) && $product->customizable} Cut or take the entire if code block as below {if isset($product) && $product->customizable} <section id="product-customization" class="page-product-box"> <h3 class="page-product-heading">{l s='Product customization'}</h3> <form method="post" action="{$customizationFormTarget}" enctype="multipart/form-data" id="customizationForm" class="clearfix"> <p class="infoCustomizable"> {l s='After saving your customized product, remember to add it to your cart.'} {if $product->uploadable_files} <br> {l s='Allowed file formats are: GIF, JPG, PNG'} {/if} </p> {if $product->uploadable_files|intval} <div class="customizableProductsFile"> <h3>{l s='Pictures'}</h3> <ul id="uploadable_files" class="list-unstyled clearfix"> {counter start=0 assign='customizationField'} {foreach from=$customizationFields item='field' name='customizationFields'} {if $field.type == 0} <li class="customizationUploadLine form-group{if $field.required} required{/if}">{assign var='key' value='pictures_'|cat:$product->id|cat:'_'|cat:$field.id_customization_field} {if isset($pictures.$key)} <div class="customizationUploadBrowse"> <img src="{$pic_dir}{$pictures.$key}_small" alt=""> <a href="{$link->getProductDeletePictureLink($product, $field.id_customization_field)|escape:'html':'UTF-8'}" title="{l s='Delete'}" > <img src="{$img_dir}icon/delete.gif" alt="{l s='Delete'}" class="customization_delete_icon" width="11" height="13"> </a> </div> {/if} <div class="customizationUploadBrowse form-group"> <label class="customizationUploadBrowseDescription"> {if !empty($field.name)} {$field.name} {else} {l s='Please select an image file from your computer'} {/if} {if $field.required}^*{/if} </label> <input type="file" name="file{$field.id_customization_field}" id="img{$customizationField}" class="form-control customization_block_input {if isset($pictures.$key)}filled{/if}"> </div> </li> {counter} {/if} {/foreach} </ul> </div> {/if} {if $product->text_fields|intval} <div class="customizableProductsText"> <h3>{l s='Text'}</h3> <ul id="text_fields" class="list-unstyled"> {counter start=0 assign='customizationField'} {foreach from=$customizationFields item='field' name='customizationFields'} {if $field.type == 1} <li class="customizationUploadLine form-group{if $field.required} required{/if}"> <label for ="textField{$customizationField}"> {assign var='key' value='textFields_'|cat:$product->id|cat:'_'|cat:$field.id_customization_field} {if !empty($field.name)} {$field.name} {/if} {if $field.required}^*{/if} </label> <textarea name="textField{$field.id_customization_field}" class="form-control customization_block_input" id="textField{$customizationField}" rows="3" cols="20">{strip} {if isset($textFields.$key)} {$textFields.$key|stripslashes} {/if} {/strip}</textarea> </li> {counter} {/if} {/foreach} </ul> </div> {/if} <div id="customizedDatas" class="form-group"> <input type="hidden" name="quantityBackup" id="quantityBackup" value=""> <input type="hidden" name="submitCustomizedDatas" value="1"> <button class="btn btn-lg btn-success" name="saveCustomization"> <span>{l s='Save'}</span> </button> <span id="ajax-loader" class="unvisible"> <img src="{$img_ps_dir}loader.gif" alt="loader"> </span> </div> </form> <div class="form-group"> <div class="help-block"> ^* {l s='required fields'} </div> </div> </section> {/if} Find the following: <div class="box-cart-bottom"> Then before the closing Div (the one just before the form: </div></form>), paste the if code block. --- So pasted code should go here -- </div></form> Then go to admin -> performance -> clear cache The customisable text should now be below the Add2cart Also, regarding the Tabs on the Product page: You can try the old @Nemo tutorial. But you may have to make some adjustments. Personally I haven't tried it as I'm using SunnyToo's great Panda theme that has this built in (along with other great features). http://nemops.com/prestashop-1-6-product-page-tabs/#.XmeZk_kzaUk Panda Theme: https://www.sunnytoo.com/product/panda-creative-responsive-prestashop-theme Whoops: In retrospect I see the request was to move the text above the Add2cart but my instructions was on how to move it just below the Add2cart. If you want the text to be above the cart, then move the code to the beginning of the Div tag.

As stated previously as well, a lot of PS 1.7 third-party modules have PS 1.6 versions. In most cases the PS 1.6 version works in TB.

Good luck and let us know how it goes

No you can't. But if the module has a PS 1.6 version, then maybe.

No not exactly. There are modules that have versions for both systems. Like Panda template and Advanced Search 4. In the case of Advanced Search 4, the latest PS 1.6 module works in Thirtybees.

Hi sorry that I'm writing in English. Maybe the Thirtybees guys can see if it's possible to create / or adapt the existing PS 1.6 Migrating Tool for PS 1.7? By the way - if you're running Panda template and even Advanced Search 4 on PS 1.7, these modules have PS 1.6 or Thirtybees equivalent versions. Worse case, redo the the site from scratch in Thirtybees. Going Thirtybees is probably the best route from PS 1.7. It's great software and a lot of PS 1.7 headaches are avoided with Thirtybees. In short, TB> PS 1.7 hands-down and is one of the best open source e-Commerce platforms around currently.

Have you tried making a complete working copy of your old PS 1.6 site, installing the Thirtybees migrator and updating from there? In theory it should migrate your site over to Thirtybees + the theme as well. If I'm not mistaken. https://github.com/thirtybees/psonesixmigrator/releases/latest https://thirtybees.com/migrate-from-prestashop/

@TomR You're welcome 😀 Yeah, I agree, the zoom feature is looking good - adding some extra pizzazz to the product images. Nice 😀 Also, site speed is really, really good - even before @toplakd's suggestions. Now, it's positively flying 😎 Agreed. You can do that + turn the sections into Tabs - especially on desktop. However, seeing that most users these days are browsing mobile, I'm not sure if tabs will make a noticeable difference for those users. There are plenty of tutorials out there that show you how to do tabs on the product page bytw. And don't forget to enable and add the Recaptcha module to the Contact page, User registration and Admin login page.

Hi Looking good 😀 Well done 😀 Just goes to show how nice a site you can build with vanilla (built-in theme) Thirtybees. I like that you're using product attributes and combinations as well + "personalisation text". Also, if you'd like to have a nice zoom effect on the product image, you can use the built-in JqZoom module: Admin -> Preferences -> Products -> Scroll down to product page -> "Enable JqZoom instead of Fancybox on the product page" = On. Also, not sure if you know this already, there is a setting that enhances Site Security as well: Admin -> Preferences -> "Increase front office security' = Yes. Hmm Regarding "CMS Pages not showing on the footer": You can use TB's custom HTML block to show content on the footer: Admin -> HTML Block. Simply create an entry and select the Hook / position that you want this entry to be displayed on (Footer). Just two other things I picked up: Currently your main banner is pointing to a page with no products (no products on special on price drop) Your link in your post is pointing to the Sitemap, and not the main site - maybe update this for the other community members. Your contact form, and likely your back end Admin does not have a Captcha installed - this is a security + SPAM issue. To fix: go to: Admin -> Modules -> Search for Captcha Ensure that it's version 1.1.2 (if lower, then do update). Register with Google recaptcha and enter site recaptcha keys + enable for User Registration, Admin and Contact form. Enjoy and all the best of luck with your shop and your business. May you continue using Thirtybees and may your shop be prosperous! 😀😀

Just pinging @datakick to see this thread 😀

Hi @datakick As you mentioned, there is a free module that works with Thirtybees - "Advanced Featured Values". I reached out to the developer last year and he is willing to donate this module to the TB Core. However it's up to the TB team to allocate time / prioritise when and if they will be incorporating this module. Regarding your concerns + our findings using the Free Advanced Featured Values Module + popular Advanced Search 4 module or with Native Layered Navigation: I understand your concerns that such a module could be "dangerous" especially in relation to Core and ThirdParty modules. However, we required this feature and had to look for a module that gave us this functionality + we needed it to work with Advanced Search 4. What's interesting is that our findings so far shows that it works 100% with TB Core and Advanced Search 4 + the native Layered Navigation. And that the "multiple values for a feature" values are being picked up and "seen" by the 3rd party module (AS4) and layered nav. So for example, you can have a feature called "paper colour" with the values "red, green, blue, orange" and assign a test product to use "green and blue". You can then create a filter in Advanced Search 4 or Layered Nav for the "paper colour" feature, it would then see all the values as separate individual values (like red, green, blue, orange). And show these as a dropdown, input boxes or whatever. Then, in the front-end, if you select either green or blue separately in the filter search, then our test product would come up as expected (it would not show for the other colours). So this works for us and our business requirements. I know it's almost impossible to test against every thirdparty and core component, and I haven't tested this with Elastic search yet either. As the code for this module is open source, perhaps you can check it out and see how it works? Perhaps it could be "safe" enough to be incorporated into TB Core or it could provide valuable insights on how to possibly solve this problem with TB in a safe way - if you guys had to code a solution from scratch. My point is that "multiple values for a feature" is a feature that imo should be part of TB natively. Or at least you guys can use this module as an add on and update it if needs be for like PHP 7.4++ compatibility in the future. For those that are interested in using the free "Advanced Features" module (multiple values for a feature), you can see this thread (contains installation steps plus minor fixes): https://forum.thirtybees.com/topic/3456-multiplefeatures/?do=findComment&comment=30387

Thanks for the feedback @datakick It's reassuring, thank you. Speaking of features: I may as well chance it here: any ideas or plans for "Multiple values for a feature" feature? I see even PS 1.7 has that now...

Thinking of European developers, have you heard of Oxid CE? At one stage back in the day when I was evaluating different e-commerce platforms, I seriously considered Oxid Community Edition. It was simple, feature rich and blazing fast. At least back then and with my initial tests. Not sure how it stacks up today - but I see it's still around and alive and well. Unfortunately there was no compatible payment gateway plugin for my country and we landed up going with Magento instead (lol and what fun! sad joke...) Oxid CE https://www.oxid-esales.com/en/why-oxid/ https://oxidforge.org/en/#top https://demoshop.oxid-esales.com/community-edition/index.php?lang=1& https://demoshop.oxid-esales.com/community-edition/admin/index.php?cl=login&redirected=1 Live site example: https://www.schiesser.com/ Years later I heard about PS and after lots of research decided on going with PS 1.6 - only to find when we were ready to pull the trigger that PS 1.7 was happening. After reading some reviews and after some frustration, and out of desperation I decided to look for a PS 1.6 fork and voila: Thirtybees 😀

2 more kids = no time for anything else 😁 Thanks for the feedback @toplakd

Thanks @toplakd it's reassuring to hear this from someone who has played this game for a while with Presta and have gone through the evolutions a few times. What's also nice to know is that you seem to be sticking with Presta-tech (for lack of a better term) and its continuation with Thirtybees. I assume this is because it's the best option, if it's not, then can you please recommend others that you find as capable and feature rich? Like which tech would you switch to if TB was no longer an option? Also... Although @toplakd 's comments have been reassuring, respected and appreciated, it's from a fellow merchant and dev. However... What I would like to see is actual feedback from the TB team / senior dev or team lead - about PS 1.6 compatibility plans and plans in general for TB. It's been oddly quiet from the guys -- there was a time until recently that they were involved with the community and communicated here and participated in discussions. Has this changed? Can you guys (the TB team and dev lead) please join the conversation and provide some feedback as well? @Traumflug @lesley @Nemo @datakick

Indeed, fair point. Same concern here. As long as TB has 1.6 support, and our 1.6 modules continue to work and we're happy with them as they are (no new features) - then we should be ok, imo. For a while at least... Lol, maybe TB should have a container or sandbox for PS 1.7 module support? (joke joke). Or maybe better still, maybe TB should fork 1.7 and call it TB 1.7 (LOL) = Either way, this way we can continue to have access to a large marketplace of modules 😂😀

Hi. Yeah, but you don't need Warehouse 😀 Thankfully, one of the best and insanely feature rich and customisable PS themes, Panda, has been updated for TB and is actively maintained by the Theme developer @Jonny Which is great and it gives you the "AAA" quality theme that you need for TB that is actively maintained and updated.

Thanks @toplakd for the great feedback and insight. My concern was that we've invested time and money into our TB stores, and required some reassurance that our critical modules (like the payment gateway, Panda and many other PS 1.6 modules) would not break in a year to 2 from now with future TB updates (like maybe TB drops majority of PS 1.6 support for example). Essentially, I'm trying to gauge the health of the platform with it's current direction and updates - especially in relation to PS 1.6 compatibility. We certainly do not want to re-platform to another platform any time soon. And I definitely do not want to go to my CEO after all the time spent learning TB, developing, buying modules, building the site, and before launch telling him that maybe it was for nothing and TB wasn't the right choice... It won't go down well. Also if we had to re-platform... Unfortunately with the modules that we're using at the moment, the most natural platform would be PS 1.7 (!) - and that is something I'd like to avoid at all costs if possible. PS 1.7 is just a crazy complete mess and would create major problems for us down the line anyway. From what I can see. And that's why we chose TB for our projects (we wanted 1.6 initially). So no... If TB can maintain PS 1.6 compatibility as much as possible going forward, then it's still our first and best choice.

Hey Windows 10 still runs XP programs - so what are you talking about? It's called a foundation. Yes the stuff on top evolves, true. And everything changes, yes. However, in the thousands of years we've been building houses, the shape outside and inside and look and feel has changed many times. But - you still build a house on a foundation. If you don't have this basic principle... So a solid foundation can stand the test of time and constant evolution on the outside... Many buildings from thousands of years ago are still standing today because of this principle. Just look at the Hagia Sophia. It became a Mosque, but was built as a cathedral initially. Lol, it evolved again, and is actually a museum now. It's changed on the outside and "evolved", but its foundation is still the same and it's still standing. It's like 1,483 thousand years old!

Hahaha - that's reassuring 😂 "Don't worry, there's no alternative." So just accept you're pretty screwed and carry on until you hit the cliff 😎 Yeah in terms in payment gateways - the one I use is for PS 1.6 as well - and will unlikely be updated for TB. No built-in TB one for that. So hence my concern. Also would be nice if the team could say something here as well...

Thanks @wakabayashi and @toplakd for the reply. I'm just curious what the plans are for PS 1.6 compatibility in the future? Like if that foundation will be removed and when? So will TB still be compatible in principle with the best and well written / correctly written PS 1.6 module in a year or two from now? Obviously provided that that module is latest PHP version compatible? I know it's difficult to predict. I'm just curious if there is a Road map. And while we're on the subject: "Multiple Values for a Feature in Core" ? What's happening with that?