Also… I just wanted to comment that it would be really nice if the documentation for Buddypress is more organized. Currently there is information about 1.5 mixed in with 1.2 and even earlier. Is it that difficult to separate major versions and keep it organized?
I came across an article in the codex talking about enqueued CSS, with lines of complex code including instructions to update a variable when changes are made to bust cache.
I am sitting here waiting for some answers without working any further on this project, thinking to myself WTF does enqueue stylesheet and bust cache mean, I cannot even get comprehensible answers googling them, and hoping that I did not waste numerous hours working on a pre-1.5 project powered by BP.
i do appreciate all the hard work put into BP, but just because it is open source doesn’t mean there is no need for any logic behind it. Obviously there is no expectation for serious projects to use it out-of-the-box with the default theme and default components, so in my opinion, it is essential to explain to your users what the next version means and what needs to done for a smooth transition. Instead of publishing several articles about an unreleased version, perhaps it would have been wiser to have done that instead. If I had the knowledge, I would have gladly offered that.
I really hope I don’t move to another platform as I love WP and really liked BP’s usability when doing my research.
There’s no end difference between installing and upgrading. Existing child themes should continue to work, as should those guidelines on the codex. It’s possible someone updated the codex incorrectly, or for an earlier beta version where we fiddled with child theme style sheets a bit (and then added more compatibility code in). Feel free to update the instructions; log in to wp-admin on the codex site and find/edit the Page.
