Cole Geissinger

I pushed on and fixed everything up to my liking (minus the odd disappearing form) and pushed forward with taking this to the live server and it doesn’t have the same issue, although this site is still running 3.4.2… It’s seems to be a 3.5 issue so far.

Just reinstalled a fresh copy without multisite and permalinks are working with no problems.

I setup back up multisite again with a different named sub-site and the problem continues. Not sure I’m missing something here?

test is the sub-site I created.

So the root install is https://localhost/wordpress-3-5/ Everything works fine here, but once I go to the network admin and create a sub-site, like test here, I get the error.

Sadly, I get the 500 internal server error still ??

What I have found, is that if I do a fresh WP install of 3.5, I get the error in any sub site I create, basically rendering Multisite useless ??

BUT if I use the WordPress Beta Testers plugin and tell it to update with the bleeding edge nightlies, I can update an older version and everything works fine…? I still think there’s a misconfiguration in the htaccess, but this must be something local to me or else I don’t think we’d be hitting RC1 if this was a global issue…. Does any one have issues installing and setting up a multisite in a folder like I did? I’ve always done it like this with no problems.

https://localhost/wordpress-3-5/test/wp-admin returns with internal server error 500 for the admin area, and then the URL rewrites don’t seem to translate for the frontend because all the stylesheets and javascript return with 404’s ??

I’m having the same issue.

Running locally on MAMP on OS X 10.8.2 and just pulled a fresh copy of beta 3. I didn’t have this issue in beta 2 though….

I was able to get everything to work by copying and pasting an old htaccess rewrite from 3.4.3-beta and everything worked.

I setup multisite (I guess they don’t need a blogs.dir setup for this any more??) and once I create a sub site using subpaths (I have mine setup like this https://localhost/wordpress-beta/test-site) navigating to /test-site returns a 500 server error. It’s almost like the rewrites it spits out in the beta is missing something or there’s a typo. Here’s the rewrites it tells you to use.

RewriteEngine On
RewriteBase /wordpress-beta/
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).*) wordpress-beta/$2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ wordpress-beta/$2 [L]
RewriteRule . index.php [L]

This rewrite returns a 500 error, then if I update to the old rewrites

RewriteEngine On
RewriteBase /wordpress/
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).*) $1 [L]
RewriteRule  ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
RewriteRule . index.php [L]

everything runs just peachy in 3.5-beta3. The difference I can find is the lack of the rewrite for the ms-files.php? But it’s obvious the supplied htaccess rewrites has a typo in there some where. Not an htaccess guru… so any insight would be sweeeeet ??

EDIT* ok, I see more of a difference now besides the ms-files.php rewrite… anyways, it seems something is off in beta3. Can anyone else duplicate?

I too am having the same problem… Anyone? Anyone? Bueller? Bueller? ??

Hey Jpyper,

Unfortunately I did not figure this out. I love this plugin, but due to this small missing feature I had to work on my own custom solution ??

one other bug I found…

When I deactivated the plugin it removed all of my active templates? ??

oh ok, I see how this is working now. ??

I haven’t seen/heard of the wp-signup page. You should try including a link to that section if possible? I wouldn’t have found that page with out some googling ??

I’m confused then.. how do I create a new site by choosing a template if it’s not working in the “Add New Site” section? Is there another area I’m not seeing?

That’s how it used to work when there was a Super Admin box in the sidenav but everything has moved to the network admin?

I’m just trying to figure out how to use the plugin with 3.1.2 ??

Thanks for taking a look at it. I’m thinking maybe the slider is conflicting with it :/
I’ll continue to debug this, at least now I have things narrowed down ??

Thanks again!!

Fixed my issue.

Ultimately I had to rely on a plugin, but works great! WP No Category Base

I have just found my issue was due to the removal of the category base from URL structure. I removed this via functions.php like so:

function remove_category($link) {
return str_replace(“/category/”, “/”, $link);
}
add_filter(‘user_trailingslashit’, ‘remove_category’);

So now I revise my issue,

How do allow multi-level (nested) categories and remove the /category/ folder that displays in the URL?? ??

Thanks!