Upgrade to 3.5 emptied Media Library and Uploads folders

most of the images in my upload folders were not transferred to the upgraded site

I’m not sure what this means, exactly. An upgrade doesn’t “transfer” anything, because nothing is actually moved anywhere. All the files that were there before should still be there.

How did you do the upgrade?

most of the images in my upload folders were not transferred to the upgraded site

WordPress does not touch the uploads folder during an upgrade. Have you checked the uploads folder for files using FTP?

The upgrade was an automatic one through my host, DreamHost. Their support folks are pointing the finger at WordPress.

The media files exist in the backup, but not in the upgraded site. And yes, I checked the actual server.

Hmmm… Tagging this topic for one of their WordPress gurus to have a look at.

This just happened to me as well after upgrading to 3.5. I am on Bluehost with a Multisite install. All of the images that were in the blogs.dir folder were deleted.

The media library still acts as the image is there ,has the titles and url’s and such, but no image.

I re-uploaded the blogs.dir to the server and now it shows that the images are in the folders but they still won’t show up on my sites or in the media library.

This has just happened to me too. All my images are missing?

So it appears it didn’t delete the images. It added a bunch of empty folders–folders labeled with years and dates that were not there before. For instance I now have a 2013 folder for each site in my blogs.dir.

The backup which was created 3 days ago, has no such folders. Do not know if that is significant or not.

So the images are on the server, listed in the media library, but appear as a broken image. When I type in the url of the image into the browser I get a 404 page.

Ok I was able to fix the problem.

The issue for me was my .htaccess file. It was completely wrong. I had previously used a plugin called BulletProof Security and it works by completely rewriting your .htaccess file. I disabled the plugin and deleted it awhile ago but I guess it still left remnants.

I replaced my current .htaccess with a backup that had the right configuration and that fixed it.

This JUST showed up in my queue, and for that I’m very sorry.

The upgrade was an automatic one through my host, DreamHost. Their support folks are pointing the finger at WordPress.

They shouldn’t be. WordPress doesn’t work that way.

What’s your domain, Jess, I’ll go take a look if we haven’t fixed this already. I am VERY sorry I missed this post ??

Mike – I’ve had to rebuild everything manually, so there’s nothing to see at this point. I went through many support tickets, and my domain was moved to a new Apache instance to deal with slowness issues as well. Needless to say, I have turned off automatic upgrading for all 60+ WordPress sites I have hosted with DreamHost. But thanks for checking in!

longshot3 – please start your own thread as your issue was completely different than mine! Same with you, whysoserious92, and provide details.

I’m marking this as resolved because I fixed it myself, though the issue itself still exists in that there is no explanation.

That is really weird :/ Both our upgrader and WordPress’s leaves your wp-content folder alone. The only time I’ve see that happen is when someone was moving servers, but you moved afterwards.

That other post you linked to seemed to have the problem in 3.4 as well as 3.5, which makes me wonder if there was a bad setup on his box. If you want to email me your domain name, I can poke around and see if anything jumps out at me for causing an error like this in WP.

mika.epstein AT dreamhost.com ??