A plugin is not the same as what you think. The terminology between Symfony and ZF is completely different.
The plugin does not mean "Connect me." I will work on your site. This is basically the name given to what the developer uses in their applications, which are called each page load. Instead of creating a base controller or some other helper, the plugin is used to create a new abstraction from your controllers. When you create the plugin, your reason should be that the code used for this should be used for every page load.
My site provides examples of some plugins
- My ACL
- My template manager. (I built a unique template engine).
Some people may even use it for caching. However, to answer your question, you will not use the plugins the way you want.
In response to your comment below: No, a module is just a way to create different levels of functions on your site that is separate from the default module.
t .. Examples of modules - blog - full-fledged online store - administration package
They naturally want to be separate from your default module.
If I were you, I would use a plugin. However, you need to create your own plugin. Easily accessible not really .. provided anywhere. Fortunately, however, the documentation shows you how to implement something.
I would definitely recommend using ZF, this is the best thing I've ever experienced in my coding career. I like it.
Layke source share