Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Pop VeKind

    (@popvekind)

    Thanks Hannah!

    Via that link, I was able to contact Mr. Ben Ritner. We are working together to improve Pinnacle.

    Hello @20supriya,

    I had the same problem. Here is what I did (all free)! However, Hannah’s solution may be better if you can afford it.

    For comment Spam:
    Antispam Bee
    https://wordpress.org/plugins/antispam-bee/

    For Form Email on Apache (pair.com):
    WPForms Lite
    https://wordpress.org/plugins/wpforms-lite/

    For NGINX (Linode) I add,
    WP Mail SMTP
    https://wordpress.org/plugins/wp-mail-smtp/

    Well, that worked for me,

    Thread Starter Pop VeKind

    (@popvekind)

    @zodiac1978 Thank You Torsten for the helpful information.

    Fortunately, Anti Apan Ver 5.5 is still working on my sites. That gives me some time.

    I have a half-dozen sites that are used only for the organizations to disseminate information, meaning no comments. Therefore any submitted comment should be spam. My plan is to put each of the three options on a couple of sites and see what they do.

    • Antispam Bee in the default mode.
    • Antispam Bee with most options turned off.
    • Inpsyde AntiSpam (js-antispam)

    I agree with you, the JS option is not the end-all, be-all solution for comment spam, as you have noted. That said it is a simple, lightweight solution for people appealing to the general masses who use off-the-shelf home computing equipment. In the many years and many sites, I used Anti Spam, the few spams I saw were human-spam. Hard to block in a lightweight system.

    However, if it can safely be added to Antispam Bee as an option, I think that would be wonderful.

    Thanks Again,

    Pop

    Thread Starter Pop VeKind

    (@popvekind)

    Thanks Tung @dinhtungdu

    I found the Github page and opened that issue after I had posted here. I will monitor it there.

    Apologies to anyone who was confused by the “410 Done” in the original post. Of course, it should be “410 Gone”. Maybe I could blame my spell checker, but it is likely my age, poor spelling, or bad typing. Or should I blame it on my great-grandchildren? Anyway thanks for being patient with me.

    I hope we can add the 404 Gone and improve the Safe Redirect Manager Plugin at Github.

    Thread Starter Pop VeKind

    (@popvekind)

    @tobifjellnerCORRECT!

    That is NOW what makes 410 Gone so powerful now that Google uses it correctly, NOW!

    Before Google behaved like this: 410 = 404. In other words leave the URL on the crawl list, retest for a while and after some time (reportedly up to a year), remove the bad URL from the index.

    The new behavior for 410 is… ASAP remove from the Index. ASAP remove from crawl list. Do NOT recrawl the bad URL unless a link is discovered too that bad URL. This makes 410 Gone a powerful Webmaster tool. So powerful that Yoast has added 410 Gone to their Pro version. Not using 410 Gone can negatively affect your site ranking.

    This is why I ask the developer to add 410 Gone to this product.

    nabihazkhan,

    Not sure if it works here but my post sidebar disappeared when I accidentally set Theme Options > Blog Options > Blog Post Defaults > Blog Post Sidebar Default to No! Might want to check that!

Viewing 6 replies - 1 through 6 (of 6 total)