lunika

@ajensen27 thanks for this link. It looks like this comes close to what I want. Instead of hiding the unavailable attribute values it marks them with a cross. I'll look into it to see if it works for my store too! But still too bad that this is not standard functionality.

Hope someone can help me with the following. My shop sells shirts with texts on the back. I now have a section (category) for men and ladies but most shirts are marked as duplicate content because I have the same text for both categories. I was planning to merge the products by adding an extra attribute for type of shirt. In that case I have 1 product where the customer can choose: Shirt type: men or ladies Shirt color: black, blue, pink, orange, green Size: S, M, L, XL, XXL The problem is on the product page. If I select men then it must show only the available colors and sizes for men. The same for ladies. Now all attribute values are shown and a message is displayed: "this combination is not available". This is not really user friendly. In prestashop 1.7 this seems to be working out-of-the box by hiding the not-available values. But prestashop 1.6 and thirtybees work different. Is there a solution or plugin to have the behavior I need? Thanks! Bart

Let me first introduce myself. My name is Bart and I’m the proud owner of a web shop that sells running shirts with funny texts: https://www.trackmyback.nl (sorry for the Dutch). Yesterday the shop went live based on thirtybees version 1.0.1 and with this post I would like to share my quest with this great fork of Prestashop. The beginning The first version of the shop was built with Woocommerce, a plugin for the popular Wordpress platform. After some time I found out that there were a lot of limitations and for almost everything (even simple e-commerce functionality) an extra plugin was needed. I decided to look for a different solution and switched to Magento. Although Magento is dedicated e-commerce software, version 2 was very unstable and version 1.9 had a lot of complexity in it. That lead me to Prestashop, because the demo was exactly what I needed and almost all functionality I needed was out-of-the box. Thirtybees When starting a new shop I had to make a choice between version 1.6 and the new 1.7 version. While I tended towards 1.7 I found out that it contained a lot of bugs and some plugins I needed for payment or accounting were not compatible. But version 1.6 also contained a lot of bugs and browsing through the forums I learned that it can take long time before issues are solved. In one of the posts thirtybees was suggested and I decided to look into that. The strategy and the changes in thirtybees were really to my linking and I haven’t regret this choice. Cudos to the developers! One very big advantage was the SEO friendly url’s without the ID’s so that made switching from my old Magento shop a breeze! Theme The theme I used for the shop is PTS Strollik, a single-product theme. It turned out to be fully compatible with thirtybees, but their Prestashop 1.7 version is more cleaner. I made some customizations to adapt to my shop. Plugins I don’t use a lot of plugins, but the ones I needed were fully compatible with thritybees: • Siel Acumulus (accounting) • Mollie (payment) • Dynamic product (for add-on pricing to customizations) • Local stock synchronizer (sync stock between products) • Content Box (create a block with custom content) Hosting Because also the hosting contract was about to expire I moved from Siteground to Clouwdays. Cloudways has default support for thirtybees, is fast and has some nice caching (Redis) options. Conclusion I am very happy with thirtybees as platform of the shop and I can’t wait to further explore all the possibilities. Until now I have had great support from the community with a question and a bug report. There is still a lot to optimize such as SEO and pagespeed improvements. That will be my goal for the short term. A big thank you to the community and developers, thirtybees is awesome! Bart

@mdekker are you sure? Because you opened the bug report yourself yesterday :-) .. based on that I did a new test with the fix that was made for 1.0.2 earlier in this topic. That had the issues you mentioned when re-opening the bug. I also read that 1.0.2 is around the corner, so it's no problem to wait for that release and re-test with that version.

@mdekker you are right! I did not notice that before because my tests were with customization. In below screenshot the first line is added without customization, the second line with customization. If i'm correct the first line of the cart should not include the customization row below it.

I tested it and it works perfect! Thank you very much for the fast fix. This was one of the last issues before going live so later this week my thirtybees site will be in production :-)

I see now our posts crossed each other .. I wil try your fix and test if that works. I'll let you know, thanks!

@mdekker no this is not the same problem, my problem is that the plus and minus buttons don't update the quantity, but they do update the total. sorry for not adding a screenshot, I thought i did but somehow it did not upload. here another try:

I have a problem with updating the qty in the shopping cart when using a custom field. Steps to reproduce: Add a text field for a product in the customization section in the admin Save the product and go to the product page In the product page at the bottom you an enter a custom text and click save Add one or more of these customized products to the cart Now on the cart page click the + in the qty column The cart totals are updated but not the input field for the customized product. Also the line above with the quantity is not updated. Regards, Bart

@MockoB Hi @MockoB Thanks for the advice, but this is not the solution when you want to have also other languages then the default one. The main language is already indexed (SEO) without the language parameter. With multiple languages the default language will also be in the URL. Sure you can create a rewrite rule, but I would prefer the solution proposed by the topic starter.

I'm also interested in this. @atolodas can you post your solution to remove the language indicator from url's related to the default language? Thanks! Bart