Viewing 15 replies - 1 through 15 (of 23 total)
  • I am not an artist and the tools for making the WP icons are limited. I will try again this week to get a better icon.

    The plugin is HUGE because of all of the country block modules. They are not activated by default, but they still take some time to unpack and install. I anticipate lots of problems from these. You are not the first to complain that the install did not go smoothly. The problem is that the WP install times out and never completes the last steps of the install.

    Keith

    Thread Starter Endymion00

    (@endymion00)

    Since you have an Add-On system now, maybe the country block modules should be separated out as multiple add-ons or at least 1 separate add-on to reduce the issue with the main plugin. Just an idea.

    Should I be concerned that any portion of the plugin is missing due to this? …or is the fact that I see the new plugin at all confirmation that it at least installed and unpacked fully, but just didn’t activate due to the timeout?

    Thread Starter Endymion00

    (@endymion00)

    I noticed something. I’m running dozens of wordpress sites, so I’ve had the opportunity to try upgrading differently.

    If I go to the Plugins page and click update there. The plugin updates within a few seconds and then activates as expected.

    If I got the Dashboard -> Updates and update the plugin there. It also updates within a few seconds but never activates.

    Something seems to be different between the 2 update procedures. Neither actually appeared to be slow due to plugin size as far as I could see.

    Great plugin…
    Noticing the changes, and it seems in the updates, you’ve removed the top level domain block (domainnamehere.xxx)

    Has this been replaced by the country block?
    I’m asking only because, I’ve got multiples signing up using the same domain name, and not sure where to place that to stop them.

    Takes a bit to get used to the new looking format, as well as finding where things are…

    Looking forward to seeing more.

    Thread Starter Endymion00

    (@endymion00)

    Top level Domain Block is still there. Look on Block Lists -> Blocked TLDs

    Thread Starter Endymion00

    (@endymion00)

    You may actually be referring to “Blocked Email Domains” which does appear to have gone missing, but maybe you can put it in the deny list with a wildcard. They show the wild card sample with the * at the end, so does the following now work?

    *@domain.com

    Wait! I am sure that I coded and tested the TLD blocks. Yes, it’s on the “block lists” menu item.

    The country blocks work differently. I’ve been collecting “bad neighborhoods” where spam comes from. I organized it by country. The country blocks don’t block countries, just the bad internet neighborhoods in the countries.

    I was going to make the county blocks a pay add-on, but they are so effective in blocking spam that I left them in the main plugin.

    Keith

    Guess it pays to read the paragraph instead of skimming it….
    Sorry bout that, the way it was already set up, led me to believe it was just the extensions….my bad
    Appreciate the reply and setting me straight….
    I love this plugin, it’s saved me a lot of grief
    Thanks again

    Just reading your mail, I will attempt to see if wildcards will work,
    shouldn’t be a problem, as for some reason today, I’ve been getting hit with user after user, ..251 for today all blocked, but they seem to keep bypassing this block for some reason.

    I’ll let you know
    thanks

    If the plugin did not completely install, it will generate errors, which will be caught and collected. You can see them if they exist on the Diagnostics page.

    I think now I’ll have to write a 100 page guide to using the plugin. Some of this may not be as obvious as it seemed when I was writing it.

    Keith

    Thread Starter Endymion00

    (@endymion00)

    Yeah, hopefully wildcards like *@domain.com work and not just the samples with them at the end like:

    spammer@spam.* or 1.2.3.*

    Nope wildcards only work at the end of the string. I did not code a very smart wildcard algorithm spammer@spam.* will work, *@domain.com will not.

    Keith

    Thread Starter Endymion00

    (@endymion00)

    So that makes email domain blocking a missing feature from the previous version then.

    Email blocking is still there, but not as a separate function

    You can put @yahoo.com in the Spam Words list.

    Spam words checks email, body, and subject. If it finds the string @yahoo.com anywhere then the comment is spam.

    I was going to take out email checking altogether. Spammers don’t use their own email. They use real emails taken from lists of good addresses.

    Keith

    @kpgraham
    Here’s a transparent image to use
    https://graphiclineweb.files.wordpress.com/2015/02/index.png
    Any images you need tweaked – let me know

    Suggestion: It may be an idea to change the way the image is called – data:image/png;base64string in /settings/settings.php to rather us a static image URL. Less likely to have the file flagged by security software or blocked by .htaccess security rules

Viewing 15 replies - 1 through 15 (of 23 total)
  • The topic ‘2 minor 6.0.1 update issues’ is closed to new replies.