Is there any way to "fix" the change WordPress made to the upload path?

  • Resolved larsenja

    (@larsenja)


    9 years, 9 months ago

    Greetings. I understand that WordPress changed multisite’s handling of the Uploaded File Path per the details here: http://codex.wordpress.org/Multisite_Network_Administration#Uploaded_File_Path

    I only recently discovered this issue as we’ve been maintaining several “older” installs and needed to start a new install.

    The long and the short of it is that Multisite was much better when the path would only reveal /files/ to get to media. In the new incarnation, forcing the full path reveals more detail than I or my customers are comfortable with.

    For example, we all would prefer that my customers could map images to theirdomain.com/files/2010/05/B1.jpg than being compelled to use http://theirdomain.multisiteserver.com/wp-content/uploads/sites/xx/2010/05/B1.jpg

    It makes their web site hosting seem so much less professional with the exposure of the server URL rather than using their domain. Make sense?

    Would love any help & feedback. I’ve searched around and so far and can’t locate any info on why this was done or if there’s a way to revert new installations to the “old” way of doing things.

    Thanks a bunch!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Marc Woodyard

    (@rune-vantage)

    9 years, 9 months ago

    This could be of some help.

    http://wordpress.org/support/topic/how-to-change-upload-directory-of-main-site-to-blogsdir?replies=11

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    9 years, 9 months ago

    Better is highly subjective. Using files was confusing, error prone, not well supported by plugins, and used more memory.

    The easiest way would be to install WP 3.4, create one site, upload nothing, and then upgrade WP.

    Frankly, it’s not worth it in the long run, and will make things harder to support down the road. BEsides, everyone knows on a single install where wp-content/ is anyway.

    Thread Starter larsenja

    (@larsenja)

    9 years, 9 months ago

    Marc, thank you for trying. That info is “old” as of the recent change in how WordPress is handling files. Given how things are working now, I would be hesitant to just muck about and make changes without really comprehending how they’ll impact the environment.

    Ipstenu, thank you for at least helping me understand why the change was made. While I hear you about the “easiest” way to proceed, what I also hear is that method shouldn’t be used because it technically is no longer supported, because plugin programmers will be less aware of the issue because the method is no longer supported, and because the new approach puts less of a burden on the servers.

    I’ll let it go. Thank you again for helping to understand the thinking.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    9 years, 9 months ago

    If devs ALWAYS remembered to use wp_content directories it would never be a problem :/ That they don’t makes things really weird (like themes with timthumb etc). It’s really the only reason I don’t miss it. I kinda liked the hiding.

    Thread Starter larsenja

    (@larsenja)

    9 years, 9 months ago

    Yeah – the hiding was awesome. Without it – multisite has a “dent” in my mind. Not enough to throw in the towel, but ugly to look at.

    It’s a shame that WordPress had to bend to the will of naughty devs rather than maintain this very cool, if subtle, feature. But I’ll bet the decision was made, at least in part, based on the volume of support handled here at wordpress.org for issues related back to that hiding.

    Again, thank you!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Is there any way to "fix" the change WordPress made to the upload path?’ is closed to new replies.