Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'spam'

Viewing 25 results - 1,926 through 1,950 (of 3,349 total)
  • Author
    Search Results
  • #20541
    Annemarie
    Participant

    I did the latest update to BuddyPress and am having some problems. I accidentally changed the link to the default posts that my site uses as it’s home page and now my site opens to Not Found. If I go to the post itself, there is no option to set it as default. I have no Site Admin section in my Admin panel. What do I do? How can I fix this? Where did my Site Admin panel go? Please help!

    Also, when I mark users as spam, nothing happens. the page refreshes, says they were marked, and they are still unmarked.

    #107228

    In reply to: HELP!!!

    Paul Wong-Gibbs
    Keymaster

    @xxxxx Stop notification spamming. Consider this your third (and final?) warning.

    #20490
    #107167
    Jose Conti
    Participant
    Rob Watson
    Member

    # There are lots of WordPress hacks designed to take the contents of your wp-config
    # file (username and password) and dump them to a text file a spambot can pickup and
    # send to a hacker. If you block access to wp-config file in your .htaccess using
    # this method, you block those hackers from getting your database login information.
    Order deny,allow
    deny from all

    # Turn off directory indexing to keep anyone from seeing the contents of a directory
    # if there is no index file.
    Options All -Indexes

    # Block known spambots and crawlers. Update the following section with newly discovered
    # spambots and crawlers. This blocks them from ripping off posts and images (costing
    # bandwidth in the process.
    RewriteEngine On
    RewriteBase /
    RewriteCond %{HTTP_USER_AGENT} ^BlackWidow [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Bot mailto:craftbot@yahoo.com [OR]
    RewriteCond %{HTTP_USER_AGENT} ^ChinaClaw [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Custo [OR]
    RewriteCond %{HTTP_USER_AGENT} ^DISCo [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Download Demon [OR]
    RewriteCond %{HTTP_USER_AGENT} ^eCatch [OR]
    RewriteCond %{HTTP_USER_AGENT} ^EirGrabber [OR]
    RewriteCond %{HTTP_USER_AGENT} ^EmailSiphon [OR]
    RewriteCond %{HTTP_USER_AGENT} ^EmailWolf [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Express WebPictures [OR]
    RewriteCond %{HTTP_USER_AGENT} ^ExtractorPro [OR]
    RewriteCond %{HTTP_USER_AGENT} ^EyeNetIE [OR]
    RewriteCond %{HTTP_USER_AGENT} ^FlashGet [OR]
    RewriteCond %{HTTP_USER_AGENT} ^GetRight [OR]
    RewriteCond %{HTTP_USER_AGENT} ^GetWeb! [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Go!Zilla [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Go-Ahead-Got-It [OR]
    RewriteCond %{HTTP_USER_AGENT} ^GrabNet [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Grafula [OR]
    RewriteCond %{HTTP_USER_AGENT} ^HMView [OR]
    RewriteCond %{HTTP_USER_AGENT} HTTrack [NC,OR]
    RewriteCond %{HTTP_USER_AGENT} ^Image Stripper [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Image Sucker [OR]
    RewriteCond %{HTTP_USER_AGENT} Indy Library [NC,OR]
    RewriteCond %{HTTP_USER_AGENT} ^InterGET [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Internet Ninja [OR]
    RewriteCond %{HTTP_USER_AGENT} ^JetCar [OR]
    RewriteCond %{HTTP_USER_AGENT} ^JOC Web Spider [OR]
    RewriteCond %{HTTP_USER_AGENT} ^larbin [OR]
    RewriteCond %{HTTP_USER_AGENT} ^LeechFTP [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Mass Downloader [OR]
    RewriteCond %{HTTP_USER_AGENT} ^MIDown tool [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Mister PiX [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Navroad [OR]
    RewriteCond %{HTTP_USER_AGENT} ^NearSite [OR]
    RewriteCond %{HTTP_USER_AGENT} ^NetAnts [OR]
    RewriteCond %{HTTP_USER_AGENT} ^NetSpider [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Net Vampire [OR]
    RewriteCond %{HTTP_USER_AGENT} ^NetZIP [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Octopus [OR]

    RewriteCond %{HTTP_USER_AGENT} ^Offline Explorer [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Offline Navigator [OR]
    RewriteCond %{HTTP_USER_AGENT} ^PageGrabber [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Papa Foto [OR]
    RewriteCond %{HTTP_USER_AGENT} ^pavuk [OR]
    RewriteCond %{HTTP_USER_AGENT} ^pcBrowser [OR]
    RewriteCond %{HTTP_USER_AGENT} ^RealDownload [OR]
    RewriteCond %{HTTP_USER_AGENT} ^ReGet [OR]
    RewriteCond %{HTTP_USER_AGENT} ^SiteSnagger [OR]
    RewriteCond %{HTTP_USER_AGENT} ^SmartDownload [OR]
    RewriteCond %{HTTP_USER_AGENT} ^SuperBot [OR]
    RewriteCond %{HTTP_USER_AGENT} ^SuperHTTP [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Surfbot [OR]
    RewriteCond %{HTTP_USER_AGENT} ^tAkeOut [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Teleport Pro [OR]
    RewriteCond %{HTTP_USER_AGENT} ^VoidEYE [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Web Image Collector [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Web Sucker [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WebAuto [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WebCopier [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WebFetch [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WebGo IS [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WebLeacher [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WebReaper [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WebSauger [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Website eXtractor [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Website Quester [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WebStripper [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WebWhacker [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WebZIP [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Wget [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Widow [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WWWOFFLE [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Xaldon WebSpider [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Zeus
    RewriteRule ^.* – [F,L]

    # BEGIN WordPress

    RewriteEngine On
    RewriteBase /
    RewriteRule ^index.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]

    # END WordPress

    r-a-y
    Keymaster

    [EDIT]
    “blocked” and “inactive” roles appear to come from bbPress as this is not native to WordPress. My suggestion would be to *not* use these roles at all for the moment.

    If you’re using multisite, just use WordPress’ native Network Admin user administration panel and set users as spammers:
    https://codex.wordpress.org/Network_Admin_Users_Screen

    Do not use the regular WP admin users screen for this!
    https://codex.wordpress.org/Users_Users_SubPanel

    Virtuali
    Participant

    NO, this is NOT a buddypress problem.

    If you mark a user as Spammer, does it block him from logging in?

    Use a plugin called “wp-ban” to ban users

    #20393
    Virtuali
    Participant

    Do you have buddypress installed? This is not really a bp issue. Although if you do have buddypress installed, just mark him as spammer

    #106782
    matthewalan
    Member

    Okay, what are some examples of software for that?

    #106770
    Virtuali
    Participant

    You must search for anti-spam plugins that filter out spam activity that the users make.

    If the “spammers” are going past the captcha, that means they are not robots, actually people, just spamming your site.

    So keep the captcha for robots, and you will need to search for anti-spam software to filter out the spam content posted on your site.

    #20361
    matthewalan
    Member

    Lately I’ve been getting a lot of spam members and blogs on my site and it’s quite annoying. It’s so bad anymore that I can’t distinguish my real members from my fake ones. Originally I didn’t have any form of CAPTCHA, but I ended up getting a lot of spam members. So then I added SI CAPTCHA and it worked for a little while, but now I am getting even more spam members than before.

    My question is how do I stop spam from my site, but yet keep my blog hosting open to anyone who wants to join? I can’t keep getting all these members.

    #106755
    phcapgh
    Member

    Hello,
    I am leaving this here in case anybody else is at wits end with this problem. I installed the following plugin:

    https://wordpress.org/extend/plugins/si-captcha-for-wordpress/

    It is a capcha for subscriber sign up. Our buddypress has not been released yet, and we were getting upwards of a dozen spam sign ups a day. I installed this plugin a week ago. So far, no spam signups. I hope this helps.

    Morgue89
    Member

    Do you put the capatcha only on the registration area or on other parts of your site as well?

    phcapgh
    Member

    I have been fighting this issue for awhile. Last week, I found this plug in:

    https://wordpress.org/extend/plugins/si-captcha-for-wordpress/

    I’ve gone from dozens of spam subscribers a day to nothing over the last week. I hope this helps.

    #106708
    Jose Conti
    Participant
    Jose Conti
    Participant
    #106706
    Jose Conti
    Participant

    Hi,

    There is a new anti-splog plugin, you can try it, is free for personal use:

    https://buddypress.org/community/groups/wangguard/

    #106648
    gregfielding
    Participant

    Thanks guys.

    #106641
    modemlooper
    Moderator
    #106637
    Pisanojm
    Participant

    Greg,

    You have to do this front-end…. go to the group.. choose the admin link –> then delete group… There are some plugins for the back-end management of groups too…

    gregfielding
    Participant

    When I mark the user as spam, you would think the Group would go away, but it doesn’t. And, I can’t find any admin menu to delete rogue groups.
    I’ve got quite a few sex toy groups on my real estate site. :)

    #106354

    In reply to: WordPress 3.1

    zkwc
    Participant

    @josh101 I totally hear ya!

    i found another (insert curse word here) bug. When you mark someone as a spammer from their profile in Buddypress – they don’t actually get marked as a spammer on backend. Probably because of this (insert curse word here) way of separating the stupid (insert curse word here) network admin from regular admin. This is totally reedonkulas. So now… deleting spam got even harder. And I know for certain some of my spam plug-ins got broken too. So they are descending upon me like …. it’s not even worth discussing anymore. I’m just going to get angrier.

    edit:

    and… (am i angrier… yes) when you delete the (cuss word) spam after you’ve clicked on “registered” to make it show last joined and first joined, it reverts to alphabetical again just to piss you off and make you have to click the stupid “registered” button again to show first joined or last joined. Welcome to HOURS of spam deleting made possible to you by WordPress… the official WP motto “we aren’t into efficiency, we’re just into kicking all of you in the stomach”

    #106345

    In reply to: WordPress 3.1

    zkwc
    Participant

    @travel-junkie – I get over 2 million hits per month to my site. I get at least 400 spam sign ups a week. This is not an efficient change!

    #106328

    In reply to: WordPress 3.1

    Anonymous User 96400
    Inactive

    @zkwc
    Well, I get around 1 spam signup a week, if that. On any of my BP sites. For me, alphabetic ordering makes sense. And it would be for most WP sites (most of which aren’t BP enabled sites, btw). Obviously, WP development is separate from BP development, so changes made to WP might not make much sense for some BP users, but a lot of sense for the majority of WP users. Just some food for thought…

    I just upgraded 7 of my sites to WP 3.1 plus a few client ones and didn’t have any plugin problems at all. With the widespread adoption of WP it’s natural that some sites will experience problems, but don’t make this out to be an issue for everybody, when in fact it isn’t.

    As for the network admin page, this way is more organized. Stay on the current blog admin page to handle everything to do with this particular blog, go to the network page for anything related to running the network, like sitewide enabled plugins. To me this makes sense…

Viewing 25 results - 1,926 through 1,950 (of 3,349 total)
Skip to toolbar