View Single Post
Old 06-09-2020, 08:27 PM   #6
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,618
Karma: 204624552
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
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.
DiapDealer is online now   Reply With Quote