[@jeffsayre Participant 17 years, 2 months ago]

@DJPaul

Sounds good!

By the way, I’m not that quick of a coder either. When it comes to coding, I say it’s better to be good than quick.

[@jeffsayre Participant 17 years, 2 months ago]

For all who are still having this issue. There was a bug fix 3 weeks ago that addressed this issue. See Changeset 1244. All widgets that come with BuddyPress were fixed with this revision.

If you are not running at least BuddyPress r1244, then you will still have issues.

Note: Custom widgets (3rd-party developed widgets), may or may not have implemented this bug fix. Therefore, if you are having translation issues with non-core BP widgets, you will need to contact the developer directly.

[@jeffsayre Participant 17 years, 2 months ago]

It looks like you’re using WPMU’s default Text widget and pasting the Google AdSense code within that. The widget’s output references a CSS selector (class=”textwidget”).

You need to use CSS to postion properly the AdSense output. You have three options:

1. Place inline CSS into the widget’s text field

2. Customize the textwidget selector

3. Create / or add to your own custom CSS file a new class called, for instance, my_ads. Then, reference that selector in the widget’s text field

[@jeffsayre Participant 17 years, 2 months ago]

Okay, a couple of questions:

1. Which version of BuddyPress are you using?

2. What did you name the file?

3. Where did you place it?

[@jeffsayre Participant 17 years, 2 months ago]

Has anyone had an opportunity to look at this yet–or even begin developing with it.

Please remember, as this is not (yet?) an official BuddyPress package, you should post any issues you find with bp-skeleton-component-1_2_URC1 in this thread and not in trac.

Of course, trac would not even be the proper place to post any issues with the official version of the skeleton component.

[@jeffsayre Participant 17 years, 2 months ago]

I have not used it before so I’m not endorsing this. But, FYI:

http://www.soderlind.no/archives/2009/02/27/toksta-chat-plugin-for-buddypress/

[@jeffsayre Participant 17 years, 2 months ago]

Very nice!

[@jeffsayre Participant 17 years, 2 months ago]

Well, it seems like you have an issue, alright. Let’s go down the list once again:

1. You’re working with a current trunk of both WPMU 2.7.1_beta1 (current: r1725) and BuddyPress 1.0_RC2 (current: r1324)
2. You’re using an old copy of wp-config.php which you updated as appropriate. In other words, you did not use the wp-config-sample.php that came with WPMU 2.7.1.
3. You did a clean install of WPMU 2.7.1_beta1 by deleting everything, except your updated version of wp-config.php, and then uploaded the unzipped Mu files
4. You then launched WPMU’s admin screen. That worked with out any problems.
5. You then went to Site Admin > Upgrade and finished the upgrade
6. You logged out of WPMU
7. Next, you installed BuddyPress by:

• moving the contents of the unzipped BuddyPress 1.0_RC2 (r1324) to the WPMU plugins directory into a subdirectory called /buddypress/
• moving the /bp-themes/ directory out of the /buddypress/ directory
• placing the various themes in their proper locations

8. You then logged back into WPMU and got a blank screen

A few follow up questions:

9. You’ve enabled error reporting as detailed above by John and Burt and after step 8 above, there are absolutely no errors being reported of any kind.

A few thoughts:

• Since this seems to be a test install and you do not have any content that needs saving, I would delete everything once again.
• This also means deleting your MySQL table that you’ve been using for this attempt and starting with a brand new database.
• I would then download the latest trunks of both WPMU and BuddyPress once again–>get rid of the old ones first.
• I would then use the wp-config-sample.php file that comes with the latest WPMU trunk and configure as necessary
• IMPORTANT: I believe when I downloaded the WPMU trunk (r1722) and looked at the wp-config-sample.php file, it had a trailing space after the closing php tag. You need to delete this!
• Now, go through steps 1 through 7 again and let’s hope when you get to step 8 it works!

[@jeffsayre Participant 17 years, 2 months ago]

Nicola-

Very nice!

I will investigate this for one of our projects. It could help with something we’ll be working on next month.

[@jeffsayre Participant 17 years, 2 months ago]

You may also want to post your request in this group’s wire: BuddyPress Job Board

[@jeffsayre Participant 17 years, 2 months ago]

@Socialpreneur

I had no option to turn on each buddypress plugins

BuddyPress is now considered a single plugin. Once you\’ve activated it in the Plugins menu, you go to the BuddyPress menu group at the bottom. Click on “Component Setup”, and you can enable and disable each component separately.

where should bp-custom go? the same dir as buddypress after r1303?

That is correct.

