Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • OK, BIG Brain fart on my end. The solution to my problem was: Adding the web root into a VitualHost Directive. This server hosts a couple of in-house web apps, a MediaWiki instance plus the WordPress MS instance. Adding the VH for the web root fixed it….once there is one virtual host everything is a virtual host…. duh.

    Hope this saves someone else a lot of frustration.

    Thanks brasofilo –

    The problem appears to be apache is not rewriting the path to the directory. In the network installation this path “Site_URL/wp-content/blogs.dir/2/files/2011/10/some-file-name.png” gets rewritten to Site_URL/name-of-blog/files/YYYY/MM/some-file-name.png” I was under the impression the .htaccess file as defined in the network set up was there to ensure these paths were properly translates. However, this could be a apache config issue as I did have to create an Alias Directive for each of the blogs on the server. Unfortunately I’m not an expert with apache yet. The httpd error log indicate there is a path issue. There are virtual host on the server, any path to the web root “html/’ is requiring an alias. Apache 2.x, php 5.3, mysql 5.2. This was not a problem with 6 individual WP installation each in their own directory in web root. Still stumped!

    So I’ve have spent three week moving 4 single site WP installation, into a network site with 4 blogs. While still on the development server using version 3.2.1 newly uploaded images presented fine on the page and thumbnails were visible. After migrating from the development domain to the production domain, newly uploaded image thumbnails and page media do not display. You can go to the media library and select “edit” to see the image though. The “crop” feature is not available you can manipulate the image orientation.
    This is a version 3.2.1 to 3.2.1 migration, all plugin off. The latest php-dg library is installed on the server,Fedora fc-12.

    Has anyone found a solution? Have I missed some obvious.

    Same problem here today, clearing cache and cookies resolved the problem.

Viewing 4 replies - 1 through 4 (of 4 total)