BuddyPress.org

If those template functions are similar, I don’t see a problem changing it, but get_template_part() fires an action, but it doesn’t let you filter things. What’s the benefit?

get_template_part() isn’t filterable, but creating a wrapper function would do the job much like the bbPress plugin is doing. (Sorry if I wasn’t clear above.)

I basically wrote a wrapper function for locate_template(). Similar to what’s suggested here:
http://bpdevel.wordpress.com/2011/01/12/there-is-a-dev-chat-today-wednesday-12t/

There’s an open ticket (#2649) on BP Trac suggesting to wait for WP core to implement the filter. However, in all likelihood, the WP filter for locate_template() will probably be implemented in a future release.

I am currently writing my own theme that looks nothing like BP-default, but I’ve been on trac almost daily with the UI tickets. I don’t know if we need a dedicated “UI/UX” team, but as long as folks are submitting on those tickets it will ease some of the other dev’s needing to mess with it. I DO think it is an important component with BP and we need to keep talking about 1.3’s problems.

I’m glad to see all the discussion going on, especially in light of all the “BP IS DEAD” nonsense. I think the biggest issue is how the forums make it hard to actually talk, but the testBP forums are great and I’m excited to see them go live here. I’m also anxious to see the new BP.org which seems to be slated to June.

My biggest issue with the BP sites I run is spam. Even my non indexed test servers get spammed. My AIGA site was deleting 250 spam users/blogs a day before shutting off new user registration. The first part of that comes from spam users being registered. There are two types of spam services, bots, and (slave) labor. These folks get through the Captcha’s and set up real fake accounts. But in my experience with my comment forms adding a Captcha killed a vast majority of spamers. Then with comments, contact forms, etc this would kill most spam. From there heuristic spam fighting from splogs, comments, etc. Also a system that users can mark a item as spam would help a ton.

Second, its that to learn how to do ANYTHING in BP I have to take something that works with the current version and hack it a part to figure out basic commands and actions. Once the new site is up I think there should be a real push on getting the Codex up to snuff(look at jQuery and WP) that have examples, resources, etc. Then have tutorials on things, hell syndicate them from other bloggers.

So as my thing(s) I want to keep being a part of fixing UI issues, and will as long as I can.
I want to write for the Codex, and am here and willing to write Blog articles for BP. Tutorials, Updates, whatever. I’m game. I will be writing tutorials for AIGA members anyway, so why not sync the content here.
I am working on the Group Documents plugin with its original developer because my sites need it.

And lastly I will be writing a BP-Spam component. I will do it as a plugin first and will want/need tons of feedback. But to get the University to sign off on my project I will need to stop all the Viagra and other inappropriate content from making it through. I will do this regardless of it being a part of BP but want to give back however I can.

I’m so psyched to see all the energy is still in this project!

I have a half-finished Akismet plugin for BP 1.3 for the activity stream if anyone wants to work on that with me

Anyone interested in UI should keep an eye on tickets marked as needing UI input: https://buddypress.trac.wordpress.org/query?status=%21closed&keywords=~needs-ui

Perhaps we can add some more reports to the Trac. Are there any on https://core.trac.wordpress.org/report that you would find useful on the BuddyPress trac?

EDIT: just added report 17 — “Needs User Experience / UI Feedback / Designs”

https://buddypress.trac.wordpress.org/report/17

@djpaul needs codex / documentation is another trac tag I follow over in core WP. This would be for anything that requires a codex entry to explain.

Also, how much work would it be to make the sidebar go on the left? Is it just a case of changing the CSS or is it lots of work?

Good question: given that the one of the prime reasons for separating presentation from content and of finally moving away from table based layouts and their rigid inflexibility was that it must always be possible to effect any presentational changes from CSS, moving a sidebar from one side to another is a classic example used to demonstrate the benefits of CSS presentation over table layouts; I would hope it’s a do-able with default layout, if not then the markup structure has interfered when it shouldn’t but doubt that’s the case.

at its most basic, switching sidebars is usually changing the floats in the css.

at its most basic, switching sidebars is usually changing the floats in the css.

Yep it ought to be adjusting no more than a few rulesets, easily set up using a token on html or body to hook contra styles onto, always set up non wp/bp sites with this option to easily adjust the site layout by simply changing a token in the header.php extending that through to user control if a backend exists.

It should be simple to set up for bp-default and not break anything.

I know how hard it *should* have been, I was asking @svenl77 if it was But that appears to have been answered, thanks

I know how hard it *should* have been

oooh pardon us for breathing I’ll get back to doing something interesting, I might provide an option to flip all sidebars horizontally.

Ive provided the option to move header to footer and footer to header written a stylesheet called btt.css and written a JS function to switch browser scrolling from top to bottom to bottom to top and turned the sidebars and content upside down and am going to market this to them that live down under .