BuddyPress.org

Alunsina-

Okay, a few questions then:

1. Do you have any plugins other than BuddyPress installed? If so, have you tried deactivating them?
2. Which version of PHP are you running?
3. Which version of the GD module?
4. Are there any errors in your error log? If so, what are they?

Alunsina & Evvscuba-

SInce this thread has not had any activity for over month, it is best to create a new thread, or find a similar thread that is less than a month old.

Please read this thread: https://buddypress.org/forums/topic.php?id=2543

Ed-

SInce this thread has not had any activity for over month, it is best to create a new thread, or find a similar thread that is less than a month old.

Please read this thread: https://buddypress.org/forums/topic.php?id=2543

Also, with regards to your avatar issue, if you have not seen this, please read: https://buddypress.org/forums/topic.php?id=2190#post-11864

Please read this post and the linked to threads for other possible advice:

https://buddypress.org/forums/topic.php?id=2190#post-11864

If you go through everything there, and still have issues, then post back here. If you find something that solves your issue, then post back here and let us know your solution.

WillPCG-

Okay,a few more questions, just to be thorough:

1. Which version of PHP are you running?
2. Have you made any changes to the .htaccess file?
3. Did you even copy over the .htaccess file from the new WPMU package to your WPMU root?
4. Questions about upgrading WPMU:

   • Where you running WPMU 2.7.1-beta1 before upgrading?
   • If so, how did you upgrade to the public version of WPMU 2.7.1?
   • Did you add the one additional define line to WPMU’s wp-config.php file? If not, compare the 2.7.1 config file to your old one. This line is new:

     define('SITE_ID_CURRENT_SITE', 1);

   • To complete your WPMU upgrade, did you go to “Site Admin > Upgrade” and finished the process?

5. Are you running any plugins other than BuddyPress? If so, have you tried deactivating them?

I don’t know what broke it from v1.1 to v1.2, I’m just making my best guess. That is why I was asking if you had a working v1.2 w/ images, then I could just download a copy and modify for my component. Like a version 1.2b since 1.2 has a bug in it.

here is the full code from v1.1 that I am guessing is the issue:

http://pastebin.com/mee09d07 (bp-example-cssjs.php)

thanks for all your assistance and I hope this helps!

I’m working on a 9-12 installation:

http://odysseyblogs.org (that’s just the testing site)

and we are, most likely, moving to Moodle next year. Currently we’re using Ning and eCollege. I’d love to make some contacts with folks using BuddyPress with secondary students and if you happen to be using Moodle to that would be a bonus. I’m available at:

distanceed@gmail.com.

Cheers.

Sgoetz-

You’ve posted this issue in another thread where I have replied specifically to you. Please go and look at my response and then provide me with additional details.

https://buddypress.org/forums/topic.php?id=2314&page=2

my profile wire is broken again.. please check…

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

@andy

@burtadsit

could the patch that burt has made here.. https://trac.buddypress.org/ticket/723 change the way that this bit of code works in my post-list.php in my theme.

<?php if ( bp_has_wire_posts( 'item_id=' . bp_wire_item_id() . '&can_post=' . bp_wire_can_post() ) ) : ?>

basically andy you offerd this as a fix but i am just wondering that now that the issues with the slugs in the core files that are fixed on groups wire now effect the way in which the wires post display on the profile side of things..

does tha make sense??

In other words i am try the fix the fact that the wire posts are not displaying on profile pages.

they were working perfectly before burt and i fixed the groups wire??

@KitWit,

That’s all I’ve done too.

I just changed base.css in the two directories, and copied my logo file over as logo.gif to both locations

base.css in

wp-content/bp-themes/bpmember/css

and

wp-content/themes/bphome/css

and logo.gif in

wp-content/bp-themes/bpmember/images

and

wp-content/themes/bphome/images

Then remember to flush the cache in your browser (F5 usually does it)

I also edited both header.php files as I wanted to change the link words from ‘blog’ to ‘News’

as @jfc said, you might need to select a member theme in Admin / BuddyPress / General Settings / Select theme to use for BuddyPress generated pages:

and then save.

Note: Since I was ‘updating’ from RC1 I had to select a different them and then re-save.

this is the same on RC2,

also not working here on buddypress.org

yes ther is problem with the slugs and certain bit of code that means that wire is broken on the groups page

burt helped me get this to work..

https://trac.buddypress.org/ticket/723

the problem i have now is that when i went through this i managed to break the displaying of the profile wire.. the post submit ok but the display of them has conked??

can any one think what it could be… they were working well before..

one thing i did do is define change ( ‘BP_GROUPS_DB_VERSION’, ‘1300’ ); to 1301 and this may have broken it i changed it back now.. could it have…

where is the display wire for profile part

Gcs123-

You’re right, switching to the default home theme solves my problem, however is there any modifications I can make to my custom theme to enable it to work?

Without knowing what you changed, and without seeing your files, it would be impossible to tell you what to change.

Your have two choices:

1. Compare your current themes to v1.2 of the Skeleton Theme and locate the differences. Then, change as appropriate.

2. Copy the standard BuddyPress themes, use them as your starting point, customize as desired.

Okay, since we’ve had a few people make this mistake I need to ask this just in case. Everyone in this thread who is having 404 issues is running BuddyPress with WPMU and not the single-user version of WordPress, correct?

This means downloading WordPress from here: https://mu.wordpress.org/download/

Specifically @Sgoetz-

Running WPMU, ran automatic upgrade to 2.7.1 prior to installing BP

Were you running WPMu 2.7.1-beta1 before upgrading?

If so, you cannot upgrade from beta1 to public 2.7.1 using the automatic upgrade feature. This is because the upgrade script “sees” WPMU 2.7.1 = WPMU 2.7.1, meaning it does not upgrade you from beta1 since it thinks you are already running 2.7.1.

So, you must manually upgrade WPMU following these instructions: https://codex.wordpress.org/Upgrading_WPMU

Bdegier-

As JFcarter suggests, you should make a backup of your database before beginning this process. Your BuddyPress data should be in the same DB as your WPMU data. You also may have some image files in other locations, so back those up as well. Finally, be carful of what you delete in wp-content. If you have any customized themes, or 3rd-party plugins, you will want to make sure you have a backup just in case.

Now, upgrading WPMU: Unless this issue has been recently fixed, you cannot use the auto update feature to upgrade WPMU 2.7.1-beta1 to the public release version of WPMU 2.7.1. This is because the upgrade script “sees” WPMU 2.7.1 = WPMU 2.7.1, meaning it does not upgrade you from beta1 since it thinks you are already running 2.7.1.

So, you need to do the old manual upgrade of WPMU following these procedures.

Upgrading BuddyPress: follow these instructions.

I make my changes in bp-member.

Only other thing I can think of is that you should go into the admin panel and check under Buddypress (almost at the bottom of the page). In the general area, you can select a theme for members. Select one, submit it and see what happens.