The Label is still "confirmed" and not "fixed", therefore they haven't fixed it yet.
Posts by GodMod
-
-
What is missing there: after following the article, there are SEO options where you can enable the seo friendly URLs.
-
No, this is built-in and there is an option in ACP for this.
-
You may don't have it enabled at your WSC installation?
-
The file phpunit.xml itself is not vulnerable, only the phpunit framework, which is not delivered with the libraries.
-
What exact problem you have with the bots?
-
Still Font Awesome 4.7
-
But this seams to be a problem of your Woltlab.
-
Just insert your domain to Twitter, without any query params. The last part of your first image describes how to.
So "https://yourdomain.com".
-
-
Why are you using an API which requires keys? Would the oembed API not provide all neccessary information?
https://www.youtube.com/oembed?url=https://www.youtube.com/watch?v=fzA8Yn80DBo
-
Maybe because you don't use a SMTP server for sending emails and your email provider flags emails coming from PHP as spam.
-
Woltlab tries its own software here before the new version gets released. So it is normal that this page is one version ahead.
-
i dont think that you can add groups into groups.
-
Recaptcha 2 is more easier than version one. Normally, you just have to do one click. If google is unsure, you have to select images like "Select all images with cookies".
-
Aslan disliked it
-
Yes, and woltlab uses standard. They test ist, against different forks and versions of mysql server. MySQL, Percona, MariaDB. So now comes an update of MariaDB, and it does not work anymore. All other forks and all other versions work. So where is the error? Yes, in MariaDB. What should they do now? Yes, file a bugreport at MariaDB. Should they do something different? Well, maybe can take a look for a workaround, but that's not really their task, if they are using standards (and SQL is one), and the other software like MariaDB has problems with that. This is not a fault of Woltlab. Fullstop.
It's the same with HTML. You can use CSS and HTML Standards, and it will look different in all browsers, because each browser has a little different implementation of how they make something or how they will show something. But is this a fault of WoltLab? No. They are trying that everything looks the same on all Browsers. But e.g. the IE changes his engine with a new version, and show buttons as checkboxes, is this a fault of Woltlab? No.
-
Yeah, I noticed that fact many times here, and I really cannot here "the other" argument anymore. Or if >10 people say that he's not right, he will still ignore that fact
-
WoltLab can tell me it's MariaDB until they're blue in the face or until the cows come home. But every development I'm using has no issue with MariaDB. None whatsoever. So I would very much like to know what distinguishes them. The argument that they're using real “Prepared Statements”, doesn't hold because IPB and XF are using real “Prepared Statements” without issue.
What is this for an argument? Software differs. Everyone is doing something different, the Queries might a bit different and so on. And that's the reason why something works on other systems, and something not. But you are always coming with "the other do" or "it works for the other". But Woltlab is not the other. They must do something different because otherwise they would only be a copy of the others. But it seams that you cannot accept the fact. You really should write your own software to be satisfied, because you will never be with any software you are using.
And there are many reasons why other Prepared statements work, and some not. But what should Woltlab do? Rewrite everything, so they using the exact thing others do? Which might be maybe more complex? Only that that's an workaround for the error of a software that is not the reponsibility of them? I don't think so.
-
And if you make it private? So nobody can follow you etc?
