WordPress 3.5 Upgrade Multisite Issues

Not something WordPress can do. It’s impossible for it to delete anything other than the files specifically listed in the delete file, and if that was the case, everyone would have screamed.

wordpress 3.5 move all my images to there blog.dir site folder however the htaccess file you guys provided didnt’ update to reflect the change through you guys automatic upgrade. also am seeing this in my view source of my website multisiple times in there

<script type="text/javascript">var sgi = [["http:\/\/mywebsite.com\/mythemefolder\/files\/2012\/07\/0bc39f29-478x361-joan2.jpg","0bc39f29-478x361-joan2",["969","772"]] </script>

No, WordPress did not move anything anywhere.

Again. WordPress cannot, will not, move your /uploads/ files for your main site, or any site. It just doesn’t.

In fact, in 3.5 any new site actually has ALL images in /uploads/

So … No. This is something entirely on your end that did this.

why is that script showing in my source when i view it, we did not change any code or folders site was running perfectly before the upgrade, and this happen right after the automatic upgrade. we had to backup our site because of this. we have gotten most of our images back from an backup. but we are not sure why that script is showing the paths to our images in the source

Either you have a bad plugin or theme, or you’ve been hacked, but that is not a part of standard WordPress.

Really, if this was something WP did, people would have the dev’s heads on spikes ?? WordPress.COM runs Multisite, so I know that didn’t happen.

This has also happened to my WP Multisite all images have disappeared + I’m unable to upload new ones after updating to v3.5

I have tried disabling all plugins and reverting to the 2012 theme nothing helps.

All the sites on my Multisite had been working fine for years until I updated to 3.5!

i knew this was an wordpress 3.5 issue because up until i upgrade thats the issue i had. site was perfectly fine in 3.4.2

Mika:

Do you enjoy talking down to people?

Stop talking to us all like we are dogs!

And this is a known wordpress issue from what I have read.

It’s impossible for it to delete anything other than the files specifically listed in the delete file.

Nothing is impossible help with the issue or dont bother to respond to our post.

It’s not known. Or rather, it’s not widespread. And I’m not talking down to you, I’m attempting to explain that this is not how WP functions.

It does not delete anything in wp-content/uploads or wp-content/blogs.dir (depending on how old your Multisite was).

Read this: https://halfelf.org/2011/how-the-wordpress-upgrade-works/

That’s how the upgrade works. WordPress can only delete the files listed in there. So if the WP automatic upgrade is deleting files, it’s not the core WP that’s the problem, it’s something else on your site.

Are the images actually deleted off your server?
Did you check your server logs to make sure they were removed at the time you ran the upgrade (you can compare that to the updated timestamps on your WP files)?
What plugins do you have?
What theme are you using?
What, if any, debugging or research have you already tried?

I am very sorry this happened to you, but I’m also 100% confident that Core WP cannot delete your images in /wp-content/uploads or /wp-content/blogs.dir, or any other place. The only way you might be able to pull that off is if you put the images somewhere in wp-admin or wp-includes.

Since I lost all my images after updating to 3.5 I must conclude it’s a problem with 3.5. The only changes made to my site was updating WP and it was working fine until the update.

I’ve checked the /wp-content/uploads files and they are now empty!

I can add that this is definitely an issue with 3.5 and a Multisite installation.

My single sites are loading fine with exactly the same theme and plugins I use on my multisites and all images are being displayed correctly.

The URL of the images on my Multisites have been shortened and changed to SiteDomain.MainDomain.com/files/2012/*/*.jpg, the correct path to the images is www/wp-content/blogs.dir/*/files/2012/*/*.jpg.
Unfortunately the media editor does not allow me to correct URL’s otherwise i could correct them manually.

Please look into this issue with Multisites.

as i stated mika, after the upgrade wordpress 3.5 moved my images from /uploads/2012 to /wp-content/blogs.dir/1 << there was folders i personaly created before the upgrade on 3.4.2 with images in them and they also got moved to that specific multisite folder where they was linked to from withing backend of site. whatever images was attached to an multisite it got moved to there respective folder under blogs.dir/ its imposible for us to move our images here to those folders when the site was working normally on 3.4.2 and on top of that we keep seeing our internal paths in our site view source from browser, we contacted our hosting company as we have certain security measures in place and file monitoring and none of that was tampered with. this happend right after the upgrade to 3.5.

This is what I experienced too

You two are the only people I’ve seen in the weeks since we’ve had 3.5 to have this problem. This is not a widespread issue, if it’s even core WP at all.

I perfectly happen to spend time debugging, but you guys have to help out here since you’re the only ones having the problem. I can’t recreate it, so I can’t even tell you where to start:

Are the images actually deleted off your server? (ahuggup86 says his were moved, christokid says deleted)

Did you check your server logs to make sure they were removed at the time you ran the upgrade (you can compare that to the updated timestamps on your WP files)?

What plugins do you have?

What theme are you using?

What, if any, debugging or research have you already tried?

wordpress 3.5 moved my images from /uploads/2012 to /wp-content/blogs.dir/1

Just the 2012 folder? There should have been one for each year.

Did it move them to blogs.dir/1/FILES/2012?

The URL of the images on my Multisites have been shortened and changed to SiteDomain.MainDomain.com/files/2012/*/*.jpg, the correct path to the images is www/wp-content/blogs.dir/*/files/2012/*/*.jpg.

That’s not wrong, and has never been wrong. That’s how Multisite is supposed to work. Your .htaccess has a special rule that accounts for that. It’s worked like that since 3.0 ??

Just to clarify, you are speaking of the images for the main site (the site with ID “1”) or all of the sites in your multisite network?

In the multi-site installations that I have done, the files for the main site (i.e. https://www.mymultisiteinstallation.com) were put into “/wp-content/uploads/[year]/[month]/” and the files for all of the other sites were put into “/wp-content/blogs.dir/[site_id]/files/[year]/[month]/”.

I can confirm that after upgrades from 3.4.2 to 3.5 on all of my multisites, that these paths did not change, however, I am not saying that they did not change for you.

Could you post the contents of your .htaccess file? If you have an old copy (pre-3.5), could you post that as well, if they are different? Make sure to enclose the htaccess code in backticks or use pastebin.com to post the .htaccess code (see https://codex.www.ads-software.com/Forum_Welcome#Posting_Code).

Other items that might help in reproducing the issue:

• You said that you upgraded from 3.4.2 to 3.5. Do you recall what version you used when you first did these multisite installations?
• What plugins are installed in the multisite network?
• Which plugins are activated on the main site?
• What theme is in use on the main site?
• Did you upgrade using the update functionality within the WordPress Dashboard or did you use an automated upgrade provided by your hosting provider (many hosting providers offer “one-click” installations of WordPress, as well as their own update mechanism)?
• What hosting provider do you use? It’d be helpful to see if there is any correlation between those who are experiencing this problem and the who they host with.
• My assumption is that your web host uses the Apache web server on Linux (the most common for WordPress), but let me know if this is not the case.

If you’re uncertain about anything I’ve asked, please let me know.

Thanks for your patience as we try to reproduce the problem and get to the bottom of it.