[@jeffsayre Participant 17 years, 2 months ago]

@Michael-

… I just updated to the latest trunk. Before I had 1303 installed…

What version of BuddyPress are you currently running? If it is 1303, that is not the latest trunk version. Try updating to the most recent trunk.

Also, 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);

Since you can see the admin screen when you remove BP, that should not be the issue. But I’m just trying to be thorough.

[@jeffsayre Participant 17 years, 2 months ago]

@Nicola-

I believe Hally was asking for the location of the wp-signup.php file.

@Hally-

Is that true? Or, are you asking where is wp-signup.php referenced within BuddyPress?

[@jeffsayre Participant 17 years, 2 months ago]

Actually, those instructions apply even if you have customized just the home theme or the member theme. Even though it does not explicitly say so, if you have customized your home theme, you should copy over the new functions.php file from the buddypress-home theme folder in RC2.

There are also some changes to the code in the header.php file that you may want to make in your custom header.php file. In fact, for good measure, you should copy over any of the files from the new theme directory that you have not hacked in your custom theme.

Finally, just in case, have you read this thread?

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

[@jeffsayre Participant 17 years, 2 months ago]

At this point in development, will i need to develop one theme for my buddypress and one theme for my bbpress? so that there will be no difference between the two?

In short, yes.

If you want your site-wide forum theme to look like your BuddyPress theme, you’ll have to customize both themes.

[@jeffsayre Participant 17 years, 2 months ago]

Hally-

wp-signup.php is a WordPress Mu file, not a BuddyPress file. Look within the directory you’ve installed WPMU.

[@jeffsayre Participant 17 years, 2 months ago]

Scotm-

Did you follow the instructions for custom themes at the very end of Andy’s first post here: https://buddypress.org/forums/topic.php?id=1994#post-10557 ?

As others started the upgrade process, and had certain issues, he made changes to the instructions. Depending on when you upgraded, you may have missed this.

[@jeffsayre Participant 17 years, 2 months ago]

Read this thread: https://buddypress.org/forums/topic.php?id=1661#post-8547

[@jeffsayre Participant 17 years, 2 months ago]

First, we need some basic information:

1. What version of WPMU and BuddyPress are you running?

Until we have that information, perhaps this thread will help: https://buddypress.org/forums/topic.php?id=1661#post-8547

[@jeffsayre Participant 17 years, 2 months ago]

Version updated to: 0.5.2

Okay, there have been a few testers of my Featured Members Plugin (widget). Thank you to all who provided feedback. I plan on submitting this plugin to the WP Plugin repository next week. So, if you have tried this plugin (or plan to try it) and have issues with it, please let me know before then.

I have made a few updates to the plugin:

1. I applied BuddyPress Changeset 1244 ( https://trac.buddypress.org/changeset/1244 ) to address localization issues.

2. I corrected a minor coding issue that had no performance impact.

Also, this version of the plugin has been tested up to WPMU 2.7.1_beta1 (r1722) and BuddyPress trunk (r1324).

If you plan on using it with the standard BuddyPress theme, you will have formating issues if you place the widget in the center or right columns and select the large avatar size. Basically, the member name gets pushed below the avatar. If that is an issue, either select the small avatar size or look at Mesgains solution above.

[@jeffsayre Participant 17 years, 2 months ago]

Looks like this was fixed in Changeset 1157. Therefore, the bug still exists if you’re using RC1.

You have two choices:

1. Either upgrade to the latest trunk (as Burt says) following these instructions: https://buddypress.org/forums/topic.php?id=1994

2. Or, wait until WordPress MU 2.7.1 is officially released and an official BuddyPress RC2 zip is available.

[@jeffsayre Participant 17 years, 2 months ago]

@Exay-

The skeleton component does not come with a language file. It has a language directory in which you can place your custom language file–if any.

It is up to each component developer to offer language support (beyond the typical l10n coding) if they choose to do so.

[@jeffsayre Participant 17 years, 2 months ago]

@Nicola-

I understand what you’re saying.

But when I look at bp-loader, I don’t see how referencing it will allow a custom plugin to access code in a switched off BP component. Only enabled components get included.

[@jeffsayre Participant 17 years, 2 months ago]

I guess I’m a little confused as well.

I know that bp-loader.php was added to the repo and included as part of the BP package in Changeset 1311, but I thought it simply managed the “loading” of activated BP components.

All custom plugins need to reference bp-core.php.

[@jeffsayre Participant 17 years, 2 months ago]

Hi, Nicola!

That code does not exist in the skeleton component. I assume you are suggesting that it be added?