• Resolved abruski17

    (@abruski17)


    That’s the error message I keep getting. I had some back and forth with support that never really went anywhere. Hoping to have better luck here. Each of the questions posed to me by the plugin author were forwarded to my host and answered sufficiently. We have them whitelisted and ping tests have already proven successful.

    If CleanTalk wants to actually explain why their stuff isn’t working, we’re all ears.

    • This topic was modified 4 years, 7 months ago by abruski17.
Viewing 15 replies - 46 through 60 (of 60 total)
  • Plugin Author alexandergull

    (@alexandergull)

    It is weird. We will check this within 2-3 workdays.
    Be well,

    Thread Starter abruski17

    (@abruski17)

    Guys – we’re getting close to two months here and we’re about five days out from your last action. You’ve sent me an email asking me to pay for service. Do you just want to say the plugin doesn’t work?

    Plugin Support amagsumov

    (@amagsumov)

    Hello,

    We apologize for the delay but we need 2 more days to investigate the issue.

    Thank you.

    Plugin Support sergecleantalk

    (@sergecleantalk)

    Hello,

    Does the problem still persist? Could you try to disable Use WordPress HTTP API option? (WordPress Dashboard -> Settings -> Antispam by Cleantalk -> Advanced settings).

    If nothing helped, could you try to uninstall and delete the plugin with “Complete deactivation” option? Then install the latest version from WordPress catalog.

    1. Enter to the Antispam by Cleantalk plugin settings. (WordPress Dashboard -> Settings -> Antispam by Cleantalk -> Advanced settings)
    2. Check “Complete deactivation” and save changes.
    4. Go to WordPress Administrator Panel —> Plugins.
    5. Find the plugin “Spam Protection by CleanTalk” —> Deactivate.
    6. Delete the plugin
    7. Install a new plugin from WordPress catalog.

    Write to us about the results.

    Thread Starter abruski17

    (@abruski17)

    Okay guys. A few things that are not okay here. First, you marked this as resolved and it is anything but resolved. Change that or there will be issues.

    Second, you just gave us instructions that we have completed from past iterations of trying to fix your plugin that obviously hasn’t been tested and does not work.

    We are nearing two months in this debacle. Address these issues within the hour please.

    Plugin Support sergecleantalk

    (@sergecleantalk)

    Hello,

    Sorry for the misunderstanding. I’ve changed status to “not resolved”.

    As for instructions. We improve our code every day. So we always ask to try the latest version to check if the problem persists. “Complete deactivation” option clears all tails from old versions.

    Did you try to disable Use WordPress HTTP API option? Did you try the latest version?

    Thread Starter abruski17

    (@abruski17)

    Guys, you need to send email as well the WP mailing system doesn’t always send mail when you respond here.

    Second, you keep giving me the same troubleshooting options over and over again.

    The answer is yes, we’ve tried everything you’ve recommended and in some cases, multiple times.

    Do you have any idea why your product does not work?

    Plugin Support SergeM

    (@serge00)

    Hello, @abruski17.

    Unfortunately, we can not fix the issue from our side. Could you give us temporary access to your website backend?

    I’ve also sent an email to you.

    Thread Starter abruski17

    (@abruski17)

    You guys asked for unprecedented administrator access to our system. We obliged. You did nothing with it and then asked afterward for two days to look at the system. We scheduled a time for you to get that access and then you didn’t show up.

    Your company is a joke and this plugin has serious issues.

    Plugin Support SergeM

    (@serge00)

    Hello, @abruski17.

    Why unprecedented? For example, just today two of our clients gave us temporary admin access for 2 days. It’s a common practice.

    4 hours of access is not enough to fix the issue. We already had about 15 tasks to do and it’s not fair to prioritize a client just because they gave us a strict time window.

    Moreover, we haven’t had such problem as you have. It’s definitely a specific problem and we can not fix it from our side easily.

    Thread Starter abruski17

    (@abruski17)

    Serge. You have had over two months to fix this issue.

    You missed your own scheduled appointment to fix the issue.

    Get a clue.

    It is not the job of your users to go through incoherent troubleshooting procedures.

    Anybody reading this thread can see for themselves that you have a security plugin that is being held together with a paperclip and bubble gum and that your approach to service is atrocious. And I’m more than willing to share my experience with anybody that is thinking about turning to this plugin.

    The last thing you want to do is give these people access to the back-end of your website when they are clearly incompetent and rather than looking in the mirror to fix their own issues they point fingers.

    What will they do to your information when they’re in there?

    Plugin Support SergeM

    (@serge00)

    Your feedback is taken into account.

    Have a great week.

    Thread Starter abruski17

    (@abruski17)

    I highly doubt it.

    Hello,

    We’ve answered you via email. Please, check.

    Best regards.

    Plugin Author Denis

    (@shagimuratov)

    @abruski17,

    We haven’t heard back from you in a while, so I’m going to mark this thread as “resolved” – if you have any further questions, you can start a new thread.

Viewing 15 replies - 46 through 60 (of 60 total)
  • The topic ‘CONNECTION_ERROR : “cURL error 28: Operation timed out after 10001 milliseconds’ is closed to new replies.