wakabayashi

That's right. This is one of the things, I was working on a few weeks ago. Unfortunately I got interrupted by other jobs and private stuff. But I will go back on this very soon 😏

With that unclear information, you will never get a reasonable answer... Please provide examples, details or links 😉 For jolisearch you would have to contact the module dev.

I guess, you have tested some stuff and have an old file on the server. Is this possible? If yes. I could imagine, that you have something like echo $variable or print_r($variable)

@e-com I hope, you are making progress on this 😊 I guess you have access to GPT-4, right? Is it much better in practice than GPT-3 or is it overhyped right now?

Ok finally I am getting back to coding / tb-work 🥵 Actually I agree with all your examples, but isn't my PR at least giving a bit more options to get accurate numbers? Nothing is worse than before, but instead you can at least create a simple system: 0.5% + €0.25 Before this was only possible for payments. Now it's also possible for shipping. In general we can argue till death, how much detailed settings we want to have in configs. Accounting can get complex, as I will demonstrate later in this post. IMO we should not try to become an acocunting software, but give merchants an approximation of their profits. In my example I calculate for all orders a profit and display it on the order detail page. Let me show you a (fictive) example: We use this now since 2-3 months. It's sick what we learned about our gains. Never thought that before. Not sure if there is any interest to include this in core. It could also be a functionality of a module. In ASM we have some kind of tracking. But you are right: it's hard to calculate a precise order profit, especially when prices are changing. When I was studying econmics it was also kind of a "hot" topic. Imagine such an process (it happens in my store): You buy product-x for 30€ from your supplier. You set the selling price to 45€. It's inflation and the supplier raises his wholesale price to 50€. - You sell your item for 45€ to customer 1. You reorder one item and set the selling price to 70€. You sell the item for 70€ to customer 2. What is your gain of the first order with customer 1? I don't know, what practice (and tax law) say. But the answer can be tricky imo. A lot of people would say, you made a gain of 15€. Ok then let's calculate the second order. This gain is: 70€-50€ = 20€. So total gain: 15€ + 20€ = 35€. I throw in, that you actually lost 5€ by the first order. Don't believe it? Ok let's imagine the same story like this: Same. Same. You react immediately and raise the price to 70€. Customer 1 doesn't buy the product now (it's too expensive in his opinion). You don't reorder. Same. What was the gain for the first order? Well its 0 as customer 1 didn't buy anything. What is your gain with customer 2: 70€ - 30€ = 40 €. Total gain: 0€ + 40€ = 40€. Oops 🙈 As I argued above: we lost 5€ with the first order 😅 Ok I admit: my story is also not always true. Third story goes like this: Same. Same. - Same. Now you say: fuck you supplier. I don't reorder with this wholesale price (as maybe nobody will pay 70€). What is your gain by first order? Obviously 15€. So your gain of order 1 depends basically on your decision, if you will reorder or not. Anybody is welcomed to bring up arguments against my point - it's in my opinion a very interesting topic. @datakick I saw now your comment on github. I have no problem to use such a system. I agree, that the idea of saving parameters with a time frame is a bit more clean and flexible. I believe it's main advantage is in backward compatibility. You can always change this values to improve your dashboard values. While I saw this as a disadvantage, it's an advantage (but only combined with the time frame ofc)! But there is currently no table, that can handle it, right? Let's keep the technical discussion on github. 😉

I don't use Mollie anymore, so I can't say 🙃

I don't know. I am also not sure, what this would help 🙈 As long as I am happy with turnstile/cloudflare I will support this module.

Do you have the folger \img\tmp?

Same here. No Spam since using this module 😎

Sorry for my late reply. Unfortunately I am very busy right now with internal stuff. I will reply to this in 1-2 weeks. Please keep it open till my answer 🙂

Yeah there is a lot of sceptism about AI. Probably rightly so. But what has it to do, if a merchant uses AI as a tool? When talking about text generation: either the text is good or not...

I don't think this will be that binary (yes/no). They also stated somewhere: as long as your texts are good, they have no problems with it. But if "good" means above average, you either have to use AI better than competitors or you should make manual corrections. I plan the latter. Always read the text from AI and rewrite it a little, so it gets even better 😏 What I also notice: I generate 5 texts from AI for the same product. In each text a like some parts and some I don't... Also want to say: these things can change so quickly. Each advise today can be wrong tomorrow. Maybe it takes only 2-3 an AI writes better than 95% of copywriters 😳

Thanks a lot for your explanation. I can feel you and I am very interested in your experiences in this field - keep us updated 🤗 We did this in the past. Sometimes you find a good copywriter to a reasonable price. But soon their prices raises as they get too many work offers. But you have to spend hours/days to find such a guy on a plattform like Fiverr. Others write worse than a 14 children. But ok now the game is anyway played differently 😅 This is the only thing I don't understand in your post. Where does the 5k tokens come from? I don't think, you want a description of 4000 words or so!? Does it just take multiple tries, to get a result back, that you like? Edit: Btw... Are you a merchant yourself? I always thought you would be a dev 🙈

Meta Title and Meta descriptions aren't always taken into account, thats true. Our site seem to have quite a good reputation at google and they take our input often 1 to 1. But actually that's exactly the reason why I want to start with such fields: they aren't that important. Category descriptions are read by real customers. So you have to make sure, that there is no bullshit in the text 😅 For me it would be too risky to take the GPT text 1 to 1 atm. I don't have any tokens yet. Do you have? Do you have an approximate value, what a category description text costs?

Will you make this module public? Atm I don't want to use it 100% that way (maybe for meta descriptions yes). Not having to start from zero, to using ChatGPT would be super cool 😀

I have had this idea too. But for our store it's not a top priority, that's why I never have looked deeper into it. I can only say, that I would do it, like you: saving the translation "normally" in BO and refresh when the main language is updated. Deepl is probably the best translation. So your plan sounds good to me 😉

This was my first idea. I thought, that size 1500 would be a benefit, but yeah this is probably a detail. My main point was, to prevent the scaling down of the actual object on an image. Both solutions wil work for this purpose 🙂

I am not totally sure, if I understand you right. My idea was something like $widthOfRetinaImage = min(2*$imageType['width'], $widthOfSourceFile); $widthOfRetinaImage = max($imageType['width'], $widthOfRetinaImage); So that the width is always between $imageType['width'] and 2*$imageType['width'], but no blurry happens. Was that your idea too?

I agree on your post. Your ideas are good. Some of them might be up to modules, others are part of the core. You are also right with this 😅

Hm but the image is scaled down in browser afterwards. I agree that scaling up (blurry) and then scale them down afterwards is very stupid. But not doing it means, that the actual object of the image becomes smaller. IMO this is worse, than the other... Here you see what I mean: https://thirtybees.genzo.ch/de/coffee-and-tea/Coffee/coffee-beans. On not so large displays, it's just having a lot of white ^^ Well ok, at least I know now, that I haven't broke it 😃

Still working day and night on this. Always find new stuff, that looks messy and can be simplified. Atm I have created a system, that even Product Images can be generated by Link::getGenericImageLink(). Image urls look like: /products/17-Niara_large/tea-cans2x.webp /categories/4-Niara_category/Coffee2x.webp /categories/thumb/4-Niara_medium/Coffee2x.webp Tests will show, if this is a bad idea or if its great to reduce code complexity. I believe, that way we will gain some new possibilities: We can quite easily give the merchants rewrite options for image urls In the long run we can (probably) add new image entites. This means that a module could use the core to generate thumbnails as well. But now something happened to me, which I need some feedback. Are retina images currently working? I don't use this setting on my live store, but played with it right now. Please check out the following to links: https://thirtybees.genzo.ch/products/19-Niara_thickbox/tea-cans.webp https://thirtybees.genzo.ch/products/19-Niara_thickbox/tea-cans2x.webp It basically adds just white space around the image (probably due to a not big enough source image). Does the current system work like this as well? Looks wrong to me, but I am not totally sure.

While trying to continue the rewrite and adding configuration selects, I noticed, that we have a general problem in image proccessing. Especially in this category controller. Cause normally when you upload an imageFile, you expect, that all imageTypes are generated for this imageFile. All entities do it like that. Only AdminCategoryController does missuse this concept: Here an imageFile upload is linked (hardcoded) to a specific imageType. I don't like this at all. And it doesn't make super much sense, that we have this on categories but not on manufacturers and suppliers (both missing link_rewrite btw). I will try to rewrite this, so that we generate all imageTypes for 'image' and 'thumb' in AdminCategoryController. If it works, it would also be no big deal to add a second image upload for other product listing pages as manufacturer or suppplier. My ultimate goal is actually to have a consistent proccess over all entityTypes. In a perfect world we would probably even have ps_image for all entityTypes (but yeah that's not gonna happen soon).

Btw try to upload both in jpg extension. Maybe there is an issue with png. Just to show, that I am not talking shit:

Well you are on 1.3 and I am kind of 1.5 tb version. That could explain some differences. I now tested it for my version with the new image system. As I told you, I replaced 'medium' with 'category_medium' (3 places). Afterwards I uploaded a thumbnail. I did nothing else. In my case it cleanly generated the file 6-category_medium.webp (yours is probably jpg) in 67x67px (as I set it up). So it all worked as expected for me. Anyway: If my proposal is not working for you. I think you have to wait for my rewrite being merged. Afterwards you should upgrade to the bleeding edge and you will be fine. I expect my rewrite being finished in 1-2 weeks. But the merge will take additional time as at the moment 56 files are involved. So in a good case I would say in a month we have this integrated. In the worst case: Datakick will refuse my PR 😅

Hmm. I can not test this right now, as I have seriously changed files on my testserver. Either you are "wrong" and it's more a caching issue or so. Or there is another bug. Imo there should be a file in "c" folder and with name "category_medium". But yeah probably it doesn't work in FO and maybe that's the reason, why you think saving doesn't work. Which theme are you using? Search for category.tpl and replace there 'medium' with 'category_medium' too.