[@tracedef Participant 14 years, 10 months ago]

Same issue occurred with us when we upgraded to 1.2… buddybar issues and my blogs disappeared… we eventually just downgraded.

[@tracedef Participant 14 years, 11 months ago]

Andy: You hit it on the head…. forgot about that pesky “Stop editing” line…..

[@tracedef Participant 14 years, 11 months ago]

Do follow is also a great way to encourage users to create and fill out a profile, specifically if you create custom fields for their “websites” in their profile. Spam registrations are already a major issue ( at least for us ) so that isn’t much of a deterrent for us at least.

[@tracedef Participant 14 years, 11 months ago]

I’m in the same boat. Have used a bunch of different captchas including the recaptcha that has been reworked for BuddyPress to no avail. Even took down our registration page for a day to make sure spammers weren’t bypassing via bbpress or somewhere else…. it was nice not having to delete spam accounts for a day. We may end up taking buddypress out at some point here until there are better spam tools in place.

[@tracedef Participant 15 years, 1 month ago]

Plus one after upgrading from pre 1.0 to 1.1.2. Some custom gravatars for groups work, some don’t and I’m unable to change my personal gravatar which is now one of the avatars that was originally used by a group. weird.

[@tracedef Participant 15 years, 1 month ago]

Similar issues here. Just upgraded from pre 1.0 version to 1.1.2. My default admin avatar was replaced with one used by groups. I’m unable to delete it and if I try to upload a new one only the small thumbnail of the two is replaced with my new upload. Trying to upload a second time fails and then both the large and small are repopulated by the original incorrect group gravatar that was originally present right after upgrading…. not sure if this helps at all…

Also just noticed that most group avatars are not showing as well…

[@tracedef Participant 15 years, 1 month ago]

Ahhh, missed this first time around.

https://codex.buddypress.org/developer-docs/conditional-template-tags/

[@tracedef Participant 15 years, 1 month ago]

J,

It looks like there was a loop conflict between multiple loops, for some reason it didn’t effect the pre-2 version of BP… thanks for the response!

T

[@tracedef Participant 15 years, 4 months ago]

Thanks for the update josswinn… was confused as to why it was back….

[@tracedef Participant 15 years, 4 months ago]

I’ve deleted all plugins (even those in the normal plugins folder) to no avail… I had to previously delete a bp add on plugin (name escaping me right now) because it was causing a white screen and it too was unable to be deactivated… so maybe even though it’s gone, it’s having some part in the issue….

[@tracedef Participant 15 years, 4 months ago]

I restored database from two days ago to see if that fixed the issue and it did… no clue what changed in the interim…

[@tracedef Participant 15 years, 4 months ago]

Haven’t touched themes… I edited original post above… it looks as though there’s actually zero buddypress code being loaded in sub-domain headers… hence no buddy bar…. so that’s the problem, the buddybar is merely a symtom….

[@tracedef Participant 15 years, 4 months ago]

Sounds like possibly this is related to BP plugin…. I would try installing buddypress with NO BP related plugins and then install them one by one to troubleshoot….. if you find one that causes white screen, then delete it via ftp and you should be able to undo white screen… let us know if you come up with anything……

[@tracedef Participant 15 years, 5 months ago]

Hey DJ! I’m not seeing any error log entries… using 1.3, btw….. will try to troubleshoot possible conflicts with other plugins in coming days….supposed to be on vacation right now.

[@tracedef Participant 15 years, 5 months ago]

It looks like this is a litespeed issue, reverting to apache solved the issue….

[@tracedef Participant 15 years, 5 months ago]

Also:

When I go to my plugins, firefox prompts me so open or save the following:

“You have chosen to download plugins.php”

which is a: Binary File

Open / Save File

*******************

The file contains the following (including weird 2008 cookie expiration) minus a page or so of random characters:

`

1248413318 2550 .

HTTP/1.1 200 OK

Content-Encoding: gzip

Vary: Accept-Encoding

Transfer-Encoding: chunked

Date: Fri, 24 Jul 2009 05:28:39 GMT

Server: LiteSpeed

Connection: close

X-Powered-By: PHP/5.2.6

Set-Cookie: bp_xprofile_meta=deleted; expires=Thu, 24-Jul-2008 05:28:38 GMT; path=/

Expires: Wed, 11 Jan 1984 05:00:00 GMT

Last-Modified: Fri, 24 Jul 2009 05:28:39 GMT

Cache-Control: no-cache, must-revalidate, max-age=0

Pragma: no-cache

Content-Type: text/html; charset=UTF-8

b0d

ã

[@tracedef Participant 15 years, 5 months ago]

@GPo1: There’s already a plugin but it doesn’t seem to be ported to Buddypress yet…. not clear on how much work will take to do so….. I’ve heard it works as is, but there are some issues with the fields that you may want required being bypassed and other minor field issues as it is only meant to work with MU….

[@tracedef Participant 15 years, 5 months ago]

To clarify, this is something we’re going to be using for paying clients, not the public at large, so that should take some of the issues raised above out of the equation.

Also, this is going to enable us to take away the 4 separate passwords / logins our paying customers need to use currently down to 2 for things like the forums, their website, billing, support, etc…. that is the main reason we’re implementing this…. otherwise we wouldn’t waste our time building something unless it was totally necessary….

I’m not concerned about whether or not it is a trend as RPX has been getting serious traction and even some big box retailers have started using it, so unless it crashes and burns, I’m not worried. If it gets us by for a year or two, I would be happy with that too.

[@tracedef Participant 15 years, 5 months ago]

Thanks for the heads up. I’m guessing that’s going to be one of a handful of considerations we’ll have to account for when implementing for buddypress.

[@tracedef Participant 15 years, 6 months ago]

I’m on 1.0.2, but that did correct the [p] tag issue. Thanks!

[@tracedef Participant 15 years, 6 months ago]

EDIT: Fixed by: upgrading taking the following from the buddypress download – /buddypress/bp-forums/bbpress-plugins/buddypress-enable.php moving to bbPress plugin folder and overwrite the existing one.

I’m on 1.0.2 and still have the issue on the home page, but it is limited to Group Forum posts that are listed. The group forum posts themselves also have them, while the posts that show in BBPress do not ….

[@tracedef Participant 15 years, 6 months ago]

Also noticed that group forum threads are showing the html markup such as [p] tags and the like when shown on group page, the markup doesn’t show up in bbpress…. strange.

[@tracedef Participant 15 years, 6 months ago]

I’ve been checking this thread ten times a day and then Andy crushes it! Thanks!!!

[@tracedef Participant 15 years, 6 months ago]

I’m using bbpress alpha 6, you may be pushing the envelope using the RC’s you mentioned.

Also, 2.7.1 and BP 1.01

[@tracedef Participant 15 years, 6 months ago]

Forgot to mention, error is occurring in header, not in logs as OP indicated….. in case you didn’t see screenshot above…

Occurs in Safari and Firefox … tried disabling all plugins and mu-plugins to no avail. It’s a somewhat new error, so trying to think of what could have possibly changed in install as of late besides plugin updates….don’t think the issue occurred in 2.7. …. not sure where to go from here…..

Any feedback or ideas appreciated, getting ready to launch and it’s kind of a bummer to have new users see this as they sign up.

Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /home/tracedef/public_html/wp-content/plugins/buddypress/bp-xprofile/bp-xprofile-signup.php on line 257