For one second I really thought you were trolling me pretty hard. Then I found out that this method actually exists....wtf 
edit: Wouldn't it be possible to detect if the WCF is running with MySQL 5.5 or higher and then NOT execute
$text = preg_replace('/[\xF0-\xF7].../s', '', $text);
?
Like...
if(MYSQL_VERSION < '5.5.0') $text = preg_replace('/[\xF0-\xF7].../s', '', $text);or something
No, because the field type must be utf8mb4 and this is not the case. Furthermore, this method is used everywhere, where people can enter text, so the whole collate in the DB must be changed.
I found a suitable way to provide Emoji support for a year or so and it works great. However, i don't want to publish it, until i found a working way to make this work properly in Redactor (i already gave up on CKEditor support).
No, because the field type must be utf8mb4 and this is not the case. Furthermore, this method is used everywhere, where people can enter text, so the whole collate in the DB must be changed.
I found a suitable way to provide Emoji support for a year or so and it works great. However, i don't want to publish it, until i found a working way to make this work properly in Redactor (i already gave up on CKEditor support).
Redactor is not the problem, because there is another development that applies emoji support and they use Redactor for their editor. I believe the problem would be within WCF if there is indeed a problem.
What exactly isn't working with Redactor?
The problem is Redactor, but not Redactor itself. It's the BBCode-Replacement stuff, made by WoltLab 
However, i'm positive that i can solve this soon. Maybe, i'm just missing a little thing. We'll see 
But as soon as i solved it, i'll release two plugins: The Emoji support and a Fontawesome-Plugin.
It's the BBCode-Replacement stuff, made by WoltLab
This isn't the 1st time I've heard about the BBCode-Replacement in Woltlab being a problem. I think it should be rewritten or reevaluated, because there are other developments that use Redactor and they use their own BBCode without issue.
The biggest problem here is, that as a non Javascript expert, you rely on some documentation or real world examples (checking out the "built in" stuff isn't enough sometimes). But since there isnt any of these, you'll have to figure out things by yourself and that's, where i'm currently a little bit lost. Inserting that stuff into Redactor is working fine, but as soon as you switch the editor mode, the code is completely messed up.
I think it should be rewritten or reevaluated
It already get's rewritten for WCF 2.2, you can see the - quite extensive - changes already on GitHub. So chances are that emoji support can be added for 2.2, both in the backend (MySQL still has some quirks with them) and in the front end (Redactor).
It already get's rewritten for WCF 2.2, you can see the - quite extensive - changes already on GitHub. So chances are that emoji support can be added for 2.2, both in the backend (MySQL still has some quirks with them) and in the front end (Redactor).
Link to WCF 2.2 via GitHub please.
(I checked Github and only could see 2.1 anywhere)
https://github.com/WoltLab/WCF/tree/next
You just have to switch to the next branch from the main repo
https://github.com/WoltLab/WCF/tree/next
You just have to switch to the next branch from the main repo
Thank you very much @Netzwerg 
Now if only I can figure out how to turn these into packages so that I can test this as a side project.
It's not functional, don't try it yet
It's not functional, don't try it yet
I wouldn't try it on a live site, but on a test site... sure...
I had e-mailed them a while back about this.
Their E-mail support is really quick
I did that as well asking for captions which they do not support themselves.
They told me the same, it would be easy to implement it with a plugin
(And I guess @Teralios did that already with his BBCODE plugin)
https://github.com/WoltLab/WCF/tree/next
You just have to switch to the next branch from the main repo
Actually it is a different branch: https://github.com/WoltLab/WCF/tree/next-redactor
Actually it is a different branch: https://github.com/WoltLab/WCF/tree/next-redactor
I'm concerned...
The one @Netzwerg shows active development, even a few days ago.
The one @Alexander Ebert shows is mostly months and years behind in development.
If I had to choose one... lol
The branch https://github.com/WoltLab/WCF/commits/next-redactor is only used by me to build the new BBCode support for Redactor. Its last commit is 4 hours ago at the time I'm writing this, see yourself: https://github.com/WoltLab/WCF/commits/next-redactor
The branch https://github.com/WoltLab/WCF/commits/next-redactor is only used by me to build the new BBCode support for Redactor. Its last commit is 4 hours ago at the time I'm writing this, see yourself: https://github.com/WoltLab/WCF/commits/next-redactor
Ah. The devil is in the details... I stand corrected.
(Proof that I'm not always right. lol 
)
Don’t have an account yet? Register yourself now and be a part of our community!
