All Activity

Hi @nicponim We've added your site. Nicely done, thank you 👍 https://thirtybees.com/powered-by-thirty-bees/shops-using-thirty-bees/

To clarify, we do have full time employees. Some of us are volunteers that are working on TB part-time. The point is that we require additional support to have more full time employees to make TB better and deliver additional features faster.

TB should invite more to their project, over time workload increases. There are volunteers here.

I wonder how our paying shop customers would react to the excuse of: Hey, I work part-time on this shop and I am alone. Sorry for all that didn't go well. I don't think that's the right attitude. And I want you to succeed. I'm not being critical to be mean.

Was funktioniert mit dem Silberseiten modul nicht?

Was Shoprunners betrifft, kann ich empfehlen, dort einfach ein ticket zu eröffnen oder gar durchzurufen.

I am grateful to hear that you are working on the most important additional functions merchants need in my opinion, like Mollie, PayPal etc. But there again is the promise, "somewhere in the future". If we do a search on Mollie alone in this forum we might find hits about this promise that go back from the Corona time. Me, as a wanna be merchant, I can't plan with promises vague like that. I need to know if I can use this until e.g. Black Friday or what ever. I have to plan ahead, like you, and I have to rely on basic functions. Roadmaps with specific timelines have become extremely important on the internet and the times we live in.

Ich wechsele das Shop-System und wohl vor dem Stichtag. Daher vorerst keine Beiträge von mir. Sorry!

Good work! Sharing is caring! 🙂

Hi everyone! For the last few years I’ve been using JoliSearch module v4.3.28. It’s been a staple in my store, but as my catalog grew to over 10k products, I felt it was time for something faster and more precise, especially for technical search terms. I’m not a hardcore developer, but I’m passionate about making my store run better. 😊 Why replace JoliSearch? JoliSearch has several limitations today: It is no longer actively maintained. Search relevance is difficult to fine-tune. Loose matching often returns hundreds of results. The first visible results are not always the most relevant. Users may leave the store because they cannot quickly find what they are looking for. In my case, searching for a popular product type returned over 500-800 products, many only partially matching the intent. That creates noise instead of helping the customer. For technical stores (industrial hardware, connectors, cables, IPC systems, etc.), this becomes a serious UX and conversion issue. Why Meilisearch? Meilisearch is a modern, open-source search engine designed specifically for high-performance, real-time search experiences. https://github.com/meilisearch/meilisearch Key characteristics: Index stored in RAM --> extremely fast response times (often 1–5 ms). Built-in typo tolerance and smart ranking. Simple and clean REST API. Lightweight and easy to self-host (currently running on same VPS as my store). Much easier to tune than older search modules. Native support includes: Synonyms Custom ranking rules Faceted search Filtering Typo tolerance controls Vector search (embeddings support) Automatic typo handling Meilisearch automatically handles common input problems: Minor spelling mistakes Missing hyphens (e.g. “usbc” vs “usb-c”) Word order variations At the same time, it allows strict control for technical catalogs: Disable typo tolerance for SKU/reference fields Limit the number of allowed typos depending on word length Keep technical codes exact (e.g. 81271, CA-SASA-12CU) This is extremely important in stores with many product references and model numbers. Dynamic suggestions & smart autocomplete The module already includes a live search endpoint and basic fast autocomplete. Further improvements (some already implemented, others in progress) include: Real-time product suggestions with image, price, manufacturer, and reference Intelligent grouping (products, categories, manufacturers, feature values) Query preprocessing for better intent detection Smart result limiting to avoid overwhelming users Even in its current state, this approach can significantly reduce search exit rates compared to classic result pages. AI integration – OpenAI embeddings & hybrid search One of the most exciting aspects is semantic search. Meilisearch supports vector search, which allows: Storing product embeddings Performing similarity-based queries Combining keyword search + semantic similarity (hybrid search) Using the OpenAI Embeddings API (or local embedding models), we can: Generate embeddings from: product name, technical parameters, categories, descriptions Store them in Meilisearch Enable natural language queries This enables: “Cable for powering laptop via USB-C 100W” “Splitter for two devices” “Industrial ethernet connector” The goal is not to replace keyword search, but to enhance it. Current status of my module After short initial testing, the results are very promising. Already implemented: Custom index (products_pl, products_eng) Batch reindexing (500 products per batch) Live progress bar in BO Live search endpoint Synonyms editor (graphical table UI) Automatic JSON generation for Meilisearch settings Query preprocessing for better intent detection Matching strategy control (strict vs fallback) Monitoring estimated result counts (to avoid result explosion) The improvement in relevance compared to JoliSearch is clearly visible, especially in edge cases e.g. “Y-type cables”, where search behavior can now be precisely controlled. The target is a search interface that behaves more like a modern SaaS-powered discovery engine rather than a traditional e-commerce search box — fast, relevant, visually structured, and intuitive for users (as shown in attached screenshot) Has anyone experimented with Meilisearch in ThirtyBees yet?

