Thanks ghia

xoops_data and _lib are above the root and have been renamed too.

I guess I can live with it, especially as the host is talking about a change 'in the future'. Perhaps some objective reasons why they should change may encourage them to think about sooner rather than later.

Thanks again
Hakim

Hi Team

This is my virgin post, so be gentle with me ...

Have just done my first and relatively straightforward install of XOOPS 2.3.3 The only snag was a security warning about open urls and the need to add: allow_url_fopen = off to the php.ini file.

Not being able to find php.ini, I did a search here and found the problem listed several times and with various solutions tried, all unsuccessfully.

Sent a message to tech support of the the hosting service I use and was told: "at this time this cannot be changed however we are evaluating changing this server wide at a latter date hope this helps"

I responded and asked if placing individual php.ini files in each directory of the XOOPS installation would work (as suggested by one poster here) and the reply was: "the ability to use a custom php file in each directory has been disabled due to security concerns (as many people were using custom php.ini files without being aware of the security implications)"

Another poster here suggested security hole was no big deal, don't worry about it.

So, after the long-winded introduction, is there any reason I should be concerned. If so, is there anything I can say to my hosting service to help facilitate the change to php.ini? Is the url_fopen setting a problem to others, or is it an XOOPS thing?

Thanks for your help.

Hakim