Getting 500 Errors when attempting to populate

If posts are not showing up in the tags blog when you publish a post then the populate is definitely not going to work.

Publish a single post then check your error logs.

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.

@drummergirl – Just to reiterate:

If posts are not showing up in the tags blog when you publish a post then the populate is definitely not going to work.

Until you have the publish single post sorted out, there is no point in trying to troubleshoot the populate feature.

Is the search engine visibility turned on in the Settings -> Reading screen? If so, then you have something conflicting with SWT and you will have to starting disabling things to see what the conflixt .

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.

Glad you found it.

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?

The www in the URL is quite possibly a bug in the tags blog (which I’ll be able to fix). However, editing the domain should not have affected SWT because internally it uses the blog ID not the domain/path to identify the tags blog.

Future dated posts are not pushed to the tags blog until they reach the publish date.

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.