Download & Extend

Failed opening '/content_taxonomy.module'

Project:Taxonomy Search Module
Version:5.x-1.x-dev
Component:Code
Category:bug report
Priority:normal
Assigned:Unassigned
Status:active

Issue Summary

    * warning: include_once(/content_taxonomy.module) [function.include-once]: failed to open stream: No such file or directory in /path/to/modules/taxonomySearch/taxonomySearch.module on line 72.
    * warning: include_once() [function.include]: Failed opening '/content_taxonomy.module' for inclusion (include_path='.:/usr/local/php5/lib/php') in /path/to/modules/taxonomySearch/taxonomySearch.module on line 72.
    * warning: include_once(/content_taxonomy.module) [function.include-once]: failed to open stream: No such file or directory in /path/to/modules/taxonomySearch/taxonomySearch.module on line 72.
    * warning: include_once() [function.include]: Failed opening '/content_taxonomy.module' for inclusion (include_path='.:/usr/local/php5/lib/php') in /path/to/modules/taxonomySearch/taxonomySearch.module on line 72.

Comments

#1

Project:CCK Taxonomy Fields» Taxonomy Search Module
Version:5.x-1.0» 5.x-1.x-dev

* warning: include_once(/content_taxonomy.module) [function.include-once]: failed to open stream: No such file or directory in /home/lucy26/public_html/dancom/drupam/sites/all/modules/taxonomySearch/taxonomySearch.module on line 72.
* warning: include_once() [function.include]: Failed opening '/content_taxonomy.module' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/lucy26/public_html/dancom/drupam/sites/all/modules/taxonomySearch/taxonomySearch.module on line 72.

#2

I suspect I have not listed all the dependencies for this module - you need CCK, but also the content taxonomy module... sorry about that.

#3

here is a link to the content taxonomy project
http://drupal.org/project/content_taxonomy

#4

Got the same error and after the field was not manageable anymore from the cck "manage fields" screen.

I was able to edit the field directly with:
http://www.123sites.com/admin/content/types/directory-entry/fields/NAME_...

You can get the name of your field inder cck "Display fields"
or under
Content Type "Fields"

This might help someone else...

#5

Can you confirm whether the problem was just that you needed the taxonomy content module as listed above?

#6

yes, i had a same issue... after installing content taxonomy module everything was OK

#7

could you please release another version of the module with correct dependencies ?

#8

This is killing my installation profile ...

(from content_taxonomy.install)

// Updates happen in random order, whether or not the module is enabled,
// so include critical code here just to be sure.
include_once(drupal_get_path('module', 'content') .'/content.module');

being called before any tables exist for no good reason ...

better method is to call
drupal_load('module', 'content');
inside each method that needs it ...

PLEASE PATCH AND RELEASE ASAP!!!

#9

Thanks for this quick fix info, this helps and I hope that this will be fixed asap.

#10

Any word on when this module will have this patch integrated and re-released.

We just wasted a bunch of time digging down to try to find the source of our problems and finally landed here. Expect others are in the same boat.

Mike

#11

yeah, sorry, all my fault, I should get round to it. It's on the to-do list.... just buried...
we need a thought-to-action drupal module :-)

Cheers

Mark.

#12

actually

Doh

I _DID_ do this, and I made a release, but I changed the major number, so it's not showing!!!

Doh.

I'll fix that up :-)

Cheers

Mark.

#13

can you confirm if you have the same problem with the 2.x release

Cheers

Mark.

#14

This is killing my installation profile ...

(from content_taxonomy.install)

// Updates happen in random order, whether or not the module is enabled,
// so include critical code here just to be sure.
include_once(drupal_get_path('module', 'content') .'/content.module');

being called before any tables exist for no good reason ...

It seems this is a different issue altogether, but I have had the same problem. What's most odd is that the content_taxonomy module was not included in the install profile at all, but prevented the installation profile from working. After removing the module from the sites/all/modules directory, I was able to install without issue. I'm going to report a bug with core.