[John James Jacoby]

Also in oci_bb_group_forums.php, I added…

if (defined(BACKPRESS_PATH))

require_once( BACKPRESS_PATH . '/class.ixr.php' );

Does the same thing on the bbPress side…

[Burt Adsit]

Ok John. If you downloaded that 0.24 zip do it again. The one on the net has initialization of globals for all components now. Except the forums component. It does something that I don’t have time to investigate right now and I don’t know the exact implications of it.

[Burt Adsit]

Create a file called oci_bp_custom.php and put it in the same dir as oci_bp_group_forums.php. Create a filter like:

function johns_filter($user){

$user = “johns info going across to bbpress and bb user meta”;

return $user;

}

add_filter(‘oci_get_user’,’johns_filter’,10,1);

This traps the filter you want ‘oci_get_user’ with add_filter(). It says trap that filter and call the function ‘johns_filter’ we just created. Give this filter a priority of 10 which is normal and the function johns_filter() takes one parameter.

The $user array that johns_filter() gets when called contains the user id as $user that was built in my fn oci_get_user(). Anybody can create more filters now and add more info that goes across and gets associated with every user.

Once you import again all your new info will get put into meta data for use each time the ‘bbGroups’ info gets pulled out for the current user. This plugin was designed for people who are not running deep integration. It works for you but frankly the xmlrpc overhead is not needed. You have access to all the bp data and functions. One thing you might run into is that the data you are trying to get at and the functions are not initialized yet by the bbGroups plugin. I only fire up the global vars for the components I need. I just do:

function oci_bp_group_forums() {

// only do this if the xmlrpc server is firing up and we are servicing a request

if ( defined(‘XMLRPC_REQUEST’) && XMLRPC_REQUEST ){

// bp’s globals don’t get set until a ‘wp’ action occurs. this seems to be all that is needed.

bp_core_setup_globals();

groups_setup_globals();

bp_activity_setup_globals();

}

}

add_action(‘init’,’oci_bp_group_forums’);

That gets core, groups and activity globals initialized. You are going to have to fire up the xprofile globals yourself:

xprofile_setup_globals();

Well, hang on a sec and I’ll include that in my ‘init’ handler.

[John James Jacoby]

Wow that’s cool… So if I understand correctly, the idea would be to add another function inside the oci_get_user_filter function that would get the xprofile info that I’m looking for? This way it exists within the bbGroups array for later access versus having to pull the query everytime?

I get the feeling that getting the xprofile info might be harder than I thought.

Also for the sake of those of us using deep integration, in oci_bp_group_forums.php if I could ask you to do…

if (!defined(BBDB_NAME))

require_once(ABSPATH . WPINC . '/class-IXR.php');

That helps check to make sure that it isn’t previously included anywhere… Require_once doesn’t seem to really cut it with deep integration…

[Burt Adsit]

I didn’t have time to dig through the xprofile component to do exactly what you want but I did have time to do this. I added a filter to the group and user data that goes across to bbpress. There are two fns that build the associative array of info that goes across and gets stuffed into bbpress forum and user meta tables.

I added the filter ‘oci_get_user’ to the oci_get_user() fn and ‘oci_get_group’ to the oci_get_group() fn. I also did a little demo of how to create such a filter for any data you want to go across to bbpress. I pulled the user’s forum list and the list of forums where the user is ‘staff’ and implemented that as a filter. It doesn’t get created or include by the fn I created for that purpose anymore. It uses a filter. oci_get_user() builds and includes info from the bp user obj and then calls the filter for the added and needed forum info.

/**

* oci_get_user_filter()

*

* Live example of how to use the filter mechanism to add info to the data going across to bbpress

* This filter adds the user’s forums and forums where the user is staff into the $user array

* @return

* @param associative array $user from oci_get_user()

*/

function oci_get_user_filter($user){

$users_group_info = oci_get_users_group_info($user);

$user = $users_group_info;

$user = $users_group_info;

return $user;

}

add_filter(‘oci_get_user’,’oci_get_user_filter’,10,1);

The data being stuff into the $user array used to be included in the oci_get_user() fn and now it’s being included in that filter.

You just need to create your own filter fn and trap the ‘oci_get_user’ filter chain like I did above. The zip with the new capability is available on my site as:

http://ourcommoninterest.org/downloads/bp_group_forums_0.24.zip

I didn’t bump the ver number, change the readme.txt or update the plugin’s blog post yet. This reply is the docs for the moment.

You have to be careful what you send across. Only primitive types can go over through xmlrpc. No objects. int, string, bool, array…

[Sgrunt]

this is the whole css, i have no gap but sorry, i’ve changed default colors.

However if you dont want to recustomize the whole css i think you should first use:

#wp-admin-bar ul li ul li

margin-top: -1px )instead of margin-bottom: -1 px

