wakabayashi

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.

I would guess, that your smtp settings are wrong. But I am really no expert on this and I personally use the email of my own domain.

The only real important error is the exception. This one needs to be shown and fixed. The imap_open() is trying to sync your email inbox with your customer service messages. But this function is anyway very shacky. I used it, but deactivated it some weeks ago as every second sync doesn't work correctly.

Na. When you click on "view" you should see something like:

You need to click on "view" on the line where it says "exception". I don't know alot about the current email system as it was changed a bit to reduce dependency. But do you have the module "Mail via swiftmailer" installed? Also pleace check your settings under "Advanced settings" => "Email". You need to scroll down to the sending options. There you find "Email transport".

What is Phenix? 😅

It's long ago that I worked on this. I personally don't even use the coins. But it was never inteded to work with FLOAT Values. So you you should try saving "1" instead of "1.00". Keep in mind, that (atm) I don't have time to develop this module any further.

It would makes sense to update mine from chesspoint.ch to https://www.spielezar.ch 😏

Für mich ist TB die Wawi ☺️ Was anderes packe ich nicht noch drauf 🙈

Ja sollte man eigentlich ändern können. Nervt mich auch immer. 😅

Yeah no spam at all. But honestly I have also implemented a new theme and 99% autospammers aren't been able to even reacht the contact form. The form is just loaded by ajax that helps a lot. But yeah turnstile does a good job as well. No idea. They say so 🤷‍♂️ Oh ok, cool. But I surely won't integrate this, as my spam problem is completly gone 🤩

Das Thema ist halt sehr länderspezifisch. Ich habe es mir so programmiert, dass wir in TB ein CSV exportieren und dies in einer einfachen Buchhaltungssoftware importieren. Ob sich das für kleine Firmen aber überhaupt lohnt ist fraglich.

I have similair warnings. Google is trying to crawl this controller=trigger urls. If I remember right, they are coming from the core. I added: Disallow: /*controller=trigger in robots.txt

It's not a big secret, what my store is 😅 https://www.spielezar.ch But as I said. I am not making a living as coder or theme designer 😉 I can not say, why no real theme designer is doing it.

I guess thats these are the numbers, where it's starting to be interesting. But how to get 500 users buying your theme? 🙂 I don't know much about the details as I am not living for designing themes. It also depends where the designer is from.

That's basically what I did. I don't remember how long it took me, but surely 2-3 years (with breaks involved). For an open source project with modules/plugins it is very hard to build a good theme. There is not only design, but also a lot of technical aspects (speed, seo and so on). A lot of merchants expect a theme to be 100-200$ and then they are fine for 10 years. Imo that's no more realistic these days. I see a lot of SaaS, that have a higher pricing per month...

Great! I am not yet on bleeding edge. But this sounds amazing for my purpose! Actually it's also kind of a shortcode usage 🙂

Is it somehow possible to get the controller name and id_entity by throwing an url? I want something like: function getControllerAndId($url) { // Use $url somewow $dispatcher->getController(); } I want to use this in a module... The idea is to recognize posted urls by customers in FrontOffice as product links and replace them. For example: www.domain.ch/category/productXY I want: Controller=ProductController id_product=352

This is a little confusing to me. Once there is jpg and once webp 🥵 But ok, as we can drop it anyway, we won't have this issue in future 👍