[@jeffsayre Participant 17 years, 4 months ago]

Do you have any plugins other than BuddyPress installed and activated. If so, you need to distill your environment down to the lowest common denominator: Use the default BP themes that come with v1.0.1 and deactivate all other plugins.

What happens then? If you do not have any more issues, then you know it has something to do with your custom theme, one of the plugins, or some combination.

You then start going back up the ladder one step at a time. Switch the default BP themes for your custom themes. Does the problem return? It not, then is has to do with your plugins. Activate one plugin at a time until the issue returns.

Here’s a thread where Paul talks about a similar error message and plugins: https://buddypress.org/forums/topic.php?id=2802#post-15313

Let us know how your testing goes.

[@jeffsayre Participant 17 years, 4 months ago]

If you are not in a hurry then I would recommend waiting for awhile. At some point, BuddyPress will be configured to function on single-user WordPress. I do not have a timeline for this as it has to do with merger of the WPMU codebase into WP.

[@jeffsayre Participant 17 years, 4 months ago]

what version of jQuery we can expect to see in the next BuddyPress update?

Well, based on the new features of WP 2.8, which WPMU will merge into its codebase, I’m going to guess jQuery 1.3.2. Perhaps Andy has a different idea.

[@jeffsayre Participant 17 years, 4 months ago]

@Erich

You are free to use the Skeleton Theme or an existing theme as your template in designing a new BP theme. The Skeleton Theme is a bare bones theme. It has the minimum header and footer code, and function set to make things work. So, if you are using a non-BP theme and trying to turn it into a BP theme, you should either look at the Skeleton Theme or the default themes that come with BP to see what is needed.

Concerning the default themes that come with BP–the bphome theme and the bpmember theme–you can also use those as templates for your new custom themes.

My standard caveat when creating custom themes from the default BP themes is as follows:

Make sure that you make a copy of both bphome theme and bpmember theme. Your customizations should be done in copies, not the originals. The copies need to have unique names. Do not rename the default themes. They stay unchanged. That way, if you have issues with your custom themes (and we all do when working on customization), you can switch back to the standard BP themes to see how things should work.

[@jeffsayre Participant 17 years, 4 months ago]

@thebloghous

You’re welcome. As others have seen me say before, we aim to please and sometimes we actually manage to do so!

[@jeffsayre Participant 17 years, 4 months ago]

Haha! I beat you to it this time, Burt!

You’ve provided a little more detail though, so–team effort wins!

[@jeffsayre Participant 17 years, 4 months ago]

Look at line 1426 of that function:

add_action( 'init', 'bp_core_action_search_site', 5 );

In your bp-custom.php, you can stop that action by doing this:

remove_action( 'init', 'bp_core_action_search_site', 5 );

You’ll need to place that within a function.

See this for more info: https://codex.wordpress.org/Function_Reference/remove_action

[@jeffsayre Participant 17 years, 4 months ago]

If you are offering paid work, you should post your request here: https://buddypress.org/groups/buddypress-job-board

[@jeffsayre Participant 17 years, 4 months ago]

Try placing your function in bp-custom.php. If that file does not exist, create it and place your function code there. This file should be placed in /plugins/. It will be loaded before anything else–see bp-core.php line 10 and 11.

[@jeffsayre Participant 17 years, 4 months ago]

Hey, no reason to say sorry!

There are too many variables of which to keep track. It is sometimes necessary to bounce issues off of others.

[@jeffsayre Participant 17 years, 4 months ago]

@Rogercoathup

Not really. The standard operating procedure on the forums is that when a given issue is finally determined to be a bug, and that bug has been isolated, that it then gets posted in trac.

But, if you think that you’ve found a bug, you can go right into trac and file a new ticket. If it is big enough of an issue, creating a thread in the forums and pointing to your new trac ticket may be in order.

[@jeffsayre Participant 17 years, 4 months ago]

Anything new since two months ago? There have been many changes to BuddyPress over that time!

Have you searched the forum and read this thread

If so, then you need to provide more of an explanation than “Having the same problems with avatars”. That tells us exactly nothing to begin the process of providing support. Please see this thread as well.

[@jeffsayre Participant 17 years, 4 months ago]

I will say that I have elected to delete some lines of code to remove some functions in the core files but they aren’t super critical, in my opinion.