and

#wp-admin-bar ul li ul li ul li:first-child {

margin-top:-2px;

i don’t remember if these 2 lines are enough to solve the problem, but if you want this is the whole css i’m using:

body { padding-top: 28px !important; }

*this body line must be the first line of the css, but the forum editor keep it in this wrong position

#wp-admin-bar {

position: absolute !important;

top: 0 !important;

left: 0 !important;

width: 100% !important;

z-index: 1001 !important;

height: 28px !important;

color: #fff !important;

text-align: left !important;

background:url(../images/admin_bar_back.gif) #818181 repeat-x !important;

font: 12px normal “Lucida Grande”, “Lucida Sans Unicode”, “Lucida Sans”, Tahoma, Verdana, Arial, sans-serif !important;

font-weight: normal !important;

}

#wp-admin-bar * { z-index: 999 !important; }

#wp-admin-bar img#admin-bar-logo {

position: absolute !important;

top: 8px;

left: 10px;

}

#wp-admin-bar a img {

border: none !important;

}

#wp-admin-bar li {

list-style: none !important;

margin: 0 !important;

}

#wp-admin-bar li * {

font: 12px normal “Lucida Grande”, “Lucida Sans Unicode”, “Lucida Sans”, Tahoma, Verdana, Arial, sans-serif !important;

font-weight: normal !important;

background-image: none !important;

}

#wp-admin-bar li a {

padding: 6px 25px 7px 15px !important;

font: 12px normal “Lucida Grande”, “Lucida Sans Unicode”, “Lucida Sans”, Tahoma, Verdana, Arial, sans-serif !important;

font-weight: normal !important;

}

#wp-admin-bar li.no-arrow a {

padding-right: 15px !important;

}

#wp-admin-bar li:hover, #wp-admin-bar li.hover {

position: static;

}

/*******************/

#wp-admin-bar ul { /* all lists */

margin: 0 !important;

list-style: none !important;

line-height: 1 !important;

cursor: pointer !important;

height: 30px !important;

padding: 0 !important;

}

#wp-admin-bar ul {

margin-left: 80px !important;

}

#wp-admin-bar ul li { /* all list items */

padding: 0 !important;

float: left !important;

background: url( ../images/admin-menu-arrow.gif ) 88% 53% no-repeat;

position: relative;

}

#wp-admin-bar ul li.no-arrow {

background: none;

}

#wp-admin-bar ul li ul a {

color: #fff !important;

}

#wp-admin-bar ul li.align-right {

position: absolute;

right: 0;

}

#wp-admin-bar ul li a {

display: block !important;

font-size: 12px !important;

font-family: “Lucida Grande”, “Lucida Sans Unicode”, “Lucida Sans”, Tahoma, Verdana, Arial, sans-serif !important;

text-decoration: none !important;

color: #fff !important;

}

#wp-admin-bar ul.main-nav li:hover, #wp-admin-bar ul.main-nav li.sfhover, #wp-admin-bar ul.main-nav li ul li.sfhover {

background-color: #000 !important;

}

#wp-admin-bar ul.main-nav li ul li:hover a, #wp-admin-bar ul.main-nav li ul li.sfhover a {

background-color:#000 !important;

color: #70cbf0 !important;

}

#wp-admin-bar ul.main-nav li ul li:hover ul li.alt a {

background-color: #333 !important;

color: #fff !important;

}

#wp-admin-bar ul.main-nav li ul li:hover ul li a {

background-color: #666 !important;

color: #fff !important;

}

#wp-admin-bar ul.main-nav li ul li:hover ul li:hover a {

background-color:#000 !important;

color: #70cbf0!important;

}

#wp-admin-bar ul.main-nav li ul li ul li:hover a, #wp-admin-bar ul.main-nav li ul li ul li.sfhover a {

color: #fff !important;

}

/* second-level lists */

#wp-admin-bar ul li ul {

position: absolute !important;

width: 185px !important;

left: -999em !important;

margin-left: 0 !important;

}

#wp-admin-bar ul li ul li {

float: left !important;

width: 183px;

margin: 0 !important;

border: none !important;

background-color: #666 !important;

border-left: 1px solid #000 !important;

border-right: 1px solid #000 !important;

border-bottom: 1px solid #000 !important;

border-top: 1px solid #000 !important;

margin-top: -1px !important;

}

#wp-admin-bar ul li ul li.alt {

background-color: #333 !important;

}

#wp-admin-bar ul li ul li:last-child {

}

#wp-admin-bar ul.main-nav li ul li a:hover, #wp-admin-bar ul.main-nav li.sfhover ul li a:hover {

background-color: #000 !important;

color:#70cbf0;

}

#wp-admin-bar ul li div.admin-bar-clear {

clear: both !important;

