Include errors with Deco. using Drupal 6.0
Kyber - February 6, 2008 - 15:45
| Project: | Deco |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
* warning: include_once(sites/all/themes/deco/forum-topic-navigation) [function.include-once]: failed to open stream: No such file or directory in /var/www/drupal/includes/theme.inc on line 283.
* warning: include_once() [function.include]: Failed opening 'sites/all/themes/deco/forum-topic-navigation' for inclusion (include_path='.:/usr/share/php:/usr/share/pear') in /var/www/drupal/includes/theme.inc on line 283.
#1
I do not get any errors using the latest 6.x-1.x-dev version and D6RC3. Are you using a completely fresh install of D6RC3, or have you added other modules, changed configurations, etc.?
#2
I get these errors too, with a completely fresh drupal-6.0 and deco-6.x-1.0 install.
#3
@CosmicVoyager: You need to use Deco 6.x-1.x-dev. There have been several updates for problems with newer releases of D6. The Deco 6.x-1.0 was released before D6 even made it to Beta.
#4
OK, that seems to have fixed the problem. Thanks!
#5
indeed it has
#6
I still have the problem, just downloaded D6 and the deco-6.x-1.x-dev.tar.gz.
Error message:
warning: theme(sites/all/themes/deco/forum-topic-navigation) [function.theme]: failed to open stream: No such file or directory in /var/www/htdocs/includes/theme.inc on line 587.warning: theme() [function.include]: Failed opening 'sites/all/themes/deco/forum-topic-navigation' for inclusion (include_path='.:/usr/share/php') in /var/www/htdocs/includes/theme.inc on line 587.
warning: call_user_func_array() [function.call-user-func-array]: First argumented is expected to be a valid callback, 'deco_forum_topic_navigation' was given in /var/www/htdocs/includes/theme.inc on line 591.
#7
I spotted this again
Not too sure why...
#8
Marked http://drupal.org/node/227207 as duplicate.
Clarifying the title.
#9
Marked http://drupal.org/node/229625 as duplicate.
#10
Marked http://drupal.org/node/231352 as a duplicate.
#11
I changed the file argument to include '.tpl.php' extension. When I add this those warnings go away.
function deco_theme() {return array(
'forum_topic_navigation' => array(
'file' => 'forum-topic-navigation.tpl.php', <== CHANGED
'arguments' => array('node' => NULL),
)
);
}
Unfortunately the forum pages now report:
warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'deco_forum_topic_navigation' was given in /home/festival/public_html/www-zompire/includes/theme.inc on line 591.So I defined the following assuming that there is suppose to be a hook defined:
function deco_forum_topic_navigation($node) {return;
}
Not sure if this is correct but there are no more errors.
#12
Facing the same problem here with an almost fresh install of 6.1.
#13
The same problem here with Drupal 6.1 (seems to be solved with clear cache from drupal. god i'm an idiot.)
#14
I still haven't reproduced this. Currently trying with D6.2 and the deco 6.x-1.x-dev.
#15
I'm getting this exact error as well, but only after a form is saved/submitted (i.e. create a new piece of content, edit then save a piece of content, save the setting of a module, etc.). I just installed a fresh copy of D6.2 and Deco on my site yesterday. Also, I don't use a forum.
#16
Exact same issue here as well. Brand-new D6.2 install with Deco as only extra theme installed, using only out-of-the-box configuration and modules. Receive the "warning: include_once.../includes/theme.inc on line 283" during basic form submissions to edit content, etc.
#17
Hi Guys,
I love this theme and use it on my art site, http://silencespeaks.com, kudos to the developers who put work into this and even incorporated the design files for personalization. I updated the release to the development 6.x-1.x-dev and this corrected my forum error that I was getting, I'll keep my fingers crossed that it doesn't randomly show up again:)
Meilena
#18
Automatically closed -- issue fixed for two weeks with no activity.