Hi Barry,
Quote:
BDW wrote:
Is the XOOPS Trust Path the same as or different from your XOOPS Root Path?
Do I have to create it?
Yes, they are different and yes, you have to create it.
Basically, you need to:
1. manually create a new directory (with a unique name of your choosing - anything you like) on your server at the same level as (i.e. parallel to) your bottom-most XOOPS website folder.
2. Define your new directory as your "xoops_trust_path"
In your mainfile.php you will have your xoops_root_path defined as "physical path"/html where /html is the folder where your website and all the other folders (class, modules, etc) sit.
Your xoops_root_path will be unique to you and your server
and it is defined in your mainfile.php using a bit of code similar to:
// XOOPS Root Path
// Physical path to your XOOPS Root Path directory WITHOUT trailing slash
// Example: define('XOOPS_ROOT_PATH', '/home/xxxxxxxxxx/public_html/html');
define('XOOPS_ROOT_PATH', 'home/xxxxxxxxxx/public_html/html');
Your /html folder may be called something else depending upon what you decided at the time of installation.
All you need to do is copy (not cut!) the above XOOPS_ROOT_PATH code from your mainfile.php and paste it in lower down. In the newly pasted in code, change all instances of "ROOT" to "TRUST" and change "/html" (or whatever yours is called) "/new directory".
You will now have a new directory on your server and some lines of code in your mainfile.php which defines this new directory as your XOOPS_TRUST_PATH.
3. Upload Protector Module
This is a two-stage process.
In the Protector 3 download there are two directories, one called "/html" and one called "/xoops_trust_path". In both of these there is a directory called "/modules" and each has a sub-directory called "/protector".
a) Upload the "/html/modules/protector" directory to your website's modules directory in the usual way so you have:
/modules/protector
b) Upload the contents of the /xoops_trust_path directory to your newly made directory so that you have the structure:
new directory/modules/protector
4. Install the module
If you already have Protector 2.5x installed then simple update the module in admin.
If you already have Protector 2.5x installed then revisit mainfile.php and amend the pre- and post-check code from "XOOPS_ROOT_PATH" to "XOOPS_TRUST_PATH"
Hope this helps
Quote:
BDW wrote:
I thought the whole idea of a CMS was to make things simpler.
Someone should make a FAQ for this as it's going to confuse a lot of people, as it did me at first
