By Anonymous (not verified) on

I'm new to Drupal (since about 10PM eastern time last night!) and I'm having a real annoying problem in getting my site set up.
It's Drupal 4.7 on SuSE 10.0 with apache2 and the install is in /srv/www/htdocs/lucii.com.drupal/

The Drupal site itself runs just fine but when I added a few modules the problems began. I installed the modules in sites/default/modules as the documentation suggested. The module adsense works just fine. The Flexinode, event, or ecommerce modules give me lots of error messages when I go to Administration->modules

Here are the details for the flexinode module errors:

I installed it in the sites/default/modules/flexinode directory as the instructions recommended.
Per the instructions:

  1. the files are already in the directory specified.
  2. I updated the database with flexinode.mysql
  3. I go to administration -> site configuration -> modules
    (actually, it's just administer->modues in my menu.)

At this point I get error messages like these:

# warning: flexinode_field_types(sites/default/modules/flexinode/contrib/field_multiselect.inc) 
[function.flexinode-field-types]: failed to open stream: No such file or directory in 
/srv/www/htdocs/lucii.com.drupal/sites/default/modules/flexinode/flexinode.module on line 17.
# warning: flexinode_field_types() [function.include]: 
Failed opening 'sites/default/modules/flexinode/contrib/field_multiselect.inc' 
for inclusion (include_path='/usr/share/php') 
in /srv/www/htdocs/lucii.com.drupal/sites/default/modules/flexinode/flexinode.module on line 17.

These messages refer to this file:

-rw-r--r-- 1 wwwrun www 3682 Nov 9 2005 field_multiselect.inc

which is in this directory:

/srv/www/htdocs/lucii.com.drupal/sites/default/modules/flexinode/contrib

The second message mentions the include path of /usr/lib/php which is NOT what I'd expect if this is to work. Is that the problem? If so, how do I change that? The settings.php file does not seem to have anything that references include files or paths.

I do NOT know Apache 2 or anything about .htaccess files. Is that where my problem lies? The default Apache 2 install on SuSE appears to be fairly restrictive for security purposes (and I'm *usually* grateful for that!)

I'm stumped by this. Not as stumped as I was by Typo3 - but that's why I'm installing Drupal now :-)

Thanks

⋅ Categories: Drupal 4.7.x

Comments

bl4h’s picture

bl4h commented

I dont believe flexinode is compatible with 4.7.3 yet

Ive read this on the module page

"Note for 4.7: Though flexinode itself has been released, we doid not yet release any form fields (the .incs). We would love your input. If you have tested (and optionally fixed) a field on a 4.7 installation, lpease tell us your findings. Once we have a well enough tested field, it will be released. One by one!"

also quite a few bug fixes lined up

http://drupal.org/project/issues/flexinode?categories=bug

Anonymous’s picture

Anonymous (not verified) commented

Good catch... I downloaded the event module and that was a 4.7 version. Since it relies on flexinode I took that to be carte blanche that flexinode would work. That solves the event/flexinode problem but leaves me with an apparently related problem: ecommerce.
When I install ecommerce I get this big error in my pages:

warning: main(sites/default/modules/ecommerce/store/store.inc) [function.main]: failed to open stream: 
No such file or directory in /srv/www/htdocs/lucii.com.drupal/sites/default/modules/ecommerce/store/store.module on line 4.

The offending statement in store.module is line 4: require_once(drupal_get_path('module', 'store'). '/store.inc');

If I go to Admin->modules I see only the following error text:

Fatal error: main() [function.require]: 
Failed opening required 'sites/default/modules/ecommerce/store/store.inc' 
(include_path='/usr/share/php') 
in /srv/www/htdocs/lucii.com.drupal/sites/default/modules/ecommerce/store/store.module on line 4

Again I see the include path is '/usr/share/php' and I believe that's got to be wrong. I'm simply not sure what to do
about it if, in fact, that is the problem.

Is 4.7.3 too new? Should I consider going to 4.6.9 for better module compatability?

Thanks again,

Eric