do you know where this shy comes from? Search code/db?
I wonder if I can force the search extension into using unicode instead of escaping soft hyphens.
or avoid using :)
private function fixEncoding($in_str) {
$cur_encoding = mb_detect_encoding($in_str);
if($cur_encoding == "UTF-8" && mb_check_encoding($in_str,"UTF-8")) {
return $in_str;
} else {
return utf8_encode($in_str);
}
}
I guess this is the smoking gun.
Nice find in the search_index code:
// no idea what this next line actually does, nothing is harmed if it's simply commented out...
The problem is likely somewhere in the
parseExcerpt()-function. Which is a complex beast.
But I still have no idead at what point the entity is actually created.
Hello Symphonists. What methods do you use to preview content before making it live? Not just new content like News that could be published/unpublished, but content that is already live? E.g the homepage has content and images, how do you update the image but preview it before the public can view it? Some kind of content version control?
If you have means of previewing unpublished backend content in the frontend, you could create a copy of your content and update only the image. Not sure if that’s what you mean.
Does anyone know if/how I could trigger fields within the section editor to reorder? I'm injecting fields in and need to update the index of each field after the injected one, but before I start looping over them I thought I'd see if I could just trigger a function within the orderable class or something. I can't see where.
Hello, all. Has anyone come across this error caused by a right single quote ’ in a field on which a data source is filtering via a Page parameter? Despite that, the handle in the XML doesn't contain ’ and matches the Page parameter. When I swapped it for a normal apostrophe ' all was fine.
Sym 2.7.10, PHP 7.3, MariaDB 5.5
This page could not be rendered due to the following XSLT processing errors:
General:
XSLTProcessor::transformToXml():
Warning: string contains a character that is out of range! Substituting "?".
Warning: string contains a character that is out of range! Substituting "?".
Warning: string contains a character that is out of range! Substituting "?".
Actually
’ is an apostrophe ;)
Whereas
' is not.
But not in programming obviously.
</smartypants>
@animaux Ah, yes, thanks. Indeed it is this url-encode utility causing the problem. I guess I should have searched my xsl files for that warning message ;)
Are you continuing to use it, or is there a UTF-8 alternative?
I'm curious about this in url-encode:
<xsl:message terminate="no"> If terminate is no (default), should it cause Symphony to display an XSLT Processing Error in the front end? (it also adds to Symphony's log).
In the url-encode.xsl utility.
@animaux Thanks. I wasn't convinced it's a safe character so I decided to leave url-encode as is and cleanse quotes before passing a string to it. Not going to mess with xsl:message for now.
Actually
’is an apostrophe ;)
Whereas'is not.
Looks like it's both https://en.wikipedia.org/wiki/Apostrophe ;)
Still, a »typewriters apostrophe« is typografically wrong to use anywhere else than on a typewriter or code. I have to be a pilkunnussija on this!
;)
German Wikipedia is more concise on this issue: https://de.wikipedia.org/wiki/Apostroph#Typografisch_falsch
