BuddyPress.org

could you open a new ticket here? https://trac.buddypress.org/newticket ?

I’ve backed up the entire wordpress directory, copied the database, downloaded the zip and overwritten everything. WordPress MU seems to work perfectly. I wonder if BuddyPress would break if I’d return it to it’s RC1 state with the newer WordPress MU installed?

OT: I also wonder why there is an \”Inactive\” above my name, bug?

I’ve tried disabling -all- plugins running my site naked, although, it didn’t work at all;

My first work was the upgrade of my existing theme to the new standards ; although that gives the same error as the “buddypress home RC2” theme.

I’m not really convinced this is themes related…

I’m 100% sure it’s not mu-plugins related either, because I’ve tried disabling all those by moving them away, disabling sunrise in wp-config.php and it did nothing else more than rendering a lot useless and giving the same 404 errors on the main domain.

the plugins directory I moved too, backed up the database before moving them, logging in, lots of things not working anymore including the slugs, which were still giving the same 404 errors …

restored the database, plugin directories, mu-plugins and enabled sunrise again, because it didn’t matter at all; except that my blog articles are currently working towards the world …

– logs do not show any errors except the normal 404’s

x.x.x.x – – [24/Apr/2009:13:10:28 +0200] “GET /members/wildchild/ HTTP/1.0” 404 9959

– WPMU 2.7.1 is installed

– Buddypress RC2 is installed for sure (https://buddypress.org/download/ has an error with the url in the title announcing the new version while pointing to the old! Only download zip is RC2 currently)

– RC2 default templates and custom templates do not change anything at all

– I’ve followed the upgrade instructions currently a dozen times

Do you have by any chance the sunrise (domain mapping) or any redirect plugins installed?

I tried by disabling them but I know WordPress is a little bit persistent on it’s redirections; if you got the same installed, it might be a good idea to look towards the mapping since the SLUGS are not working at all.

Justme1-

Okay a couple more questions:

1. You say that your site is now up and running. Did adding that additional line to WPMU’s config file make that happen?
2. When you upgraded to WPMU 2.7.1, did you log into the backend as site admin then go to the Site Admin > Upgrade and finish the upgrade?
3. Are you using a custom theme?
4. Did you move the themes into their proper location following these instructions?
5. Do you have any plugins other than BuddyPress activated?

The last question should not be a factor, but it helps to know your overall setup.

If you are not using custom themes yet, just delete everything and start from scratch with RC-2. By the looks of it, you don’t have much data yet.

Follow the install instructions step by step and you will be fine:

https://codex.buddypress.org/getting-started/installing-buddypress/

Also, please don’t use “buddypress” in your domain name. When we get a hosting page set up on this site, we can’t link to your site if it breaks the domain policy.

Using RC2, WPMU 2.7.1, subdirectories

hmmmm – sorry to bring that up again… the post slugs in the activity feed are showing now sometimes just the actual site url…

I think this mostly occurs with the slugs mentioned above:

Root/main blog is using: (buddypress home)

/%year%/%monthnum%/%postname%/

site1.example.com is using:

/%category%/%post_id%/

But it could also be, because I am using for some of the posts the Plugin TDOMiniForms (sorry burtadsit for bringing it up again, but I don’t get why the slugs are only in BP-components wrong the the normal WPMU works just fine – everywhere…)

Would be great if someone could help! I just went live on http://www.young-people.ch (see for the bug http://young-people.ch – although it updating the information every minute now)

We just went life with our new portal for young people:

http://www.young-people.ch

(sorry, it’s german, but you will see the functions…)

Those “specials ” are implemented so far:

– totally customized theme (home and member)

– home theme with special friends-activity stream when logged in (like on facebook)

– lots of user generated content (media-reviews directly connected with amazon, ressources, downloads, etc etc). I used the TDOMiniForms Plugin for that…

– special use of the premium-plugin “upgrades”. Instead of having to buy credits for more blog-space you earn credits by submitting articles to the public

– some bp-dev components (subscribe to blogs, etc)

It still has some bugs, but hopefully they are solved after the beta. The old Portal (running on Lotus Nots – how wan’t to believe that ) had 2500 Members. Right now every minute there are registering new members…

Check it out and post a feedback in my wire …

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.