[@peterverkooijen Participant 16 years, 9 months ago]

IF Blogs = Sites

AND Sites/Domains = Networks

THEN Sites = Networks = Domains

(tada!)

This is coopting words that already mean something else and then shuffling their meaning around. If you want to create a lot of confusion, this is the way to do it.

If you want to bring more clarity, I’d make up some new words. Instead of ‘blogs’ you could say ‘webspaces’, or ‘spaces’ for short.

I’m not sure what aspects of WP(MU) ‘Sites/Domains = Networks’ refers to, so I don’t know what to suggest there.

@Bowe, I’m sorry basic logic makes your head hurt.

[@peterverkooijen Participant 16 years, 9 months ago]

Blogs = Sites

Huh?!

A site is: mywebsite.com. It’s a spot on the www.

If WP(MU) creates mywebsite.com/stupidusername and mywebsite.com/anonymouscreep, they are NOT different sites; they’re blogs or profiles or sections or folders on the same site.

Similarly “Sites/Domains = Networks”. They are not the same, even if the WP powers-that-be declare they are. A network is interconnected nodes. Sites/domains can be nodes on a network.

Or am I missing something? I don’t get it…

[@peterverkooijen Participant 16 years, 9 months ago]

If you can wait a few months, you could wait, but by then everybody will be talking about BP 1.3 and WP/WPMU 3.0.

I tried to upgrade from version 1.0 to 1.2-bleeding edge and quickly ran into trouble. I’m now upgrading to 1.1.3, which already is costing me longer than I’d like.

But at least 1.1.3 is somewhat stable. If you’re actually going to use your site, there is a lot to be said for staying one generation behind.

[@peterverkooijen Participant 16 years, 9 months ago]

Lots of changes in both the core and the theme.

I’ve noticed it’s mainly (?) name changes for functions. Is there/will there be a list of these name changes, so you can do search-replace in your custom theme/code/plugins and fix a lot of problems?

I’m one round behind, upgrading to 1.1.3, so hurray for this documents plugin! Making the groups more useful is priority #1 in this version of my project.

[@peterverkooijen Participant 16 years, 9 months ago]

That’s hilarious. I love it.

But I’m a bad person…

[@peterverkooijen Participant 16 years, 9 months ago]

Last post from me on this thread, just for the record and to summarize, I support John James Jacoby’s vision 100%.

Restructering friending around groups and microblogging/activity stream is a next step in where social web is going. Groups would become extremely useful for all kinds of use cases. It would really set Buddypress apart.

Buddypress can’t be all things to all people imho. Development should focus on a conceptually coherent core, with APIs that make it easy to plug in other more linear functionality, like classic friending and forums.

Do we need to re-invent the wheel ?

Buddypress shouldn’t just copy Facebook – apart from perhaps the registration process… BP has the opportunity to do things different, better, move things forward.

[@peterverkooijen Participant 16 years, 9 months ago]

Change the template tags in the template files, I think profile/index.php

[@peterverkooijen Participant 16 years, 9 months ago]

… forums and groups seem commingled in a way that is pretty darned counterintuitive

My solution is to just ignore/remove forums and focus on communication between members via (micro)blogging and threaded comments.

It’s cool to have the option of BBpress integration if you want it, but I don’t understand why it is becoming a default core component of BP. I hope BP steps back from that brink…

[@peterverkooijen Participant 16 years, 9 months ago]

I’d like to know as well. I’m not a php programmer. I’d noticed this function is specific for the members template, index I guess.

global $site_members_template;

I guess we need to add a global there. Or replace it in a separate function. I’ll try some things as soon as I have time.

Ideally I’d like to have a function that works anywhere in the theme…

[@peterverkooijen Participant 16 years, 9 months ago]

That’s how BP works. There is almost no security, privacy and member management built into BP. The focus is on expanding features.

There are various efforts underway to bolt better management on via plugins etc. This plugin for example offers new member moderation.

Jeff Sayre is working on a privacy component, but apparently has decided he needs to be compensated – and rightly so!

[@peterverkooijen Participant 16 years, 9 months ago]

I got this solution here earlier. This in functions.php or bp_custom.php:

