[@jeffsayre Participant 17 years, 5 months ago]

Dbascent94-

Are you still having issues? A week ago you posted this:

I tried using the default themes and the same problem persists. I could really use a pointer on where to even begin looking for a fix for this

But you failed to tell us which version of BuddyPress you are running. Two weeks prior, you stated that:

I downgraded to RC1. I am going to wait for 1.0 and then try again.

Does your problem exist when using the public release version 1.0?

[@jeffsayre Participant 17 years, 5 months ago]

We don’t have sufficient information to beginning helping either of you. Please read this and post accordingly: https://buddypress.org/forums/topic.php?id=2674

[@jeffsayre Participant 17 years, 5 months ago]

Codyb-

The forum link I provided is a free alternative to the premium plugins available at wpmu. I have not tried the suggestions in that link, so I do not vouch for them.

Your other option is the paid route: http://premium.wpmudev.org/project/rebranding-wordpress-mu

[@jeffsayre Participant 17 years, 5 months ago]

Log into WPMU backend as site admin. Go to Appearances > Plugins. The version of all your plugins, including BuddyPress, is displayed there.

Here’s the versioning info you should see with regards to the BuddyPress plugin:

For BP public release version 1.0 –> 1.0

For BP RC2 –> 1.0-RC2

For BP RC1 –> each individual BP component will show up as it’s own plugin.

As of r1303, which is where RC2 started I believe, BuddyPress was turned into one, big plugin suite.

[@jeffsayre Participant 17 years, 5 months ago]

If you’re still having this issue, you need to remove as many variables as possible. Since you are using a custom theme and a number of 3rd-party plugins, this is where you should focus your efforts.

Before starting this process, make a backup of your MySQL DB just in case. Also, it is advisable that you back up all your custom themes and 3rd-party plugin files just in case you make some major mistake.

Now, switch to the standard themes that come with BuddyPress. Try creating a group again. If the problem appears to be resolved, switch back to your custom themes and try creating a group again. If the problem returns, contact the theme designer.

Next, assuming the problem still exists with the standard BuddyPress themes, you should deactivate your 3rd-party plugins one at a time. Deactivate just one, try creating a group again. If the problem still exists, then deactivate another 3rd-party plugin. Keep doing this until either the problem goes away, or all 3rd-party plugins are deactivated. You can also go about this the other way: deactivate all plugins except BP and then reactivate one at a time, checking to see if the issue occurs again with each new reactivation.

If you find that the problem goes away after a particular 3rd-party plugin is deactivated, then you may have found the culprit. Contact the developer of that plugin and ask for advice.

Please report the results back in this thread.

[@jeffsayre Participant 17 years, 5 months ago]

Since, as Andy indicates, this is patched in trunk, I’m setting this thread to resolved.

[@jeffsayre Participant 17 years, 5 months ago]

This is actually a WPMU question, but I think you should find an answer here: https://buddypress.org/forums/topic.php?id=2042

[@jeffsayre Participant 17 years, 5 months ago]

I’m glad you’re back up and running.

Just in case you don’t know, phpMyAdmin is a MySQL administration tool. Whenever a task requires that you access your MySQL DB directly in the backend, this tool is what most WordPress developers and designers use.

[@jeffsayre Participant 17 years, 5 months ago]

Try this:

1. Fire up phpMyAdmin
2. Go to the appropriate DB for your WPMU install
3. Navigate to the wp-site table
4. Click the “Browse” tab. You’ll see the data in that table
5. The first record should be for your website’s domain with the path to your WPMu install
6. If that is different than what it should be, make the change there, save, and close.

Of course, as always, back up your database before making any changes to your data directly or changes that could affect the accessing of your data.

[@jeffsayre Participant 17 years, 5 months ago]

Shakera-

If I understand your issue, you are having problems localizing BuddyPress into Cyrillic.

Please check this BuddyPress codex page first as there is a translation of BP for Bulgarian.

If you are making your own translation, then you should read the Translating WordPress codex page.

[@jeffsayre Participant 17 years, 5 months ago]

The core Buddypress files do not live in /mu-plugins/ anymore. They should be in /plugins/ instead. If the location of BuddyPress is hardcoded into the Toksta chat plugin, then that is the problem.

Contact the Toksta chat developers and ask them to update their plugin to the proper path–and not via a hardcoded path.

[@jeffsayre Participant 17 years, 5 months ago]

Evvscuba–

Here are a few thoughts:

1. Do a test with your users by switching to the standard BuddyPress themes. If the problem goes away, then it’s most likely a theme issue.
2. Make sure that your users are uploading avatar files with sufficient dimensions. At a minimum, each dimension needs to be at least 150 pixels.
3. Upgrade your version of GD. It is a little outdated. There may have been some browser-related bug fixes since your version (note: I’m just suggesting that possibility; I have not verified this though). The current, stable version is 2.0.35
4. Finally, contact Sgrunt, the desinger of Facebuddy, and ask for his advice. He may be aware of an issue with IE 6 & 7. If he is not aware of your partciluar issue, he most likley will appreciate you keeping him in the loop–wether or not this particular issue has anything to do with his custom theme. Share with him the results of the above steps.

[@jeffsayre Participant 17 years, 5 months ago]

Jfcarter-

