Language files in wp-content

[Nazgul]

Currently language files have to be stored in wp-include/languages, while other "user content" like plugins and themes are in wp-content. It makes more sense (to me at least) to place language files in wp-content as well.

This also simplifies upgrading, because you don't have to remember to save/backup your language files, before deleting the wp-includes folder, as per the installation instructions.

[Nazgul]

Attached patch uses wp-content/languages folder if it exists and falls back to wp-includes/languages if it doesn't.
This fallback keeps existing installations working.

[Viper007Bond]

Good thinking.

[markjaquith]

I like it. No modified files or directories should be in wp-admin or wp-includes

[ryan]

Why not.

[idle]

In response to Ryan's comment:

Because future upgrades will overwrite the modified files, unless you want to manually update your files. Adding new files to wp-includes or wp-admin is a whole different arm, however.

Personally, I never delete my wp-includes directory, but keep my global functions in a file of its own inside that directory. Anyway, I like this patch. Nice work, Nazgul!

[ryan]

By why not I meant, +1. :-)

[markjaquith]

slightly more streamlined logic

[markjaquith]

Newer patch with more streamlined logic... no need to nest those ifs so deep.

[markjaquith]

(In [4446]) make /languages/ directory default to /wp-content/languages/ with fallback to /wp-includes/languages/. Props Nazgul. fixes #3315