majecdad
Forum Replies Created
-
Cool, glad to hear its coming along. I appreciate your attention to it.
Yes, it was from a ‘What’s new’ box. And the new (unapproved) user that I saw was listed in the Members sidebar widget.
Just a FWIW, but in a perfect world, after more testing, the Private Network might be too locked down for our use. The Moderation would be better. The rationale for us is that it would be fine for new (unapproved) users to see the ‘Public’ (Privacy=’Anyone’) posts in the Activity Stream. But not interact with them (comment, like), or add their own comments to the Stream.
Also, allowing them to at least see whats out there in the BP pages gives them a chance to see the various Groups and Forums they might be interested in. Hope that makes sense.
Thanks again for your work on this.
I thought the ability to post to everyone prior to approval might have been related to having the buddypress activity privacy/ plugin active – which allows multiple privacy choices (including ‘Anyone’) for post visibility.
But after deactivating it, the above issues remain.
I just wanted to update you as I tested from this end.
Thanks.
I just modified the site to test in the ‘Private Network’ mode. That could be doable. I like the way it shows all the profile page icons, but they are not functional.
I also think the reg process and messaging is very well done.
One issue there though. In my testing, the new user (not approved), while restricted from seeing any of the information from/of others (good), is still ABLE to post in the stream and have it seen by everyone else (notsogood). That, of course, is potentially really spammy.
The (unapproved) new user is also added to the users list. It seems it would be better to keep them in the BPRO approval queue instead.
Lastly, I am going to test with a potentially conflicting privacy plugin deactivated, and will followup.
Thanks.
βRight, my (maybe incorrect?) understanding was that having just ‘Moderate’ precluded βthe new user from interacting with the platform components (except their own profile), where ‘Private Network’ hid everything.
I don’t have a problem enabling the more restrictive of the two, it was just ‘Moderate’ (as I understood it) was the perfect fit for not-too-much/not-too-little.
Regardless, let me know what you recommend, I’m flexible.
More importantly, thanks for diving in to resolve!
I made a change to how you can access (removed Login plugin). You can try again, and I will send you a quick email.
A/O, also, yes, feel free to hijack users.
Hey Michael,
So it’s been a bit since the initial report, I was wondering if you were able to replicate the issue? Or if you had hit the site with the login info I submitted?
I also reverted to BP 2.1.1 on another test site I have – I figured it might be a 2.2 issue – but the problem was there too.
Please let me know if I can do anything else to help.
Thanks.
Hey Michael,
I thought I recognized you from somewhere – didn’t make the AppPresser connection. Great product, loads of potential, wish I could have gained better traction with it. I think I got stuck on PhoneGap. I need to look again before all my licenses expire. π
WRT this matter: First
_bprwg_is_moderatedis set as trueSecondly, you may have a point with other plugin functionality. I have about a dozen BP plugins in place (plus way too many others). I know I deactivated some in testing, I’ll continue to look at that. (edit: have deactivated all BP plugins excl: BP and BPRO, issue remains).
Re: ‘adding public message where’ – If the New User goes to /members/existingmember/ the New User can see the existing user profile and the buttons that say ‘public message’ and ‘private message’ (as well as the aforementioned add friend) as referenced, the Public message button was visible by the NewUser in the existing user profile, but clicking on it gave the White Screen of Death. (‘oh by the way’ update: after deactivated all the other BP plugins, NewUser is now ABLE to post a public message update to an existing user profile page – ooops – go figure).
Here are the BP plugins I had active, but a conflict here doesn’t seem to be the issue.
BP Group Hierarchy Propagate by Christian Wach version 0.3.2,
BP Group Hierarchy by David Dean version 1.4.3,
BP Group Organizer by David Dean version 1.0.8,
BP Profile Search by Andrea Tarantini version 4.0.3,
BP Registration Options by Brian Messenlehner and Michael Beckwith of WebDevStudios, Jibbius version 4.2.4,
BuddyPress Activity Privacy by Meg@Info version 1.3.3,
BuddyPress Group Email Subscription by Deryk Wenaus, boonebgorges, r-a-y version 3.5,
BuddyPress Like by Darren Meehan version 0.2.0,
Buddypress Xprofile Custom Fields Type by donmik version 2.1.5,
BuddyPress by The BuddyPress Community version 2.2.0,Lastly, happy to provide you access. Just know it is a total – I mean really – sandbox site… so no laughing at it. π
LMK where you want credentials sent.
Thanks for your efforts here.
I would add some more results of testing, the New User – still unmoderated – DOES show up in the standard BP Members widget, shows up in the Member directory, and is calculated in the All Members qty.
Plus he can comment on existing Updates from other users.
Thanks for any insight you can give as to whether I might be looking at intended functionality totally wrong.
Forum: Plugins
In reply to: [BP Group Hierarchy Propagate] Privacy rules in PropagationTo clarify, I was seeing Items posted in Public Group 1 fed downstream into Private subGroup 1.1 – when the User posting was NOT a member of subGroup 1.1. That was the issue.
I agree with your statement above
‘I don’t understand why members of “(Private) subGroup 1.1” would want to see only activity items from its own members in “(Public) Group 1”.’
… they should see all member content in the PUBLIC group, but not (non-member) Public Group content IN the Private subGroup.Strangely, as I try to replicate the issue today, I can’t. Yet I still see the comments I made yesterday in the stream that created this impression. In all the testing, I may have had a setting tweaked. I think I’ll step away for a bit and come back to it. π
Regardless, thanks again for both a fantastic plugin and the timeliness of your support replies. Have a great day.
Forum: Plugins
In reply to: [BP Group Hierarchy Propagate] Privacy rules in PropagationHello Christian,
Firstly, thanks for the timeliness of your reply, excellent.
So I updated the plugin to 0.32, here’s whats happening: (activity set as bi-directional)
If User A posts in (Public) Group 1, the content is also seen by User A in (Private) subGroup 1.1 (that he is a member of). It is NOT seen by User B, who is NOT a member of (Private) subGroup. — that’s good.
If User A posts in the (Private) subGroup 2, if feeds up stream to (Public Group 1) — but only seen ny members of the (Private) subGroup 2. — that’s good.
However, if User B posts in (Public) Group 1, it IS propagated to (Private) subGroup 1.1 (even though he is NOT a member there). User B can NOT actually see the post in (Private) subGroup 1.1, but other members of the (Private) subGroup 1.1 CAN see it. – no bueno, shouldn’t even be there.
All this testing has been good in that it has me reevaluating my structure to feed downstream too. Original thinking was that it was important, I’m not so sure. But if it would work – and be subject to the privacy considerations – it would at least give that option.
A tangent, if I may – you know what would be cool, selectively allowing only Admin or Group mods to have downstream posting capabilities. Thoughts?
Thanks again for your efforts here. Let me know if you have an update that you want further tested.
Also, WRT your comment and link, I would refer to the statement you made in that thread… “Why would a private or hidden group have a public child group?” — Seems like a really edge case use, and sometimes it comes down to just because you can do something, doesn’t mean you should do something. π
Forum: Plugins
In reply to: [OpenTickets Community Edition] No People, no RolesThanks Simon… although I read about every page on the site(s) (many of them twice!) π I don’t think I caught that difference in role management options. Many of the features listed in the Features tab on the site were somewhat difficult to distinguish one version from the next. I’ll continue to test and see what else I come up with. π
Thanks again.
Forum: Plugins
In reply to: [Plugin Organizer] Fatal Error after UpdateInstalled PO 5.6.1 and all is good in the world again. π
Thanks again for a fantastic piece of code.
Forum: Plugins
In reply to: [Plugin Organizer] Fatal Error after Updatephp 5.3.10
Forum: Plugins
In reply to: [Plugin Organizer] Fatal Error after UpdateJust to confirm, I get the same error as the OP re: line 922 on my update to 5.5.
Using: WP 4.0, Genesis 2.1.2, PO 5.5.
Thank you for all your efforts in what has become an indispensable plugin. I’ll revert to 5.4 until you can get to any fix here.
Forum: Plugins
In reply to: [WP RSS Multi Importer] Image sizes vary in AutoPostAfter modifying (yet again) settings in the rss image plugin, the last three posts have come in with the proper image size. I am going to mark this as resolved for now. I’ll update if the issue reappears. Thanks.