Thanks for the report @spikey, it looks like there was a similar string-related issue fixed for 2.15.0 but it's not quite the same as this one. This issue is specific to strReplace. I've verified the issue and we'll have this fixed in the next patch.