Page 1 of 1

What is wrong with the good old include plugins?

Posted: Mon Mar 09, 2009 3:47 am
by exesteam
Hello guys and gals. I wonder what is so bad about including plugins/modules in your core app and then use output buffering to get the outputted data. What is bad about it? Why is no one using that method, instead people use frameworks that need hooks and are limited in many ways.

For example, if I hook my plugin to a "comment posted" action, I can easily alter the way the comment is posted. I got it, but what if the action or what ever you call it does not exist? What if you can't hook it. With the old inclusion everything is possible for plugins on the other hand. So, can someone enlighten me and tell me what is wrong about the good old fashioned approach?

Also, in all frameworks, if they update the core files, it is possible that the plugins/modules are not working anymore! That is one big con in the hook approach.