Thanks for the extra details. I was able to reproduce. That seems to be limited to English AU. We’ll get this fixed!
You can follow our progress here:
https://github.com/Automattic/jetpack/issues/2791
I’ll also post again here as soon as I have some news.
Thanks again for the report.
I have the latest version of jetpack 3.9.1 and I’m getting this error.
Is also affecting the New Zealand version changed back to US and I can now edit pages again
Thanks for the report. I’ve added en-nz to the list of language codes we need to fix.
I have no idea what the issue’s are here, but if i simply comment out wp-content/plugins/jetpack/modules/notes.php lines 159-172 i receive no errors.
I assume this may be a bad work around until jetpack locales issues is fixed (though i currently don’t see any visual issues)?
Is anyone able to do a quick summary of the problem? 6 months is a long time for a issue to go unfixed. I’m willing to try to fix this issue if someone is able to provide easy to understand information. (or is this external problem?)
@markcoker In short, WordPress.org’ language codes don’t always have a matching language on WordPress.com, where notifications live. The Notifications module currently tries to pull a Javascript file matching the language on your site, but if you use a language that doesn’t exist on WordPress.com, the file won’t exist, and you’ll get a 404.
We’ll need to either update our list of locales on WordPress.com, or create a fallback to a different language (en_US in some cases like en_NZ, another language in other cases, like es for en_MX).
We haven’t forgotten about this issue, though, and we’ll try to get this fixed in the next release.
Is this related to the same thing?
Yes, that’s indeed the same issue. We’re still looking into this, and I’ll post again here as soon as we make progress.
Is there anything I can do to avoid the error?
When do you think there is a fix for this issue?
https://widgets.wp.com/languages/notifications/nb.json
When do you think there is a fix for this issue?
We do not have an ETA yet, but you can follow our progress on this here:
https://github.com/Automattic/jetpack/issues/2791