• I have just installed a fresh multisite installation to compare it with my other multisite installation where I had problems with the image file upload paths after upgrading from an earlier wp 3.0 version to RC3.

    In went through all necessary steps but the permalinks don’t seem to work.

    After creating a new site test I am getting an email that the site has sucessfully set up (still I cannot access it) and in addition a new user was created with the name of the new site together with a password.

    This is a completely fesh installation and my feeling is that something is messed up with the multisite feature.

Viewing 9 replies - 16 through 24 (of 24 total)
  • i still have this problem.
    All the things that i tryied in local with my ubuntu server make me understand that maybe is not my fault..but of my hosting..
    i can create the subsites in subdirectory but when i try to visit them or go to the backend i receive a 404 the page cannot be found.

    but i think that the problem could be that my hosting is windows.
    there’s a way to make it works?

    thank you.

    but i think that the problem could be that my hosting is windows.

    Could be. You really need the mod_rewrite module working. A good way to check is to see if the pretty permalinks on the main blog work.

    the permalinks works properly…
    but this seems like the problem i had on my local web-server when i didn’t know how to enable “override all”.
    my site is:
    https://www.risorsegeologiche.com/blog/
    and all the sites(that doesn’t works) are under that folder
    for example
    https://www.risorsegeologiche.com/blog/prova/

    the strange thing is that i’m not able to see the backend too(of the subsites).

    Open up the apache confgi file and in the vhost entry for that domain, put:

    AllowOverride FileInfo Options

    ……
    i do not have the “power” to do that….my hosting make this things by his own…if he wants..

    may i change something in my .htaccess to make it works?
    this is mine:

    RewriteEngine On
    RewriteBase /blog/
    RewriteRule ^index\.php$ - [L]
    
    # uploaded files
    RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]
    
    # add a trailing slash to /wp-admin
    RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
    
    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule ^ - [L]
    RewriteRule  ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
    RewriteRule  ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
    RewriteRule . index.php [L]

    i do not have the “power” to do that….my hosting make this things by his own…if he wants..

    may i change something in my .htaccess to make it works?

    Well, no… the command I gave above is to *force* the htaccess into being read.

    Sometimes if mod_rewrite is enabled, it’ll let the permalinks work on the main WP blog, but won’t really be reading the htaccess file. If it’s not reading the file, the extra blogs/sites will not get served up.

    that’s just how it works.

    tell your host you need the htaccess file enabled.

    Open up the apache confgi file and in the vhost entry for that domain, put:

    AllowOverride FileInfo Options

    the command I gave above is to *force* the htaccess into being read

    so I can’t do it….or not? i don’t think my host will change this for me..

    I just did .htaccess for wp3.0 ms.
    I also moved the existing media from their respective old blogs individual folders to

    wp-content/blogs.dir/<blog id>/files/uploads

    and set up the .htaccess so that the existing image urls from pre 3.0 MS resolve to their new locations (at least for the primary blog).

    I’m using wildcards and subdomains and AFAIK all that is resolving correctly with DNS and virtual hosts with wildcard etc.

    I found this link:
    https://www.ads-software.com/support/topic/386527?replies=13

    that told me to add this line
    RedirectMatch 301 /wp-content/uploads/(.*)$ https://www.mysite.org/files/$1

    to .htaccess

    Now I have three compllicated QUESTIONS so bear with me:

    #1
    Given that the remainder of my .htaccess is what’s recommended for wp3.0 ms I can see that the 301 Redirect redirects EVERYTHING with wp-content/uploads in the url to the main URL for all blogs.

    Then this rule:

    RewriteRule ^(.*/)?files/(.*) wp-includes/ms-files.php?file=$2 [L]

    kicks in and it rewrites yet again to dynamic code to resolve the file to the appropriate place. But it seems to me if the domain of the second request is always the main domain no matter what domain you’re serving media for, it will have no way to know which blog id folder to look in, and that’s borne out because images with old URL’s only render correctly on the “main” blog.

    Question #2

    I see a lot of upload URL and path fields in my uberadmin config for these blogs. Some clearly pertain to plugins (many of which aren’t even active!!) and I noticed when I uploaded new media it sets the URL to exactly where the file lives. I.E. none of those rewrite rules would be necessary. I have it configured to do that I guess, because I set all uploads URLS and paths to somethig with blogs.dir/<blog id>/files in it. It seems like going through all those rewrites introduces overhead so maybe that’s what one wants. But I haven’t seen documentation for exactly what those upload urls and paths control, for example is one for generating blog post URLS from uploads or what? What is considered best practice for the log run?

    Question #3

    Finally, it seems to me like someone might write a script to sequence through all the blog posts at database level and replace all media URLS that are currently working through complicated rewrites and redirects with straight URLS that resolve properly the first time? I have the skills necessary to write such a script if anyone thinks that would be a good thing to do.

    Actually one more What the *** is a “mature” blog? Does that mean it’s no longer being updated??

    Thank you!!!

    What the *** is a “mature” blog? Does that mean it’s no longer being updated??

    ?? No, it means the blog has mature content and will be skipped in public listings.

    Without copy& pasting specific questions, you’d be better off doing a search & replace in the db and chancing the URLs within the posts to the new folder. Then you won’t need the extra rewrite rule and you should be good.

Viewing 9 replies - 16 through 24 (of 24 total)
  • The topic ‘Multisite problems with RC3’ is closed to new replies.