include_once() function fails?

There isn't a views_content.views.inc -- at least in Views. I'm not sure why a file of that name would be getting included. Maybe CTools related?

Update to latest views and ctools dev versions.
If the problem persists, provide clear steps for reproducing the bug.

Cheers.

I've seen this on a couple of sites with CTools and Views RC1. Investigating…

I've tried to trace back to where this come from on my local installation where I have the latest clean copies installed of views 7.x.3.x-dev and ctools 7.x-1.x-dev and Drupal 7.8. This is pretty much a vanilla installation where I have only enabled the themes I want to use (Omega 3.x + subtheme and Seven 7.8 (for admin)).

It seems to me that there is some cache problem/conflict with the theme template entry.

Steps I do to reproduce.
1. Clear cache.
2. Do something on site, such as reload home page, create content or do something in admin. Warning appear.
3. Do the same action again as in 2, warning gone.
4. Do a search for views_content.views.inc in database and I find a reference in cache and watchdog. Watchdog is the error report. In cache the cid for the result is either theme_registry:seven and/or theme_registry:[my_omega_subtheme], depending what I did in 2.
I also did a search for views_content.views.inc in all my local Drupal folders, but found nothing.

I tried to drill down with backtrace. In theme.inc I found that views_theme returns views_content.views.inc as a file name on views_view_unformatted as key ($result['views_view_unformatted']['file']). See attached image on dpm().

In views_theme, I looked into $plugins (after $plugins = views_fetch_plugin_data(); around line 95) and found views_content.views.inc is in $plugins['style']['ctools_context']['theme file']. See attached image of dpm().

This is where my knowledge of the inner workings of Views lets me down. I hope that this helps somebody find the problem. If there is anymore testing you want me to do, please let me know.

Initially I thought it was Omega theme that was the problem, but I get the same with Seven 7.8 (in core).

After doing a complete new installation of Drupal 7 and latest modules, this issue was resolved. I can't put my finger on it, but I think some where along the many upgrades (not just Views) some bug crept in.
Found another problem with Views which made me re-installing everything.

This is definitely still a problem. The file in question is part of the views_content module, shipping as part of CTools (ctools/views_content/plugins/views/views_content.views.inc).

It seems there's a naming collision or something. In any case, Drupal becomes confused about the location of the views_content.views.inc file and starts looking inside the views/theme folder. This pops up at random (and often inconvenient) moments.

Have you tried this in latest CTools -dev?

I can reproduce this with CTools 1.x-dev, Panels 3.x-dev and Views 3.0-rc1, but now it's consistent. I get this every time I run drush cc all:

% drush cc all

include_once(/srv/www/drupal7/sites/example.dk/modules/contrib/views/theme/views_content.views.inc): failed to open stream: No such file or directory theme.inc:413 [warning]
include_once(): Failed opening '/srv/www/drupal7/sites/example.dk/modules/contrib/views/theme/views_content.views.inc' for inclusion (include_path='.:/usr/local/share/pear') theme.inc:413 [warning]
include_once(/srv/www/drupal7/sites/example.dk/modules/contrib/views/theme/views_content.views.inc): failed to open stream: No such file or directory theme.inc:413 [warning]
include_once(): Failed opening '/srv/www/drupal7/sites/example.dk/modules/contrib/views/theme/views_content.views.inc' for inclusion (include_path='.:/usr/local/share/pear') theme.inc:413

Okay, I figured out what’s going on.

1. The error messages show example.dk
2. The actual sites runs at example.com
3. The files are located in sites/example.dk
4. sites/example.com is a symlink to sites/example.dk

This seems to confuse Drupal sufficiently to mess up something with the registry rebuild process causing weird issues like these. This is likely a core bug.

Actually I think this may be a side effect of a Views bug that was fixed, later unfixed, then fixed again. Most recent CTools commit along with Views 3.1 should fix this completely.