[wp-trac] [WordPress Trac] #14295: 2.9.2 to 3.0 htaccess not upgrading & breaks image paths

[WordPress Trac]

#14295: 2.9.2 to 3.0 htaccess not upgrading & breaks image paths
--------------------------+-------------------------------------------------
 Reporter:  gazouteast    |       Owner:                                                                     
     Type:  defect (bug)  |      Status:  new                                                                
 Priority:  normal        |   Milestone:  Awaiting Review                                                    
Component:  General       |     Version:  3.0                                                                
 Severity:  blocker       |    Keywords:  BUG, htaccess, 404, images, ms-blogs.php, blogs.dir.php, WPMU 2.9.2
--------------------------+-------------------------------------------------

Comment(by gazouteast):

 Replying to [comment:2 nacin]:
 > As Ryan explained, we don't update the .htaccess file when running
 multisite.
 >
 > The MU .htaccess file, of which there are many variations as it evolved
 over the years, works fine in 3.0. The old .htaccess files use wp-
 content/blogs.php, which we do not delete on an upgrade, and you only need
 to switch to ms-files.php if you choose to do so.
 >
 > I don't see a bug here. I've ran a few MU-to-3.0 upgrades and have not
 experienced problems with content loss or image path corruption. The old
 MU .htaccess file worked fine, though I did end up upgrading them to use
 ms-files.php and the new .htaccess file.

 In which case nacin you have introduced another new bug - the admin
 screens carry a warning to delete blogs.dir and change to ms-files whilst
 keeping the public side in maintenance mode and inaccessible - there is no
 OPTION given, it is a MUST DO action following upgrade.

 On a clean 2.9.2 install, auto-upgraded to 3.0, the old htaccess DID NOT
 "work fine" for me - on 3 servers on two continents.  You obviously failed
 to test something, or had a reversion after testing, which then broke
 something - why are so many forum threads complaining about this?  It it
 looks like a cow, smells, like a cow, and moos like a cow, then it
 probably is a cow.

 Again - you do NOT need to delete the old htaccess - you could rename it
 for roll back purposes, or append as I answered to Ryan.

 Why are you both obfuscating and avoiding?  Is this a path to generating
 paid support requests?  Go read the wp.org forums and you'll see how many
 people's sites this upgrade has broken.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/14295#comment:4>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software