WPEngine plugin

  • fgrubercpa@yahoo.com

    (@fgrubercpayahoocom)


    10 years, 7 months ago

    I switched FROM WPEngine to another host, and I still have a lot of WPEngine junk around – for example, they have a separate Link on the DashBoard, There is a WP Engine System Plugin that is listed under the Must-Use plugin category. Also, when I am editing the Menu now, the top 1/3 rd of the page fills with:
    __________________________________________________________
    Warning: fsockopen() [function.fsockopen]: php_network_getaddresses: getaddrinfo failed: Name or service not known in /home/content/57/11389357/html/wp-content/mu-plugins/wpengine-common/plugin.php on line 1898

    Warning: fsockopen() [function.fsockopen]: unable to connect to lbmaster:9002 (php_network_getaddresses: getaddrinfo failed: Name or service not known) in /home/content/57/11389357/html/wp-content/mu-plugins/wpengine-common/plugin.php on line 1898

    Warning: fsockopen() [function.fsockopen]: php_network_getaddresses: getaddrinfo failed: Name or service not known in /home/content/57/11389357/html/wp-content/mu-plugins/wpengine-common/plugin.php on line 1898

    Warning: fsockopen() [function.fsockopen]: unable to connect to lbmaster:9002 (php_network_getaddresses: getaddrinfo failed: Name or service not known) in /home/content/57/11389357/html/wp-content/mu-plugins/wpengine-common/plugin.php on line 1898

    Warning: fsockopen() [function.fsockopen]: php_network_getaddresses: getaddrinfo failed: Name or service not known in /home/content/57/11389357/html/wp-content/mu-plugins/wpengine-common/plugin.php on line 1898

    Warning: fsockopen() [function.fsockopen]: unable to connect to lbmaster:9002 (php_network_getaddresses: getaddrinfo failed: Name or service not known) in /home/content/57/11389357/html/wp-content/mu-plugins/wpengine-common/plugin.php on line 1898
    ____________________________________________________________________

    Does anyone have some suggestions? I just want to make sure that my site isn’t somehow proprietarily tied to WPEngine, and it’s going to blow up as soon as my annual hosting that I paid for with them expires.
    thanks
    frank

Viewing 4 replies - 1 through 4 (of 4 total)
  • Jason Cosper

    (@boogah)

    10 years, 7 months ago

    You just have to get rid of the /wpengine-common/ directory inside of /wp-content/mu-plugins/. That’s where the menu item and everything else comes from.

    Hope this helps!

    Thread Starter fgrubercpa@yahoo.com

    (@fgrubercpayahoocom)

    10 years, 7 months ago

    I tried that and my site disappeared completely. The only thing that appeared on the screen was:
    ________________________________________________________
    _Warning: require_once(/home/content/57/11389357/html/wp-content/mu-plugins/wpengine-common/plugin.php) [function.require-once]: failed to open stream: No such file or directory in /home/content/57/11389357/html/wp-content/mu-plugins/mu-plugin.php on line 25

    Fatal error: require_once() [function.require]: Failed opening required ‘/home/content/57/11389357/html/wp-content/mu-plugins/wpengine-common/plugin.php’ (include_path=’.:/usr/local/php5_3/lib/php’) in /home/content/57/11389357/html/wp-content/mu-plugins/mu-plugin.php on line 25
    _____________________________________________

    Restoring the folder restored my site. Any ideas?
    thx
    f

    doeppel

    (@doeppel)

    10 years, 7 months ago

    I’m having the same issue. I’ve asked wpengine to tell me how to remove them. I’ll post if they respond.

    imagistic

    (@imagistic)

    10 years, 1 month ago

    OMG. Here’s hoping this post will save others hours as well.

    Yes, you must remove the wp-engine code from your mu-plugins directory. AS WELL – you must remove the mu-plugins.php file itself. This file is not something required by WordPress and in fact contains the calls to the wp-engine code. (Technically, you could just remove the mu-plugins.php file and you’ll be fine since the mu-plugins structure is such that WordPress doesn’t read in sub-directories like it does in plugins.)

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