wakabayashi

Sounds clever 😅 👍

Hm solche Dinge sind immer etwas komplex. Sind das die einzigen Produkte, die du verkaufst? Falls du nicht hunderte bzw. tausende andere Produkte hast, würde ich nach einer Lösung streben mit mehr Produkten und weniger Varianten/Optionen.

Pretty sure, otherwise all links would be broken or not?

Yeah, this is kind of logical. The problem is not the source files or the thumbnails. It's the rewrite.

Then I would bet, that your htaccess or nginx configuration is wrong. As the product images changed the url path. I made this to have a clean structure in urls. My nginx looks like this: # Rewriting for images pretty url location ~* \.(eot|gif|ico|jpg|jpeg|otf|pdf|png|svg|swf|ttf|woff|webp)$ { rewrite ^/categories/([0-9]+)/([^\s/]+)\.webp$ /img/c/$1.webp break; rewrite ^/categories/([0-9]+)-([^\s/]+)/([^\s/]+)\.webp$ /img/c/$1-$2.webp break; rewrite ^/categoriesthumb/([0-9]+)/([^\s/]+)\.webp$ /img/c/thumb/$1.webp break; rewrite ^/categoriesthumb/([0-9]+)-([^\s/]+)/([^\s/]+)\.webp$ /img/c/thumb/$1-$2.webp break; rewrite ^/manufacturers/([0-9]+)/([^\s/]+)\.webp$ /img/m/$1.webp break; rewrite ^/manufacturers/([0-9]+)-([^\s/]+)/([^\s/]+)\.webp$ /img/m/$1-$2.webp break; rewrite ^/scenes/([0-9]+)/([^\s/]+)\.webp$ /img/scenes/$1.webp break; rewrite ^/scenes/([0-9]+)-([^\s/]+)/([^\s/]+)\.webp$ /img/scenes/$1-$2.webp break; rewrite ^/scenesthumb/([0-9]+)/([^\s/]+)\.webp$ /img/scenes/thumbs/$1.webp break; rewrite ^/scenesthumb/([0-9]+)-([^\s/]+)/([^\s/]+)\.webp$ /img/scenes/thumbs/$1-$2.webp break; rewrite ^/stores/([0-9]+)/([^\s/]+)\.webp$ /img/st/$1.webp break; rewrite ^/stores/([0-9]+)-([^\s/]+)/([^\s/]+)\.webp$ /img/st/$1-$2.webp break; rewrite ^/suppliers/([0-9]+)/([^\s/]+)\.webp$ /img/su/$1.webp break; rewrite ^/suppliers/([0-9]+)-([^\s/]+)/([^\s/]+)\.webp$ /img/su/$1-$2.webp break; rewrite ^/products/([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.webp$ /img/p/$1/$1$2$3.webp break; rewrite ^/products/([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.webp$ /img/p/$1/$2/$1$2$3$4.webp break; rewrite ^/products/([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.webp$ /img/p/$1/$2/$3/$1$2$3$4$5.webp break; rewrite ^/products/([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.webp$ /img/p/$1/$2/$3/$4/$1$2$3$4$5$6.webp break; rewrite ^/products/([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.webp$ /img/p/$1/$2/$3/$4/$5/$1$2$3$4$5$6$7.webp break; rewrite ^/products/([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.webp$ /img/p/$1/$2/$3/$4/$5/$6/$1$2$3$4$5$6$7$8.webp break; rewrite ^/products/([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.webp$ /img/p/$1/$2/$3/$4/$5/$6/$7/$1$2$3$4$5$6$7$8$9.webp break; rewrite ^/products/([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.webp$ /img/p/$1/$2/$3/$4/$5/$6/$7/$8/$1$2$3$4$5$6$7$8$9$10.webp break; allow all; try_files $uri $uri/ /index.php?$args; }

https://crew-mgr.com/shop/ is your shop, right? I really don't know, but these images are just loading normally for me!? 👻 Edit: or is this your live version and you have another version?

While this is very stressful, I would still first try to find out, where the security hole is. Otherwise they might be around soon again.

