wakabayashi

15959#0: *1869971 upstream sent too big header while reading response header from upstream Found now this in the logs. Which clearly indicates, that you were right @datakick. What confuses me a lot: he has apache selected, so why is there a nginx error? I contacted the webhoster. As it is shared, they refuse to increase any values. Is this normal? Does it mean, that thirtybees and shared webhosting is not really an option? I mean personally I have a dedicated server for multiple reasons, but I always thought, that it's possible to use shared hostings as well. What is your experience with this? Is this hoster total shitty or is it kind of normal to get problems with it? I noted, that it's not so easy to go the next step after shared webhosting. Let's say you pay 2-15$ for shared and often 80$ or more for private managed server. An unmanaged server is no option for 99% of merchants. I see a lot of vps/cloud stuff, but often this is not managed as well. Am I missing something or is it not so easy to get something managed for 35$, that is better than shared webhosting offers?

If this was possible at PS 1.6, then there is some point in your request. I am not totally sure, if it was and if it was intended... https://devdocs.prestashop-project.org/8/modules/concepts/module-class/#name But ok lets get productive. What is the problem in renaming them? I understand that this is no option for a merchant, but I am asking YOU as a DEV. Which modules are you actually talking about, cause in my years I have never seen one with capital letters...

Not worth the time 😅 Sorry, but if you are a module dev you have no reason to use uppercase. It's just not clever. Exactly as naming your module generic "paypal" is also not clever... Luckily I read at the beginning of my coding "life" the book from Fabien Serny about prestashop (modules). He explained this very well... That's why all my modules have prefix "genzo_". @musicmaster Are these really the main issues you have with tb and ecommerce in general? I mean then you are the luckiest dev/merchant around here.

Thanks to @datakick, who submitted a PR and improved some minor issues! In general this module works great for me to block spam. Personally I have none at all, right now. So it was time to make an official release of v.1.0.0. https://github.com/eschiendorfer/genzo_turnstile/releases/tag/v.1.0.0

Theoretically no problem. It's a question of the theme displaying the stuff...

@datakick any idea why this could happen? The server is using cloudflare. I was logged in on his site. Then logged out. Now wanted to log in again. Got the 502 error. Deleted cookies. Login/Logout works without any problem. Unfortunately I didn't test after the 502 error, if I was actually logged in or not 😞 Edit: Somehow I could get the error again. But no idea how exactly. Only worked once to recreate. Either it has something to do with checkout. There I could imagine mollie or loyalty. But both a bit unlikely. What I much more suspect: Could it be, that a deactivated captcha module causes it? If a module has overrides but is deactivated. Are these override still active!? I mean technically I would be surprised, if they aren't. But I have never thought about it...

Ja. Ich kann das bestätigen. Es ist bei mir auch passiert. Dann Cookies gelöscht und jetzt kann ich es nicht mehr reproduzieren. 🙄

Eventuell brauchst du folgendes Modul: Mail via swiftmailer v1.0.0 - von thirty bees

You are right. But ok that's the wrong thread to talk about it. See my new post in:

As some may have seen in another thread. This project is somehow stuck. As I invested weeks of work and it's fundamental functionality for the future of my shop, I won't drop it. But if it doesn't make it to the core, I have to develope on a highly customized version of tb (70 files are changed). Even with git rebase this is kind of a pain and since I am going to use it in all my modules. All my work, won't be compatible with core anymore. It will mean the end of genzo_krona and my contribution for core stuff. The only solution to this would be, if the core is changed in some way: My alpha version is further integrated as intially planned in collaboration of community, datakick & me. Tb implements the same/similar functionality themselfes Both seem very unrealistic to me now. The first one is basically where we are, but it doesn't go forward at all. The second one: why would you do that, if I have already done 80% of the job? Yesterday I had suddenly a third idea. Maybe it could be implemented, if I (& maybe others) pay for the hours, that Datakick need to invest to make it more robust. But nor do I know if it's realistic, nor do I know if it's in my (companies) interest. Probably depending on the amount. 🤑 Maybe that's more about @Smile than @datakick!? Cause I guess as smile is paying, he decides on what is worked on (kind of understandable). And probably webp support is not on high priority for smile!? Otherwise it is, what it is 🙈 Live goes on a for all sides 🤗

