Thread

Well there is no absolute reference to the current module controller… so not really.

@WanWizard

How is your “Modular CI” different from wiredesignz’s implementation?

@ralf57, He may feel better to answer in his Modular CI thread. Thanks.

You’re right wire,
sorry for “polluting” the thread

In the Modular Separation maintained by Phil he created an enhancement (i thought do anyway) that would load extended classes from the core-folder.

Like Base_Controller extending MX_Controller (located in core-folder).

Is this something you plan to add? It keeps my library-folder cleaner 😊

Hey Johan, yes entirley possible to add autoloading from application/core.

Bitbucket is now updated with spl_autoload for application/core base classes. Thanks Johan.

Great!
Thanks for some really good work!

Thanks for bringing that up Johan, it’s good to have that feature back.

I’m getting an error now that I’m pushing v1.1 of my CMS to live (which contains Modular Extensions minus the MX_Controller stuff). This is all working perfectly fine on local, but when it gets to my CentOS live server I get the error:

Fatal error: Class ‘MX_Loader’ not found in /usr/local/www/application/third_party/MX/Ci.php on line 47

As you’ve pointed out before this code is rather complex so instead of faffing, debugging and false fixing like before I figure I’d let you answer.

Hi Phil,

I may be wrong on this, like you said the code is complex.

But i think it’s missing this at the top!

require_once 'loader.php';

InsiteFX

@Phil, do you have MY_Loader.php in application/core which includes MX / Loader.php like so.

<?php (defined('BASEPATH')) OR exit('No direct script access allowed');

require APPPATH."third_party/MX/Loader.php";

class MY_Loader extends MX_Loader {}

@InsiteFX, Modular Extensions relies on CI to load the MX_loader class via MY_Loader.php allowing for future user extensions of the class.

Thanks wiredesignz, that’s good to know.

As always it takes a little time to get use to new code.

InsiteFX

Im having the same problem as Phil on this ! soon as i put it on a live environment its giving the same fault :( ??

@Bainzy, It is beginning to sound like a file naming issue or loading sequence issue.

EDIT:
Try moving the code on line 3 of MX/Loader.php ...

(class_exists('CI', FALSE)) OR require 'Ci.php';

... to a line after the end of the MX_Loader class declaration.

Is it feasible to include config & libraries inside a module where the module library is using an instance of the ci object to load a module config file (module/config/foo.php) with $this->ci->load->config(‘module/foo’) or another a config in another module like config(‘other/foo’)?

I’m having difficulty with attempting to load any type of module files like configs or models in this manner from a module library, what would be the best way to implement this?

Is it feasible to include config & libraries inside a module where the module library is using an instance of the ci object to load a module config file (module/config/foo.php) with $this->ci->load->config(‘module/foo’) or another a config in another module like config(‘other/foo’)?

I’m having difficulty with attempting to load any type of module files like configs or models in this manner from a module library, what would be the best way to implement this?

Well it seems once I dropped MY_Config and MY_Lang into application/core and extended their respective MX classes this took care of the issue…