Active
Project:
Abessive
Version:
6.x-1.4
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
20 Mar 2009 at 15:06 UTC
Updated:
23 Jun 2009 at 14:10 UTC
New to Drupal and Theme updates but I keep getting the following error when trying to configure, even after emptying the cache.
Getting the following error: Fatal error: require_once() [function.require]: Failed opening required 'themes/garland/abessive_settings.php' (include_path='.:/Applications/MAMP/bin/php5/lib/php') in /Applications/MAMP/htdocs/drupal/sites/all/Themes/abessive/theme-settings.php on line 23
Comments
Comment #1
nicholasthompsonWhy is it looking in the garland folder for the abessive settings?! Odd!
How many themes do you have enabled? What is the default?
Also - it's better practice to keep all filenames / folder names to lowercase when working with Drupal... so your sites/all/Themes folder shouldn't have a capital T.
Cheers,
Nick
Comment #2
phils-okc commentedYeah, I kinda felt the same thing about the garland folder but couldn't track down why it was looking there.
Garland is the default.
I have 12 themes enabled.
Comment #3
nicholasthompsonTWELVE ENABLED?! Ok...
I'll have to do some testing to see why abessive doesn't like more than 1 theme being enabled.
Comment #4
DanPerTech commentedSame thing here.. Salamander4 is my default theme, and here is what I get if I try to configure the abessive theme.
Fatal error: require_once() [function.require]: Failed opening required 'sites/all/themes/salamanderskins/salamander4/abessive_settings.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/monteres/public_html/sites/all/themes/abessive/theme-settings.php on line 23
Danny
Comment #5
workerbee5499 commentedDitto. If I click "Configure", I get:
Fatal error: require_once() [function.require]: Failed opening required 'themes/garland/abessive_settings.php' (include_path='.:/usr/local/php5/lib/php') in /home/content/n/h/b/nhbdpeex/html/sites/all/themes/abessive/theme-settings.php on line 23
Garland is my default theme for the Admin pages.
No offense meant, but perhaps you might consider rolling back to a previous version of the theme, rather than posting one that doesn't work? Or perhaps offer this one only as a development snapshot?
Comment #6
mwoodwar commentedJust FYI, I got the same type of error until I 'disabled' all other themes
Mark
Comment #7
robhamm commentedHm... I enabled about twenty themes on a local test server to test this--including Salamander and Garland--and Abessive still works fine for me. Perhaps there is another factor involved.
Comment #8
bmetzler commentedI received the same errors and narrowed it down to the fact that I had Garland set as my administrative theme. As soon as I changed the setting back to "System default" the theme worked just fine. It also didn't seem to matter that I had other themes enabled - it was strictly an Administrative Theme problem. Hope this helps resolve the error.
Comment #9
chcamps commentedIn fact, problem raises when you used 2 themes : one for the content and one for administration.
In that case, the Abessive configuration script (theme_settings.php), for exemple, in line #23 makes a call :
require_once path_to_theme() .'/abessive_settings.php';but the path_to_theme will return the path to the administration theme directory (because you're in administration section), and there no abessive_settings.php in there !!
Simply copy the file 'abessive_settings.php' (or what else you content theme needs) from your content theme directory in your adminstration theme directory.
Hope this is enought clear.
(sorry for my english, i'm just french)