Tested this on my site, and it works fine. Do you have any plugins in mu-plugins?
Did you update your .htaccess?
Does this work on the MAIN site?
1°) Yes, i have any plugins :
– Sidebar Login v 2.3.3
– Role Scoper v 1.3.46
– NextGEN Gallery v 1.8.4
– Lightbox 3 v 3.0
2°) I just added “Options All -Indexes” to the file.
I did a test without this line, but there is no change.
3°) Yes, very well, but the files aren’t in the /blog.dir/1/files/2011/11
For the main site, the header files are in uploads/2011/11
is it normal ?
The locations are normal for your URLs 🙂
What’s IN your .htaccess?
Can you upload and use ANY image on the front end of your site? That is if you upload an image to a post on the subsite, does the image show up when you view the post?
It’s possible your server doesn’t have AllowOverride set to ALL in the httpd.conf, which you may need to ask your host for help with.
Thanks for your help !
1°) see my htaccess
SetEnv PHP_VER 5_TEST
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]
# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L]
RewriteRule ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
RewriteRule . index.php [L]
Options All -Indexes
2°) Yes i can update image and put in a post.
I can just insert the image, or even insert a gallery without any problems in the sub-site.
3°)Is it possible to access and edit the httpd.conf to see this directly ?
Sorry, my computer programming skills are limited …
English too;) but I try!
Is it possible that this is the file wp-blog-header.php that is corrupt?
Here’s what it contains:
<?php
/**
* Loads the WordPress environment and template.
*
* @package WordPress
*/
if ( !isset($wp_did_header) ) {
$wp_did_header = true;
require_once( dirname(__FILE__) . '/wp-load.php' );
wp();
require_once( ABSPATH . WPINC . '/template-loader.php' );
}
?>
Okay that’s a bit weird. I use 2011 and it works fine on sub-sites.
Are you running any network plugins?
I told you all the components and plugins I installed.
I have them all off to a test and there was no change.
Now, of course, I have reactivated.
The French forum also can not find the solution and can not reproduce this error on their test sites.
Here the discussion
This is really bizare … especially since I have not added any code!
I am still awaiting the response from my host to httpd.conf.
My French is bad 😉 But I can’t reproduce this either. I asked about the network plugins because there are two kinds of plugins in MultiSite.
1) Plugins you activate for the network
2) Plugins you activate for each site.
Sorry for the long response time. It was later here when you posted your last message.
No, I think your French is excellent ! “thank you google translation”:)
I dared to offer this link to show you what has already been tried and to save your time.
But it is perhaps not a good idea since we have not found a solution …
I installed all the plugins (detailed above) by the super admin in the main site.
I then “activate on the network.”
So, I have new menus that appeared directly in the administration of each of the subsites and was able to use the new features in each of the subsites.
But in the menu “extensions” of the admin of each sub-site, the installed plugins are not shown. I can not disable them individually and reactivate again.
I only have access to new menus (nextgen gallery, or role scope or side bar login) that appeared in the admin panel.
hello Ipstenu,
I finally have the answer to your question in the httpd.conf
Forgiveness of elapsed time, but I struggled to get it.
I hope now it will be possible to solve my mysterious problem.
3°)Is it possible to access and edit the httpd.conf to see this directly ?
AllowOverride FileInfo AuthConfig Limit Options Indexes FollowSymLinks =, Indexes, MultiViews, Includes, ExecCGI, SymLinksIfOwnerMatch
it is only valid with this directive