Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Encoding troubles #137

Closed
Arood opened this issue Aug 8, 2017 · 3 comments
Closed

Encoding troubles #137

Arood opened this issue Aug 8, 2017 · 3 comments
Labels

Comments

@Arood
Copy link

Arood commented Aug 8, 2017

Hi,

First of all, I'm not 100% percent sure if this is an error caused by Tailor or if something is incorrectly configured on my system since I have a new workstation. However, my issue only happens in Tailor so I'll start here to see if anyone more familiar with the code can help me troubleshoot.

The problem I'm having is that each time I open a page with Tailor, all "special" characters break, like a classic encoding issue. So this text:

Våra center håller öppet hela dagen och inträdet är gratis för alla deltagare

becomes this:

Våra center håller öppet hela dagen och inträdet är gratis för alla deltagare.

This only happens when I open the page in Tailor. Writing these characters and saving works, and opening the page in the WordPress editor works fine.

Can someone help me?

@munirkamal munirkamal added the bug label Aug 9, 2017
@munirkamal
Copy link

Hi @Arood,

Thank you to report this, i can confirm it's a bug and we will get it fixed.

Regards,
Munir

andrew-worsfold pushed a commit that referenced this issue Aug 22, 2017
* Added - The ability to modify the default media query sizes.
* Improved - Frontend CSS is automatically recompiled from project SCSS files when Customizer settings are updated.
* Improved - The performance of the tailor_modify_colorpicker function.
* Fixed - Element CSS not loading when restoring the "Initialized" history snapshot.
* Fixed - Notice of undefined index [body_class] displayed on the Gutenberg edit screen [GitHub 134](#134).
* Fixed - Certain character sets are not being encoded properly [GitHub 137](#137).
* Fixed - Custom elements are not being correctly extracted from saved HTML content [GitHub 138](#138).
@munirkamal
Copy link

Hi @Arood,

This should be fixed now with the latest release. Please try again and let me know if you still get any errors.

Thanks

@kkkrist
Copy link

kkkrist commented Aug 23, 2017

Seems to work for me now with 1.8.1. Thanks for the quick fix, much appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants