[FirstResponderBlogs.com]

Hi there,

I have been going through this thing off and on throughout the day. My conclusion, and don’t call me obvious, is this release is definately not stable.

In regards to this specific error…

…I was experiencing this earlier today when I had a clean install. I got so annoyed, I decided to wipe everything. After doing a complete wipe, I reinstalled everything manually. To my surprise… … the error continued.

So… I did what any annoyed and flustered script monkey would do… grabbed a coke and began to dig in.

I have managed to defeat this error by doing a clean install of WPMU 2.8.4 manually. I completely wiped the DB as well. I also did a fresh install of BP 1.1.

The issue, and it may not be this easy for all, appears to be “cleaning house”. Ensure when you are manipulating, transfering, and removing files, that you are replacing them with the 1.1 release rather than the 1.0.3.

I would provide more information; however, I am encountering more issues after defeating this. So rather than robbing Peter to pay Paul, I will wait till either I have a proven resolution for you or someone else beats me to it.

I will say this, once you review your theme files, you may find somewhere in all the code the path specified for the new theme structure appears to not have been completely updated or addressed. This is the issue I am currently working to defeat.

I hope this finds some of you well.

[FirstResponderBlogs.com]

You are not the only one with this issue. I have reinstalled this release about 6 times. By the numbers the first three to ensure I hadn’t missed a step.

I am trouble-shooting this bloody issue and pulling my hair out. Somewhere in the directives of one of these files, it is still searching for the themes at /wp-content/bp-themes, despite the instructions stating to delete that directory and point to the new structure in this release of 1.1.

If anyone figures this out, please post it up asap. I have been trouble-shooting all day and it seems this release was not stable. Kas3, no worries. You are not alone. I am debating digging into the code tonight, but am so annoyed with this right now, I may get back to it later.

I’ll keep you posted if I resolve it.