Support

March 6, 2015 at 2:51 am

Hi Joanne Tjia,

Those warnings usually mean your server has fopen disabled, specifically allow_url_fopen() which is used by the DOMPDF library that Event Espresso uses.

I would recommend issuing a ticket with your host provide to have them enable it.

March 9, 2015 at 7:37 am

Hi Joanne,

Just to note, disabling WP_DEBUG on your site will also remove those errors from view, however that won’t fix the issue they are reporting which basically means your invoices/receipts will not have a logo displayed within (or any images for that matter)

March 10, 2015 at 8:24 am

I did a little more investigating into those errors and it appears to be a DNS problem.

I found this:

http://stackoverflow.com/questions/6275535/php-error-php-network-getaddresses-getaddrinfo-failed-while-getting-informat

and this:

http://stackoverflow.com/questions/2880563/file-function-file-php-network-getaddresses-getaddrinfo-failed-temporary

I would once again recommend contacting your host to investigate this (you can send them the above links and screentshots you provided). Apache may just need to be restarted but they should know more on that than I.

One other thing to note is that if you have:

define(‘WP_DEBUG’, false);

and the errors are still showing on your site it means that display_errors is enabled on the server, this is great for debugging (like now as you can see those errors) but not so great for live.

Under that line I would add this:

@ini_set( 'display_errors', 0 );

To stop your site displaying the errors.

If you want to view the errors on a live site, we recommend swapping the above two lines out for something like this:

define( 'WP_DEBUG', true ); // Or false
if ( WP_DEBUG ) {
    define( 'WP_DEBUG_LOG', true );
    define( 'WP_DEBUG_DISPLAY', false );
    @ini_set( 'display_errors', 0 );
}

When WP_Debug is enabled it will store the errors in a debug.log file in /wp-content/