[@r-a-y Keymaster 16 years, 7 months ago]

Keep the sidewide posts blog private.

Then it won’t show up.

[@r-a-y Keymaster 16 years, 7 months ago]

Thanks for that bug report, will fix it up.

[@r-a-y Keymaster 16 years, 7 months ago]

Check out this function:

https://codex.wordpress.org/Function_Reference/maybe_unserialize

[@r-a-y Keymaster 16 years, 7 months ago]

Add a filter to bp_album_upload_path.

function my_bp_album_upload_path() {

$path = ABSPATH . 'wp-content/uploads/album';

return $path;

}

add_filter('bp_album_upload_path','my_bp_album_upload_path');

This code snippet is untested, but should give you some ideas.

You’re basically redefining the upload path that BP Album+ has set.

Lucky for you that the plugin offers a filter to change the upload path!

[@r-a-y Keymaster 16 years, 7 months ago]

You should be okay to upgrade directly to 1.2.3.

[@r-a-y Keymaster 16 years, 7 months ago]

Well, let’s do one thing at a time

What happens when you upload a new avatar?

[@r-a-y Keymaster 16 years, 7 months ago]

I’ll look into it; no guarantees though.

[@r-a-y Keymaster 16 years, 7 months ago]

How have you built your chlld theme?

Your child theme should reside in /wp-content/themes/.

If you did this, your theme would not be overwritten when you upgrade BP.

Read up on how to build a child theme:

https://codex.buddypress.org/how-to-guides/building-a-buddypress-child-theme/

[@r-a-y Keymaster 16 years, 7 months ago]

This plugin doesn’t do that.

You could try using MrMaz’s BP-Links plugin.

It’s more robust.

[@r-a-y Keymaster 16 years, 7 months ago]

Wrap it around a hyperlink:

<a href="YOUR IMAGE URL">download this awesome image</a>

[@r-a-y Keymaster 16 years, 7 months ago]

Were uploaded avatars working for you before BP 1.2.3?

Looks like your entire site is using gravatars at the moment.

[@r-a-y Keymaster 16 years, 7 months ago]

Since you customized your theme in an earlier version of BP 1.2, you need to update your header.php in your custom theme.

Check out /bp-themes/bp-default/header.php and note any changes between your header.php and the default.

[@r-a-y Keymaster 16 years, 7 months ago]

If you do a search on that javascript snippet on Google, you’ll find a ton of matches.

It could be a WP plugin that’s causing it.

Disable your plugins and re-enable them one-by-one.

[@r-a-y Keymaster 16 years, 7 months ago]

You should be linking to the URL of the SmugMug page and not the JPG.

[@r-a-y Keymaster 16 years, 7 months ago]

If you have a custom BP theme, you don’t need to move it to the /plugins/buddypress/bp-themes/ folder.

It should reside in /wp-content/themes/.

[@r-a-y Keymaster 16 years, 7 months ago]

I’d create a child theme of the default, copy over header.php and remove all the BP nav items, then you’d have a theme you can use for user blogs that looks exactly like the default BP theme.

[@r-a-y Keymaster 16 years, 7 months ago]

1) You can do this, but not by default. Requires a plugin or some custom code.

2) Depends on your server.

3) An open source project will always have bugs that’s why there’s new releases! Who says you have to pay someone to upgrade? BP is free and will always be free.

4) Possible via custom code.

5) There is no native support for photo albums; however, there are plugins that you can use to add support for this. BP Album+ and BP-Gallery are a few plugins that can do this.

6) This can be done via creating a custom theme.

[@r-a-y Keymaster 16 years, 7 months ago]

@putnum01

You have to add support for Smugmug to WordPress’ embed provider whitelist yourself.

Smugmug offers oEmbed support so this should be quite easy.

—

You can either add Smugmug support via wp_oembed_add_provider():

https://codex.wordpress.org/Function_Reference/wp_oembed_add_provider

Or if you can’t wait, you can upgrade your copy of /wp-includes/class-oembed.php to the latest trunk version:

https://core.trac.wordpress.org/changeset/13203

As the next version of WP will offer oEmbed support for SmugMug natively.

[@r-a-y Keymaster 16 years, 7 months ago]

@andy

The author of the plugin is M:

https://buddypress.org/developers/wpsec/

[@r-a-y Keymaster 16 years, 7 months ago]

You don’t need WPMU to use BuddyPress.

If you are testing this on a new install, I’d advise you to start from scratch.

Get WP, then get BP and everything should work.

Read this:

https://codex.buddypress.org/getting-started/setting-up-a-new-installation/

[@r-a-y Keymaster 16 years, 7 months ago]

@heathj85

Please either PM Dave or post on Dave’s support site for his plugin:

http://getpaidfrom.us/groups/buddypress-ajax-chat-support

Dave doesn’t frequent these forums often.

[@r-a-y Keymaster 16 years, 7 months ago]

You can try purging blog posts from the BP activity table and then using the following plugin by Boone Gorges:

https://wordpress.org/extend/plugins/bp-import-blog-activity/

[@r-a-y Keymaster 16 years, 7 months ago]

I don’t believe it’s the oEmbed plugin.

You could try disabling it and see what happens.

Do you have any other WP / BP plugins installed?

What is that piece of javascript you posted there?

[@r-a-y Keymaster 16 years, 7 months ago]

This is the expected behavior.

You’ll have to write some additional CSS if you want parts of your site to resemble the BP default theme.

[@r-a-y Keymaster 16 years, 7 months ago]

BuddyPress doesn’t create any pages (at least not in the current version).

It should be safe to use the BP Template Pack plugin.

But, as always, make a backup of your filesystem and your database just for safety measures.

Also, before making any changes on your live site, you should have some type of development site so you can test things like BuddyPress on it without worrying.