Fatal error opening required theme.inc in content.module

I think both issues are the same. So marking this one as a dup of #615760: Enabling views crashes whole site - only plain text error message (smoking ruin)

AFAICT, CCK code is correct. The file should be there (it is included in the package), and it should be accesible with that statement (Drupal executes from the Drupal root, and ./sites/all/modules/cck/theme/theme.inc is relative from there), unless something odd is happening in your system. Maybe the file is not there (caused while upgrading from an earlier version? ), or maybe another module has changed the current working directory, or maybe it is a filesystem issue, permissions?

@markus_petrux, in fact, as thomasmurphy noted (at #615760: Enabling views crashes whole site - only plain text error message (smoking ruin)) the issue I've reported above is related to CCK while his is about Views.

Not wanting to keep toggling the status, could I ask you to reconsider and reopen this issue.

Indeed, ./sites/all/modules/cck/theme/theme.inc is there on the server; checked.
Filesystem perms are just like for any other file there.
No other errors like that - always this one error msg repeated in the log (see above).
If it were any less important module I'd disable it until a new version, but I obviously need CCK. So what do you recommend - what can I check for, how to find out what causes this. Thanks.

@vacilando: looking at that issue, moved to the Views queue, you'll see how merlinofchaos also states it's not a problem with the module, but something else. He says, it's user error. I also add that it could be caused by another software component, or even hardware related. Please, read my second paragraph in #1.

I'm switching the issue to "fixed" so that it is more visible in the queue, but still nothing to do with CCK itself, otherwise it would be failing to everyone else, which is not the case. The require_once invocation is correct. So the problem may come from something else.

- Check the file is there.
- Check file permissions.

If that's seems correct, then it could be that another module has changed the current working directory of the process. We (and any other code in Drupal) assume the current working directory is the same directory where Drupal itself is installed, aka Drupal root. So we should be able to use relative paths that work everywhere.

Line 177 in content.module is part of content_theme() function. This is implementation of hook_theme() in content module. This function is invoked when Drupal rebuilds the Theme registry. To check if the current working directory is still Drupal root, you could do this:

The quickest way I know of to force a Theme registry rebuild is from the icon menu in Administration menu.

@markus_petrux, thanks for your exhaustive answer.

Yes, I did read your 2nd paragraph in #1, and answered it in my 3rd paragraph in #3 :-)
The solution that worked in the other issue does not apply to me as all of the files are indeed uploaded.

This leaves just one possibility, that is that something else is altering the path.
But what? What kind of modules could tinker with the current working directory? Perhaps Memcache API module which I am using? Other ideas?

Btw: all modules are up to date on my system.
Yes, I did clear the theme registry.

Thanks a lot.

First thing would be to try the code I posted in #4. That should reveal if the cwd has been changed, and where it has been set.

Another thing would be to look at the Drupal logs and find these errors. Are all related to the same URL? Can you see a pattern here?

Another thing: scan the code of all module in your site for code that may alter the current working directory. Function chdir()?

Another thing: if you know how to reproduce the error, then start a debug session to find out where the cwd is being changed. This could be done adding drupal_set_message(__FILE__ .' - '. __LINE__ .' - '. getcwd()) here and there.

Thanks for all recommendations. I think I've found the problem thanks to backtrace in PHP. The problem seems to be caused by Memcache API. Moving this to that module's issue queue.