Is this still an issue? If so, would you please provide a link (assuming your site is not on you local server) so that we can look into this more closely.

[@jeffsayre Participant 17 years, 5 months ago]

Freaking Wildchild-

I do understand that this has been a big mess for you. Please don’t take my last post personally. I appreciate your willingness to share your issues.

If you have not yet done so, I suggest starting a new thread to discussion this particular issue and to track the progress you are making. Now that we know more about your particular setup, it will be interesting to see how this works itself out.

[@jeffsayre Participant 17 years, 5 months ago]

Freaking Wildchild-

I do understand that this has been a big mess for you. Please don’t take my last post personally. I appreciate your willingness to share your issues.

If you have not yet done so, I suggest starting a new thread to discussion this particular issue and to track the progress you are making. Now that we know more about your particular setup, it will be interesting to see how this works itself out.

[@jeffsayre Participant 17 years, 5 months ago]

Suleiman-

Since you state that this is no longer an issue. I’m setting this thread to resolved.

[@jeffsayre Participant 17 years, 5 months ago]

You have got to be kidding!

I’d recommend switching hosts.

[@jeffsayre Participant 17 years, 5 months ago]

Freaking Wildchild-

Well, what is surprising to me is that you were trying to debug this with plugins other than BuddyPress running. qTranslate is a WordPress plugin.

In the fifth post in this thread, Burt advised you to:

Disable all other plugins

I had been under the assumption from that point on –even with your new attempt at a fresh install–that you did not have any other plugins installed and activated other than BuddyPress.

When trying to debug something as complex as WPMU + BuddyPress, you need to remove as many variable from the equation as possible. That means, among other things, deactivating all plugins other than BP.

Anyway, it looks like you have your culprit narrowed down. I’d suggest contacting the qTranslate plugin dev and asking for help.

[@jeffsayre Participant 17 years, 5 months ago]

Kit-

I’m sorry you’re having troubles with your theme folders. To be clear, I want to make sure that you realize that you were not, as you state:

advised to change my “bphome” name to preserve it in case of future BP upgrades.

I assume you’re talking about the discussion we had in this thread you asked:

I assume renaming the theme is simply changing the name of its folder?

I responded:

That is correct. Make a copy of the bpmember theme, rename your copy, make whatever changes you want to it, and you have–in effect–a custom theme! Just make sure you keep your new theme in the /wp-content/bp-themes/ directory.

Also, in this thread where I advised you to:

Follow the same procedure as before. Make a backup of the standard bphome theme, rename it to something new…

This means, rename your backup to something new, not change the name of the original theme folder.

Furthermore, as per a private conversation you initiated with me on May 6 via the members messaging system, I state that:

Make sure that you make a copy of both bphome theme and bpmember theme. Your customizations should be done in copies, not the original. 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.

And, as we were talking about CSS issues in that private message and you stated that you had WordPress theming experience, I assumed you knew that the primary style file in BuddyPress, style.css, would need to reflect your new theme’s name.

If you were confused by my advice, I do apologize. But, if you had done what I advised, you would have made a copy of the original theme and altered the copy. As I stated in my private message response to you, do not alter the original theme files.

[@jeffsayre Participant 17 years, 5 months ago]

Misterfunk74-

Posting a new request for support in a thread that is marked resolved is not the best way to get help. Why? Because those of us who offer help tend to skip over resolved posts and look for threads that need our attention.

If you’re still having an issue, then please start a new thread. Here are some support guidelines to get you started: https://buddypress.org/forums/topic.php?id=2676

[@jeffsayre Participant 17 years, 5 months ago]

Codyb-

Yes, you have to have a basic mail server set up. Otherwise, the mail will not go out.

You’re running CentOS, if I remember: http://www.linuxmail.info/postfix-smtp-server-howto-centos-5/

[@jeffsayre Participant 17 years, 5 months ago]

Erich73-

Toni is using the P2 theme. You can get it here: https://wordpress.org/extend/themes/p2

[@jeffsayre Participant 17 years, 5 months ago]

Bbn-

Rather than trying some fancy install via packaged tarballs, I’d suggest a plain, simple install from scratch. Even though you went back and, as you state, “tried to do a more careful replacement of the files,” try a clean-slate install.

Delete everything, including your MySQL DB–assuming you don’t have any important data. Then, download and install WordPress Mu 2.7.1 from here. Get it working before attempting to install BuddyPress.

Once it is working, download BuddyPress and follow the readme.txt instructions.

Looks like this is happening to a lot of sites

I understand your frustration. But, when I search Google for “Failed+opening+required+’BP_PLUGIN_DIR”, I can count exactly 6 actual sites with this error and then several comments within blog posts that indicate the same issue.

Combine that with the half a dozen reports in the BP Forums for this issue, and you get maybe 15 people–assuming none of these people have commented in multiple places. That is not “a lot of sites”.

[@jeffsayre Participant 17 years, 5 months ago]

Codyb-

Excellent!

So there was a rouge .htaccess file gumming up the works. Those dang invisible files are tricky!

[@jeffsayre Participant 17 years, 5 months ago]

Maythil-

Look for this line of code in the header.php files of both your bphome and bpmember themes:

<div id="search-login-bar">

<?php bp_search_form() ?>

<?php bp_login_bar() ?>



<div class="clear"></div>

</div>