This CMS is for my freelance business, not something I release to the public, so don’t worry about that

I’ll be happy to donate some code into PyroCMS, I twitted you about that, I only need some contact info to talk to you about it.

This CMS is for my freelance business, not something I release to the public, so don’t worry about that

I’ll be happy to donate some code into PyroCMS, I twitted you about that, I only need some contact info to talk to you about it.

If I was starting PyroCMS again these are certainly things I would think about working into the core, but Pyro has evolved purely as and when I have needed features or clients have asked for them.

Instead of starting YaCICMS would you consider working some of these features into PyroCMS? With v0.9.8 almost out in the wild we will soon be ready to work on the game-changing v1.0 which will include all sorts of insanely awesome features I am keeping to myself and the dev team.

If not, best of luck with your project. I’ll be keeping an eye on it.

If I was starting PyroCMS again these are certainly things I would think about working into the core, but Pyro has evolved purely as and when I have needed features or clients have asked for them.

Instead of starting YaCICMS would you consider working some of these features into PyroCMS? With v0.9.8 almost out in the wild we will soon be ready to work on the game-changing v1.0 which will include all sorts of insanely awesome features I am keeping to myself and the dev team.

If not, best of luck with your project. I’ll be keeping an eye on it.

My idea for modules is very simple, as you described its all about subfolders.

For users module, you’re structure can be like this:

controllers/user/

add.php
login.php

models/user/

muser.php
musergroup.php

views/user/

add_user.php
add_group.php

I think the separation in the views is much more critic and useful because you probably have more views then controllers or models, and views folder can get very messy.

About the dependencies,
If you create user module, in other module you probably checking for valid authentication or permissions, so it this case I suggest to add some code to your MY_Controller class and see if user module exists – if so

..
Hope you got the idea.

Good luck!

My idea for modules is very simple, as you described its all about subfolders.

For users module, you’re structure can be like this:

controllers/user/
–add.php
–login.php

models/user/
–muser.php
–musergroup.php

views/user/
–add_user.php
–add_group.php

I think the separation in the views is much more critic and useful because you probably have more views then controllers or models, and views folder can get very messy.

About the dependencies,
If you create user module, in other module you probably checking for valid authentication or permissions, so it this case I suggest to add some code to your MY_Controller class and see if user module exists – if so

..
Hope you got the idea.

Good luck!

Since I’m new to CI and CMS concept, I think this article is really helpful. One question is, how the modules created in CI? Is it using sub folder in controller folder, or something else? And how about the dependencies of a module? I think a module has to not have any dependencies with other modules.