C'est la même galère ... serait il possible de trouver ce qu'il ne va pas => comme précédement, quand je configure les options Allowoverride j ai droit à une belle erreur 403 ...
- Code: Tout sélectionner
<Directory /home/e-smith/files/ibays/blogs/html>
Options None
Options +Indexes
Options +Includes
AllowOverride FileInfo Options
order deny,allow
deny from all
allow from all
</Directory>
- Quand AllowOverride est en "none" le gestionnaire de wordpress MU s'affiche parfaitement, mais la visualisation d'un blog hébergé est impossible (erreur 404) ...
- Quand AlowOverride est en "All" j ai droit à une erreur 403 autant pour WP MU que pour les blogs générés ...
Il me fait le même type d'erreur sur clarkonnect mais fonctionne sans problème sur Centos 5.1 (même configuration que précédement citée pour l'accès à l'ibay) ...
Voici ce qui est mis pour apache et php dans le fichier readme de WPMU
- Code: Tout sélectionner
Apache
======
Apache must be configured so that mod_rewrite works. Here are
instructions for Apache 2. Apache 1.3 is very similar.
1. Make sure a line like the following appears in your httpd.conf
LoadModule rewrite_module /usr/lib/apache2/modules/mod_rewrite.so
2. In the <Directory> directive of your virtual host, look for this
line
"AllowOverride None"
and change it to
"AllowOverride FileInfo Options"
3. In the <VirtualHost> section of the config file for your host there
will be a line defining the hostname. You need to add the following
if you want virtual hosts to work properly:
"ServerAlias *.domain.tld"
Replace domain.tld with whatever your one is, and remove the quotes.
PHP
===
1. Don't display error messages to the browser. This is almost always
turned off but sometimes when you're testing you turn this on and forget
to reset it.
2. If your PHP is compiled with memory limit checks, the default is 8MB
which is much too small. You should increase this to at least 32MB or 64MB
to avoid PHP out of memory errors. Look for "memory_limit" in your php.ini
file.
3. GLOBAL variables must be turned off. This is one of the first things
any security aware admin will do. These days the default is for it to
be off!
The easiest way of configuring it is via the .htaccess file that is
created during the install. If you haven't installed WPMU yet then edit
the file htaccess.dist in this directory and add these two lines at the
top:
php_flag register_globals 0
php_flag display_errors 0
This is NOT included in that file by default because it doesn't work on
all machines. If it doesn't work on your machine, you'll get a cryptic
"500 internal error" after you install WPMU. To remove the offending lines
just edit the file ".htaccess" in your install directory and you'll see
them at the top. Delete and save the file again.
Read here for how to enable this: http://ie.php.net/configuration.changes
If you don't want to edit your .htaccess file then you need to change your
php.ini. It's beyond the scope of this README to know exactly where it is
on your machine, but if you're on a shared hosted server you probably
don't have access to it as it requires root or administrator privileges
to change.
If you do have root access, try "locate php.ini" or check in:
/etc/php4/apache2/php.ini
/usr/local/lib/php.ini
Once you have opened your php.ini, look for the sections related to
register_globals and display_errors. Make sure both are Off like so:
display_errors = Off
register_globals = Off
You'll have to restart Apache after you modify your php.ini for the
settings to be updated.
4. If you want to restrict blog signups, set the restrict domain email
setting in the admin.
- Aurais je mal compris la doc ?
- Y'aurait il une librairie manquante sur sme ?
- Une option du httpd.conf doit elle être ajoutée ou mise en true ???
Merci d'éclairer ma lanterne sur cette incompatibilité que je ne m'explique pas
](./images/smilies/eusa_wall.gif "Brick wall")