I have installed a brand new 2.016 and edited mainfile.php and made it ready for Protector 3.0 and the Trust Path. This path is outside my web area and linked correctly in mainfile.php. Like this:

define('XOOPS_TRUST_PATH', '/xxxxx/xxx/home/myweb/secret/protector');


The protector files & folders in Trust Path are all in their place.
The files & folders in the public module are all in place.


Xoops starts up, no error messages. But the module will not show up in system admin?? I tried to remove the Protector folder and re-FTP it all, but still: It won't show up at all???

I'm a bit exhausted...

Is your xoops_root_path defined as something like:

/xxxxx/xxx/home/myweb/html/

or

/xxxxx/xxx/home/myweb/

If its the latter then move your "Trust path" files to:

xxxxx/xxx/home/secret/

and alter the xoops_trust_path in mainfile.php accordingly.

The xoops_root_path and xoops_trust_path should be exactly "parallel" to each other.

Hope this helps.

Quote:

Thanks John, I will try that! I haven't made the "trust path" as a paralell to the plugin path, but I will try later on. Again: Thanks!

Hi,

Quote:

I'm not sure what you mean by "the plugin path", but I do know that the "Root Path" and the "Trust Path" should be parallel to each other, i.e.

"physical path"/website root/
"physical path"/trust directory/

The "physical path" is the one that you'll find defining you "Root Path" in mainfile.php and is the path to your files on the server.

When you copy the file from the module download you should have a stucture that looks like this:

"physical path"/website root/modules/protector
"physical path"/trust directory/modules/protector

In the download file there are two directories:

/html
/xoops_trust_path

Each has a subdirectory called "modules"........ it should be logical after that

Good luck - I know it does work.