Webhost requirements for plugin to function correctly

  • mrpatulski

    (@mrpatulski)


    12 years ago

    I am trying to use this plugin to create a 4 networks on the same domain each as subfolders. I have tested your plugin on my local OSX amp Stack and on my web host and it works partially ie everything performs as expected in the original network. When I go to second and third networks it stops working.

    [1] It will create additional networks.
    [2] The top level site and the wp-admin/network/ all work as expected in each network.
    [2] It will create a second or 3rd site within a network and the wp-admin causes “This webpage has a redirect loop”
    [4] When I go the sub-site of the second network the site displays with out any styling–basically not connecting to the default theme–2014.

    What do I need to do locally and ask my web host to make it work as expected?

    Any help will be appreciated.

    MRP

    https://ww.wp.xz.cn/plugins/wp-multi-network/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter mrpatulski

    (@mrpatulski)

    12 years ago

    One more point:
    I am setting up the network under the same domain:

    mysite.com/network1
    mysite.com/network1/site2
    mysite.com/network1/site3

    mysite.com/network2
    mysite.com/network2/site2
    mysite.com/network2/site3

    mysite.com/network3
    mysite.com/network3/site2
    mysite.com/network3/site3

    jswan2

    (@jswan2)

    11 years, 11 months ago

    One thing you might do is look at your .htaccess rules. I don’t know the cause of the infinite redirect, but you can access wp-admin/ if you go instead to wp-admin/index.php. I changed the standard rewrite rule for adding a slash to wp-admin so it adds a slash and an index.php and that seems to work okay.

    RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/index.php [R=301,L]

    As far as your other problem, I had another .htaccess workaround that worked in my limited testing. Essentially, your static resources are getting forwarded to index.php instead of getting served. Essentially wordpress thinks they are pages or posts in the site. What I did (and this may not work for your setup because you’re doing it a little differently than I am) is add a slash to the regex for the wp-content,admin, and includes url rewrite rule.

    RewriteRule ^[_0-9a-zA-Z-\/]+/(wp-(content|admin|includes).*) $1 [L]

    This, in my instance at least, allowed wordpress to look past the second slash in the static resources URL so http://wwww.domain.com/network/site/wp-content/themes/mytheme/style.css gets served as a static asset.

    There’s still a lot of problems that I’m running into and it sure would be nice if the plugin authors checked the support forums.

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

The topic ‘Webhost requirements for plugin to function correctly’ is closed to new replies.