[@johnjamesjacoby Keymaster 17 years, 5 months ago]

$user_id = the id of the person you want to get;

echo bp_core_get_userurl($user_id);

There is also bp_core_get_userlink which works in similar fashion but has more parameters. Open bp-core.php and check it out, it’s fully documented.

[@johnjamesjacoby Keymaster 17 years, 5 months ago]

@Frecking Wildchild: The problem with qTranslate is currently being addressed, kind of. Let’s hope these issues aren’t because of another URL re-writing plugin.

qTranslate also won’t play nice with BuddyPress because of a few issues I addressed in a recent BuddyPress core patch. I’m using qTranslate for a multilingual project I’m working on that also uses BuddyPress, so I’m learning the ins and outs of qTranslate as I go also. I’ve modified it to work as a site-wide plugin similar to BuddyPress, and I’ve created a patch/plugin to allow users to specify their default language in their user preferences.

BuddyPress won’t play nice with a whole lot of language switchers or URL hi-jackers yet, but it will as improvements are made to the core.

[@johnjamesjacoby Keymaster 17 years, 5 months ago]

Well, a component can be considered a type of plugin similar to any other WordPress plugin, except instead of hooking into WordPress alone, it’s hooking into BuddyPress AND WordPress.

Widgets are accessories, more or less. They aren’t 100% necessary, but most people welcome them as they’re an easy way to include whatever content it is that your plugin is supposed to spit out, on whatever pages that someone has enabled widgets to be displayed on.

A new component is needed when BuddyPress simply doesn’t have the capability that you want or need. The two next components currently in development are status updates (think twitter) and photo albums (think flickr.) Those are functionalities that don’t currently exist in BuddyPress.

Now both of those components may/will have their own widgets also, to do different things. The status update widget may incorporate the ability for the blog author to update their status from their blog, or it might display x amount of recent updates, or both. The photo album widget may include the most recent x photos, recent photo comments, etc…

In the case of BuddyPress, most widgets will come as part of a component. The component will bring in new functionality, and the widgets will allow that function to be displayed without knowing any HTML or PHP.

[@johnjamesjacoby Keymaster 17 years, 5 months ago]

Bryan868, the short answer is there are some larger changes in the WordPress.org 2.8 and 2.9 pipeline that have been strongly hinted at recently. Those changes won’t make their way into WPMU necessarily at the same time, so we’re mostly safe for now using WPMU.

BuddyPress will continue to get updated as WordPress versions change, however because there are a lot of dependencies there, and lots of distinct differences between a .org install and an MU install, it isn’t just flipping a switch and making it go.

It is going to happen, just not as soon as most people wish unfortunately. Hopefully everyone that’s salivating at the chance to open up their own .org sites to start adding friends and making profiles can understand the dev process and try to be patient.

I know it isn’t exactly what everyone wants to hear, but it’s the straight forward truth of the matter as it stands today. It may change tomorrow, but that’s where it is now.

[@johnjamesjacoby Keymaster 17 years, 5 months ago]

Sorry Seahawknationblog, as easy as that may sound, it isn’t how it works.

I hate to speak on anyone’s behalf, but I think there’s too many possibilities and liabilities to have a stranger poking around your install and files and data.

The goal here with our support is to do our best to help you help yourself out of your situation.

My suggestion, since it sounds like your AJAX request is failing, is to install Firebug in your Firefox browser, and see if there are any JavaScript errors on the page(s) in question. If so, track them down and repair them. If you need more help after that, chime back in and we’ll keep trying to help out in whatever way we can.

[@johnjamesjacoby Keymaster 17 years, 5 months ago]

Ahhh… The truth, shall set you free…

Any possibility that the Drupal install is mucking this up? I’ve got no experience with that one.

(To explain what’s going on, this isn’t a matter of directory structure, because those directories are virtual; they don’t really exist anywhere. There is no physical folder anywhere in your install called “members” or “users” or anything. The URL is caught by .htaccess and WordPress, and is virtually re-written to match the content it is displaying.)

Does that make more sense? I know it’s hard to understand and have faith in at first, but I promise it’s totally fine.

[@johnjamesjacoby Keymaster 17 years, 5 months ago]

Here’s a wild, wild guess. I’m not usually one for shooting in the dark, but lets give it a shot.

Open up your .htaccess, and the second line, do you have:

RewriteBase /wp/

[@johnjamesjacoby Keymaster 17 years, 5 months ago]

Good find Jeff. :thumbup: I needs me one of them fancy Macintoshes.

[@johnjamesjacoby Keymaster 17 years, 5 months ago]

Dworldon, if you don’t know how to find your error logs (which is understandable) you’re best bet might be to contact your web host and see if they can help you.

