• Krissy

    (@krissy)


    I read the huge article written Andrew, I just want to confirm something:

    Where exactly am I adding the following term:

    # Disables all core updates:
    define( 'WP_AUTO_UPDATE_CORE', false );

    wp-config?

    My host has disabled just about every blog running on 3.7.1 for me claiming that I’m violating their MySQL Usage TOS. I know it couldn’t have been ‘hack’ related as I make it a point to keep everything as secure as possible, the only major change was upgrading from 3.7 to 3.7.1.

    Either way I have 10 years of blog archives (on multiple domains) that I can no longer access… and it’s 100% because of this recent WP update.

    So to confirm, is it going in wp-config?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Krishna

    (@1nexus)

    wp-config?

    Yes.

    For other problems contact your host as it seems they are overenthusiastic about blocking everything for security.

    Thread Starter Krissy

    (@krissy)

    Thank you Krishna.

    I updated my wp-config file.

    I’ve already contacted my host, but I’m sure anyone hosted with HostGator could easily agree they’re completely useless. They put a block on my .htaccess file and I’m not even allowed to override it myself or it will result in “Corrective Action”. So until someone gets off their booty and decides to answer one of my numerous ticket responses, I won’t even know if disabling the updates will work to avoid this issue from coming back up.

    Krishna

    (@1nexus)

    I’ve already contacted my host, but I’m sure anyone hosted with HostGator could easily agree they’re completely useless.

    I don’t think so as I have seen in recent times that a lot of problems reported are related to newly implemented server configurations and it is not limited to one host. Some of them neither inform their users nor place proper instructions at their sites so that users can easily locate them and follow instructions to solve problems.

    Thread Starter Krissy

    (@krissy)

    While I agree with your statement, I’m also dealing with on-going non-stop problems with them over the course of the past three months. I honestly wasn’t too surprised that they found yet another reason to shut something down. So I’ve been scrambling to figure out how to keep things up until I can transfer away from them completely.

    Either way, I do think for all of the useless emails that hosts randomly send to customers, something like this (when they supposedly are up to date on technology) should have been noted since the 3.7.1 launch. If HG, or any host for that matter, was going to be unable to keep up with the new WP configuration, they should have informed users otherwise, not just shut down every site they host that’s using 3.7.1 claiming it’s a MySQL/TOS violation.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Disabling auto updates’ is closed to new replies.