Maybe it's just me who can't understand this....

"- set XOOPS_TRUST_PATH into mainfile.php"

Sorry but that doesn't tell me anything.....does it mean something like this?

define('XOOPS_TRUST_PATH', '/home/flagship/www/www/metroOKC/xoops/xoops_trust_path');

yep.

and.
what do you think the instruction should say instead?

something to this effect.....

define('XOOPS_TRUST_PATH', '/home/flagship/www/www/metroOKC/xoops/xoops_trust_path');

granted, would be different for each site.

Just my 2 cents.

Ok, so I added this to the mainfile.php, right after MAINFILE_INCLUDE line.

define('XOOPS_TRUST_PATH', '/home/flagship/www/www/metroOKC/xoops/xoops_trust_path');

I followed the syntax of this line below.

define('XOOPS_ROOT_PATH', '/home/flagship/www/www/metroOKC/xoops');

I then created a directory called 'xoops_trust_path' in the root of the xoops folder. I then uploaded the contents of the libs folder (contains ALTSYS folder) into the 'xoops_trust_path' directory.

I then uploaded the contents of the HTML folder into the modules page. The HTML folder contained a folder called ALTSYS.

Now when I go into the module admin page the display is messed up and the module is not listed to install.

Any thoughts?



I removed the ALTSYS folder from the module directory and the Module Admin page is fine again.


I also tried moving the DEFINE statement to just infront of this line...

if ( !defined("XOOPS_MAINFILE_INCLUDED") ) {

so you have the 'xoops_trust_path' in the xoops folder?
define('XOOPS_TRUST_PATH', '/home/flagship/www/www/metroOKC/xoops/xoops_trust_path');


or above the xoops folder (same level as the xoops folder).
define('XOOPS_TRUST_PATH', '/home/flagship/www/www/metroOKC/xoops_trust_path');

in the XOOPS folder

ok. then lets make a php file and put this in it

put that file in the xoops_trust_path folder and see if shows the same path as you defined in mainfile.php

path Is /home/flagship/www/www/metroOKC/xoops/xoops_trust_path

wow. i dont know whats wrong.

i installed altsys on my site about 15 minutes ago. it took about 5 minutes..
. make folder (xoops_trust_path).. upload the libs folder to that folder
. define the trust path (xoops_trust_path) in mainfile.php
. uploaded the altsys folder (which was in the html/modules folder) to the modules folder on my site.. and install.

maybe try debugging or reuploading the files?

at what point in the mainfile.php did you put the define line?

i put mine right below the line where 'XOOPS_ROOT_PATH' is defined. i could have put it above that line instead.

. he got it working now.

Yep, upon IM'ing with Bandit-X, I found I uploaded a directory wrong. Thanks again Bandit-X

Hey jimbofoxman, can you tell me exactly what went wrong? I am having the same problem and haven't figuredit out yet.
Thanks, man.

I dare to ask "why cannot altsys be installed?".

- patch class/smarty/xoops_plugins/resource.db.php if you use XOOPS 2.0.14/15/16
- clear templates_c/
- install/update altsys in module admin

That's all.

Hi GIJOE,
Thank you for your help.

I use 12.0.16, indeed. When trying to install altsys (same problem for Protector) I do everything in the README but can't see the module in SYSTEM ADMIN when getting to the installation part.

I created the trust path in /var/xoops_trust_path, updated mainfile.php and copied the files so that I have the following folders:
/var/xoops_trust_path/libs/altsys/...
/var/www/html/xoops/modules/altsys/...

I patched class/smarty/xoops_plugins/resource.db.php, cleared templates_c ... and I still don't see the module in SYSTEM ADMIN.

Can you see anything wrong in what I've done so far? I'd really appreciate your help!

hi Stu.

Quote:There are two reasons.

- Turn debug on
-- a fatal error can hidden it

- Check whether XOOPS_ROOT_PATH/modules/altsys/xoops_version.php exists or not

Hi GIJOE,

I turned debugging on - no error reported. Just queries.
XOOPS_ROOT_PATH/modules/altsys/xoops_version.php exists.

Is there anything else I can look at?

Thanks a lot.

I face something similar recently updating demo XCL with Gijoe modules. Some files were lost or corrupt while uploading (ftp issues).

Check if your host allow you to run scripts outside public folder.
Check your folder structure and mainfile links.
Try to re-upload your module files !

Have Fun !

Quote:Really?

Don't you misunderstand XOOPS_TRUST_PATH instead of XOOPS_ROOT_PATH?

Check whether XOOPS_ROOT_PATH/modules/altsys/ have the permission of 700 etc.

Hi guys,
Thanks for the help. It was a permissions issue.

I had selinux installed by default with a restrictive configuration.

The permissions looked OK, but the web server couldn't read the sub-folders and files under xoops_trust_path.

It's good now. Thanks again.