Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 4.5.0-b1
-
Component/s: None
-
Labels:None
-
Epic Link:
Description
- Update `plugin_actions` to support translating the `options` field to pull names using language from the plugin. The plugin can then set an action that will represent the language definition to use (e.g. "SupportManagerPlugin.nav_primary_client.main")
For the structure of the options field, see https://docs.blesta.com/display/dev/Plugin+Actions#PluginActions-AvailableActions - Whenever plugin actions are retrieved, load up and instantiate the associated plugin
Call $this->_(..plugin definition..) on the plugin action definition to translate it
- The navigation cache may need to be reset whenever someone changes their language or a plugin is installed/upgraded (which may or may not already take place)
Note: The language for the actions are assumed to come from /plugins/plugin_name/language/en_us/plugin_name_plugin.php*. If not set here then it will use the name of the plugin as given
Issue Links
- relates to
-
CORE-2987 Support Manager: Use language keys for plugin actions
- Closed
-
CORE-2991 Order: Use language keys for plugin actions
- Closed
-
CORE-2992 Mass Mailer: Use language keys for plugin actions
- Closed
-
CORE-2993 Billing Overview: Use language keys for plugin actions
- Closed
-
CORE-2994 Blesta Reseller: Use language keys for plugin actions
- Closed
-
CORE-2995 Client Documents: Use language keys for plugin actions
- Closed
-
CORE-2996 Download Manager: Use language keys for plugin actions
- Closed
-
CORE-2997 Feed Reader: Use language keys for plugin actions
- Closed
-
CORE-2998 Reassign Pricing: Use language keys for plugin actions
- Closed
-
CORE-2999 System Overview: Use language keys for plugin actions
- Closed
-
CORE-3000 System Status: Use language keys for plugin actions
- Closed