Forum Replies Created
-
Same issue here. My time zone is set correctly (and the same) in my WP options and on my server. Email timestamps are all 4 hours behind.
Did you ever figure this out? Times are fine everywhere else in my BuddyPress installation… but in emails they are all 4 hours behind. Is this a PHP / server configuration issue?
There are two popular solutions for regular WordPress (not sure how they would work with BuddyPress… I guess they would only translate the blog portion of the site). The two options are WPMU and qTranslate. WPMU make a separate post for each language while qTranslate puts all languages in one post separated by special comment tags. I found the management of a WMPU blog to be confusing. qTranslate has a simple tabbed user interface… so within your edit page for your posts… you get a tab for each language.
Well… with regards to SPAM… I’m not certain… but I suspect that’s actually BuddyPress-related. I’ve never had that issue on any of my other WordPress sites. But my BuddyPress sites are rife with SPAM signups. No matter what I do it seems. The only solution I found (after trying literally everything I could find here and at wpmu) was to block all proxy methods.
f) BuddyPress does not have all the features of […] Usenet.
– – –
I would like to see more Gopher features! Hypertext is sooooooo 1994.
@raynerlim36 So that worked for you?
There are multiple entry points for SPAM bots… so any one measure probably won’t accomplish much. I posted a list of everything I did in the “Spam, Spam and more Spam” thread. Worse case… you could try captcha.
@Magganpice: I’ve had two SPAM registrations since banning proxy connections.
I leveraged the existing drop down method in BuddyPress and created the following code. Three files in my child theme. Modify for your needs.
- header.php
- _inc/css/custom.css
- _inc/scripts/nav.js
header.php
<div id="wp-nav-bar">
<ul id="nav" class="main-nav">
<!-- Community Drop Down -->
<li <?php if (
bp_is_page( BP_ACTIVITY_SLUG ) ||
bp_is_page( BP_MEMBERS_SLUG ) || bp_is_member() ||
bp_is_page( BP_GROUPS_SLUG ) || bp_is_group() ||
bp_is_page( BP_FORUMS_SLUG ) ||
bp_is_page( BP_BLOGS_SLUG ) ) : ?> class="selected"<?php endif; ?>>
<a href="<?php echo site_url() ?>/<?php echo BP_ACTIVITY_SLUG ?>/" title="<?php _e( 'Community', 'buddypress' ) ?>"><?php _e( 'Community', 'buddypress' ) ?></a>
<ul>
<?php if ( 'activity' != bp_dtheme_page_on_front() && bp_is_active( 'activity' ) ) : ?>
<li<?php if ( bp_is_page( BP_ACTIVITY_SLUG ) ) : ?> class="selected"<?php endif; ?>>
<a href="<?php echo site_url() ?>/<?php echo BP_ACTIVITY_SLUG ?>/" title="<?php _e( 'Activity', 'buddypress' ) ?>"><?php _e( 'Activity', 'buddypress' ) ?></a>
</li>
<?php endif; ?>
<li<?php if ( bp_is_page( BP_MEMBERS_SLUG ) || bp_is_member() ) : ?> class="selected"<?php endif; ?>>
<a href="<?php echo site_url() ?>/<?php echo BP_MEMBERS_SLUG ?>/" title="<?php _e( 'Members', 'buddypress' ) ?>"><?php _e( 'Members', 'buddypress' ) ?></a>
</li>
<?php if ( bp_is_active( 'groups' ) ) : ?>
<li<?php if ( bp_is_page( BP_GROUPS_SLUG ) || bp_is_group() ) : ?> class="selected"<?php endif; ?>>
<a href="<?php echo site_url() ?>/<?php echo BP_GROUPS_SLUG ?>/" title="<?php _e( 'Groups', 'buddypress' ) ?>"><?php _e( 'Groups', 'buddypress' ) ?></a>
</li>
<?php if ( bp_is_active( 'forums' ) && bp_is_active( 'groups' ) && ( function_exists( 'bp_forums_is_installed_correctly' ) && !(int) get_site_option( 'bp-disable-forum-directory' ) ) && bp_forums_is_installed_correctly() ) : ?>
<li<?php if ( bp_is_page( BP_FORUMS_SLUG ) ) : ?> class="selected"<?php endif; ?>>
<a href="<?php echo site_url() ?>/<?php echo BP_FORUMS_SLUG ?>/" title="<?php _e( 'Forums', 'buddypress' ) ?>"><?php _e( 'Forums', 'buddypress' ) ?></a>
</li>
<?php endif; ?>
<?php endif; ?>
<?php if ( bp_is_active( 'blogs' ) && bp_core_is_multisite() ) : ?>
<li<?php if ( bp_is_page( BP_BLOGS_SLUG ) ) : ?> class="selected"<?php endif; ?>>
<a href="<?php echo site_url() ?>/<?php echo BP_BLOGS_SLUG ?>/" title="<?php _e( 'Blogs', 'buddypress' ) ?>"><?php _e( 'Blogs', 'buddypress' ) ?></a>
</li>
<?php endif; ?>
</ul>
</li>
<?php do_action( 'bp_nav_items' ); ?>
</ul>
</div>custom.css
/* Subnav */
ul#nav li ul {width: 30.7%;}
ul#nav li ul li {float: none; width: 100%;}
ul#nav li ul li a {background: none !important; padding: 5px 15px;}
#wp-nav-bar ul li ul {position: absolute; left: -999em; z-index: 1;}
#wp-nav-bar ul li ul li a span {display: none;}
#wp-nav-bar ul li:hover ul,
#wp-nav-bar ul li li:hover ul,
#wp-nav-bar ul li.sfhover ul,
#wp-nav-bar ul li ul li.sfhover ul {left: auto;}nav.js
startList = function() {
if (document.all&&document.getElementById) {
navRoot = document.getElementById("nav");
for (i=0; i<navRoot.childNodes.length; i++) {
node = navRoot.childNodes;
if (node.nodeName=
"LI") {
node.onmouseover=function() {
this.className+
" sfhover";
}
node.onmouseout=function() {
this.className=this.className.replace(" sfhover", "");
}
}
}
}
}
window.onload=startList;
j(document).ready( function() {
/* Admin Bar Javascript */
j("#wp-nav-bar ul.main-nav li").mouseover( function() {
j(this).addClass('sfhover');
});
j("#wp-nav-bar ul.main-nav li").mouseout( function() {
j(this).removeClass('sfhover');
});
});A full admin can do everything… including creating new users.
The issue is simple… bp-events is essentially the only option and there’s been a lack of communication from Erwin. So now we know. Good. Time to move on. I can now tell my organization that we have a plan going forward and that we can finally launch our site. We’ll just have to use a regular WordPress calendar instead of bp-events. Not ideal but it’s the best we can do. I’m fine with whatever… as long as I have a plan.
Should be integrated with groups but also have a global directory listing / calendar.
A number of people have asked me what my alternate solution is… it’s just a WordPress events plugin. There are lots of them. There’s no BuddyPress integration. It’s not ideal… but it will do for now. Specifically, I chose this plugin: https://wordpress.org/extend/plugins/calendar/
In fairness… I don’t think anyone ever said they felt they were owed anything. People just wanna know what the deal is. That’s fair enough. That said… I don’t know what kind of emails Erwin has been getting.
For my part… I’ve done exactly as suggested. I gave up on bp-events a long time ago. I have a site that has to launch, so I went with an alternate solution. It’s not nearly as good as bp-events… but it’ll do for now until something better comes along. I’m not a programmer so forking or coding my own is not an option. And the website is for a volunteer organization I’m involved with so hiring someone is also not an option.
It’s bp-events. But it’s not 1.2 compatible.
Well it’s been 3 full days now without a SPAM signup.
@Kunal17: I’m sure that’s probably just a coincidence.
@pushi22le: That’s a new tip. Thanks :o)
BTW… since banning proxies from accessing my site… I haven’t had a single SPAM signup.
I have no information… but based on the history of it’s development… I would say… don’t hold your breath. Which is not to say I don’t think it will ever come out. I’m sure it will. Eventually. But I wouldn’t count on any projections about release dates.
They could be legitimate proxies… yes… but I’m assuming they are in the minority.
I don’t think I have no referer rules. I’ll look into that.
So you just accept it? What a pain.
I just clued in that these bots are probably all using proxy servers… and compiling a big list of them all would be futile. So I found this htaccess code that blocks servers based on their methods. I know this topic has gone beyond specific BuddyPress fixes… but I’ve done all of the BuddyPress fixed (and more) and I’m STILL getting SPAM signups. So perhaps this will help someone else.
RewriteEngine On
# block proxy servers from site access
RewriteCond %{HTTP:VIA} !^$ [OR]
RewriteCond %{HTTP:USERAGENT_VIA} !^$ [OR]
RewriteCond %{HTTP:FORWARDED-FOR} !^$ [OR]
RewriteCond %{HTTP:FORWARDED} !^$ [OR]
RewriteCond %{HTTP:X-FORWARDED-FOR} !^$ [OR]
RewriteCond %{HTTP:X-FORWARDED} !^$ [OR]
RewriteCond %{HTTP:PROXY_CONNECTION} !^$ [OR]
RewriteCond %{HTTP:XPROXY_CONNECTION} !^$ [OR]
RewriteCond %{HTTP:XROXY_CONNECTION} !^$ [OR]
RewriteCond %{HTTP:HTTP_PC_REMOTE_ADDR} !^$ [OR]
RewriteCond %{HTTP:HTTP_CLIENT_IP} !^$
RewriteRule ^(.*)$ - [F]Credit goes to: http://perishablepress.com/press/2008/04/20/how-to-block-proxy-servers-via-htaccess/
Just got another registration from a .info email address. It occurs to me that that is not necessarily the domain they are coming from since my htaccess deny had no effect. The email ban setting also had no effect. Nor does hashcash or any of the other multiple measures I have put in place. I have no idea what to do anymore. I’ve tried everything. I’m resorting now to banning individual IP’s as they come in.
I’ll try. I just got a new registration from ANOTHER .info email address. Minutes ago. Ugh
Unreal.I’ve done everything mentioned in this thread and MORE. And no dice. Kind of at my wits end. How the heck are they signing up?! Unless it’s humans signing up. But I assume all SPAMers use bots. Even if it’s not a bot… I don’t know how you’d ever find the signup page with Google. It has a custom slug and I’ve gotten rid of the default BuddyPress text.
Anyway. Thanks Andrea.
I wonder if this would work in .htaccess
deny from .*\\.info.*@Andrea_r How do your say “SPAMbots please screw off” in Latin? LOL. Maybe Google can translate for me.
No more SPAM registrations since my last post. Fingers crossed.
Did you find out how to use regex in the WPMU “banned domains” setting?
I wonder if attempting to rename bp-core-signup.php might help. Who know how many things I could break though. LOL.
Anyway, I just duplicated the /registration/register.php file in my child theme and completely deleted this line… maybe that will help
<p><?php _e( 'Registering for this site is easy, just fill in the fields below and we\'ll get a new account set up for you in no time.', 'buddypress' ) ?></p>Okay… I am STILL getting SPAM registrations. I’ve done the following:
- Changed signup slug
- Installed hashcash (works with BP now)
- Disabled “Allow blog administrators to add new users…”
- Deleted BuddyPress credit in footer.php
- Deleted wp-signup.php
- Created a robots.txt file to disallow robots from my signup slug
Any more ideas? Short of Catcha? Altho’ I’m thinking even that won’t work.