Okay, as I’m sure you know, this type of sentence scares all of us who try to offer support.

The real question is this:

If you boil everything down to the lowest, common denominator (LCD), does everything work. This means using BuddyPress without any core mods, using the default themes, and not running any other plugins in WPMU except BuddyPress.

If everything works, then this is an issue caused by something you are doing. If you still have this problem, then you need to talk with your hosting firm or system admin (if you are in a business/institutional setting) because it could have something to do with your server setup (DB server maybe).

But, if everything works as it should when you’ve distilled the WPMU/BuddyPress install down to the LCD, then it clearly is something you’re doing. It could be your core hacking, the single-sign-on coding, a 3rd-party plugin conflict, any combination of changes. You need to go back to the bare bones foundation and then start adding stuff back, implementing your changes one at a time and throughly test in between each new change.

[@jeffsayre Participant 17 years, 4 months ago]

A few additional thoughts can be found here:

https://buddypress.org/forums/topic.php?id=2779#post-15393

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

[@jeffsayre Participant 17 years, 4 months ago]

Jessica-

I can’t remember if you’ve tried this yet. If not, it is worth a shot.

Switch to the standard bbPress theme. Place the calls to wp-head and wp-footer in the appropriate places. Don’t worry about the calls to the search-login-bar. We’re only doing a test to see if we can get the top menu bar to appear.

Also, does your BuddyBar show for logged in users but just not for those who are logged off?

[@jeffsayre Participant 17 years, 4 months ago]

@Burt

I’m particularly proud of my discovery of the true nature of the relationship between bp/wpmu/bbpress when it comes to integrating the three

Gluons and quarks! That made me laugh. You are a strange, charmed, down to earth, up to the challenge, top of your game, and never on the bottom of a list.

Yes, that is quark humor.

[@jeffsayre Participant 17 years, 4 months ago]

This is because BuddyPress currently runs only on WPMU, not the single-user version of WordPress

[@jeffsayre Participant 17 years, 4 months ago]

Matt-

Have you looked at the Trent’s detailed instructions here? His instructions work with bbPress RC1.

Also, is you’re not using BP v1.0.1, it may be a good idea to upgrade.

[@jeffsayre Participant 17 years, 4 months ago]

Well, it depends. In your first post, you stated that

slimbox and other similar plugins aren’t working.

If you are talking specifically about Slimbox1 (notice the number 1), then the answer to your above question is you don’t. Slimbox1 relies upon the Mootools framework, not the jQuery toolkit. However, if you are talking about Slimbox2, it was rewritten to utilize jQuery.

So, first make sure that you are using Slimbox2 as Mootools and jQuery do not always play well together. Second, upgrading jQuery in an 3rd-party component is beyond the scope of this forum. It is best to let the plugin developers handle such upgrades.

[@jeffsayre Participant 17 years, 4 months ago]

Rogercoathup-

The standard WP procedure should work fine. Just make sure that you select all the BP tables as well when backing up! Before deleting your database, if that is your plan, make sure the backup worked.

Also, remember that some files, such as media files, are not stored in the database. You need to back these up separately.

[@jeffsayre Participant 17 years, 4 months ago]

@Sean

Are you still having this issue? Everything looks fine when I visit the link you’ve provided.

If this issue is resolved, please set the light on top to green. If not, please answer these questions: https://buddypress.org/forums/topic.php?id=2674

[@jeffsayre Participant 17 years, 4 months ago]

Well, upgrading the JQuery version that the plugin uses is an option, but it’s best to contact the plugin dev and let them now about the issue. Ask them to update their plugin so that it supports BuddyPress.

[@jeffsayre Participant 17 years, 4 months ago]

Home themes need to be located in:

/wp-content/themes/

Member themes need to be located in:

/wp-content/bp-themes/

Read this for more info: https://codex.buddypress.org/getting-started/installing-buddypress/

[@jeffsayre Participant 17 years, 4 months ago]

Saraswati11-

You may need to update your themes to be consistent with the the default BuddyPress Themes that come with v1.0.1.

[@jeffsayre Participant 17 years, 4 months ago]

This may shed some light on the issue:

https://buddypress.org/forums/topic.php?id=3165#post-17435