background-color: #666 !important;

}

/* third-and-above-level lists */

#wp-admin-bar ul li ul ul {

margin: -28px 0 0 183px !important;

}

#wp-admin-bar ul li:hover ul, #wp-admin-bar ul li li:hover ul, #wp-admin-bar ul li.sfhover ul, #wp-admin-bar ul li ul li.sfhover ul { /* lists nested under hovered list items */

left: auto !important;

}

#wp-admin-bar ul li.align-right:hover ul {

right: 0 !important;

}

#wp-admin-bar ul li:hover ul ul, #wp-admin-bar li.sfhover ul li ul {

left: -999em !important;

}

#wp-admin-bar ul li ul li ul li:first-child {

border-top: 1px solid #000 !important;

margin-top:-2px !important;

}

/* Menu item css */

#wp-admin-bar img.avatar {

float: left !important;

border: 2px solid #fff !important !important;

margin-right: 8px !important;

}

#wp-admin-bar span.activity {

display: block !important;

color: #fff !important;

margin-left: 34px !important;

font-size: 10px !important;

background: none !important;

border: none !important;

padding: 0 !important;

}

#wp-admin-bar li a:hover span.activity {

color: #ccc !important;

}

#wp-admin-bar ul.author-list li {

height: 55px !important;

}

#wp-admin-bar ul li#bp-admin-notifications_menu a span {

background: #333 !important;

padding: 0 6px !important;

color: #fff !important;

font-weight: bold !important;

font-size: 0.8em !important;

-moz-border-radius: 2px !important;

-khtml-border-radius: 2px !important;

-webkit-border-radius: 2px !important;

margin-left: 2px !important;

}

[Burt Adsit]

This is something every site admin wants to know and there are about a million solutions for this. Try the mu forums and the wp plugins area. Everybody has different requirements and solutions. The answer is there is no builtin way to do this in wpmu. wpmu leaves that up to the site admin/designer/programmer.

[tekanji]

No problem; I should have been more clear with my question anyway. I don’t have all that much experience with open source, but I can certainly understand being defensive about software that you’re very involved in.

For the record, this is the first time I’ve actually participated in development forums for any software I’ve developed for. Most of the time I just lurk and hope my questions get asked by someone else. It speaks very highly of BP that installing it spurred me to actually make an account here and start posting questions and whatnot.

[Fabrício Yutaka Fujikawa]

Hello! I’ve just downloaded the 1132 trunk but the problem still remain for the Brazilian Portuguese translation. The behaviour is exactly as described in thread https://buddypress.org/forums/topic.php?id=1250.

Does anyone know how to solve it?

Thanks!

[Burt Adsit]

You are asking in a support forum why design decisions were made and why, considering the evolutionary nature of software, bp ended up as it did. As an end user of bp I have absolutely no idea how to answer either of those questions.

The real answer is that things don’t have to be like they are if you don’t want them to be. Come up with an enhancement and share it with us. That’s the beauty of open source under a GPL license.

Code is Freedom.

[Trent Adams]

These forums are not meant to be a job board. They are for ideas on expanding buddypress and support in general. If someone asks for paid support they must leave their contact information and the thread will be closed.

[Alex]

There’s a quick five-line plugin to do that in this thread:

https://buddypress.org/forums/topic.php?id=1095

Just change:

$redirect_to = bp_core_get_userurl($user->ID);

to whatever URL you want the user to be redirected to.

[federicobo]

In this post (in WordPress MU forum) I’ve found a possible solution, but I’ve tried and seems not functioned (the user can again create more than one blog).

Some feedback?

https://mu.wordpress.org/forums/topic.php?id=5930

[John James Jacoby]

https://bbpress.org/plugins/topic/bbpress-latest-discussion-for-wp/

[Burt Adsit]

oldskoo1, see this thread here for info about that: https://buddypress.org/forums/topic.php?id=1095

Buried in there is a little 5 line plugin that allows you to redirect on login.

[Burt Adsit]

From this thread: https://buddypress.org/forums/topic.php?id=1223

– If you upgrade from a previous version and are using your own custom theme, you will need to copy over the functions.php from the latest buddypress-home theme.

Try that Keith. It may be the problem. That is an issue for *all* wp themes that take the place of bp’s home theme.

[mdsports]

yes please direct us to the pseudo-widget…

[nicolagreco]

you should update your script with the new $bp structure

$bp should be $bp->current_component

[Burt Adsit]

Here’s a scenario.

I belong to a group on a site. I visit the group and I go right to the ‘Tags’ screen under ‘Forum’ in the group home.

In the ‘Tags’ screen I see the following:

---

TYPE: [All] [Recent] [Author] [Tagger] [Site] [Blog Post] [Forum Topic] [Image] [Wire Post] [Uncategorized]

---

