Forum Moderators: phranque

Message Too Old, No Replies

mediawiki .htaccess problems (among other things)

1and1 hosting troubles...

         

MaxxJ

7:22 pm on Jan 25, 2008 (gmt 0)

10+ Year Member



Hello everyone,

Since I'm used to my own server setups, I absolutely don't understand the behaviors of the 1and1 hosting servers... Here is the main structure of the directories at this moment:

/example.com/wiki/mediawiki

http://wiki.example.com/ points to the above directory

At first, I wanted to run http://wiki.example.com/config/index.php
It returned some 300 multiple choice errors, something I never encountered before, I've searched and found something to bypass this. So I've run the script, but it returned some error because it couldn't access some files (../maintenance/tables.sql for example) that actually exist and are at the exact address it says it can't find them at.

I've tried a few .htaccess configurations, but now it looks all messed up:
* When I type in http://wiki.example.com/, it tries to access http://www.wiki.example.com/example.com/wiki/mediawiki/ ... (lol)
* If I try to access http://wiki.example.com/config2/ or http://wiki.example.com/index.php, it works (but not if I remove the "index.php", I can access the installation script.

At the moment, the htaccess files are as follow:

/.htaccess contains

RewriteEngine off

(tried this to fix the weird url rewriting)

/example.com/wiki/.htaccess contains

AddType x-mapp-php5 .php
AddHandler x-mapp-php5 .php

(that's what made the config script work)

Oh, and the error at the end of the config script are:

Warning: chdir() [function.chdir]: No such file or directory (errno 2) in /homepages/1and1filestructure/example.com/wiki/mediawiki/config2/index.php on line 756

and
Warning: fopen(../maintenance/tables.sql) [function.fopen]: failed to open stream: No such file or directory in /homepages/1and1filestructure/example.com/wiki/mediawiki/includes/Database.php on line 2183
Could not open "../maintenance/tables.sql".

I'm lost in this mess. I have no idea how to make all this work correctly. Maybe there's a .htaccess solution that could be put in / to recursively fix all these problems? or not... anyway, any help on this would be highly appreciated.

Thanks,
Max J

[edited by: encyclo at 7:45 pm (utc) on Jan. 28, 2008]
[edit reason] switched to example.com and fixed formatting [/edit]