Search Results for 'private'
-
AuthorSearch Results
-
May 25, 2010 at 6:49 pm #79632
In reply to: private messaging broke on 1.2.4 upgrade
piphut
Participant@r-a-y I think I just created a new administrator account and then deleted the old admin account but honestly it has been awhile so I could be wrong.
May 25, 2010 at 6:47 pm #79631In reply to: private messaging broke on 1.2.4 upgrade
r-a-y
KeymasterThis is not a “problem” per se.
It’s a matter of customizing the language file:
https://codex.buddypress.org/how-to-guides/customizing-labels-messages-and-urls/Most users will input a subject… so I don’t see this being a big issue. You could possibly add javascript validation so the subject has to be filled out before the form is submitted.
Also, just wondering how you changed the username? This will help with others who encounter this problem later.
May 25, 2010 at 6:44 pm #79630In reply to: private messaging broke on 1.2.4 upgrade
piphut
Participant@r-a-y That worked but now there is a new problem. When a user tries to send a PM but leaves the subject blank they get a generic error that says “There was an error sending that message, please try again”. Is there anyway to either a) just make the subject of blank messages “no subject” or b) specify in the error message that a subject has to be entered before they can send?
May 25, 2010 at 6:39 pm #78569In reply to: private messaging broke on 1.2.4 upgrade
r-a-y
Keymaster@piphut – It should… but if it doesn’t… try the snippet I posted above.
Also, this begs the question… how did you change your username in the first place? Did you edit it through the DB or through a plugin?
May 25, 2010 at 6:35 pm #79629In reply to: private messaging broke on 1.2.4 upgrade
piphut
ParticipantHi @r-a-y I checked my database and “admin” IS the nicename. If I change that in my db will that fix the problem?
May 25, 2010 at 5:59 pm #79625In reply to: private messaging broke on 1.2.4 upgrade
r-a-y
Keymaster@piphut – Try adding the following in wp-config.php:
define( 'BP_ENABLE_USERNAME_COMPATIBILITY_MODE', true );It’s possible that “admin” is still used as your “user_nicename”.
May 25, 2010 at 12:24 pm #79583In reply to: private messaging broke on 1.2.4 upgrade
Oliver Wrede
ParticipantI am having the problem that sending a private message points to “/members/_myuserid_/messages/compose//” which in turn responds with a Forbidden-Error page. My User ID is not “admin” though I do have site admin privileges.
This does not seem to be the bug describred in the ticket at https://trac.buddypress.org/ticket/1820
Regards,
OliverMay 25, 2010 at 4:14 am #79551In reply to: private messaging broke on 1.2.4 upgrade
piphut
ParticipantJust on the admin account, yes. I re-opened the ticket thanks.
May 24, 2010 at 11:38 pm #79529In reply to: private messaging broke on 1.2.4 upgrade
r-a-y
KeymasterThis is only happening for your admin account right?
This ticket is related to your issue:
https://trac.buddypress.org/ticket/1820Might want to reopen it.
—
Also try disabling any third-party plugins (including the Usernames only plugin)… see if your problem disappears.
May 24, 2010 at 10:25 pm #79518In reply to: private messaging broke on 1.2.4 upgrade
piphut
ParticipantMore info: for some reason it returns my username as “admin” even though I deleted the “admin” user a long time ago. My profile page even uses “admin” in the URL: http://piphut.com/members/admin
However I user @r-a-y ‘s username only plugin and it shows up correctly as “piphut” in my blog comments.
So the problem appears to be in is passing the wrong username in the r= string when people try to private message me, and therefor the ‘send to’ is not being populated correctly, though it was working correctly before the upgrade to 1.2.4
Thoughts? Quick fixes? Free fish?
May 22, 2010 at 6:11 pm #79216In reply to: Alternative to Facebook
Jeff Sayre
Participant@arxpoetica et al –
I just created the private BP group Semantic Web and Open Stack Integration to focus our discussions. As it is a private group, you must request membership. I felt it was better to create a private group so that we could ensure the conversations are maintained at the proper level.
May 22, 2010 at 2:15 pm #79192Anja Fokker
ParticipantAnd for the users of BuddyPress version 1.2.4:
I have also tested it with 1.2.4 and it’s still working great.May 22, 2010 at 11:17 am #79165Boone Gorges
KeymasterHappy to hear that it works!
May 22, 2010 at 8:50 am #79157Anja Fokker
ParticipantYEZZ, it works again. Thanks for your help again!
The only things what are needed:In the root of BuddyPress (version 1.2.3):
In bp-blogs.php, change rule 379 of
if ( (int)get_blog_option( $blog_id, ‘blog_public’ ) || !bp_core_is_multisite() ) {
IN:
if (get_blog_option( $blog_id, ‘blog_public’ ) > 0 || !bp_core_is_multisite() ) {and change rule 427 from
if ( (int)get_blog_option( $recorded_comment->blog_id, ‘blog_public’ ) || !bp_core_is_multisite() ) {
IN:
if (get_blog_option( $recorded_comment->blog_id, ‘blog_public’ ) > 0 || !bp_core_is_multisite() ) {and the MU plugin:
ds_private_blog.php: http://wpmudev.org/project/More-Privacy-OptionsWith regards Anja(afoka)
May 21, 2010 at 10:23 pm #79123In reply to: private mail at buddypress.org ?
r-a-y
KeymasterPMs are disabled on here for now due to spam; I’m guessing the old messages are still in the DB though.
Awaiting further word about this from Andy.May 21, 2010 at 10:23 pm #79122In reply to: private mail at buddypress.org ?
abcde666
Participantthe old website of bp.org was much easier to navigate and find information.
at least for myself…..May 21, 2010 at 4:59 pm #79091Boone Gorges
KeymasterOops, yeah, you’ll need to remove the parenthesis before get_blog_option in both of those.
I don’t know about the blog class thing. Try without changing it and see what happens.
May 21, 2010 at 4:47 pm #79089Anja Fokker
ParticipantStrange… In both cases if I change the rules (379 and 427), is this the result:
Parse error: syntax error, unexpected ‘{‘ in betawordpresswp-contentpluginsbuddypressbp-blogs.php on line 379
Parse error: syntax error, unexpected ‘{‘ in betawordpresswp-contentpluginsbuddypressbp-blogs.php on line 427
I have also as before changed the rule In buddypress/bp-blogs/bp-blogs-classes.php
if ( !(int)$wpdb->get_var( $wpdb->prepare( “SELECT DISTINCT public FROM {$wpdb->base_prefix}blogs WHERE blog_id = %d”, $blog_id ) ) )
in
if ( $wpdb->get_var( $wpdb->prepare( “SELECT DISTINCT public FROM {$wpdb->base_prefix}blogs WHERE blog_id = %d”, $blog_id ) ) < 1 )May 21, 2010 at 4:15 pm #79086In reply to: Disable All RSS Feeds
F. Saint
ParticipantSo I’m a total newb at this and I don’t understand how to disable the RSS on BP. I tried putting the code in to the file you suggested (at the end of the current code) but I’m not sure I’m doing this correctly. Can you offer any help, or some more detailed instructions (in layman’s terms) so that I can make my RSS feed for all site activity go away? I want to have a completely private BP community.
May 21, 2010 at 3:35 pm #79083Boone Gorges
KeymasterIn bp-blogs.php, change 379 from
if ( (int)get_blog_option( $blog_id, 'blog_public' ) || !bp_core_is_multisite() ) {
to
if ( (get_blog_option( $blog_id, 'blog_public' ) > 0 || !bp_core_is_multisite() ) {Also, change 427 from
if ( (int)get_blog_option( $recorded_comment->blog_id, 'blog_public' ) || !bp_core_is_multisite() ) {
to
if ( (get_blog_option( $recorded_comment->blog_id, 'blog_public' ) > 0 || !bp_core_is_multisite() ) {I haven’t tested this but it should work.
May 21, 2010 at 1:33 pm #79072Anja Fokker
Participant@Boone Gorges, well I do have the same problem in BuddyPress 1.2.3 . I can find the rule in /bp-blogs/bp-blogs-classes, but……
the file bp-activity (in the root of BuddyPress) changed so much, that i don’t know where to find the rules like you’ve discribed.
Will you help me again? Or maybe you know if there is a plugin for it?With regards Anja (afoka)
May 20, 2010 at 1:46 am #78936In reply to: Private communities
lifemore
ParticipantThank you so much r-a-y. I appreciate this.
vidaMay 19, 2010 at 9:13 pm #78911In reply to: Private communities
r-a-y
KeymasterYou’ll have to wait for Google to check your site again.
You can expedite this process by signing up for Google’s Webmaster Tools and requesting your site to be delisted.
Also make sure your WP site is blocked from search engines:
https://codex.wordpress.org/Settings_Privacy_SubPanelMay 19, 2010 at 8:01 pm #78896In reply to: Private communities
lifemore
ParticipantThank you Rich:
I have used “registered user only” plugin for the site. It works OK. But apparently the member’s activity page still shows in Google cache and I can’t make that disappear even when I delete that user’s profile
May 19, 2010 at 6:36 pm #78884In reply to: Private communities
-
AuthorSearch Results