Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Problems with Google Pagespeed | Event Espresso - Staging Server
I have implemented Google Pagespeed on my WP site (hosted by GoDaddy). When I changed the DNS record for http://www.echenique.com from an A record with my site IP to a CNAME pointing to pagespeed.google.com I started getting the following errors on my site:
Warning: file_get_contents() [function.file-get-contents]: php_network_getaddresses: getaddrinfo failed: Name or service not known in /home/content/46/11433946/html/wp-content/plugins/espresso-requirements/espresso_requirements_check.php on line 106
Warning: file_get_contents(http://www.echenique.com/wp-content/themes/suffusion/style.css) [function.file-get-contents]: failed to open stream: php_network_getaddresses: getaddrinfo failed: Name or service not known in /home/content/46/11433946/html/wp-content/plugins/espresso-requirements/espresso_requirements_check.php on line 106
The simplest answer would be to turn off the Requirements plugin.
That wouldn’t solve the root issue which seems to be the fact that the url has changed, so while the plugin is looking for it in X place it is in fact in Y place. Though why PageSpeed would affect the admin I do not know.
Can you de-activate the Requirements plugin and see if there are any other issues occurring?
Thanks for the update Carlos, and glad that it’s working now.
Viewing 3 reply threads
The support post ‘Problems with Google Pagespeed’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.