Files directory inaccessible in MS upgrade from MU in blogs.dir/1/files.
|Reported by:||memitch08||Owned by:|
|Severity:||major||Keywords:||Upgrade to 3.0, files path corrupted, bad htaccess updater|
I upgraded my WPMU sites to WP 3.0 RC1 - and updated nightly builds till the release of 3.0. With the auto upgrade of 3.0 - my url path to my files became inaccessible. Namely - blogs.dir/#/files. The issue is limited to the word "files".
I have .htaccess configured for re-write as:
# uploaded files RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]
I have tried to disable plugins, added Wordpress to WordPress filter plugin, manully upgrade - all to no avail.
I checked permissions on the folder, and my host says that the ownership of the directory is consistent with the other directories. The files are available through FTP access - but when putting the path to the file/image url in the browser - the WP 404 page appears.
This has happenned on all (3) of my WP upgrades.
Also - it should be noted that adding new files through image upload - shows the file name in the media library - but when I try to access the file I get the 404 page - so it is not isolated to old files.
If I put the file in the blogs.dir directory without any subdirectories then the file is accessible.
It is still fine here: http://hanover4square.org/wp-content/blogs.dir/1/4sqlogo.jpg
But if I move the same file to the files sub-directory within blogs.dir it is not accessible?
But if I create a sub-directory called file1 the file is accessible?
To magically redirect it would be:
But that returns a 404 too.
Change History (7)
comment:6 gazouteast — 3 years ago
- Cc gazouteast added
- Keywords Upgrade to 3.0 files path corrupted bad htaccess updater added
- Resolution invalid deleted
- Severity changed from normal to major
- Status changed from closed to reopened