Just in the core updater, where you updated to bleeding edge...

How does this look like on your store?

I am not totally sure, how the update works technically. But have you done the DB updates as well? 🤔

Thanks for your work, guys! Still very happy to use thirty bees. Obviously I support the project with the monthly subscription and with paid support hours. 😉 I hope, I can find some time for some useful PR on github ⏲️ But I am very busy with my own work, so atm the financial support is easier 🤑

I basically click the button: Sometimes I seem to be logged in. Sometimes not. 🤔 About the routing/redirect. I am not so sure. My nginx settings don't contain anything special with "connect", nor do I have modules that are looking for this. At least thats my feeling.

Is this https://accounts.thirtybees.com/connect broken? I just get: It's correct to login with forum credentials, right? Cause the credentials form the store, don't work...

When will you update the list? 🙈 BTW: I am finally back on bleeding edge 🤩

What kind of errors do you get? When I open your link, it seems to work fine. Maybe your webhoster forced you to update the php version and this caused some issues. This is just my random guess, when somebody claims "I haven't done anything at all". If you need help, I normally would buy offical support hours: https://store.thirtybees.com/. I buy hours there too and I am a coder myself 😅

Uh two different installations 🥵 I think it would be possible, but much more complicated.

Yes it's possible. At least I think so. I have started this project (for my company), but not totally finished it. In general I looked for all db tables with id_shop or similair columns. Then I wrote some helper functions, how to merge them. Cause sometimes you want to hold the information, sometimes just delete it. Example: ps_orders you surely want to hold, so you just rewrite the id_shop from 2 to 1 ps_product_lang you want to check, if the product was already existing in shop 1. If yes, you probably just want to delete the rows for shop 2, otherwise you probably want to rewrite 2 to 1. All this worked fine for me. But honestly, I haven't finished the project yet. In my BO I still have the 3 shops. But not because I fear any issue. I just didn't have time to finish this project cleanly. Maybe @datakick can shortly answer, if he sees any potential problem with my advise!?

Puh, da hat mich mein Gedächtnis im Stich gelassen. Aber interessanterweise sagt auch Petr, dass die Fehlermeldung keinen Sinn ergibt. Am besten kommentierst du wohl auf Github, dass du den Fehler immer noch erhältst. Ich frage mich, ob ein Bild eines Produktes defekt ist. Kann ja irgendwie kein Zufall sein, dass es immer an der selben Stelle abbricht.

Noch nie gesehen. Bin mir auch nicht so sicher, ob das sinnvoll übersetzt wurde. Welche Version nutzt du denn?

You can't remove them. They should go away over time. But I have entries in search console, that were fixed a year ago (with canonical and so) and google still tries to crawl the old version. The search console even tells, that there is no referring page to the url they want to crawl 😂 🤦‍♂️ It surely helps, when you have the bleeding edge AND the robots.txt disallow. Personally I think this has no realy influence on SEO, but it helps to clean search console. With a clean search console it's simpler to find real issues...

As the robots.txt solution is also not perfect, I have opened an issue on github: https://github.com/thirtybees/thirtybees/issues/1844

Could you tell more about the reasons?

I am a day zero user of tb. It looks like the best deicision I could have made. While this project had ups and downs, it's still alive. There were so many huge improvements. Things may take longer here, but are done in a high quality way: Core updater (this is fucking awesome) Extraction of dependencies New image support (webp) Bug fixing / php support I am sure @Eolia has his reasons, why he is doing this on his own. But as I can see, his project is not on github. Which very likely means, that he is really doing this his own. For me that would be too risky.

Right. The module rewrite is not yet done and it might need some tweaks in the core again. Some modules even use their own way of generating images. But one of my goals was, that in the future, it should be super easy to implement image support in a module 🙂

Diese Dinge sind alle recht komplex und schwer von der Seitenlinie zu beurteilen. Funktioniert BO und FO nicht mehr? Hast du den Debug mode eingestellt? Wie lautet, dann der Fehler? Eventuell siehst du auch in den server logs etwas zum Fehler.