[@r-a-y Keymaster 13 years, 6 months ago]

@marcio-batista – Which translation is causing this problem?

[@r-a-y Keymaster 13 years, 6 months ago]

It’s possible that a plugin could be interfering with the activity stream.

Try disabling all BP-related or any caching plugins and see if the problem still occurs.

[@r-a-y Keymaster 13 years, 6 months ago]

`no-ajax` tells BP that:

• we want to use pagination instead; or:
• we shouldn’t use AJAX for this page because we haven’t implemented it yet (unfortunately).

[@r-a-y Keymaster 13 years, 6 months ago]

You’re most likely using a plugin for this.

Check your plugins list and see if anything is related to BP registration.  Also check to see if you added any BP snippets in your wp-content/plugins/bp-custom.php file or your theme’s functions.php file.

[@r-a-y Keymaster 13 years, 6 months ago]

@martyn_ @valuser – BP Follow was just updated today and should fix the DB issue.  Let me know if it doesn’t.

[@r-a-y Keymaster 13 years, 6 months ago]

Sounds like you’re using a plugin for the login popup.

If you disable the login popup plugin, does this problem occur?  If it does, try asking the plugin author about this.

[@r-a-y Keymaster 13 years, 6 months ago]

hnla is absolutely correct.

You can place `buddypress.php` in the `buddypress` subdirectory.

You can treat `buddypress.php` like any other template.

So what you want to do is do a conditional check to see if you’re on a profile page.

Since you only want to show the sidebar on non-member pages, you could use the following code snippet:

`<?php if ( ! bp_is_user() ) { get_sidebar(); } ) ?>`

This snippet should replace the `get_sidebar()` line in your `buddypress.php` template.

[@r-a-y Keymaster 13 years, 6 months ago]

A quick Google search for your 324 error came up with this:
http://www.roezer.com/fixing-chrome-bug-error-324-neterr_empty_response/

Appears to be a Chrome-related bug.  Try the solution in that blog article and see what happens.

Also try using another browser and see if that error occurs.

[@r-a-y Keymaster 13 years, 6 months ago]

What theme are you using for the parent?

If it is not bp-default, `buddypress.php` should reside at `wp-content/themes/child-theme/`.  Not in a subdirectory of your theme.

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

Thanks for posting about this.

I’ve just committed a fix for this here:
https://buddypress.trac.wordpress.org/changeset/6903

It should make its way into BP 1.7.1 once that is released.

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

Cool!  The change was made for the better as custom themes shouldn’t need to add all that BP conditional logic in their custom buddypress-functions.php file.

If possible, please share a link to the new site once it’s launched!

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

Fanoop, can you help debug this issue for us?

What avatar URLs are showing up in the HTML source on BP 1.7 with your multi-network setup?  As always, can you try doing this locally or on a development environment?

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

Yes, it did 🙂

Which is why I asked if you started a custom theme using the new method.  Glad you figured it out!

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

Are you using BP 1.7 on a WP theme?

First, read through hnla’s doc on theme compatibility:
https://codex.buddypress.org/developer/theme-development/a-quick-look-at-1-7-theme-compatibility/

After you’ve read it, follow these instructions.

Copy `page.php` and rename it to `buddypress.php.`  Now edit this file and remove `get_sidebar()` and make any additional changes you want and then save.

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

Sounds like a problem with the Gantry BP plugin.

Try disabling that and see if that fixes things.

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

Anything in the server error log?

Are you using any other plugins beside BP?  Have you already started a custom theme using the new method in BP 1.7 perhaps?

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

Hi, check out the answer I gave in this thread for some info on avatars:
https://buddypress.org/support/topic/registerchange-buddypress-avatar-for-user/#post-158822

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

Avatar information is not stored in the database, but rather in the filesystem.

Check your WP uploads folder, followed by another folder called “avatars”.

Avatars use a hash followed by a suffix to denote the type of avatar.

eg.

`/wp-content/uploads/avatars/USER_ID/dfjkljlksjdflksjdklf-bpfull.jpg` -for full-size avatar
`/wp-content/uploads/avatars/USER_ID/dfjkljlksjdflksjdklf-bpthumb.jpg` -for thumbnail avatar

You could, in theory, use anything for the filename of the avatar.  Just make sure the suffix is there.

Give that a shot.

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

In your stylesheet, you need to clear your #footer.

Try adding a`clear:both;` and see if that fixes your problems.

[@r-a-y Keymaster 13 years, 8 months ago]

Hi,

You might want to take a look at this article by our mod, hnla:
https://codex.buddypress.org/developer/theme-development/a-quick-look-at-1-7-theme-compatibility/

[@r-a-y Keymaster 13 years, 8 months ago]

@vegaskev – The codex articles were moved around a bit.  Apologies!

The new link to the article is here:
https://codex.buddypress.org/developer/releases/developer-and-designer-information/

Scroll down to “Group avatar uploading doesn’t work” to view the fix.

[@r-a-y Keymaster 13 years, 8 months ago]

I don’t think this is possible by default.

You’ll probably have to either:
* Write a small plugin to disable the forum post form for regular group members; or:
* Modify the bbPress post form template and do your checks in there.

[@r-a-y Keymaster 13 years, 8 months ago]

If you’re on a new install of BuddyPress and bbPress, follow this guide:
https://codex.buddypress.org/user/setting-up-a-new-installation/installing-group-and-sitewide-forums/#b-set-up-group-and-sitewide-forums

[@r-a-y Keymaster 13 years, 8 months ago]

For the Home page, create a regular WordPress page and assign it as the “Front page”:
https://codex.wordpress.org/Settings_Reading_Screen

For the Contact page, create a regular WordPress page and install one of the many contact forms for WordPress:
https://wordpress.org/extend/plugins/tags/contact/

[@r-a-y Keymaster 13 years, 10 months ago]

If you use any of these selectors, the ajax loader should show up:

• a.loading
• input.loading
• a.button.loading
• input.loading[type=”submit”]
• input.loading[type=”button”]
• input.loading[type=”reset”]
• ul li.loading a

I believe the old span selector was removed awhile ago.