| HMVC the right way ?! |
(05-27-2015, 10:29 PM)kilishan Wrote: In WireDesignz' HMVC solution, you can call Modules::run() to call a controller from another module and get some content back. This is a bad thing in CodeIgniter's case, because it wasn't designed to work that way and can cause problems with multiple instance of the CI singleton in play, confusing things horribly. Sorry to post two replies instead of covering this in my last post... In WireDesignz HMVC specifically, this isn't really much of a problem, as long as you use the supplied MX base classes (especially the controller). As you (@kilishan) may remember, the problem arose when we attempted to move away from those base classes in Bonfire, but the /MX/Base.php, /MX/Controller.php, and /MX/Loader.php contain some very specific code to address that issue, though it's not always pretty or easy to understand/debug. Still, I would certainly recommend avoiding calling Modules::Run() unless you have a very specific need for it, and it should never be done if any of the controllers involved do not extend MX_Controller (or a base class which extends MX_Controller). If I were drawing a map, the intersection of CI_Controller and Modules::Run() would be a stormy region guarded by the hydra. |
| Welcome Guest, Not a member yet? Register Sign In |
