So I set my
Code:
$MODULEDIR = "/home/mydomain.com/formproc/modules";
and my
Code:
$FMCOMPUTE = "fmcompute.php";
and the files are indeed in those directories, but I got:
Error=Cannot load FMCompute module from file '/home/shanwhit/mydomain.com/formproc/modules/fmcompute.php': include_once() [<a href='function.include'>function.include</a>]: Failed opening '../tectite//home/shanwhit/mydomain.com/formproc/modules/fmcompute.php' for inclusion (include_path='.:/usr/local/php5/lib/php:/usr/local/lib/php')
It appears that it's prepending "../tectite/" when trying to open it, so it looks like it will always fail unless I create a directory called "tectite" that's "../" to my tectite formmail.
Looking in the source code, I found
Code:
if ($bAdvTemplates)
{
$FMCTEMPLATE_PROC = true;
if (!include_once("../tectite/$MODULEDIR/$FMCOMPUTE"))
Error("load_fmcompute",GetMessage(MSG_LOAD_FMCOMPUTE,
array("FILE"=>"$MODULEDIR/$FMCOMPUTE",
"ERROR"=>$php_errormsg)),false,false);
}
and
Code:
if ($bAdvTemplates)
$FMCTEMPLATE_PROC = true;
if (!include_once("../tectite/$MODULEDIR/$FMCOMPUTE"))
Error("load_fmcompute",GetMessage(MSG_LOAD_FMCOMPUTE,
array("FILE"=>"$MODULEDIR/$FMCOMPUTE",
"ERROR"=>$php_errormsg)),false,false);
Indeed, all the hooks are called in a similar way.
So, I moved my modules directory to "../tectite/modules" and it started working fine.
I'm not complaining, I just think it's a bit odd that you provide a way to configure MODULEDIR and HOOK_DIR, but then it's always assumed they are going to be under "../tectite/"

So I thought I'd point that out.
Bookmarks