[waveslider]

It was strange. I think I’ve fixed it now, but the disconcerting thing is that I’m not sure why what I did fixed it.

Here’s what I did:

Initially, I just deleted the broken subdomain blog and recreated it with the same title and subdomain as before (after I confirmed that my test subdomain blog worked fine). This failed however; the permalinks were still redirecting to the 404 page.

Then, I checked the database for artefacts after deleting the broken blog. In table wp_bp_user_blogs, there were two records remaining that contained the blog_id of the deleted blog. So I backed up the table and then deleted those entries.

Afterwards, I recreated the blog a second time. Now it seems to be working perfectly. But I don’t know why

[waveslider]

Ok, I created a test subdomain blog, and it worked perfectly – didn’t have any of the issues the other one did.

I’d really like to investigate this to find out what went wrong, so I can hopefully prevent it from happening again. But for now, in the interest of saving time, my boss just asked me to delete the malfunctioning blog and recreate it.

[waveslider]

It is version 2.9.1.1 of MU.

That’s a good call – I’ll try setting up a test subdomain blog and see if I encounter the same problem.

[waveslider]

Yeah, no www. was included in the link, and it only happens on that one particular subdomain blog (although it is our only subdomain blog). And it definitely was not happening before today.

[waveslider]

I am using version 1.1.3 and am also having this problem. I thought it was an apache configuration problem or .htaccess syntax error, but aside from getting the “exceeded max redirects” error from apache when attempting to access the /activity/delete/id url, i didn’t experience any other issues (except for the 404 not found page being displayed, of course).

[waveslider]

I just did a clean install, but the problem persists for me. Is there any other solution for this one? Thanks.

[waveslider]

bump..