jordan314

For now, in inc/fau_settings.php if you change both function fau_color_settings() and function fau_secondary_color_settings() to function __construct() it works

Got the same error. Both of those errors are in example files in the included library log4php. They’re not used by the plugin. I upgraded and it’s running fine. You can tell WPEngine to disregard those errors.

I also used the WPEngine compatibility checker. That file is an example file in an included library (log4php), the instant articles plugin doesn’t actually use it. So until they fix this, you can ignore that error.

They allowed me to do it with this code:

//allow orderby=menu_order
add_filter( 'rest_post_collection_params', 'my_prefix_add_rest_orderby_params', 10, 1 );

function my_prefix_add_rest_orderby_params( $params ) {
    $params['orderby']['enum'][] = 'menu_order';

    return $params;
}

Yeah, this plugin nuked my whole plugins page with a 500 error. I’d delete it for now. The error is an uncaught exception: “The user must be an administrator of the page in order to impersonate it.”

Hi,
I’m also seeing this, this can be fixed on line 111 of simply-instagram-functions.php by changing $data['data'][$i]['caption']['text'] to
htmlspecialchars($data['data'][$i]['caption']['text'], ENT_QUOTES)
just like it is on line 95

Thanks for this, I had the same problem

Ok I figured it out. It had nothing to do with wordpress. *sheepish grin*
I ran a phpinfo(); in wp-login.php and wasn’t seeing any of the REQUEST variables. I tried making my own POST php file and it wasn’t getting any of the posted variables anyway.
I tried deleting my .htaccess file and everything started working.
Because we upload large videos to the site, I had these two lines in my .htaccess file:
php_value upload_max_filesize “20MB”
php_value post_max_size “50MB”
This was so that we could upload files larger than the default 8 MB limit.
Turns out for some reason on the new server that this breaks PHP from getting and posting values to itself. Weird!
Thanks for your response vkaryl, it was a copy of the old database on the new server in domain root.

I upgraded to 2.0.1 and still have the same problem.