The content property is definitely one that gets parsed for urls to update when renaming files. But I can't immediately see why your non-url value is getting detected as an url. The regex is a bit convoluted. I'll have to stare at it for a while. But it's definitely getting detected as an url. That's the only reason the url-encoding would be applied.
It's definitely a bug on our end.
|