Are these instructions still relavent?
activelyOUT - May 23, 2009 - 06:46
new
There is different documentation for this module in the README, in doc directory, and on this page. Can you specify which we should be looking at?
A few things to note:
1. Create marmoset not marmoset_package
the module asks for
/sites/all/modules/calais_marmoset/marmoset/header.php once you add the lines of php to page.tpl.php
so the directory created should be marmoset not marmoset_package
2. If I fill in the module settings, do we need to touch the config file at all?
3. If we have opencalais installed do we have to make the additional changes specified above?
4. The downloaded version of Calais Marmoset files seem to already be included in the module directory. Are both needed?
Thanks,
Chris
Comments
Comment #1
emackn commentedThe correct instructions are found here, http://drupal.org/node/361166.
I'll be updating those today if they are incorrect.
1. There's supposed to be a marmoset_package directory in the tar ball, but there isn't one. So make the marmoset_package directory and unzip the marmoset package into it.
2. Yes, since i'm not including the package, you will have to make changes to the config file for now.
3. opencalais has it's own settings, none of the settings for opencalais pertain to marmoset, and vice versa.
4. the 6.x-1.0 version does not include the marmoset package files, you have to download them separately.
Comment #2
socialnicheguru commentedplease note that the install called for marmoset not marmoset_package
Comment #3
pyxio commentedI'm having the same problem ... this is the error I get.
Fatal error: require_once() [function.require]: Failed opening required 'header.php' (include_path='.:/usr/share/php:/usr/share/pear') in /users/ittags.com/htdocs/sites/all/themes/theme201/page.tpl.php on line 6
I'm pretty sure I have followed the setup instructions carefully. Please advise. Thanks!
Comment #4
emackn commentedprint out the path you are expecting to find header.php at. If it doesn't exist, there's your problem. Check the marmoset package settings as well. That has been the source of a few problems.
Comment #5
WildBill commentedI had a similar error and it was fixed when I changed the access permissions of all nested folders within /marmoset to 755.