Hi stephan
These are all new downloads on an advanced host that runs :, WP, Joomla etc on apache etc latest. But this is the first Xoops.

I am carefully following instructions from here:http://www.xoopswiki.org/modules/mediawiki/index.php?title=Starting_a_New_XOOPS_Site and individual user guides from modules.

So I'm on Xoops2.0.16 and retrieved the latest module downloads only from Frameworks, Backup, Xoopsinfo newbb and protector.

I will completely remove Xoopsinfo and Protector now again, and try to get one of them up (the others load fine). I do not get any error messages even with debug on, just no icon to enable me to 'activate' the mods (PS any other way of doing it??)

Will let you know what happens next.
Thanks
Zaph

Some progress!!!

I undid everything to do with the Protector and Xoopsinfo mods (including redownloading the zips) and then tried just Xoopsinfo - HEY PRESTO it was there in the Modules Admin and is now activated.

HOWEVER Protector still will not show up.

I have meticulously followed the instructions in Protector V3.02 module documentation: Which says:

Installation
Installation of the module does not follow the standard procedure as a few files must be modified. Additional modifications are necessary to fully implement the security improvements recommended by the module. These are covered in the Security Advisory section below, but for the moment, lets just get it installed.

1. Unzip the compressed archive and you will find two directories inside:
/XOOPS_TRUST_PATH
/HTML
2. Upload the contents of HTML into the root folder of your website. Basically you want the folder HTML/modules/protector to end up in your_site_root/modules/protector.
3. Create a new folder outside of your website root to serve as your 'trust path'. You can call the folder anything you like, but I'll use 'my_trust_path' in this example. If your website root is called public_html, the directory structure would probably look something like this:

/home
/my_account
/public_html [this is the website root, your site is in here somewhere]
/my_trust_path [lies outside the website root]

4. Upload the contents of the XOOPS_TRUST_PATH folder into my_trust_path (or whatever you have called it).
5. Change the permissions of my_trust_path/modules/protector/configs to make it writable (777, but on some servers you may be able to write with a more restrictive setting).
6. Edit mainfile.php, which is in your website root folder. You need to define XOOPS_TRUST_PATH as a new constant here by adding a new line. The value should be the physical path to the trust path folder, eg:

define('XOOPS_TRUST_PATH', '/home/my_user_account/public_html/my_trust_path');

Add the line near the other constant definitions near the top of the file (for example, under XOOPS_ROOT_PATH). If you don't know what the physical path to your trust path folder is, you can see the directory structure in the definition for the XOOPS_ROOT_PATH constant.
Go to administration => system => modules and install the module.

THIS IS WHERE I AM STUCK - which means I cannot complete the rest of the instruction - or can I??

(
8. You need to add two more lines to mainfile.php as per the red lines in the code example below. You will find it close to the bottom of the file. Important: Do not do this until after you have installed the module or it will not work.

include XOOPS_TRUST_PATH.'/modules/protector/include/precheck.inc.php';
if ( !isset( $xoopsOption['nocommon'] ) && XOOPS_ROOT_PATH != '' )
{
include XOOPS_ROOT_PATH."/include/common.php";
}
include XOOPS_TRUST_PATH.'/modules/protector/include/postcheck.inc.php';

9. Installation should now be complete. Don't forget to change the permissions on mainfile.php back to read only (444), as this file contains the password to your database account!
)

PS: All my files and permissions are organised and set as per suggestions from you all. Any new ideas?

Thanks
Zaph

Quick update - I am now able to add modules EXCEPT protector just fine - SO this is a Protector install issue. I have uninstalled and re-read the process 3 times and read different instructions (there are some fixes needed).

Questions:
1. Protector is said to be a 'must' - if I can't install it what are my options?
2. Is there any other way to force it to activate (it is there)?
3. If it's essential then why isn't it part of the 'core'?

And

Should I start a new thread now that the problem has been parsed down to the Protector install? Or is there a way to link threads?

Thanks to all who helped so far (and those who read but couldn't assist).

Hoping to get to content this weekend!!

Zaph

Hi,

can you do this:

go to admin -> xoopsinfo, click "PHP Info" tab and scroll down a little to "Configuration - PHP Core". Find the "open_basedir" value and see if it is set. Is it same as your XOOPS root?
(in that case you should set trust_path inside root_path - check here:
http://xoops.peak.ne.jp/md/d3forum/index.php?post_id=8881
http://xoops.peak.ne.jp/md/d3forum/index.php?topic_id=2443
)

go to admin -> xoopsinfo, click "PHP Info" tab and scroll down a little to "Configuration - PHP Core". Find the "open_basedir" value and see if it is set. Is it same as your XOOPS root?

This may be telling me something... Under Sysinfo there is no PHP Info tab. There are 7 Info tabs starting with XOOPS Info, then Server Info etc...

But in any case when I select any of them I get

XOOPS path check: Script is not inside XOOPS_ROOT_PATH and cannot run.

Does this mean anything to anyone? It doesn't make sense to me as the Phpsysinfo folder is there at the fist level under my root at the same level as modules folder per skenow's screenshot. So how can it not be inside XOOPS_ROOT_PATH? Does it think that the script itself is not there? All the downloaded files of Phpsysinfo are there (11 starting with ChangeLog and ending with templates, alphabetically). ???

And any thoughts on my previous 3 questions - can I get Protector in another way? Do without it? etc. GIJOE are you out there?

Thanks all
Z

Hi

Quote:
Tryhttp://xoops.peak.ne.jp/

Quote:
You may try older version of protector that is not D3 and does not need TRUSTED_PATH (if the problem is there) ...

You may go without protector, but it is good to have it. And solving such problems will help you get familiar with XOOPS

You may check php settings by creating your php file with
text editor and this

upload it to your server and access it with a browser...

If you have access to web server logs you may look there for clues ... (access log, error log, mod_sec log if it is installed)

about

Quote:

check this

https://xoops.org/modules/newbb/viewtopic.php?topic_id=55999&forum=1&post_id=247817#forumpost247817

Quote:

I have a feeling you may have an issue with your mainfile.php and how XOOPS_ROOT_PATH and XOOPS_URL are defined. The path check occurs in mainfile, which is loaded with every page. Remember, filenames and folder names are case sensitive, and www.yoursite.com is different than yoursite.com

Protector problem Resolved!
(still have error on XoopsInfo)

Protector is now installed. The problem was indeed with the XOOPS_ROOT_PATH inside mainfile.php...
- The code for XOOPS_ROOT_PATH was right.
- The root was right, as reiterated by the use of a php file with "<?php phpinfo(); ?>" inside.
- The permissions & security were all OK and proved not to be the problem
- The folders (or directories) were all correctly positioned.

The problem was that, in preparing for the XOOPS_TRUST_PATH by cutting and pasting 4 lines of code, the word ROOT had been replaced by TRUST except in one line... so XOOPS_ROOT_PATH was being defined under a dfiferent directory!

OOPS indeed.

Consequently, knowing now that the mainfile gets invoked each time, it makes sense that the error message from the end of the if statement appears.

My apologies for missing this error, as one of you has said, sticking it out has taught me something about XOOPS & how it works.

Thanks for all your help. I will now investigate why XoopsInfo still gives the same error message. I'll try a reinstall first.