[wp-trac] [WordPress Trac] #18200: Language Packs
WordPress Trac
noreply at wordpress.org
Sun Oct 6 13:40:59 UTC 2013
#18200: Language Packs
---------------------------------+-----------------------
Reporter: nacin | Owner: nacin
Type: task (blessed) | Status: accepted
Priority: normal | Milestone: 3.7
Component: Upgrade/Install | Version:
Severity: normal | Resolution:
Keywords: 3.7-early has-patch |
---------------------------------+-----------------------
Comment (by Chouby):
Replying to [comment:89 nacin]:
> Thankfully, it's a bit smarter than that. :-) The version of the plugin
is also considered. If Twenty Ten 1.5 is installed, only a translation
designed for 1.5 (or earlier) would be installed. Try installing Twenty
Ten 1.5 — you won't get a language pack installed. But if you update to
Twenty Ten 1.6, you'll immediately get a pack.
When I made the initial test, I just asked for a core update and did not
notice that the theme was automatically updated to 1.6 (even if I did not
want). Note that other (non-default) themes were not updated. So in some
way you are right, the language pack matched the theme version. But not
exactly the way you are describing. Just because in that case auto upgrade
was acting
I tried with:
{{{
define('AUTOMATIC_UPDATER_DISABLED', true);
}}}
in wp-config.php but that did not avoid theme update as the same time as
core.
I modified permissions of the theme directory to disallow theme update
(but kept my languages directory writeable). And now as described above, I
have unmatching themes and translations. I recognize that it's far-fetched
and I got an 'update failed' message so I would not be surprised if
something would be wrong late. But so far, I don't know how to avoid theme
update at the same time as core to make the test as you described.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/18200#comment:90>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list