All Activity

My problem was an override I had done that caused the problem. Make sure you check for that.

Did you follow the guide from page 1? All entities set correctly? Here is an example from Warehouse: Have you regenerated all thumbnails with the new settings down the page: Did you regenerate your htaccess and does it include the images as: .... RewriteRule ^categories/([0-9]+)(\-[_a-zA-Z0-9\s-]*)?/.+?([2-4]x)?\.(avif|gif|jpeg|jpg|png|webp)$ %{ENV:REWRITEBASE}img/c/$1$2$3.$4 [L] .... RewriteRule ^products/([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?/.+?([2-4]x)?\.(avif|gif|jpeg|jpg|png|webp)$ %{ENV:REWRITEBASE}img/p/$1/$2/$1$2$3$4.$5 [L] and so on...

Configure the entities first and after that if you're using custom theme it might be coded to use hardcoded links to the images, not the one supplied by the core. After the image rewrite the links are different.

Was any solution found for this? Or what triggered it? I'm experiencing a situation where, after updating to version 1.6, the thumbnails in the category previews are populated with the camera icon when there's no actual image. Previously, nothing was displayed there at all, just a blank white space. I have the .htaccess files from versions 1.5.1 and 1.6 for comparison, but of course, I'm stuck.

Thanks for the info. I knew about the other topic but couldn't find it right away (the one from the link). However, my experience is different; the camera icon is displayed in the category overview, but it's white in the article itself.

thank you @the.rampage.rado!

In 1.6 there was a rewrite of the whole images section thanks to @wakabayashi and @datakick. In order to update to 1.6 and later you have to follow this guide in the BO -> Images:

I have the same situation when I tried to move to 1.6.

I am struggling to add Google pay and Apple pay on my website, but it is not appears. Is there any other settings needed apart from enable the button? I am using PHP 7.4 Thirty Bees 1.4.0 Stipe module v1.9.4

As for a descriptive list of changes for version 1.7.0, it does not exist yet, because this version is still under development. This is a programming list of changes: https://github.com/thirtybees/thirtybees/compare/1.6.0...main Without knowing which module you are using to create these articles, it is difficult to say anything.

What is your experience with it? Did it sink your shops or you get lucky and win? My shops experienced vast volatility during 11-14th and right after that a huge swing down. Now I'm like, at least 50% down in impressions. All my vital keyword niches are messed up. It promoted shops that don't sell sporting goods but have a huge market in toys and junk items, it also boosted small, unknown sites that don't look professional at all. Since 1st of January I don't see any further volatility, but I'm stuck on those lower impression levels. "Luckily," January is always a low point for me during the year and I'm hoping a small update will pass around the end of the month. Of course - no blackhat stuff, all links are natural, nothing bad is made SEO wise. Simply a low number of external links and Google thinks you no longer need this first place and moves you to 38th position. What is your experience with it?

Just checking a year later to see if these errors have been fixed in the Bleeding Edge release so I can try it.

Hi Yabber, not sure about thirtybees 1.7.0 (can anyone tell the details for changes from 1.6 to 1.7 ?). My theme is well-programmed and stable, but at some point it will probably come to an end... but yes, i will try in the next days. Most important is to have the live-shop at php8.1 Now on version 1.6, it shows me the empty images (placeholder camera) for articles without a picture... hmm, so simple, but how do I change that?

Since you're already spending time on upgrades and testing, it's best to upgrade thirtybees to 1.7.0 (Bleeding edge) and enable PHP 8.3.

Yes, the direct jump to 8.1 isn't documented in the manual, but it shouldn't really matter whether it's 8.0 or 8.1... I'm very careful to use only absolutely necessary modules. This saves a lot of time and effort when such a change is needed. But i have some manually changes to some files (mostly theme-related for a good look). The modules and the theme I'm using don't seem to have any problems with PHP 8.1. I'll be monitoring the collect logs for a while now. All tests are still being conducted in the test system. If nothing unusual comes up, I'll make the same changes to the live shop.

If you build your install for 8.1 and any third party modules are running on it it's not big trouble. thirty bees is stable on 8.1 since years.

Hmm, okay. I see that `nd_pdo_mysql` isn't loaded under PHP 8.0, but it is under PHP 8.1 (and I can't change that while testing). Just so you know, I'm currently only changing the PHP version for a single directory (for testing purposes, there's a test shop in a subdirectory with a subdomain). I do this by .htaccess . Maybe this can cause the problem? So I have to switch from PHP 7.4 to 8.1 (which is rather unusual, I think).

Here is my config on php 8.1 and litespeed:

i am on a Litespeed server and i think nd_pdo_mysql is better for php 8.x ?

You have to run pdo_mysql. In order to quickly view if you do access AdminInformation controller in BO and append "&display=phpinfo" (no quotes), this will launch phpinfo where you can check if it's running. If not - turn it on and check again.

Hi everyone, I want to upgrade from version 1.5 to 1.6 (that's already done and went quite smoothly), and of course I also want to upgrade to PHP 8.0 and higher (I'm currently on PHP 7.4). I have activated nd_pdo_mysql in cPanel. However, I'm encountering the following error, and I'm stuck... Does this have anything to do with: https://github.com/thirtybees/thirtybees/issues/1600

hi. Over the past month, I've been having serious problems with a huge amount of spam carts (almost a thousand a day). Searching online, I found a module that permanently solved my problem. I hope it can be useful to anyone who, like me, continues to have this problem. The module is called ThirtyBees PS Block IP Spam Carts. You can easily find it with a Google search.

It is not just a matter of module compatibility with a given version of Prestashop. This module is based on the SaaS model and requires the “ps_accounts” module to be installed and the store to be integrated with Prestashop servers. Soon, you will have to pay a subscription fee to use these modules, and if you don't pay, Prestashop will be able to disable any modules it wants in any store it wants.

Funny that the absence of issues related to e_commerce is not a plus in the customer-group shop owners. Do shop owners need a forum where all kinds of issues are brought to light? One of the few forums where few real issues show. It is a sign of quality after all

it is important to do a follow up on orders when done over the phone.