just an update - doing the local install on xampp of a completely fresh 2.4.3 it looks as though I have mucked something up on the running site when carrying out the 2.4.2 to 2.4.3 upgrade, not sure what yet.

I may just go ahead with a total rebuild locally, get that working to my satisfaction, then transpose it over to the remote site host.

hmmm I have moved things as you have pointed out, a slight issue putting protector inside XOOPS lib/modules under the trusted dir.

Didn't work, I tried uninstalling protector and reinstalling it as well it made no difference it didn't work under XOOPS lib it had to be outside of the lib to work.

Off to play with a local install of 2.4.3 to compare setups (ie see what I have done wrong)

@ghia

the library and data folders do match the settings in the mainfile

A side effect is now that the protector module config options page gives a blank page on setting any options with the go button.

One step foreward.....

interesting I reactivated it and now it works without the lines, it does give the warning within the module about the precheck lines missing from the mainfile, but at least the site doesn't fail to load.

I have to sort the database factory patch also.

Thanks for the tips, is it possible that when I deleted the original site that the server still actually had files on the drive, as I had to recreate the same XOOPS folder name as people linked posts within the forums, so that when I moved over the new build there could have been stuuf there albeit invisible to me via ftp?

I may try to rebuild the whole site again on xampp at home from 2.4.3 fresh install - to see what differences there are.

I have deactivated protector and removed the lines from mainfile and the site works, it also worked before removing the lines with protector deactivated.


The version that protector reports is 3.41 I selected the install from the build on XOOPS 2.4.2 as far as I am aware we never had protector previously.

Hi if I remove those lines the site does not run!

Like I stated, I did a complete fresh build of 2.4.2 ie backed up my old site (just incase) then I did a clean build into an empty folder, then set about rebuilding the site from the base core.

Re the PHP I am on


System Overview

XOOPS Version XOOPS 2.4.3
PHP Version 5.2.11
mySQL Version 5.1.39-community

does it need to be 5.0 only?


I'll check the layout when at home sourceforge is blocked at work :) but the libraries and data appear to work, or are they not allowed to be in another directory?

Hi

I have recently taken over administering our XOOPS based site it was previously on 2.0.18 (I think) I did a fresh install of 2.4.2 and got more or less the old modules used updated where possible and working.

I then this week carried out the update to 2.4.3


The site is working but I have a few conflicts with the advice on here.


Where I am getting confused is by the use of Protector.

Currently our mainfile .php has to have

Quote:

in the mainfile for the site to function

currently our site is along these lines




Is this correct?

or should it be along the lines of





I am confused why I have to have the pre and post checks in the main file.


Like I say the site works my various paths are set in mainfile.php protector detects various things

I do have other issues but one step at a time and considering this is the first time I have tried anything like this, it has been a bit of a leap of faith but aided by the excellent information on here.



System Overview

XOOPS Version XOOPS 2.4.3
PHP Version 5.2.11
mySQL Version 5.1.39-community
Server API isapi
OS WINNT
safe_mode Off
register_globals On
magic_quotes_gpc Off
allow_url_fopen On
fsockopen On
post_max_size 60M
max_input_time 600
output_buffering 1
max_execution_time 30
memory_limit 256M
file_uploads On
upload_max_filesize 60M