with a busy store that's quite hard to do, though. We have an installation with average of 1M daily requests, that's hard to comb though manually. You can install some software to detect anomalies, but that's it. When you find an infection on your store, you know from the file modification date when it happen (unless the script changed it, but in my experience they rarely do), so that can help a lot. You just need to detect it and still have access logs

And check every day.

Yes, if this code exists in your tpl files, it means your store is already infected. But the fact that it isn't present doesn't mean your store is not vulnerable to this attack. We don't know about any vulnerability in the core that would allow attacker to modify/write to tpl files. We regularly check CVE database for prestashop vulnerabilities, and look for those that are relevant to ps16 codebase (so they are relevant to us, most likely). Again, that doesn't mean that they don't exists, we just don't know about any at the moment. But there were some that we have fixed in the past - running very old thirty bees versions is not encouraged. Most of the time the culprits are third party modules, usually those that allow uploading files (images usually) and do not properly sanitise inputs. That may allow attacker to upload php files instead of image, and then they have complete access to your entire store. Thankfully, you can use core updater module to check if any of the core files have been modified. If your store is infected, you will see it there as well. If your store is infected, it's not enough to just remove the infection. You need to find out the back door that was used to install the infection. That can be quite hard. Your server access logs can help a lot, so keep a few months of them if you can.

They do outline the script code to look for. I just searched my website via f12 and then looked through the website code via MS Code and didn't find this expression anywhere, so I assume that I am not affected. " <script>(function(){var x=new XMLHttpRequest;x.open('GET',atob"

Bonjour à tous, Nouveau membre de la communauté thirty bees, je m’intéresse de près à l'optimisation des performances de vente. Je suis le fondateur de Funnelsflex, une plateforme dédiée à la création de tunnels de vente haute performance. Je remarque souvent que beaucoup de marchands perdent des clients à cause d'un parcours d'achat trop complexe. Selon mon expérience, simplifier le "tunnel" de vente peut augmenter le taux de conversion de plus de 20%. Je serais ravi de discuter avec vous de vos stratégies : Utilisez-vous des landing pages spécifiques pour vos publicités ? Quel est votre plus grand défi en marketing cette année ? Au plaisir d'échanger avec vous et d'apprendre de vos expériences sur thirty bees ! Cordialement, L'équipe Funnelsflex

The standard procedure in Prestashop is to release beta versions with thousands of bugs and security vulnerabilities for download as stable versions, and then fix these bugs in dozens of subversions. If stores do not update the engine and modules, they get hacked. There was a security vulnerability in PS 9.0.2, which was patched in the latest version 9.0.3. The basic order completion module “ps_checkout” used since PS 1.7 also had a vulnerability Here are all the security vulnerabilities detected in Prestashop and its modules: https://security.friendsofpresta.org/

They didn't disclose attack vector - we don't know how those shops were infected with this malware. Without that information we can't really say if thirty bees is affected or not.

They posted a link as well You can also check this page for further details on the situation.

Is this all information they gave? No technical details?

Had this in an email from Prestashop. Is it an issue for Thirtybees? <——————————————————————- We have recently identified a security threat affecting some online stores within the PrestaShop ecosystem. A malicious script (“digital skimmer”) has been detected and may have led to the theft of customers’ payment information. This malware operates by replacing the legitimate payment buttons on the checkout page with fraudulent ones. When a customer clicks on one of these fake buttons, they are redirected to a counterfeit payment form designed to capture their bank card details. At this stage, we strongly recommend that you contact your PrestaShop expert agency or PrestaShop Support as soon as possible to perform a thorough security check of your store and ensure it has not been compromised.

Hi Vincent Thank you for your post and for your support. We are aware of the issues of communication, lack of a clear roadmap, the improvements to the premium modules etc. We will have a discussion with the team and will be posting about our roadmap in the future. For now however, I can reveal that we have been working on updating Mollie as well as PayPal. However, with limited resources, this has proven to take longer than expected. But we're getting there and there will be a release with those modules in the future. Also, I will discuss the outdated shipping modules with the team to formulate an action plan. Regards

No not really, it inreases the size of the page slightly but using pagespeed to test it seems to improve performance. Have you had issues?

I see that you use Rocket loader. Do you notice any issues with it?

Thanks 🙂 Spent a lot of time optimizing the site for speed.

Advanced parameters--> Logs --> and decript the long string.