[eluser]tieungao[/eluser]
hehe i said that "Not familar" means i not understand too much about some professional way like extended and modified standard CI. I've make many projects using CI and i understand about HMVC also.
I come to your Bonfire because i need one admin panel with nice-looking interface with Auth, and i can using it in every projects later. And i belivered u build the bonfire to help ppl do that.
I've searched this at this forum and at google for long time, i've tried pycroCMS, ionze cms, fuel CMS, but only your bonfire match what i need. You can see it easily because i active almost here.
That's great to hear that u will make a tutorial soon. Im waiting for that.
I have some problems more, can u help me to solve :
- Like you said at docs :
With the exception of the Public context, creating a controller for your module for a specific controller is a simple as naming your controller to match the context. A controller for the content context, would be named content.php, while one that shows up in the settings context would be named setting.php. For the public context, the controller should be named the same as the module. For example, a Pages module would have a public controller called pages.php.
I've tried to understand that and I guess u suggest user to name the controller like content.php and setting.php maybe because u add some like at routes.php for auto recognize them, but im not sure.
Note : I see in the core_modules have some controller name settings.php
Thank you for your time and sorry for my English.
