BuddyPress.org

@davidtcarson Thanks for the update, it’s looking awesome – especially the sidebars! Might wanna style the nav drop downs, though (http://i56.tinypic.com/15q53y9.png)

Shit. This forum deleted the code that I typed, and won’t let me edit the post.

You need to go into the editor, and change the header.php.
Find the section of code that relates to the navigation bar, and change the forward slash ‘/’ to ‘/index.php/’.

I wish I could write the code here, but the forum deletes it. Sorry

Hi Amanda,

It’s quite simple to fix from inside the theme editor.
Once you have changed the permalink structure to something other than default…

> Appearance > Editor > Header (header.php)

Find ‘

‘,

Underneath is a bunch of coding for the navigation bar. You need to find:

<a href="//” title=””>

And change it to:

<a href="/index.php//” title=””>

Notice all that has changed is ‘/index.php/’.
Do this for all of the navigation links.

It worked for me!

P.s. Note that if the buddypress developers don’t include this change in their next update, these changes will be wiped out. You would have to create a ‘child theme’ to avoid this changes resetting.

Also note, this does not work for the admin bar links.

Tom

That’ll either have been the BuddyBar, from BuddyPress, or perhaps the admin bar from WordPress 3.1+.

There are a few here may suit: https://buddypress.org/extend/plugins/?search=chat

I kind of agree with @djpaul. The average user will (or at least should!) have WP_DEBUG disabled, and will (or should!) have error reporting turned off. In that sense, those plugins are in fact compatible with BP 1.5. (To put that another way, if we go by the strict standards, they were never compatible with any version of BP )

I’m not sure if it’s good to fail a plugin purely because it has PHP warnings revealed with WP_DEBUG. Those warnings, if output to HTML rather than a log, can also cause problems with the rest of the plugin. We’re checking for BP 1.5 compatibility, not whether a plugin meets WordPress’ coding standards. Thoughts?

Closing thread

@r-a-y – hey man thanks for being a great help here to the community. I’ve been reading most of your posts in the forums over the past several hours fighting with my permalinks in activity streams.

I saw your .htaccess redirect post for mismatch 301 and tried it but I think I need it customized for activity streams?

In my example, certain activity posts are just going to the front page of my site rather than the post itself, they’re all coded like: http://www.site.com/activity/p/0001 when you click ‘view’ it just goes to the home page

Pulling my hair out trying to figure out how to get them to refresh or something. My permalink structure is /%post_id%/%postname%

It’s making me crazy lol

Install https://wordpress.org/extend/plugins/bp-template-pack/ to make WP theme compatible.
https://codex.buddypress.org/theme-development/wordpress-to-buddypress-theme/
https://codex.buddypress.org/theme-development/bp-template-pack-walkthrough-level-easy-2/

How would we be able to understand how to solve issues with activity links (where it says ‘view’ in the stream) redirecting to the home page? Not all of them are doing it, but a good enough number. I guess even (1) would be considered a bug.

I am using BP 1.2.9 with WP 3.2.1 multisite atm – made the upgrade this weekend and running into these issues..

Now having the same issue as Don on my BP 1.2.9 (WP 3.2.1 Multisite).

Certain activity links are now redirecting to the home page rather than the item. I tried seeing if there is a pattern as to why it’s doing this but it’s apparently random (to me). Certain ‘view’ links in the stream will redirect to the home page, some go to the activity.

I’ve tried changing permalinks a couple times and that didn’t help.

I updated to the new BP version last week. Any suggestions?

What do you mean that the website “crashed”?

It’s highly, highly unlikely that BuddyPress would have caused you to lose any data. If, after activating BuddyPress, your screen goes white, it usually suggests that you have insufficient memory on your server. In that case, simply navigate to wp-content/plugins with an FTP client, and delete the buddypress folder. WordPress stores content separately from its program files, and your data is still safe.

Here is a very helpful codex page on “blank screens”, which is what I assume you mean by “crashed”: https://codex.buddypress.org/troubleshooting/blank-pages/

Great!

If you’ve got command-line access to your server, you can check out latest development version via Subversion. Create an empty directory /wp-content/plugins/buddypress/, and then
`svn co https://svn.buddypress.org/trunk`
The nice thing about this is that you can then upgrade to the latest development version at any time by going into that directory and typing
`svn up`

It’s not recommended that you run the trunk version on a production server, though – only a development or test server.

@karmatosed thanks for updating https://codex.buddypress.org/releases/1-5-plugin-compatibility/

OK so I’ve had the same problem and have built a very clumsy workaround.

PROBLEM: When the user click the email verification it sends them to verify.php and logs them in to WP but my Buddypress doesn’t know they are logged in and asks them to login. If the user just ignores the login request there is no problem but users don’t do that so they try to login and get the same “error..please provide a valid activation key” message because the account is already active.

MY RUBBISH ANSWER: The only thing that worked for me was to hide the BP admin bar and handle login links manually then change the text on the verify.php to a simple ‘congratulations, you’re in’ message. The downside of this is that I lost the use of my BP-Sliding-Login-Panel which I love. so I would be very grateful for a real solution to this.

When using the Buddypress Template Pack, make sure you’re using that to insert the Buddypress CSS and JS in your theme as well, which is why it probably didn’t work for @abccreativity right away.

I’m not familiar with the Headway BuddyPress plugin. But first things first, are you install Buddypress 1.2.9 or 1.5-beta-2?

Found the answer in this thread: https://buddypress.org/community/groups/bp-album/forum/topic/upload-size-limits/

So, to be able to use upper case extensions go change line 525 in plugins/buddypress/bp-core/bp-core-avatars.php and change

(jpe?g|gif|png)
to
(jpe?g|gif|png|JPG|GIF|PNG)

(change it twice in that line)

Hope this helps!

I am having similar issues trying to get my BuddyPress install to work with my Headway BuddyPress Addon. I set up the BuddyPress plugin. -no problems- I then downloaded and set up the recommended BuddyPress Template Pack plugin. -site still working- However when I activate the Headway BuddyPress Add-On plugin, I receive the following error:

Fatal error: Cannot redeclare bp_dtheme_ajax_querystring() (previously declared in /home/mbctv/public_html/test4_2/wp-content/plugins/headway-buddypress-add-on/lib/buddypress-theme/_inc/ajax.php:2) in /home/mbctv/public_html/test4_2/wp-content/plugins/buddypress/bp-themes/bp-default/_inc/ajax.php on line 81

Has anyone received this message? And can someone please help me?? Thanks!

Becky