the.rampage.rado

Merchants can always upload 1px transparent blank images if they only want graphics for only some of the categories.

The team is working on a surprise. When they are ready, it will be revealed. 🙂

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.

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:

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?

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.

Here is my config on php 8.1 and litespeed:

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.

It's active. Go through the branches and see what is cooking underneath. 🙂 And there are other BIG projects that are not on github but they took long time to develop.

There is a bug in thirty bees or the core updater that not every time the update runs define('_TB_BUILD_PHP_', '8.1'); in settings.inc.php is updated. It is not critical and you can manually edit this if you're sure the update propagated and your shop is running OK. This isssue was spotted a while back and @datakick advised that it can be fixed that way but nobody tracked down the issue so it's still present for some users in some scenarios.

Currently edge has no pressing bugs (in fact it has quite lot of work done since 1.6 in terms of bugs and small new features). If you have a test installation I would strongly recommend updating there to 1.7, see if it's working with php 8.3 (it should work but third party themes and modules might have a problem) and then update your production after you've made a working backup of it (files structure and db). I use edge on my production and I can't remember when was the last newly introduced but I noticed in my daily work. But thirty bees 1.6 would also work on php 8.3 (with few more deprecation warnings which should not be conserning) so if you only want to make your install work on php 8.3 I would recommend to play with only one variable - update your current store and make it working robustly on 8.3 and only then update it to edge if you see any reason.

Could you try and follow this procedure and tell us if it makes any change. At this very moment if you're updating to version 1.6, the same version should be in your BO. If you update to edge channel your BO should show 1.7 (which is currently not released as final version). When you switch between php versions you update only dependencies, the core is not updated.

The module in github from above is for thirty bees and it works flawlessly.

Not all stores use google accounts. 🙂 Turnstile is separate service from Cloudflare. There is no need for your store to be behind it to use Turnstile. Yes, account with them is needed but I advised for this module as it offers smoother flow for the real customers imho.

https://github.com/eschiendorfer/genzo_turnstile Do you have this module for turnstile in FO? If not, I highly recommend installing it and checking if the bots will stop.

As I said in the SQL manager, you are using there are forbidden statements or nested queries, etc. The export functionality in Customers is prepared query that does not run through thirty bees' SQL manager. As DRMasterChief said - if you have tool at hosting level similar to phpMyAdmin and you're confortable using it - do so but always keep a fresh copy of your db so not to end in a bad situation (only one deleted column in this table can brick your shop). You want a list containing those columns? SELECT c.id_customer, c.id_shop_group, c.id_lang, c.firstname, c.lastname, c.email, c.newsletter, c.date_add FROM ps_customer c; Of course edit the table prefix to match yours.

The SQL manager is heavily restricted in the operations it can do to limit exposure of the DB to bad actors. Give us the query you want to run so we can check for a better version.

Yes, the best one https://www.getdatakick.com/ Bonus - you can use it for far more than that.

https://www.getdatakick.com/ The best solution for any data feed for thirty bees.

Yes, I would start troubleshooting with your hosting first or the person that is maintaining your server. Because they have made some changes recently and we're here just guessing. In general if the thirty bees settings work - they work. Most of the issues are changes - of the merchants or hosting environments. It's not necesary an account/password issue - it might be some additional configuration of the mail server regarding transport/security.

Edited vulnerable information from your link. Did you use php8.2 before? Is it happening for every email sent out?

Sorry, now I remembered that if the generator tag is present core automatically changes it to thirty bees from one of it's classes. You found the solution - just remove it, that way core does not play with it. Regarding the top line look for Block Links module - it is reposnsible for adding links in the header top bar. The module Block Top Menu is the one with the drop down menus. Everything above it is header teritory.

<meta name="generator" is used to identify the CMS under the website (for noobs). You can safely remove the whole tag if you do not wish to advertise thirty bees. In your example it does nothing (brings no SEO).

Title comes from SEO URL settings - adjust your meta title for index. Generator tag is located in header.tpl of the theme you work with. Note that if you edit Niara's header file it will not be updated for Community. After that, go to Performance and clear your caches. Both mentions should be gone.