Hello all!
I have (what seems to me, at least) an odd issue. I'm trying to install WEC. If I follow the instructions - decompress the .zip file (even though my server supports symlinks, it won't create them when uncompressing from a .tar - go figure), chmod the fileadmin, typo3conf, typo3temp, and uploads directories to 0777 -R, then type in the main address, I get a screenfull of errors, the first of which says:

Warning: fopen() [function.fopen]: open_basedir restriction in effect. File(/hsphere/local/home/silvercf/web.silvercreekfellowship.org/typo3conf/temp_CACHED_ps4d30_ext_localconf.php) is not within the allowed path(s): (/hsphere/local/home/silvercf:/usr/local/lib/php:/hsphere/shared/apache/libexec:/tmp:/var/tmp) in /var/hsphere/local/home/silvercf/web.silvercreekfellowship.org/t3lib/class.t3lib_div.php on line 2453.

There are other errors after this, but I'm pretty sure they're all related to the fact that we're obviously not playing nice with the typo3conf directory. Just to let you know, PHP is running with open_basedir on.

So then, I chmod the fileadmin, typo3conf, typo3temp, and uploads directories to 0775 -R, and I get the first page of the 1-2-3 install tool! It wants me to input my MySQL database info, which I do. However, when I click "continue", I get a message that localconf.php is not writeable. So then I chmod the localconf.php file to 0777. I still get the first 1-2-3 page, but now when I click "continue", I get this error message:

Warning: fopen() [function.fopen]: open_basedir restriction in effect. File(/hsphere/local/home/silvercf/web.silvercreekfellowship.org/typo3conf/localconf.php.TMP.php) is not within the allowed path(s): (/hsphere/local/home/silvercf:/usr/local/lib/php:/hsphere/shared/apache/libexec:/tmp:/var/tmp) in /var/hsphere/local/home/silvercf/web.silvercreekfellowship.org/t3lib/class.t3lib_div.php on line 2453

So, I'm stuck! Not sure how to work around an open_basedir issue. I can't edit the PHP config at all, I'm on a shared hosting service. But I find people (including typo3 developers) who say that open_basedir shouldn't cause an issue at all! So, I'm wondering - has anybody else encountered this? Does anyone have any ideas on how to fix it? Your help is muchly appreciated! You'll understand why if you visit our current website (which I had nothing to do with creating!).

Every Blessing!
Cory Walz
Silver Creek Fellowship
Silverton, OR

Cory,

Okay, let's try to figure out the trick to make this work. As I read about open_basedir it appears that only files in a specific directory can be written to by PHP. And symlink tricks pointing outside that directory don't work. But perhaps you can symlink into it and we can keep TYPO3 happy by creating symlinks that don't change its paths. Would it work to move all the directories you changed to 777 to /hsphere/local/home/silvercf and then create symlinks to them with the same directory name. So, for example, typo3conf in your root directory becomes a symlink to /hsphere/local/home/silvercf/typo3conf. TYPO3 should not mind that, and open_basedir should be happy because the files live in the right place. What do you think?

Also, if this hosting location is too restrictive, your life might be lots easier by changing hosting companies. If they made this restriction, there is a likelihood that other restrictions are coming too that may be even more painful.

In Him,
Mark

Mark,
While your solution seemed like it would work, it doesn't. I've spoken with the hosting company, who says that the TYPO3 configuration thinks that the correct path to it is /hsphere/local/home/silvercf/wectest.silvercreekfellowship.org. The path actually needs to say /var/hsphere/local/home/silvercf/wectest.silvercreekfellowship.org . In other words, the main path setting in the WEC configuration files needs to be changed to add /var in front of it. I've looked, and looked, and looked some more - but I can't figure out for the life of me how to manually change the path configuration for TYPO3/WEC.
Does anybody know how? If you want to see the error, visit wectest.silvercreekfellowship.org

Every Blessing!
Cory Walz

Cory,

The only path like this that I am aware of is the symlinks themselves. What if you change the symlinks to include /var/ at the beginning of the path. TYPO3 is just going where the symlinks tell it to go. So maybe that is the solution.

In Him,
Mark