TAGS: [Tag A] [Tag B] [Tag A] [Tag B] [Tag A] [Tag B] [Tag A] [Tag B] [Tag A] [Tag B]

[Tag A] [Tag B] [Tag A] [Tag B] [Tag A] [Tag B] [Tag A] [Tag B] [Tag A] [Tag B]

[Tag A] [Tag B] [Tag A] [Tag B] [Tag A] [Tag B] [Tag A] [Tag B] [Tag A] [Tag B]

[Tag A] [Tag B] [Tag A] [Tag B] [Tag A] [Tag B] [Tag A] [Tag B]

---

YOU SELECTED: [Recent](x) [Tag A](x) [Tag B](x) – <CLEAR> <SUBSCRIBE TO THIS>

---

VIEWING: 1 of XX … Page [1] [2] .. [99] [Next >>] SHOW AS: <List> <Grid>

---

xxxxxxxx xxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

yyy yyyyyyyy yyyyyyyyyy yyy yyyyyyyy

yyy yyyyyyyyyyy yyyyyyy yyyy yyyyyyyyyyyyyyyy

xxxxxxxx xxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

yyy yyyyyyyy yyyyyyyyyy yyy yyyyyyyy

yyy yyyyyyyyyyy yyyyyyy yyyy yyyyyyyyyyyyyyyy

xxxxxxxx xxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

yyy yyyyyyyy yyyyyyyyyy yyy yyyyyyyy

yyy yyyyyyyyyyy yyyyyyy yyyy yyyyyyyyyyyyyyyy

xxxxxxxx xxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

yyy yyyyyyyy yyyyyyyyyy yyy yyyyyyyy

yyy yyyyyyyyyyy yyyyyyy yyyy yyyyyyyyyyyyyyyy

When I select one of the ‘Type’s which are meta tags for all tags I get a list/cloud of the tags that belong in that ‘type’. ‘All’/’Recent’ are the defaults.

This is a neat user interface to a WP blog : http://www.swiss-miss.com/

It’s got the ajax category/tag selection with list/grid selection for viewing. It would be a useful interface for this type of content.

[Burt Adsit]

Content discovery is a filtering mechanism that narrows down the view for the user to what they want to see. Content should have top level organization of what?

Content types:

Website/Blog url

Blog post

Forum topic

Image

Wire post

Anything with an url

User interface to content. Sorting and filtering:

By date: most recent, date range, ascending, descending

By tag(s): and/or/not

By content author

By user who created the tag

By type: blog post, site url, forum topic …

Content display options:

List

Grid

Titles only

Title and excerpt

When the user browses the content should they be able to add/remove tags for each item? Like bbpress? Only group staff can maintain tags?

Questions, questions.

[Alex]

A great addition for me would be to create ‘Group Events’, events which are associated with specific groups.

Say my group wanted to organise a meetup, we could go to our group page and under “Forum, Wire, Members” etc there would be a “Group Events” option, which when clicked would show all our events and have an option to add a new one. When creating that event we could choose to send invites to the members of the group instead of adding them individually.

If the group is private or hidden our events would also be private/hidden. Group Events would also appear on my personal Events page.

[gpo1]

@jimthedj65, Regarding WP video framework plugin integrated into BP, you need to liaison with ddmitry on this. He got it working on his site !!

https://mu.wordpress.org/forums/topic.php?id=10778&page=2

[terryjsmith]

See my response here: https://buddypress.org/forums/topic.php?id=1152 for a solution as well.

[Burt Adsit]

When you use deep integration bbpress clears all the actions and filters. bp runs on actions. It does this as part of the load sequence.

In bb-settings.php:

/**

* Remove filters and action that have been set by an included WordPress install

*/

if ( defined( 'ABSPATH' ) ) {

$wp_filter = array();

$wp_actions = array();

$merged_filters = array();

$wp_current_filter = array();

}

When I’m using xmlrpc I have to manually fire up the bp globals I want to refer to like:

function oci_bp_group_forums() {



// only do this if the xmlrpc server is firing up and we are servicing a request

if ( defined('XMLRPC_REQUEST') && XMLRPC_REQUEST ){

// bp's globals don't get set until a 'wp' action occurs. this seems to be all that is needed.

bp_core_setup_globals();

groups_setup_globals();

bp_activity_setup_globals();

}

}

add_action('init','oci_bp_group_forums');

That gets triggered by the end of the wp-load.php sequence. do_action(‘init’) is the last thing that happens there.

bp gets woke up by listening to the ‘wp’ action. I think all of bp gets activated by ‘wp’.

I just remember having some problems with xmlrpc and the ‘wp’ action so I manually tied things to the ‘init’ action. All the plugins for bp load, it’s lots of other stuff that gets initialized by ‘wp’.

[bobman024]

Sigh…