martinremy

Thanks everyone who’s reported this issue, we’ve found the cause and are working on an a new release for Monday to fix this. The reason I didn’t see it on my site is that it occurs when using the admin over SSL. There are two possible workarounds if you would like to re-activate Jetpack right away to keep tracking stats:

1) De-activating the Notifications module within Jetpack should get rid of this error. (Click on “Learn More” under Notifications, then deactivate).

2) Use the admin over https:// instead of forcing SSL

@surveillancetips sorry, I thought that text was coming from the plugin, wanted to make sure we’re using the same one. I confirmed I’m running the same versions, also on WP 3.4.2, and still not seeing the issue, but I’ve asked some others to test the same setup. Please stay tuned.

@surveillancetips, thanks for the detailed report. Unfortunately, I can’t reproduce the issue, I have the same versions of WordPress SEO and Jetpack installed as you and the WPSEO Titles & Metas page is working for me.

Did you have previous versions of Jetpack and WordPress SEO installed?

In spite of having the same version, the WordPress SEO Titles & Metas page looks slightly different here (no “WordPress SEO comes alive message” and no solid line underneath the tabs): https://cl.ly/image/2j12371m2j3C

Thanks for your patience. Unfortunately I’m out of ideas at this point and I’m able to see the correct Russian encoding in Jetpack Stats with the settings as I’ve described above, and I haven’t seen reports of Jetpack Stats displaying with the wrong encoding from other users.

Perhaps someone in the Russian WP forum has some additional ideas:
https://ru.forums.www.ads-software.com/

In Chrome’s View -> Encoding, please try turning off (uncheck) auto-detect and select UTF-8 manually.

When you go to the stats page in Chrome, could you look at the “View” → “Encoding” menu, what is checked?

Thanks for the patch @bobbingwide! Committed and will be in the next Jetpack update.

With these 3 things set, are you still not getting the correct encoding in your stats page?

1) Change to define(‘WPLANG’, ‘ru_RU’); in wp-config.php

2) Set the encoding of your blog to UTF-8 in Dashboard->Settings->Reading, look for Encoding for pages and feeds”.

3) Set the interface language on WordPress.com to ru in https://wordpress.com/#!/settings/

WPLANG is set in your wp-config.php file, you can set it to ru_RU following these instructions:
https://codex.www.ads-software.com/Installing_WordPress_in_Your_Language#Single-Site_Installations

WPLANG is probably already correct if you have installed a Russian version of WordPress.

The encoding of your blog is set in Dashboard->Settings->Reading, look for Encoding for pages and feeds”. This should be UTF-8.

As a test, I configured the following on my Jetpack-enabled blog:
– Set WPLANG to ru_RU
– Set encoding to UTF-8
– Set interface language to ru here: https://wordpress.com/#!/settings/

With these settings, I am able to see my Jetpack stats with the correct encoding in Russian (https://cl.ly/image/1Q2y3h2Y3w26). I don’t know if the translations are correct, but the encoding seems to be correct.

Can you verify your settings in those 3 categories above? Thanks.

I confirmed that the spell and grammar checker in Jetpack does recognize US and UK spellings, i.e. both -ize and -ise. Your browser’s spell checker may also be active. Please check that your browser’s spell checker is set to UK.

To invoke Jetpack’s spell checker, click the checkmark/ABC in the lower right corner of the text box. This spell checker will give you solid underlines (red for spelling and blue for grammar). If you’d like, please link to a screenshot and I can check whether Jetpack’s or another spell check is at work. Thanks.

Hi, your browser encoding is probably fine (it should be UTF-8). Which encoding you are using in your WordPress installation? Please check the page Dashboard->Settings->Reading for the “Encoding for pages and feeds”. That should also be UTF-8.

You’re right, folding frontpage views into “Homepage / Archives” would make sense, I’ll make a note to do some more testing and hopefully we’ll have a fix soon.

The entry “Home Page / Archives” also comprises archive/category/tag/author pages. Do category pages feature in your client’s site? If yes, that’s probably the explanation for the two entries.

Hi, you should have only one entry for your frontpage, “Home page / Archives”. What is the URL of your site?