Hi again. Yeah my application folder config setting is set correctly in the index.php file and have the Base4.php as above. Still issues :(...Anyway. i’ve gone for a more low-fi version of want to do for now and i’ll come back to this when i’ve got some time on my hands. Cheers dyna

Great work dynazack!

We can make our web applications more organized this way - into logical parts for each web module.
I tried it and it works fine on my CI setup - using PHP5 of course.

But how do you call a ‘global’ view that is not in the current module’s view folder. I may want to apply a generic / same view (such as a header or footer) to construct a page even though different modules are used.

To explain further, view files are stored in a ‘views’ folder under modules/MODULENAME folder

/system/application/modules/MODULENAME/views/

But how do I use a view file from the following folder?

/system/application/views

First of all, kudos dynazack.

Ericos - 11 December 2006 07:07 PM

But how do I use a view file from the following folder?

/system/application/views

To use the default views directory, you simply load the view as normal. If you look at dynazack’s code, the $view is only loaded from the module’s views directory if it exists there, otherwise it falls back to default views folder. So unless you also have a header or footer in the module’s views directory there should be no conflict.

Thank joeles…

Your comments are very helpful. Should have studied the code more carefully.

I think this should be a core feature for CI since application can really get out of hand and we do need a way to organize our codes.

I am trying the module concept and have applied your classes, but I am getting “Headers already sent by MY_Router.php” errors when trying to use with other classes such as Native_session or the URL Helper, etc.

I am assuming this is due to the order of how the classes are loaded. Sill looking into it, but thought I would post this in case someone has any tips.

Cheers.

slillig - 13 December 2006 05:11 PM

I am trying the module concept and have applied your classes, but I am getting “Headers already sent by MY_Router.php” errors when trying to use with other classes such as Native_session or the URL Helper, etc.

I am assuming this is due to the order of how the classes are loaded. Sill looking into it, but thought I would post this in case someone has any tips.

Cheers.

That error is caused by something being output to the browser before the headers are sent. It’s sometimes caused by another error being sent, but if you don’t see another error on the page, it’s more than likely caused by extra white space before PHP open tag or after your close tag.

Have you checked for any whitespace before or after the <?php or ?> marks?  That is a common culprit.

edit: Joeles beat me to it.  Whoops!

I think that was it… thanks for the quick response.

I am trying to integrate Peccavi’s UserAuth as a module, so I am onto debugging other problems at the moment. Will post more if I get it running correctly.

i was trying this modularity capability againg in my CI apps

dynazack, can the controllers placed in the original controllers folder be still used?

i managed to solve it!

dynazack’s MY_Router class replaces CI_Router’s original function _validate_segments(). However, CI_Router’s _validate_segments() returns the $segments variable that was passed to it as a parameter but MY_Router’s _validate_segments() doesn’t.

So the fix is a simple one. Just add the keyword “return” to the last line of code, as follows:

Now you can have modularity when you require it but also when you don’t.