Otherwise, you might have a “logs” directory in your web root that might have some files in there for you to open in Notepad and poke around in.

[@johnjamesjacoby Keymaster 17 years, 5 months ago]

I know you don’t believe me, but I promise you that I’ve looked this over on every Windows browser, and it looks just fine to me.

Can you post up a link to a screen shot of what you see?

[@johnjamesjacoby Keymaster 17 years, 5 months ago]

Your best bet with white pages is to check your PHP and Apache error logs, which you can usually acquire by either looking in your “logs” directory or asking your host for them.

White pages can mean all sorts of things, but usually there’s something missing or in the way that WordPress can’t trap. Doesn’t happen often, but it does happen.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Andy,

The code that I recommended go in bb-config.php actually does what you’re doing here on bp.org, plus it avoids an XMLRPC conflict, plus it bypasses the 404 errors that pop up when viewing the forum from inside WP, plus it loads WP/BP in the admin area by using the absolute path.

Not sezzin’ it’s better, just sezzin’ is all…

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Stand off Jeff.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

JadedEvan,

Regarding the elusive die(‘0’) in bp-core-ajax-handler.php, if you have an alternative that you feel works better or will be more future proof, drop a ticket in the Trac with a fix or a patch.

The BP 1.0 release is the first stable, reliable, full working version of the core of BuddyPress. Right now there are a number of specific things going on behind the scenes, including security sweeps, code cleaning and beautification, bug hunting, etc…

It is anticipated that there will be a certain amount of bugs and quirks even in the 1.0 version of BuddyPress, and the dev team is still steadily submitting patches and updating the trunk almost daily with little changes and tweaks.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

I second the notion for not worrying about it. Unless you make your widgets wider to accommodate the maximum possible width of the longest possible date, this situation is unavoidable.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

I’m not exactly sure what you mean by including the file correctly. Which file do you mean?

include_once( '/your/absolute/path/to/domain/wp-blog-header.php' );

^—Did you change the path to be your ABSOLUTE path to that file? Not the URL to the file, but the absolute path.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Either you fixed it, or I’m missing it, because it looks fine in Chrome, Firefox, and IE for Windows.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Sounds to me like you’re not including the file correctly. If you were, the function would exist.

Basic integration has very little to do with what you’re trying to do. They are unrelated in most ways. Basic integration just allows cookies to match up, so that you have a unified login scenario, where you can login and out freely from either side of WP or BBP.

Deep integration involves loading bbPress inside WordPress, and WordPress inside bbPress, so that all functions and data are available to both sides at any point.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

You’ll want to put this at the top of bb-config.php:

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

define('WP_USE_THEMES', false) ;

include_once( '/your/absolute/path/to/domain/wp-blog-header.php' );

header("HTTP/1.1 200 OK");

header("Status: 200 All rosy") ;

}

The & should be just the &

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Firstly I notice that your Avatar cropper javascript is failing on registration. Also looks like bits of your site are missing, and messing with the BuddyBar (sub-sub menus aren’t appearing on hover.)

Otherwise, it’s working the way you have it setup. If what you’re asking is “why doesn’t my home theme look like testbp.org” it’s because you didn’t change your active home theme in WordPress.

Not sure what’s up with your member theme though. Might be missing some files or have some funky CSS or JS somewhere. Haven’t really looked into it for you.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

I think the next step is not installing WPMU/BP inside a directory called “members”

The problem is that the members area hijacks the URL and looks for “members” in it; that’s how it knows to display the member area.

I’m going to try this myself and see what happens, but I’m almost certain that is the issue here.

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

No reason to bump your topic, especially three times in 2 days.

We’ll see it and answer you when we’ve got a moment.

If it’s a custom page, with HTML that you’re making, then you can view the source of any BuddyPress powered site and snag the HTML.

<input id="rememberme" type="checkbox" name="rememberme" checked="true" value="forever" title="Remember Me"/>

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Do you have a link to your site I can check out?

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

Try:

function my_help_link(){

if (is_user_logged_in()) {

?>

<li><a href="http://someplace.org">Help</a>

<ul class="your-ul-list-css-classname">

<li><a href="http://someplace.org">Help 1</a></li>

<li class="alt"><a href="http://someplace.org">Help 2</a></li>

<li><a href="http://someplace.org">Help 3</a></li>

<li class="alt"><a href="http://someplace.org">Help 4</a></li>

<li><a href="http://someplace.org">Help 5</a></li>

</ul>

</li>

<?php

}

}

add_action( 'bp_adminbar_menus', 'my_help_link', 14 );

[@johnjamesjacoby Keymaster 17 years, 6 months ago]

You bet! I’m marking this resolved. If you need more help with this you can still reply, or change the ticker back to unresolved.