modules::run in view problem

[eluser]Webjema[/eluser]
[quote author="osci" date="1308369302"]Is account extending MX?
[/quote]
But "account" is module name.
Controller name is "sign_in".
My answer is "no". Is this necessary?
I've changed to "extends MX_Controller". No effect.

[quote author="osci" date="1308369302"]
Is your loader correct?
[/quote]
I do not know. I've downloaded it today.

[quote author="osci" date="1308369302"]
Do you have a custom MY_Loader?
[/quote]
Yes. In [app/core] folder.

[eluser]osci[/eluser]
module::run as stated above must call an MX controller not CI.

[eluser]wiredesignz[/eluser]
If the module and the controller have different names you must also use the method name to make it clear. ie: modules::run('account/sign_in/index');

[eluser]Webjema[/eluser]
[quote author="osci" date="1308370317"]module::run as stated above must call an MX controller not CI.[/quote]

Ok. Thank you.
Now:

Code:

class Sign_in extends MX_Controller {

But still:
"ERROR - 2011-06-18 02:15:10 --> Module controller failed to run: account/sign_in"

[eluser]Webjema[/eluser]
[quote author="wiredesignz" date="1308370519"]If the module and the controller have different names you must also use the method name to make it clear. ie: modules::run('account/sign_in/index');[/quote]
Oh. A lot of things. I was not carefully with wiki?

So. I have call modules::run('account/sign_in/index');
It looks like module is loaded.
But {elapsed_time} stop work.
And:

Code:

DEBUG - 2011-06-18 02:18:03 --> File loaded: app/controllers/../modules/welcome/controllers/welcome.php
DEBUG - 2011-06-18 02:18:03 --> Controller Class Initialized
DEBUG - 2011-06-18 02:18:03 --> File loaded: app/modules/welcome/views/welcome_message.php
DEBUG - 2011-06-18 02:18:03 --> File loaded: app/controllers/../modules/account/controllers/sign_in.php
DEBUG - 2011-06-18 02:18:03 --> Sign_in MX_Controller Initialized
DEBUG - 2011-06-18 02:18:03 --> Loader Class Initialized
DEBUG - 2011-06-18 02:18:03 --> File loaded: app/modules/account/config/account.php
DEBUG - 2011-06-18 02:18:03 --> Helper loaded: language_helper
DEBUG - 2011-06-18 02:18:03 --> File loaded: app/modules/account/helpers/ssl_helper.php
DEBUG - 2011-06-18 02:18:03 --> Helper loaded: url_helper
DEBUG - 2011-06-18 02:18:03 --> File loaded: app/modules/account/libraries/Authentication.php
DEBUG - 2011-06-18 02:18:03 --> Session Class Initialized
DEBUG - 2011-06-18 02:18:03 --> Helper loaded: string_helper
DEBUG - 2011-06-18 02:18:03 --> Encrypt Class Initialized
ERROR - 2011-06-18 02:18:03 --> Severity: Notice  --> Undefined property: CI::$encrypt /FULL_PATH/app/third_party/MX/Loader.php 165
DEBUG - 2011-06-18 02:18:03 --> Database Driver Class Initialized
ERROR - 2011-06-18 02:18:03 --> Severity: Notice  --> Undefined property: Welcome::$db /FULL_PATH/sys/libraries/Session.php 201
DEBUG - 2011-06-18 02:18:04 --> Config Class Initialized
DEBUG - 2011-06-18 02:18:04 --> Hooks Class Initialized
DEBUG - 2011-06-18 02:18:04 --> Utf8 Class Initialized
DEBUG - 2011-06-18 02:18:04 --> UTF-8 Support Enabled
DEBUG - 2011-06-18 02:18:04 --> URI Class Initialized
DEBUG - 2011-06-18 02:18:04 --> Router Class Initialized
ERROR - 2011-06-18 02:18:04 --> 404 Page Not Found -->

Two notices, but "404 Page Not Found" in log =(

[eluser]wiredesignz[/eluser]
Your view is attempting to load some resource that is not available and your .htaccess code is then calling another instance of CI via index.php.

Whenever you see Config class initialized followed by Hooks class, that is the entry point into a CI instance. You should only have that sequence once per page load. (unless you are using Ajax callbacks)