Should I make this a Different Module in HMVC Codeigniter?
It really depends, and it's up to you If you want the comment system to apply to other modules some day, definitely make it it's own module. If it's only related to blogs, you could leave it in the blogs modules as it's own controller. This is also where modules::run() and $this->load->module() can come in handy, calling a controller from anywhere to get view fragments, to display the comments I would probably make everything it's own module It's pretty much impossible to be truly 100% modular, there will always be certain dependencies.
The best thing you can do is try to organize it in a way that makes sense to your particular project. In general, modularize as much as possible - if you decide to get rid of blog comments some day, you can just delete the comments module.
It really depends, and it's up to you. If you want the comment system to apply to other modules some day, definitely make it it's own module. If it's only related to blogs, you could leave it in the blogs modules as it's own controller.
This is also where modules::run() and $this->load->module() can come in handy, calling a controller from anywhere to get view fragments, to display the comments. I would probably make everything it's own module. It's pretty much impossible to be truly 100% modular, there will always be certain dependencies.
The best thing you can do is try to organize it in a way that makes sense to your particular project. In general, modularize as much as possible - if you decide to get rid of blog comments some day, you can just delete the comments module.
I concluded this since the module name has to be same as the controller name/filename. Is this true? – Nyxynyx Jun 8 at 1:53 1 It's not true.
You can have as many controllers as you want. For instance, a "comments" controller within the "blogs" module, accessed by the url /blogs/comments/comment_method – Madmartigan Jun 8 at 2:42 I understand now.In other words, the default controller for the "auth" module will be the "auth" controller, which can be accessed via /blogs/auth as well as /blogs/auth/auth – Nyxynyx Jun 8 at 3:24 1 Your auth module should not be within your blogs module - I'm not sure what you mean by that - so no. However, you are right about the first part.
The default controller name matches the module name, but other controllers can be accessed as well. For example, if I have two controllers in my blogs module called blogs and comments, I can access comments->index() by /blogs/comments. I know you are using tank auth, so really the only thing you should be doing with it is logging in and out and managing users.
Care to explain more what you are trying to do? – Madmartigan Jun 8 at 3:37 Right sorry for the confusion, my auth module is not within the blogs module, I included '/blogs' into the exmaple url by mistake. I'm just implementing tank auth into the system to allow visitors to interact with the site by leaving comments and interact with each other via profiles and private messaging.
Thank you, cleared up my many doubts! – Nyxynyx Jun 8 at 4:01.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.