Global lans for plugins

[CaMer0n]

Currently plugins have no simple way to assign a LAN which may be used site-wide for everything from sitelinks to extended-user fields.

[CaMer0n]

This has been added, but all plugins need to be updated with an English_global.php file and plugin.xml modified to use the terms within it.

[Moc]

@CaMer0n @SecretR Are all language files automatically detected? ie. Can we remove all occurrences in every plugin.xml?

[CaMer0n]

[Language]_log.php and [Language]_install.php and [Language]_global.php are auto-detected. Currently about 11 plugin.xml files still have reference to 'languageFiles' which need to be removed.

[Moc]

Done a whole bunch, think I got them all. Loads more plugin clean-up to do: useless LAN -> need replacing by general/global ones. Commented some of those useless LANs out, so there may be broken LAN references in the plugins admin. (related to #6)

[nlstart]

What should be done with the plugin.xml texts?

[Moc]

What do you mean with 'texts'?

[nlstart]

E.g. the plugin.xml description is not overwritten by the text from the English_global.php.

[Moc]

I see what you mean. @CaMer0n ?

[Moc]

Talked to Cameron. They should remain there as they are used on e107.org. The PHP files are not loaded on e107.org for security reasons so the global LAN's cannot be used there.

Within each e107 installation in the plugin manager, both are used:
Installed > uses LANs
Not Installed > uses LANs
Search > uses English (strings in-between the description tags)