I’m not saying separation is a bad thing, far from it. BuddyPress adds new template tags that have changed from version to version. If you create a theme with these template tags that are no longer present, things will break.
The only way BuddyPress is going to upgrade without being a pain is if you either use one of the bundled BuddyPress themes as a parent, or use another framework that is kept up to date.
If you build a theme from scratch built on a copy of another theme, or do not create a child theme from a parent that is kept up to date, you are going to have a bad time.
This will always be the case, since BuddyPress is a tight combination of plugin code and theme code.
To be honest, if you’re unsure how to fix this sort if thing, don’t run the trunk version. Stick with official stable releases. It looks like your folder permissions are wrong. They should be 644 or 755.
@mrmaz Why not start up premium support by means of a forum? Or perhaps offer more advanced tutorials or docs for paying supporters. Quite a few people have found this to be a successful model, and it doesn’t shut everyone out – reducing overal interest.
As a general notice: Please do not upgrade or use the trunk if you are not prepared to encounter errors. The trunk is best for developers who can debug and fix problems. I know a lot of people are itching to try it out and upgrade, but it’s still not close to being ready for general use.
Perhaps when this site is updated to 1.2 (after release) and plugin developers can create groups for their plugins, we can attach a paypal donate link. That way each plugin developer(s) will get their own group, activity stream, forum, donate link and perhaps some of the other great extensions being released as plugins.
I’ve added the WP abstraction code that will allow BuddyPress to run on all WordPress versions to the trunk. This code will more than likely be needed even after the merge, so I want to get it in there and up and running for 1.2.
I’ve had it going for a while locally, so it seems silly to sit on this until 1.3. After the merge I will tweak where needed, but I don’t anticipate much change since the multiblog features of 3.0 will simply be an on/off setting.
The name field was previously split into “First Name / Last Name” fields, but this is an issue for internationalization. In future versions it may be possible to apply rules to profile fields that will determine the content allowed.
