-
-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Global lans for plugins #50
Comments
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. |
[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. |
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) |
What should be done with the plugin.xml texts? |
What do you mean with 'texts'? |
E.g. the plugin.xml description is not overwritten by the text from the English_global.php. |
I see what you mean. @CaMer0n ? |
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: |
Currently plugins have no simple way to assign a LAN which may be used site-wide for everything from sitelinks to extended-user fields.
The text was updated successfully, but these errors were encountered: