Failed opening required 'sites/all/modules/defaultcontent/plugins/defaultcontent_condition.inc' [#1873128]

Full error:

PHP Fatal error: require_once(): Failed opening required '/var/aegir/platforms/drupal-7.12/sites/all/modules/defaultcontent/plugins/defaultcontent_condition.inc' (include_path='.:/usr/share/php:/usr/share/pear') in /var/aegir/platforms/drupal-7.12/includes/bootstrap.inc on line 3066

Trouble is that file exists but in a different directory: sites/all/modules/defaultcontent/context/plugins/defaultcontent_condition.inc. For now, the quickest solution was to create a symbolic link from sites/all/modules/defaultcontent/plugins/defaultcontent_condition.inc to sites/all/modules/defaultcontent/context/plugins/defaultcontent_condition.inc but that won't work for shared hosting (you'll have to copy the file).

So, I'm asking the owner if there's a particular reason for searching for the file in plugins directory as opposed to context/plugins directory? And is there an elegant way to solve this?

Thanks

Comment	File	Size	Author
#3	defaultcontent-update_file_registry_location-1873128-3.patch	830 bytes	tjmoyer
#3

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

Jeffrey C. CreditAttribution: Jeffrey C. commented 26 December 2012 at 12:22

Status:

Active

» Postponed (maintainer needs more info)

Hello,

Could you please confirm this error exists on a fresh Drupal installation of the latest version along with the latest version of Default Content?

Comment #2

jking1224 CreditAttribution: jking1224 commented 8 February 2013 at 23:33

Yes, I can confirm this is an issue with the 7.x-1.0-alpha9 version of defaultcontent.

Issue is on line 479 of defaultcontent.module reference to file defaultcontent_condition.inc with
'path' => drupal_get_path('module', 'defaultcontent') .'/context/plugins',

Comment #3

tjmoyer CreditAttribution: tjmoyer commented 11 February 2013 at 18:48

Assigned:	Unassigned	» tjmoyer
Status:	Postponed (maintainer needs more info)	» Needs review

File	Size
defaultcontent-update_file_registry_location-1873128-3.patch	830 bytes

I'm not sure if this occurs in a fresh install or not, but definitely happens on upgrade. The problem seems to be that the file, in previous versions, was located in the module's '/plugins' directory but has been moved to '/context/plugins' directory, and there was no update function provided to update the database entry in the 'registry' table. So when you upgrade your module it causes a fatal error on attempted bootstrap.

I have written an update function for the install file, included in this patch, which updates this entry and truncates the cache_bootstrap table to clear up this issue.