15
ok, I am having issues installing Protector 3.2 and defining my trusted path
here is a snippet from my mainfile.php
// XOOPS Physical Path // Physical path to your main XOOPS directory WITHOUT trailing slash // Example: define('XOOPS_ROOT_PATH', '/XXX/XXX/XXX/XXX/family');
define('XOOPS_ROOT_PATH', '/XXX/XXX/XXX/XXX/family');
define('XOOPS_TRUST_PATH', '/XXX/XXX/XXX/XXX/family/xoops_trust_path');
I know it is listed in the same directory as my Xoops_Root, but I want to get it to work first, and then I will move and rename it
Each time I go to install the module, I see this: set XOOPS_TRUST_PATH into mainfile.php
on the module Admin screen and the module is not listed to install.
I have uploaded both folders to the appropriate directories, but can't seem to get the trusted path to be recognized or working. I have also edited the mainfile.php for the pre & post check.
My XOOPS version is 2.0 (will uprade once I get my modules installed) or should I be upgrading the core first?
Thanks for any help!