majecdad

Nice job on 1.3.4. This update resolves the issue posted above. There is a new links conflict, I’ll post about that separately. Glad to see you active again. Thanks.

Hey Michael,

Circling back around to update this. Further testing of 4.2.5 has gone fine. Only issues are those previously referenced (e.g. member widget, pre-moderated registration in Stream, etc…)

I saw a reference to 4.3 somewhere… then I went and looked at github and saw a 4.2.6 too (that dealt with b, above) – cool. Just to clarify from that githib issue info; The ‘prevent xyz has registered activity stream message’ – would it ultimately pass that information to the Activity Stream *only once Approved*?

Any idea when 4.2.6 will drop?

Thanks.

Hey meg@info,

I’m glad you’re still around. 🙂

As I mentioned in my earlier post, I had already done what was referenced in your link, and had actually increased WP Memory to 256MB. The issue remained until I deactivated the plugin.

The error:
“Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 7680 bytes) in /URL/wp-content/plugins/buddypress/bp-core/bp-core-functions.php(138) : runtime-created function on line 1”
remains, and is on the page after the user submits “Post Update’

No error shows on the other users (non-sender) pages and the update comes through (+ Load newest) as expected.

Once the original sender (manually) refreshes their page, the error message goes away.

And again, once the BPAP plugin is deactivated, posting does not generate the error.

Let me know if I can help in any further testing.

I look forward to your upcoming release.

If they’re not approved, it’d be great to exclude them from everywhere but their own profile.

I am seeing new registrations, where unapproved members are listed in both the BPRO moderated area and the ‘Pending’ area of wp-admin users. I wish they didn’t even go into users until *after* they were moderated.

I’m not sure if it’s related, but unmoderated users, even though they can’t post in the recent update-in-progress, they are still shown as “xxx became a registered user” in the BP Activity Stream – wish that didn’t happen as some – shall we say “creative” – names would be populated in that stream… no bueno.

Let me know what else I can do to help test.

Thanks!

In case anyone out there smarter than me (big numbers there) 🙂 wants to dig into this, here’s something of interest:

For me, posting from the ‘What’s new’ box to the main “My Profile” is broken, no matter which Privacy I choose.

HOWEVER, posting to any Group from that same box, or on any Group page directly, WORKS, without the error.

Make any sense? Any thoughts?

Gave 4.2.5 a quick run through last night… things look great. I could not post or comment as a new (unapproved) user. You already know of the sidebar widget, so only three issues came up, were relatively insignificant, and IMO were likely beyond the scope of your work, and related to the other plugin(s). I pass them along only FYI to you and others.

Using Invite Anyone, the link in the email sent allows the ability to accept the friend request. Since that was from an invite, a ‘friendship’ is assumed.

Using BuddyPress Like, the new (unapproved) user is able to ‘like’ any content that they see. NBD, really.

Using myCRED, the user got activity points before being approved. Again, 3rd party.

The only thing I would add is that I went through the ENTIRE process as a new user a couple of times, in the last go round I went ahead and ‘approved’ the request as an admin. The ‘hey, welcome to the club’ (paraphrasing) email was never delivered. I’ll try that again soon.

Again, these usage issues are not likely in your domain, and are minor stuff, really. I’ll update as needed as I mess with it more.

Thanks again for your work on this. Have a great weekend.