Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter maxbatt

    (@maxbatt)

    Not accurate:

    1.) As other customers have verified, no, version 2.25 does not fix the cron tasks. Our site still has 58,000 cron tasks, despite installing the update. If HUGE-IT is honestly still confused here, they can easily get more info by searching Google and seeing other people who’ve said the same thing.

    2.) The information about Facebook is also not accurate. The only assistance your team offered via Facebook (after many time-consuming back-and-forths) was to request direct access to our company’s database, which is not a realistic request for obvious reasons.

    Luckily, we did finally receive instructions for a patch – which actually came from another customer (not Huge IT). We will try this patch after we’ve had time to make a back up. But again, Huge IT support did not help us at all here …

    • This reply was modified 7 years, 6 months ago by maxbatt.

    This is simply untrue – the issue is not resolved.

    Version 2.2.5 does stop the plugin from spamming the server, but it does not address the previous cron records that we cannot remove from our database. Over 60 thousand entries!

    We really need a tool (or method) for removing these records.

    Hello all,

    This thread is very much unresolved – can someone pease mark it as such. Every one of our sites has crashed do to this same issue – HUGE IT producing thousands of cron logs which eventually crashed our server.

    After spending a very large amount of time with our host we were able to recover the sites, however there are still thousand of “cron” logs in our databases that were not removed by following HUGE IT instructions (install updated plugin)

    This has already cost our business an enormous amount of time to fix – and it’s crucial that we get a fix from HUGE IT immediately.

    Failure by HUGE-IT to produce a fix here will force our team to look into legal options to recover lost time and money, along with the additional development resources we will need to clean our servers.

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