Support » Plugin: Spam protection, AntiSpam, FireWall by CleanTalk » Cookies and the plugin version 5.82+

  • ResolvedPlugin Author Safronik

    (@safronik)



    Good day to everybody!

    Starting 5.82 version the plugin doesn’t use any PHP Sessions.
    Instead it uses cookies. Cookie becomes very important for plugin’s correct execution.
    If you disable “Set cookies” option in the plugin advanced setting there could be some issues with spam prevention.

    Here is the description for cookies we are using in the plugin:
    apbct_cookies_test – Сookie to validate other cookies, so they can’t be spoofed.
    apbct_* – Group of cookies which are set from backend and contain information about current user.
    ct_* – Group of cookies used for storing dynamic variables from browser.
    ct_sfw_* – Group of cookies used for our SpamFireWall technology.

    Let us know if you have any questions!

Viewing 7 replies - 1 through 7 (of 7 total)
  • Hi,

    I’m using Varnish, does it cause any problem?
    How can I test the cookies?

    Thanks

    Plugin Author Safronik

    (@safronik)

    Hello,

    No it shouldn’t. You don’t have to change or test anything (if it works).
    If you faced spam(i bet you won’t), you would mark it as spam here: https://cleantalk.org/my/show_requests

    Contact us if you have questions.

    Earl_P

    (@earl_p)

    My site settings are set to “YES” under “Set Cookies” setting, but yesterday my site crashed and the tech support at my host, DreamHost, sent me the following message. They use Varnish and apparently I was having this PHP conflict. My site has CleanTalk 5.83.2 already installed, which you say above does not use PHP.

    Here is the message:

    Hello,

    Thank you for contacting DreamHost support!

    I am sorry to hear about your recent downtime issues. Reviewing the site
    and server, the issue is that Varnish isn’t able to properly cache the
    site, which is causing the site to use more resources than it should
    require and the server ran out of memory. I was able to determine which
    plugin is the cause for you though. The culprit plugin is
    “cleantalk-spam-protect”. This plugin is generating PHP sessions which is
    effectively breaking varnish. I would suggest deactivating this plugin
    and contact the plugin developers to see if they can make it Varnish
    friendly. If they aren’t able to I would suggest looking for a different
    anti-spam plugin, such as Akismet.

    Once Varnish is properly working the site should not only not have that
    issue again but should also be faster as well. Hope this helps!

    Thanks,
    Evan S

    Plugin Support sergecleantalk

    (@sergecleantalk)

    Hello,

    Thank you for your request.

    Could you tell us what website you have the problem with? We will investigate this more detail. Please give us 2-5 working days.

    We will contact you as soon as possible.

    Best regards

    Plugin Author Safronik

    (@safronik)

    Hello,

    Thank you for the feedback.
    I can confirm that the plugin doesn’t use any sessions since 5.82 version. The latest version is 5.84, please install it if you haven’t done it so far.
    Please, create a support ticket (https://cleantalk.org/my/support) so we could investigate the issue more closely. We could use some cooperation with you.

    Please contact us.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Plugin Review Team Rep

    Starting 5.82 version the plugin doesn’t use any PHP Sessions.
    Instead it uses cookies.

    How is it using cookies?

    If you’re putting down unique cookies for every single visitor, logged in or out, then you’re going to have the same resource issue with Varnish.

    In an optimum world, you should only be putting down the cookie when someone starts a talk session. Think of it like a cookie for a shopping cart 🙂 If there’s nothing in the cart, there should be no cookie (or session) and everything should be caching. If there IS something in the cart (or in your case, chat) then a cookie would be placed to indicate caching should not take place.

    Plugin Author Safronik

    (@safronik)

    Hello,

    It was a step to solve the Varnish issue. Next step is to forgo using cookies.

    Thank you for detailed explanation =)

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Cookies and the plugin version 5.82+’ is closed to new replies.