Thanks for the feedback! I’ll pass this along to have it looked into.
-Brian
Hi,
Brian asked me to take a look at this. This is a known issue, for local language packages. We’re currently looking at the safest way to handle this difference without compromising security. For now, I think you can select “ignore until the file changes”.
I’m adding your thread to the internal ticket to address this.
tim
FB518
Hi Tim,
Yes I have been clicking “ignore until file changes” but as you can guess with the recent round of updates (unusual I know, having so many in short space of time) it has been annoying.
Hope you come up with a solution. Thanks for getting back to me.
Yes, i have been experiencing the same thing, just a thought maybe checksum have default checksum then a checksum for + $wp_local_package = ‘[all languages]’;. I know its a bit more work and not idea but just a thought. Id be interested in what you guys come up with. let us know 🙂
Thank you for the input — this is being actively worked by the dev team, and will be included in a future release.
-Matt R
@ WF team,
Any idea when this difference will be ignored?
Or better, any clue why the update gives a localized version of that file. I have multiple sites, all set to Dutch and for some sites I get the file with that localized file and some don’t.
I have posted this question in various WP help forums and nobody seems to have the answer.
@john-pierre Cornelissen: I don’t have a date for when this will be included in a release yet, but it should be relatively soon!
I think the difference between how sites are updated depends on how the site was originally installed — whether it was using the official zip file for a given language, or if it was a standard WordPress installation that had the language options added after installation. I don’t know specifically how WordPress determines which way it is running though.
-Matt R
