Using controller in plug-ins [DraftMode]
- Plugin_Bootstrap class must not be named "Bootstrap" but for example "Init", otherwise you get Zend Issues
- As Example see class editor_Plugins_TmMtIntegration_Init
- An ACL entry must be added for resource: "editor_plugin_tmmtintegration_resource"
Decision helper for new features
New features can be implemented as core feature or as plug-in.
The following questions shall help in a non dogmatic manner to find the best way of implementation:
| Question | As plug in | As core feature |
|---|---|---|
| Can translate5 be used without this feature? | Yes | No |
| Does only a few clients need this feature? | Yes | No |
| Does the feature provide events where other features can hook in? | No | Yes |
| Is the implementation technically clearly dividable from the core code? | Yes | No |
More content has to be added. Until then please visit our source code repository and look for the plug-in documentation in the docs-folder of Zf_Extended.
An overview over already existing plug-ins you can find here.