• Resolved dixonge

    (@dixonge)


    OK, maybe it was my old profile? I can’t seem to post anything here without triggering spam filters and locking the thread. Maybe someone can actually reply to this one…fortunately, I found another login I used to use!
    ———————
    I have my main site and one add-on site up and running on multisite. Today I had a major issue come up with a third site and the host admin ended up pretty much wiping the install directory, so I decided it would be a great time to go ahead and migrate this third site into my multisite install.

    So far, after lots of SQL insanity, I seem to have managed to get the main content back up and running. But when I went to put my old original header image back up, I just hit a brick wall. Here are what I believe are the relevant image path settings as they stand right now:

    Uploads Use Yearmonth Folders = 0
    Upload Path = wp-content/blogs.dir/3/files
    Upload Url Path = site3/wp-content/blogs.dir/3/files
    Fileupload Url = site3/wp-content/blogs.dir/3/files

    When I attempt to upload a new header image, it is broken. WordPress is trying to assign it this URL: site3/files/cropped-Server+Room2.jpg

    htaccess contains the following:

    https://pastebin.com/QwzxLh7R

    Any ideas?

Viewing 6 replies - 46 through 51 (of 51 total)
  • I use mod-rewrite and have changed the upload settings for all blogs including the multisite. From the information below, it appears based on that the httpd.conf file is allowing instructions to be written.

    httpd.conf is a configuration file which is used by the Apache HTTP Server. It stores information on various functions of the server, which can be edited by removing or adding a number sign “#” at the beginning of the line, thus setting values for each directive.
    The httpd.conf file can be located on any UNIX-based system that complies with the Filesystem Hierarchy Standard under the following path: /etc/httpd/httpd.conf.
    This file, httpd.conf was once used in Microsoft’s Internet Information Services
    There is a module, invented and originally written in April 1996, called mod_rewrite that is designed to provide a rule-based rewriting engine, based on a regular expression parser, to rewrite requested URLs on the fly. This module operates on the full URLs (including the path-info part) both in per-server context (httpd.conf) and per-directory context (.htaccess) and can generate query string parts on result. The rewritten result can lead to internal sub-processing, external request redirection or to an internal proxy throughput. It has been described as “voodoo,” and Brian Behlendorf of the Apache Group has said, “The great thing about mod_rewrite is it gives you all the configurability and flexibility of Sendmail. The downside to mod_rewrite is that it gives you all the configurability and flexibility of Sendmail.”[1]

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    There was very little MultiSite changed in 3.3

    There WAS a lot of PHP and JS being changed, but seeing as you’re the only person with this issue, the odds are it’s something particular to your server.

    The block’o;text you quoted doesn’t tell us what I’m asking about. Go look at the httpd.conf file. SEE if AllowOverride is set to ALL. Seriously, it doesn’t take that long and you’ll have performed one of the integral checks in debugging.

    What is different from the MultiSite PHP and JS that is different from the single WordPress PHP and JS? I have not lost any functions from the single installs, all load images and have no issues. As I understand it, there isn’t much of a difference any more?

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    I was about to say ‘nothing’ is different between the code in Single and Multi but … well, KIND of nothing.

    The code is the same code, it’s just called differently, and a large percentage of that is controlled by the .htaccess file which redirects things for you. Since it’s JUST images, AND Andrea and I, being experienced in this matter, know that uploaded images are handled by the line in your .htaccess that has /files/ in it, it’s our educated guess that your server’s not parsing that line correctly.

    Hence why I’m badgering you about at least checking the httpd.conf. Which, if you won’t, I’m done.

    What is different from the MultiSite PHP and JS that is different from the single WordPress PHP and JS?

    Not a single thing. It;s the exact same files.

    I found an old .htaccess file from October and overwrote the current one. I’m not sure what was written to it by 3.3 but that resolved the issue. Thanks for helping to isolate where the issue would be.

Viewing 6 replies - 46 through 51 (of 51 total)
  • The topic ‘Image path issues and confusion’ is closed to new replies.