lonnieezell / Bonfire

Jumpstart your CodeIgniter web applications with a modular, HMVC-ready, backend.
http://cibonfire.com
1.39k stars 524 forks source link

Latest Pull #179

Closed ndcisiv closed 13 years ago

ndcisiv commented 13 years ago

I just grabbed the latest pull and am running into the following error when I click on the Developer tab.

An Error Was Encountered Invalid driver requested: Cache_

The log file simply shows: ERROR - 2011-08-27 08:13:22 --> Invalid driver requested: Cache_

I'm not sure where this is running into the error, just thought I'd bring it up.

ghost commented 13 years ago

Hi @ndcisiv

I can't think why that would happen.

Did you use the pull as is or are you pointing it to your own CodeIgniter directory?

ndcisiv commented 13 years ago

I did a pull as is. Everything within the Developer context works fine (Database Tools, Logs, etc), it's only the default page that throws that error.

ghost commented 13 years ago

Hmm I'm not seeing that.

Is it the homepage or after you've logged in to the admin?

Can you enter some more of the log entries?

Icehawg commented 13 years ago

Nor am I. Odd...did you, um, maybe lose your session or something? I'm just grasping there....

ndcisiv commented 13 years ago

The homepage works great, logging in works great, every other context works great, everything within the developer context works great, it's just the initial front page of the developer context that causes the error. If I log everything, here's where it happens in the log:

DEBUG - 2011-08-27 08:37:08 --> Update MX_Controller Initialized DEBUG - 2011-08-27 08:37:08 --> Loader Class Initialized DEBUG - 2011-08-27 08:37:08 --> File loaded: /Users/ndcisiv/Sites/MAMP Pro/testsite.com/bonfire/application/core_modules/update/libraries/GitHub_lib.php DEBUG - 2011-08-27 08:37:08 --> GitHub class initialized DEBUG - 2011-08-27 08:37:08 --> Helper loaded: filehelper ERROR - 2011-08-27 08:37:09 --> Invalid driver requested: Cache DEBUG - 2011-08-27 08:37:12 --> Config Class Initialized DEBUG - 2011-08-27 08:37:12 --> Hooks Class Initialized DEBUG - 2011-08-27 08:37:12 --> Utf8 Class Initialized DEBUG - 2011-08-27 08:37:12 --> UTF-8 Support Enabled DEBUG - 2011-08-27 08:37:12 --> URI Class Initialized

I only included the five lines before and after the error, but can include more if it would help. If I go back to the previous pull I was working with, it works fine, and I don't see any differences that are obvious anywhere. Anything you can think of I could check?

ghost commented 13 years ago

The File cache driver is loaded in the Base_Controller. Unless there is another loaded for the request to get the latest updates from the bonfire repo?

Not at my computer now so can't check.

ndcisiv commented 13 years ago

After you said that I turned off the "Check for Updates" option and the problem went away. Ideas from here?

ghost commented 13 years ago

Thanks. It must be a cache on the curl request or something like that.

I'll check later if nobody else gets to it.

ghost commented 13 years ago

I'm not seeing that error on the front page of the Developer context.

I had a look now - developer index view is calling

<?php echo modules::run('update/update/update_check'); ?>

which is checking the cache but the update controller extents the Admin_Controller so the File Cache should already be loaded at that point.

@ndcisiv - Did you make any changes to the MY_Controller file?

Icehawg commented 13 years ago

I just threw out my copy and grabbed a fresh pull. No error message. To see if it was maybe curl, I disabled the cURL extension on my PHP extensions and restarted apache, but, still no error.

ghost commented 13 years ago

Ok over to you @ndcisiv - is there anything you may have changed to the code base before this error appeared for you?

In particular did you change core/MY_Controller.php ?

ndcisiv commented 13 years ago

Sorry for not getting back sooner, I was spending the weekend at the Grand Canyon with the kids. I seem to have been having an issue with permissions on the cache folder, because once I set write permissions manually it began working again as expected. I'm not sure why the permissions were messed up for me, but as you both stated - a fresh pull didn't have the problem so I wasn't sure what was going on. Thanks for looking into it!

ghost commented 13 years ago

No problem - thanks