Unfortunately this is completely stuck. I kind of developped an alpha version and wanted push it forward with the help of datakick and some testers. But probably datakick was scared of too many issues in the alpha version or the whole project isn't of interest for tb. So there is no progress at all since months. And this is a big issue for me: It's very complex to code this part and I already forgot some stuff. So with every week it takes more engergy to get back to it. I really need this. For my new theme. I wanna have a clean/fast website with webp images. But I also want it for multiple modules. I invested weeks of work to make the alpha... I won't drop it. Today I wanted to do a bleeding edge update. But in my case this is no more a one click thing. I have to rebase my branch with 70 changed files. This is kind of horrible to do regularly. Hopefully I can test tomorrow, if it even works as hoped. But this means in other words, that I am working on a version that is quite different to the core. It's not possible to solve this with overrides or so. As long as this is the situation my contribution to tb will tend to zero. There are only two solutions: Either my initial plan with my branch is continued and merged in a decent amount of time. Thirty bees solves a lot of the image system themselfes and my whole rewrite becomes kind of obsolete. IMO both are very unlikely. So for now I try to go my own way, as good as possible 😊

Sure. There is no plan to switch the software. 🙂 I am just in a dead end atm and it's hard to find out. So I reduce all (possible) workload around it. And I don't like, if people put hopes on something, that never will happen, so I prefer to inform about it.

Unfortunately I have to tell, that I will drop development of genzo_krona. As users of this module surely noticed, I didn't work hard on this for a couple of years, but I always believed myself, that one day I get back to it and fix php errors and improve it in general. In recent weeks & days I had to understand, that it's not realistic. With my new theme I will use a lot of ajax stuff, that won't work for other themes. Surely this could be handled, but it's a lot of additional work 😩 My Todo-List for my own shop gets longer and longer... In addition it takes me days to update my store to bleeding edge, since I want to use a huge rewrite on image system. I will use this rewrite on krona and all my other modules. But this would completly break the module as long as the image rewrite is not part of the core. So I don't see a serious chance to drive the public version of krona forward and it's better to draw the line. 🤗 If any dev wants to continue this module, I am completly fine with it. You can do whatever you want 👌

While I make actually pretty good progress on my own theme, I want to make official, that it won't ever get published. I always stated, that it's unlikely, but in the recent weeks/days I understood, that it's completly unrealistic. Just wanted to tell as I got PMs from time to time about the state of it. So please don't wait for it. I guess Niara or Cisero is the way to go. 😉

Das kommt drauf an wie die Übersetzungen implementiert wurden. Eventuell erscheint es auch unter Übersetzungen > Theme. Sonst zeige mal wie die entsprechenden Textstellen in den TPL files hinzugefügt wurde.

I see. I believe this idea never came to my mind 😅 Sometimes it's good, to be not too clever 😏

Does this block subqueries or is this something different? I am talking about a SELECT in a SELECT...

Die Zeiten als ich das gratis gemacht habe, sind vorbei. Ich bin ja kein Dev, der als Dev leben muss (deshalb habe ich früher auch mal was gratis gemacht). Sondern bin Dev, weil ich die Webseite in unserem Betrieb komplett programmiere.

🤣 immerhin mag ich deinen Humor. Frage: Ist deine Muttersprache überhaupt Deutsch oder ist das Translator? Ja sich schützen, ist allen Lebensbereichen empfehlenswert 😅

Why would this be helpful in the backoffice? Do you have attacks there? I never had... Your url shouldn't be public anywhere, so this sounds a bit unlikely to me. No idea, about the second one. Tbh I coded this module in a few hours/days. It was very basic but flexible. It solved all my problems with spammers up to now. But if there is really more interest here, I can improve it ofc.

Bei allem Respekt, aber ich glaube nicht, dass du viel über die Thematik weisst...

Spätestens, wenn du mal Opfer einer bekannten Sicherheitslücke in einer alten Version wurdest, weisst du warum... Ein DEV kann das relativ schnell fixen denke ich. Tendenziell würde ich sagen 2-3 Stunden Arbeit. Früher habe ich solche Sachen auch Mal (nahezu) gratis gemacht, aber die Zeiten sind vorbei 🙃

Ja, das zeigt halt, dass PS 1.6 langsam aber sicher ausstirbt. Du kannst natürlich einen DEV engagieren, der die Warnings behebt oder du kannst einfach damit leben, solange die Funktionalität noch gegeben ist.

Viele Fehler kommen doch von den Modulen: mollie und trustedshopseasyintegration

Ok, I came back today. When do you get this warnings? Are they still showing up? I believe, they only happen, when the configuration setting was never set.