Title: Problem with html entities
Last modified: August 24, 2016
---
# Problem with html entities
* Resolved [saschapi](https://wordpress.org/support/users/saschapi/)
* (@saschapi)
* [11 years ago](https://wordpress.org/support/topic/problem-with-html-entities/)
* Hi!
* I tried this plugin on another project and it helped really well.
* With a new site I run into problems.
* This string does not translate:
`_e( 'Next Events »', 'tribe-
events-calendar' )`
* Problem seems to be the `»` which becomes » once saved.
* Any idea?
* thanks for you help in advance! 😉
* Sascha
* [https://wordpress.org/plugins/say-what/](https://wordpress.org/plugins/say-what/)
Viewing 6 replies - 1 through 6 (of 6 total)
* Plugin Author [Lee Willis](https://wordpress.org/support/users/leewillis77/)
* (@leewillis77)
* [11 years ago](https://wordpress.org/support/topic/problem-with-html-entities/#post-6180931)
* Hi;
* I don’t run the plugin in question, but I added the output you quoted to a dummy
plugin and was able to override it just fine, so not too sure what the problem
would be.
* Thread Starter [saschapi](https://wordpress.org/support/users/saschapi/)
* (@saschapi)
* [11 years ago](https://wordpress.org/support/topic/problem-with-html-entities/#post-6180941)
* it does not work for me. While I can easily change other strings that do not
contain html entities, strings with entities includes (same goes with `&` are
a problem, as they seem to be saved as the UTF-8 counter parts.
* Plugin Author [Lee Willis](https://wordpress.org/support/users/leewillis77/)
* (@leewillis77)
* [11 years ago](https://wordpress.org/support/topic/problem-with-html-entities/#post-6180961)
* Hmm, I think I’ve managed to reproduce this. It works fine the first time you
save the entry, but if you edit the replacement, the » gets replaced with the
actual entry. I’ll see if I can work out a fix.
* Plugin Author [Lee Willis](https://wordpress.org/support/users/leewillis77/)
* (@leewillis77)
* [11 years ago](https://wordpress.org/support/topic/problem-with-html-entities/#post-6181007)
* So – this is because of an inconsistency (bug) in how one of WordPress’ internal
string escaping functions works. I’m not really keen on working around that by
using less-secure escaping features, but I’m confident it’ll get fixed in WordPress
at some point.
* In the mean time, if you change the string, just swap the » for » before you
save and you should be all good.
* Hope that helps.
* Plugin Author [Lee Willis](https://wordpress.org/support/users/leewillis77/)
* (@leewillis77)
* [10 years, 11 months ago](https://wordpress.org/support/topic/problem-with-html-entities/#post-6181049)
* Just to follow up on this, part of the fix is included in v1.5 – however you
won’t see any benefit from that in this case until you’re also running a version
of WordPress that includes the fix from [https://core.trac.wordpress.org/ticket/17780](https://core.trac.wordpress.org/ticket/17780).
* The good news is that that looks like it will be in 4.3.
* Once you have that, then editing these will work as you’d expect.
* Thread Starter [saschapi](https://wordpress.org/support/users/saschapi/)
* (@saschapi)
* [10 years, 11 months ago](https://wordpress.org/support/topic/problem-with-html-entities/#post-6181050)
* Nice! Thank you for supporting your plugin so well! 🙂
Viewing 6 replies - 1 through 6 (of 6 total)
The topic ‘Problem with html entities’ is closed to new replies.
* 
* [Say What?](https://wordpress.org/plugins/say-what/)
* [Frequently Asked Questions](https://wordpress.org/plugins/say-what/#faq)
* [Support Threads](https://wordpress.org/support/plugin/say-what/)
* [Active Topics](https://wordpress.org/support/plugin/say-what/active/)
* [Unresolved Topics](https://wordpress.org/support/plugin/say-what/unresolved/)
* [Reviews](https://wordpress.org/support/plugin/say-what/reviews/)
* 6 replies
* 2 participants
* Last reply from: [saschapi](https://wordpress.org/support/users/saschapi/)
* Last activity: [10 years, 11 months ago](https://wordpress.org/support/topic/problem-with-html-entities/#post-6181050)
* Status: resolved