drummergirl

Thanks – I have not optimized the personal site associated with my WP account yet. I have been busy optimizing it on my company site and for clients. I will keep this in mind when I get to that site. Thanks.

Totally fixed it.

Thanks so much for the quick reply!

I’m having this exact same issue. I setup a chapter admin role, but I don’t want them editing plugins and themes, so I disabled those settings. I can login as that chapter admin role, but can’t access the dashboard.

So I changed the chapter admin role to have all permissions (checked all the boxes), but I still can’t access the dashboard with that chapter admin role.

What are we doing wrong?

Thanks for the update!

Thanks for checking. I just talked with my client and I think they are ok with disabling the Jetpack comments for now. That should resolve the issue for them.

So there’s no way around this…. will this be added in a future upgrade?

Kind of a deal breaker for me. :/

Same problem here. Upgraded to 2.0.11 and the problem persists.

Sorry for the bump, but I’m still looking for a solution to this.

By “future” I meant any posts published after I set up the tags blog, not posts with a scheduled publish date – I guess that was misleading.

I’ll run another test tomorrow and see if I get the same scenario as described above.

Ron – still having an issue with this. It seems that when the plugin tries to create the tags blog, it creates it as “tags.www.domain.com” instead of “tags.domain.com”. That blog won’t open for me because it can’t resolve the name, of course.

If I change the site name manually to “tags.domain.com”, I can see the posts, but then no future published posts show up in that blog. The plugin just creates another “tags.www.domain.com” blog.

I’ve deleted everything and started over but it still creates the initial tags blog as “tags.www.domain.com”. For blog name, I am just leaving it as “tags”.

I’m sure this is a setting in my network somewhere, but I’m stumped as to where to look. I can create other blogs just fine. Any ideas what I should do here?

Ron – still having an issue with this. It seems that when the plugin tries to create the tags blog, it creates it as “tags.www.domain.com” instead of “tags.domain.com”. That blog won’t open for me because it can’t resolve the name, of course.

If I change the site name manually to “tags.domain.com”, I can see the posts, but then no future published posts show up in that blog. The plugin just creates another “tags.www.domain.com” blog.

I’ve deleted everything and started over but it still creates the initial tags blog as “tags.www.domain.com”. For blog name, I am just leaving it as “tags”.

I’m sure this is a setting in my network somewhere, but I’m stumped as to where to look. I can create other blogs just fine. Any ideas what I should do here?

Solved it. Needed to add the new taxonomy to the child theme being used on the member sites.

Ok – I figured this out. We had 2 blogs with the name of “tags”. The url for the one I was trying to populate was tags.domain.com. The plugin had created a blog called tags.www.domain.com and was trying to populate that one, which is why I was seeing the not found errors.

I removed the first ‘tags’ blog and then corrected the url by removing the .www and now it’s working as expected.

Ron – I just published a post from the main blog, a user blog and on the tags blog itself. The only one showing on the tags blog is the one published from the tags blog.

So I ran the populate posts function again… first with the blog ID of the user account. It said it completed, but no new posts showed up. Ran it again and checked “all blogs” and it it gives me the 500 error again.

Found the problem… I had added another function farther down that was showing the thumbnails in the dashboard overview (list view for posts). It had the line:

add_theme_support('post-thumbnails', array( 'post', 'page', 'gifts', 'affiliates') );

Once I added my new post type, the featured image box showed up. Will go clean that up now.

Doh.