WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] 3.5.1 Error logs for rewrite in Multisite (5 posts)

  1. _Redd
    Member
    Posted 1 year ago #

    Hi, I have a new install of 3.5, which was upgraded to 3.5.1 Beta via the plugin.

    I set up a test site, Multisite using subfolders.

    The URL of the test site is http://cook-my-catch.com

    The test site reads the CSS for some, but not all of the child themes. The test themes A and B have EXACTLY the same css code as the child themes for sites that works, only the "name" of the style.css sheet was changed, as well as the name of the folders. Yet, the CSS works for some of the sites, but not the others.

    This problem was true in 3.5, and I upgraded to 3.5.1 to see if the problem would be fixed, but it was not.

    At first I thought bad child themes were the problem, but I never got an error message from them (debug is set to true). In my insecurity, I completely wiped out the code of the broken themes and replaced them with the code of the good child themes. That didn't make a difference. The multisite set up seems to read the CSS for some of the themes, but not all.

    Here's what's in the "allowed themes" field of wp_meta, blog site 1

    a:6:{s:12:"twentytwelve";b:1;s:21:"twentytwelveHomeChild";b:1;s:22:"twentytwelveSitesChild";b:1;s:20:"twentytwelve DLChild";b:1;s:24:"twentytwelveSitesChild A";b:1;s:26:"twentytwelveSitesChild - B";b:1;}

    It's my understanding (please correct me if I'm wrong) that according to this, all themes are allowed.

    Here's the rewrite rules generated by WordPress, and...
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [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]

    ...Here's how they are incorporated in the .htaccess files of my test site:
    # Use PHP5 Single php.ini as default
    AddHandler application/x-httpd-php5s .php

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [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]
    </IfModule>

    # END WordPress

    I get multiple, repeated errors in the logs as follows:

    [Mon Jan 07 08:41:37 2013] [warn] RewriteCond: NoCase option for non-regex pattern '-d' is not supported and will be ignored.
    [Mon Jan 07 08:41:37 2013] [warn] RewriteCond: NoCase option for non-regex pattern '-f' is not supported and will be ignored.

    Any insights you have are appreciated. Thanks again to the awesome team that is WordPress!

  2. Jesús Franco
    Member
    Posted 1 year ago #

    Which version of Apache are you running?

  3. _Redd
    Member
    Posted 1 year ago #

    Good morning, Jesus.

    My personal scratch site is on Bluehost. According to this wiki,Bluehost, the server software is Apache HTTP Server version 2.2.23, and OpenSSL version 0.9.8e.

    Again, thanks for everything!

  4. _Redd
    Member
    Posted 1 year ago #

    One other thing, I just noticed--not sure if it relates to the current problem, but here is some more information.

    The archives for this test site are for December 2012, with the "Hello World" post dated December 11, 2012.

    I didn't create the site until January 4, 2013.

    Where are these archives, dated before the creation of the site, coming from? Or, "why" are they dated as December 2012 instead of January 2013?

    If the problem of the wrong month for archives is a known bug, and unrelated to the theme CSS/theme no-CSS issue, please feel free to disregard it. I just wanted to add more information as I found it.

    Thanks again, Jesus!

  5. _Redd
    Member
    Posted 1 year ago #

    Hi, we've narrowed it down a bit.

    Seems like the rewrite errors are generated only when I've put WordPress in a domain, due to application/x-http-php5s .php file. Since this server environment only applies to the scratch site, our development server isn't expected to generate similar rewrite errors.

    It doesn't fix the problem of css loading only for some, but not all, of the themes in multisite, but, apparently, that's a different issue unrelated to anything with the .htaccess file.

    I'm marking this resolved for now, and wiping the scratch site to start over.

    Thanks again, Jesus, et al, for following as you have, and all the work you've done to this point. Best regards.

Topic Closed

This topic has been closed to new replies.

About this Topic