function bp_custom_member_list_xprofile_data( $field ) {

echo bp_custom_get_member_list_xprofile_data( $field );

}

function bp_custom_get_member_list_xprofile_data( $field ) {

global $site_members_template;

return xprofile_get_field_data( $field, $site_members_template->member->id );

}

And then this in the template:

<?php if ( $company = bp_custom_get_member_list_xprofile_data('Company') ) : ?>

<p><?php echo $company ?></p>

<?php endif; ?>

I didn’t come up with this myself. Forgot who deserves the credit…

EDIT:

BTW, this seems to work as well:

<p><?php echo bp_custom_get_member_list_xprofile_data('Company') ?></p>

Or am I missing something?

EDIT2:

Or further cleaned up:

function custom_xprofile( $field ) {

echo bp_custom_get_member_list_xprofile_data( $field );

}

function bp_custom_get_member_list_xprofile_data( $field ) {

global $site_members_template;

return xprofile_get_field_data( $field, $site_members_template->member->id );

}

In the template:

<p><?php custom_xprofile('Company') ?></p>

[@peterverkooijen Participant 16 years, 9 months ago]

@Travel-Junkie, my current theme isn’t “widget-aware” at all. That’s how I found that codex page. My theme for version 1.1.3 is widget-aware, even though it’s basically a copy of the current one. But the widget looks like a mess, presumably because I didn’t use UL. It also includes a title I don’t want.

I just don’t have the patience to go through that codex page telling me how I should do html. If widgets are this much hassle I’d rather not use them. I just want the functionality, without any of the layout (requirements). Apparently 1.2 is going more into that direction, so that’s great.

[@peterverkooijen Participant 16 years, 10 months ago]

Great, thanks!

When I put this in the template

<?php bp_activity_widget(); ?>

Or

<?php widget("BP_Activity_Widget") ?>

I get a Call to undefined function error. Still missing something…

[@peterverkooijen Participant 16 years, 10 months ago]

I’d like to use the features in the widgets, specifically site wide activity in 1.1.3, but want more control over the layout than the widget system provides – see this obnoxious codex page that says you must use unordered lists or else…

Where/how can I find the code that widgets add to the pages? I’d like to just add that code to my template pages, perhaps via template tags.

Apologies if this is thread hijacking, but I suspect finding the original code would also solve thecorkboard’s problem and clear up confusion over versions.

[@peterverkooijen Participant 16 years, 10 months ago]

What would the site wide widget normally look like? Where is it? Is it like a template tag?

I don’t get widgets, don’t use them…

[@peterverkooijen Participant 16 years, 10 months ago]

Found this in bp_core_activation.php:

/***

* bp_core_disable_welcome_email()

*

* Since the user now chooses their password, sending it over clear-text to an

* email address is no longer necessary. It's also a terrible idea security wise.

*

* This will only disable the email if a custom registration template is being used.

*/

function bp_core_disable_welcome_email() {

if ( '' == locate_template( array( 'registration/register.php' ), false ) && '' == locate_template( array( 'register.php' ), false ) )

return true;



return false;

}

add_filter( 'wpmu_welcome_user_notification', 'bp_core_disable_welcome_email' );

So I guess I could just remove this function?

Is sending that password really such a “terrible idea security wise”? Are criminal gangs intercepting these emails to break into WordPress accounts?

EDIT: Yes, removing that function works. A regular WPMU welcome email is sent.

But the password in the email is eight numbers instead of the eight letters password I’d entered. Why?! Does Buddypress do its own encryption on the password? Does it use other tags or “placeholders” or whatever they’re called to call the password?

Going to sit in a corner and cry…

[@peterverkooijen Participant 16 years, 10 months ago]

Does anyone know how to get a welcome email in BP 1.1.3 without resorting to the Welcome Pack plugin?

There are some clues here, but I have no idea what to do with them and if this would even apply to Buddypress registration process.

Should I just stick this in a template files somewhere? Where?

<?php wpmu_welcome_user_notification($user_id, $password, $meta); ?>

Would it take the text from the Options in the admin area?

Or does BP have its own function for this?

[@peterverkooijen Participant 16 years, 10 months ago]

Using the Javascript trick: 1. make sure the Javascript is included in the head, 2. add onkeyup=”copyinput()” to the input tag for the Username, 3. edit the Javascript so that this line…

document.getElementById('blogname').value = tmp;

…has the id of the input tag for the Name, instead of blogname. The Javascript would copy the input for username upon typing to name.

[@peterverkooijen Participant 16 years, 10 months ago]

You can make pages in the regular WordPress part. And maybe this is helpful.

[@peterverkooijen Participant 16 years, 10 months ago]

I have 1.1.3 on Bluehost as well. No problem with activation email, so there must be something else going on.

If you’re sure you have a clean install, call Bluehost to check PHP mail settings. They have a pretty good help desk.

[@peterverkooijen Participant 16 years, 10 months ago]

Can I use “tags” (?) in the Welcome email in the Welcome Pack plugin?

I would like to include the password, so new members have a reminder in their inbox what they entered when they signed up.

What would the tag for the password be? And for the fullname?

[@peterverkooijen Participant 16 years, 10 months ago]

This is my pet peeve with Buddypress! Wasted at least two weeks on this issue last Summer.

I use the same Beau Lebens email as login plugin that David Lewis found. So I wanted to get rid of username entirely and have basically only real name and email address on my registration form.

To integrate a mailinglist script I needed separate firstname + lastname. Buddypress doesn’t store them out-of-the-box. This is NOT a WPMU issue; WP/WPMU has firstname + lastname in wp_usermeta, but Buddypress simply refuses to synchronize those fields, so you can’t count on the data being there for other scripts (mailinglist, events, etc.).

Here’s my solution:

How to synchronize firstname+lastname between xprofile field_1 and wp_usermeta upon registration

And

How to autogenerate blogname (url) from Blog Title (or username from fullname!)

The Javascript I use for fullname->username looks like this

function copyinputuser()

{

var tmp = document.getElementById('field_1').value;

tmp = tmp.toLowerCase().replace(/^s+|s+$/g, "").replace(/[_|s]+/g, "");

tmp = tmp.replace(/[^a-z0-9-]+/g, "").replace(/[-]+/g, "").replace(/^-+|-+$/g, "");

document.getElementById('signup_username').value = tmp;

}

Unfortunately a lot of people sign up with only one name in the Fullname (field_1) field. Question:

Would anyone know how to validate/check the input for a two-part (minimum) name? You’d probably have to check for a space, make a space required. How would that script look?

No firstname/lastname because this does not work for a lot of international users.

Which countries are you talking about?! Name them.

With all due respect, this is such a bizarre argument. Not only the western world, but India, China, etc. all have no problem whatsoever using two or more names. Countries that use only one name or more than four can write their own plugins, along with the language pack etc.

More than two names is no problem; separating first and last name is primarily about having a first name available. Users can put their other two, three, four names in the second field.

If Facebook, LinkedIn, etc. have no problem requiring separate firstname and lastname, why is this such a controversial issue for Buddypress? Why make life difficult for 80-90 percent of Buddypress users just to prevent offense to 10 percent with different customs?

[@peterverkooijen Participant 16 years, 10 months ago]

I’ve tried this regular WordPress plugin for New User Email Setup, but it didn’t do anything at all for Buddypress activation.

This BuddyPress Registration Options has some very useful features that I probably need anyway, but it still doesn’t allow you to change the From and Subject lines. [username] seems to be the only available tag, not [fullname]. You can’t make any changes unless you check Moderate New Members.

Why is more control over the registration process not built into the Buddypress core? It’s essential to a social network imho.

[@peterverkooijen Participant 16 years, 10 months ago]

Has editing the activation/welcome email become any easier in versions 1.1.3/1.2?

What changes have been made?

Is the pastebin code now obsolete? I’ve noticed in 1.1.3 the default setting (?) is that new members enter their own password on the sign-up form, so I guess the “you will receive *another email* with your login” no longer applies?

[@peterverkooijen Participant 16 years, 10 months ago]

Comment deleted. I had already mentioned this plugin… Oops.