Hey vmassol,
Looking at the bug I don’t entirely think your understanding of ‘Xwiki working fine with utf8’ is true. Yes, for a plain installation without default skin it works (i’ve tested that as well) but as I can’t install one of the default extensions, the ‘My Activity Stream’, without having utf8mb4 I would say Xwiki doesn’t work fine without utf8mb4. If your understanding was true it should install without problems but, like you said, not support emojis which would be perfectly fine for me. (I’m sorry vmassol! I’ve read over your last sentence! Keeping this paragraph in here just as a reminder for myself)
The problem is that not having utf8mb4 (for mysql at least) breaks the default skin as the “My Activity Stream” just doesn’t install with a clean (docker) install and also post-installing the plugin just doesn’t work as it installs about 7 translations of the notifications macro but not the notifications macro itself, which it probably also does when installing the default skin!
In my eyes the whole installation of the default skin should fail when it has db-query errors, ESPECIALLY if it’s trying to insert or change something in there! It doesn’t do that at the moment, it installs the skin, throws a few small exceptions inline but after says it’s A-OK, which it clearly isn’t.
The same goes with post-installing the notifications plugin (or any plugin for that matter) as soon as the minimum requirement can’t be installed (i.e. XWiki.Notifications.Code.Macro.NotificationsMacro) it shouldn’t install the translations for it and it should actually just delete the installed translations for it and throw up an error about WHY it failed (which it doesn’t say in the frontend when installing extensions)
As I’m having troubles with xwiki on another system (CPU load suddenly surges to 100% and keeps it there, which makes xwiki get stackoverflows/out of memory errors), I’m now afraid it maybe has something to do with some upgrade I did where I didn’t see the inline error which made this mess.
To be a littlebit more specific about this:
I upgraded a 13.x.x (which worked perfeclty on utf8) to 14.10.0 which looked like it worked flawlessly it upgraded all the plugins… even the Notifications plugin, I thought, but it looks like it didn’t upgrade it because of my utf8 DB so it now, probably, uses some werid mixture of 13.x.x Notifications pages mixed in with 14.10.0 translations on it. It does seem to work, but it makes me think if more plugins have this problem at upgrading what kind of issues could arrise from it (like surging CPU loads and such as there is some compatibility issues, race conditions or unlimited threads spawning because of mismatches).