Closed sbrl closed 6 years ago
This needs some serious investigation. I have no idea what's going on here!
This looks like it's related to #99, but it's not.
Aaaaahhhhhh. I think I may have figured it out. The problem lies in the fact that the conventional string manipulation functions do not support unicode characters - so we need to use mbstring
instead. It looks like a huge task!
At the very least we should use the mbstring functions from now on.
Fixed! I've learnt a lot about utf8 whilst fixing this one.....
We'll have to comb over the rest fo the codebase to replace any remaining str_replace()
calls - as it doesn't support utf8 :-(
If I include special characters in a pages name (such as
é
for example), it causes a nasty warning to show up if they appear in the search results: