BuddyPress.org

The action that triggers the ‘no linking’ workaround doesn’t exist in RC2. I made it easier to specify what fields you do not want linked. I haven’t tested this but it should work.

function my_no_links(){

remove_filter( ‘bp_the_profile_field_value’,’xprofile_filter_link_profile_data’, 2 );

add_filter( ‘bp_the_profile_field_value’,’my_no_links_filter’, 2, 3 );

}

add_action(‘plugins_loaded’, ‘my_no_links’);

function my_no_links_filter($field_value, $field_type = ‘textbox’, $field_id){

$no_links = array(1,5,99);

if ( in_array((int)$field_id, $no_links))

return $field_value;

else

return xprofile_filter_link_profile_data($field_value, $field_type);

}

This is also up on http://buddypress.pastebin.com/f461fc21e

Put the field ids that you do not want to have automatically linked in the $no_links array.

If you are running RC2 just go into the buddypress menu on the back end and disable the blogs and the groups components. BuddyPress > Component Setup.

If not, then upgrade and then do that.

I’m eagerly awaiting this plugin as well.

I have something similar at my current home-baked site; members can add an RSS feed to their profile, showing their blog on their profile page and the latest posts of all members on the members homepage.

My version uses SimplePie as well, but there’s a lot wrong with the code. It doesn’t properly check if the submitted URL is really an RSS feed for example.

And I would have no clue how to transport it to BuddyPress, with the complicated way profile data is stored over several tables.

Go Nicola Greco!

Andy, do you mind commenting on this?

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

I want to know what direction to take in converting my component. If there will be an “official” version, I might wait.

Lastly, will our components be “Future Proof” like the themes from here forward?

https://buddypress.org/blog/news/why-your-buddypress-themes-are-future-proof/

Thanks for your input!

Someone needs to confirm this, but I believe that the conversion from RC1 to RC2 eliminate some activity stream tables.

Parts of this thread my answer your question, Jfcarter.

@Justme1-

If you do not have that line in your wp-config file, it means you used an older version. I just checked a new WPMU 2.7.1 download and the wp-config-sample.php file has this additional line in it.

Anyway, this line goes in the section that starts with this comment:

/** The Database Collate type. Don’t change this if in doubt. */

As far as your last question, yes. You will have lots of issues using the BuddyPress themes until BuddyPress is successfully activated.

Okay, a few questions:

1. Which versions of WPMU and BuddyPress are you running?
2. You say that you were “beginning to alter the colors”. I assume you’re using the default BuddyPress themes and you only worked with the CSS files. Is that true? Or, did you make changes to some of the php files as well?
3. Are you running this on localhost or a remote site?

Are you using a brand new wp-config.php file–the one that comes with WPMU 2.7.1? Or, did you use an older version?

If so, there is an additional define line added to WMPU’s config file as of 2.7.1:

define(\'SITE_ID_CURRENT_SITE\', 1);

Also, before installing BuddyPress, but after upgrading WPMU to 2.7.1, did you got to Site Admin > Upgrade in site admin and finish the upgrade?

Have you upgraded from RC1? If so, read through https://codex.buddypress.org/getting-started/installing-buddypress/upgrading-from-rc-1/ then come back here if it still doesn’t work after reading that carefully.

Okay, at this stage I’d say it’s time to clean house.

If this is a test dev install–meaning you do not have it in production mode–then I recommend deleting absolutely everything. This means the database file as well.

Install a clean, new copy of WPMU 2.7.1 plus BuddyPress RC2 and see what happens. After WPMU is properly installed, then install BuddyPress RC2 using the plugin browser as described here: https://codex.buddypress.org/getting-started/installing-buddypress/

Let us know how that goes.

Maythil-

I believe this issue has been resolved in the RC2 version of BuddyPress. If you have not yet upgraded, I’d recommend doing so. Read this thread: https://buddypress.org/forums/topic.php?id=2298

Yes, thank!)

If you mean a POT file for translation: https://trac.buddypress.org/browser/trunk/bp-languages/buddypress.pot

Today i ugraded WPMU to 2.7.1 and BP to RC 2. Good work!

Maybe some newest language files will be for this version?

Jfcarter-

The upgrade process will remove a few BuddyPress tables that are not needed anymore in RC2. Don’t worry, though. All the important data is safe. So, as long as you have a recent backup of your DB, you’ll be fine.

As far as shutting down your site during the upgrade, I usually make a post the day before stating that I’ll be performing upgrades. Since it is should take no more than 10 minutes, usually it is not an issue.

But part of the upgrade process has been to delete everything except your wp-config file, various files in /wp-content/ (and of course your database), if someone attempts to go to the site during the upgrade, there may be no files to serve. So, with more established sites, I’ll stick an index.html file in root so that it will be served if someone comes while I’m upgrading. In that file, I have the logo and a “be back soon” or something like that message. This is overkill for most sites though.

Finally, you could look at the Lock Outplugin. I’ve never used it and I do not know if it works with WPMU 2.7+.

Good luck!

BuddyPress RC2 will consolidate your activity streams and merge the tables. It will also go through and add any additional settings that are missing and set them as default if for some reason they do not already exist.

As long as you have not hacked the core of your install, upgrading from RC1 to RC2 should not harm any of your existing data.

There is a built in maintenance mode when using the automatic update feature of WordPress, but for something manual (such as RC1 to RC2), I might recommend something like…

https://wordpress.org/extend/plugins/maintenance-mode/

Congratulations, Andy! This is another important milestone for BuddyPress!

Thank you for your hard work, determination, and dedication in making the BuddyPress platform a wonderful tool for creating cutting-edge, vibrant social networks. I look forward to seeing where this goes!

For those of you tuning into us via SVN:

BuddyPress RC2 = BuddyPress Revision 1406

Anything +1406 can be referred to as “trunk” again.

Check these topics for some important reading on upgrading your existing BuddyPress installs.

BuddyPress Directory Changes and New File Locations

Reminder to move your old install, and what error you’ll receive if you don’t

i think the problem your having is the fact that p2 is not a “buddypress theme”

like in the main theme how it has a large widget area and 2 small ones, and also has a BLOG tab where the main blog is

the problem your having with p2 (and any other standard wordpress theme) is the BLOG tab is displayed on the main page rather than a large widget sidebar, as the recent blog posts thing is actually a widget, if you put this widget in your p2 sidebar you will see a direct comparison between the 2

currently you cant have a p2 “theme” that aggregates ALL blog posts like the buddypress widget does,

all the users will be posting to the main blog if you want them to use p2, and if you do then the current skin should be fine? it was designed to show comments

im sure you could add some nice jscript to add collapsing comments? this would probably bring better functionallity to your site if you didnt want the comments taking up the whole page?

there is a plugin to disable the dashboard but then obviously they cant edit the blog?

i think what your looking for is just plain wordpress (not mu / multi user) and buddypress which is upcoming, theres a thread about it in the forum if your interested, it would definately be worth a read and then base your decision on that

i kinda know how to do this, i am planning on switching the members profiles to http://username.hyrxx.com and the blogs to http://username.hyrxx.com/blogs /comments /photos etc

so it brings more of a focus onto the profile than the blog

because buddypress is about the profiles right?

ill let you know how i get on

And… if you make these changes to the BP core files, don’t forget to save them when updating BP.

Oh, and BTW, upgrading to the paid godaddy hosting will most likely fix the ad code injection issue you’re having; but I would concur with the negative comments about godaddy — paid or not — as a host for a buddypress project. You’ll keep running into problems trying to do more advanced stuff on their servers. That’s just not the market that they’re serving.

I haven’t tested this, but you should probably be able to edit

/wp-content/themes/buddypress-home/style.css

delete the @import directive that is there and instead add:

@import url(css/base.css);

@import url(css/custom.css);

This might hose some of the functionality added by loader.php, but should be the easiest place to make the change.