I’m basically one-week new to BuddyPress and but I agree, right now, it’s a bit difficult to be theme agnostic since you have to provide the page templates yourself. We’re going to have to work with Andy and the other devs to find a way to start moving more toward the way WordPress does it:
https://codex.wordpress.org/Template_Hierarchy
This way your plug-in’s action, i.e. create new link, just uses the template framework’s create.php page and you don’t have to provide your own. Same with directories. There should be one directory.php file in a theme and every directory uses it.
Granted this is a huge task 
But maybe we can spur it via Links since Links is kind of the poster child for BP component plug-ins. I’m available to help hammer that out if any devs catch this thread.
This is absolutely great news for everyone who wants to use buddypress in the fields of education. Thank u very much for sharing with us. Is it all working on the frontend, or does the user has to enter the wp-backend?
Thoughts:
1. A searchable “wiki” directoy page would great.
2. Tags would be great – with a sidebar tag cloud widget on the directory page.
3. I also like ur idea of vertical “page” listing.
What a great xmas present
@Bpisimone
I am assuming it won’t work because 1.2 has a new theme. I have not even looked at theming for 1.2 yet, because from what I hear, it is still under heavy development. Once it has stabilized I will create a new theme with templates that work with the new 1.2 theme.
So this won’t be working for 1.2 bleeding then? Haven’t tried it yet, but I was going to very soon.
@Suzanne
Thanks for the kind words!
Managing themes in BP is a chore, but I think a lot of it has to do with the fact that there is just so much HTML required to display it. I tend to agree with you though. Simply extending the existing default theme is the quickest way to get up and running, so you end up with most websites just changing the colors, and not much of the layout. A separate framework for developing themes would be awesome, but you are still at the mercy of the direction of the project.
When 1.2 comes I will have to re-theme this plugin, so I will take all of the help I can get at that point! Any input as to how to re-make the templates so they are more generic would be great.
@lsddesign
I think you are probably getting that error, because buddypress-links requires PHP 5.2 or higher.
Found it.
For anyone else that has this problem, go into your Buddypress > bp-core > bp-core-adminbar.php
Find create-a-blog and change it to create
Your blogs can now be created.
Trunk changes daily and often times a few times per day, so you’ve probably got an incomplete revision.
https://trac.buddypress.org/log/trunk for the log.
Maz you have my vote for awesome plug-in as well. I’m excited about this one and the addition of the social media stuff this round was a great surprise.
If you want help with the presentation layer, I will help you. That’s my forte. I’m developing a theme framework for BP right now and am finding a lot of plug-in developers writing their code with a dependence on the BP theme framework 
I’d like to see everybody move toward theme independence where you create tags that theme developers can drop into their page templates. I realize we may need BP to serve up a standardized page template, with all the appropriate hooks and standardized list navigation for plug-ins however, but we have to start somewhere. I just don’t want everyone to get so far down the road where we’re all stuck with using the BP theme framework because all the plug-ins were written with its HTML and its CSS.
Ping me and I’ll help you.
P.S. I use Safari 4 so you’d have that piece covered too.
You don’t need two threads for the same issue. Since you have https://buddypress.org/forums/topic/can´t-upload-avatar, I’m closing this one.
@erich73, yes it’s possible to do, but I’m not sold that it’s a good idea to auto change slugs. Right now it works the same as WordPress does. Since slugs are important for SEO, automatically changing them can do more damage than good.
I’ll probably make it an option via a constant because I can see value in this for some setups.
This is BuddyPress centric forum, so if you are having wpmu problem, you should visit he forum at mu.wordpress.org as there’re more users than we have here on buddypress.org
Also please read and follow the step by step guide on asking question on forum.
https://buddypress.org/forums/topic/help-us-help-you
We are happy to help, but without enough information we can’t.
Is this on the new buddypress theme? Not sure what the reason is that the buttons are messed up. Can you provide a link?
5563306Inactive
Hi Ron!
Yes, avatars could be uploaded before upgrade.
No, I didn´t have to change file permissions to complete the upgrade.
We are using WordPress MU 2.8.6 and BuddyPress Versión 1.1.3
Yours,
Francisco
Dear JJJ,
I just saw that when I change the Group-name (as a user, not as the Admin), then the URL of that Group-page does not get changed but remains the URL from the originally created Group-name.
How to solve this, so that the URL gets updated when the user is changing the Group-name ?
Is this actually possible to do ?
Many thanks !
I’d be fine with an index / directory page. That page could perhaps even use sorting / filtering (at some point) similar to the BuddyPress directory pages in the latest default theme… i.e. most active, most recent… my wikis, all wikis… etc. And if you’re leveraging WordPress functionality… another way to organize the wikis would be by tags and categories… perhaps with a sidebar widget and a dynamic directory page depending on which tag / category you click on. Lots of ideas
@DJ
Thanks for the tip. I will keep that in mind when I tackle it
@Everyone
I didn’t receive many bug reports for this RC, probably because nobody will notice they can upgrade until the stable tag changes. Nobody has reported any catastrophic failures, so I went ahead and tagged version 0.2
Thank you very much to everyone that took the time to test this out and give feedback!
Just thought I’d give people an update.
1) As discussed, we moved to making use of inbuilt wordpress functions as much as possible and hence avoid the nightmare of trying to make mediawiki work in a way that is ‘nice’ with buddypress.
2) We’ve taken inspiration from the following plugins: front-end-editor, bp-groupblog and wp-wiki. We currently aren’t using any of the code from these, but many thanks to the authors of these plugins for their very informative code.
3) Work is progressing very nicely. Sadly we probably won’t have a working beta before xmas but I’m going to post up a few screenshots next week with some luck. In the meantime, here are two to whet your appetite slightly:
Group Wiki Create Screen
http://linktart.co.uk/_files_/dev/wiki1.png
Group Wiki Home Screen
http://linktart.co.uk/_files_/dev/wiki2.png
Please note: Our designer hasn’t re-styled these pages yet so bits of it look quite rough. Apologies about that. Functionality-wise we’re probably about 50% of the way there, with a few placeholders here and there until we can finish things.
Any thoughts? I realise that there isn’t exactly much to go on at the moment I should also probably again mention that we were looking for quite a simple wiki plugin for our students, not a fully blown wiki system…
Check trac ticket #1479 for continued discussion on having a base component.
When the BP plug-in is installed instead, I believe we should change the function bp_core_screen_signup() from the file: /wp-content/plugins/buddypress/bp-core/bp-core-signup.php in order to tell BP to accept our local mailserver in a similar way that the one described just before. Since I don’t need to do this for now, I haven’t written exactly the php sentences.
Best regards.
Note I am using the old default them (the orange one!)
I haven’t thought through how practical or difficult it would be to support the existing component structure. But, what if there was a base component class that all components extended (the way widgets extend the base widget).
In the child class you would need a registration process providing the component identifiers & possibly the URI to catch, activity logging, settings maintenance handler, a display handler, etc.
The end result would be that BuddyPress would become an activity based framework that the features plugged into.
Andy-
I agree. This discussion should be held in a developers area, away from the regular forum. Unfortunately, Trac and IRC are not great places to hold in-depth conversations, nor do either provide a mechanism with which to do so effectively.
In the past, there was a discussion about creating a developers’ resource section on BP.org–a place that would not only contain a library of code snippets, but provide an arena for the type of discussion that we’re having in this thread.
That discussion happened 8 months ago and lost steam. Read the entire thread as it starts out as a discussion about snippets and evolves from there:
https://buddypress.org/forums/topic/buddypressorg-needs-a-common-place-to-share-code-snippets#post-11852
@Andy Just updated to 2207 this morning and all looks fine so far. One question though:
on /groups/groupname page I see that “View Thread” is there in place of “Comment” for forum postings, which speaks to the sync issue being discussed on other threads but the link on “View Thread” is the group slug not the forum thread slug. For example on my dev site on the page
http://mjpratt.com/groups/usma-1987/
I see a nice listing of activity. The activity item “posted on the forum topic Yet another another test in the group USMA 1987: 3 days, 23 hours ago” has a “Vew Thread” link which points to:
http://mjpratt.com/groups/usma-1987/
Is this on purpose or a bug?
I see it’s generated on line 24 of activity/activity-loop.php in bp-default with
<?php if ( !bp_is_activity_permalink() ) : ?>
" title="<?php _e( 'View Thread', 'buddypress' ) ?>"><?php _e( 'View Thread', 'buddypress' ) ?>
<?php endif; ?>
I need to look further into the return of bp_activity_thread_permalink()
