Closed bondarewicz closed 10 years ago
Hi There, I wonder if someone faced the same issue or could point us in the right direction here...
Imagine situation where content writer enters following on the page content in prismic:
£34.01
once the content is fetched via php-sdk it comes as:
£34.01
after using html_entity_decode() we still get
html_entity_decode()
£34.01
we could use
str_replace("Â", "", $content)
but it seems to be happening for other special chars as well like ™ ® ©
™ ® ©
ok, nothing to do with sdk at all :) content="text/html; charset=utf-8" fixes it.
content="text/html; charset=utf-8"
Hi There, I wonder if someone faced the same issue or could point us in the right direction here...
Imagine situation where content writer enters following on the page content in prismic:
once the content is fetched via php-sdk it comes as:
after using
html_entity_decode()
we still getwe could use
but it seems to be happening for other special chars as well like
™ ® ©