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
Strang warning on ticket | Event Espresso - Staging Server

Support

Home › Forums › Ticketing › Strang warning on ticket

Strang warning on ticket

Posted: November 23, 2012 at 10:39 am

Viewing 3 reply threads


Chris

November 23, 2012 at 10:39 am

We are using a customized ticket which is located at
/wp-content/uploads/espresso/tickets/templates/index.php

After upgrading to 3.1.28.5.P the following message appears on top of every ticket:

Warning: getimagesize() [function.getimagesize]: php_network_getaddresses: getaddrinfo failed: Name or service not known in /home/youcan1/public_html/you-can-fight.com/wp-content/plugins/espresso-ticketing/functions.php on line 192

Warning: getimagesize(http://you-can-fight.com/wp-content/uploads/2012/08/YOU-CAN-FIGHT1.jpeg) [function.getimagesize]: failed to open stream: php_network_getaddresses: getaddrinfo failed: Name or service not known in /home/youcan1/public_html/you-can-fight.com/wp-content/plugins/espresso-ticketing/functions.php on line 192

Rest of ticket is displayed just fine.

How can we get rid of that ugly ingredient?


Josh

November 23, 2012 at 2:18 pm

Hi Chris,

This may be a file permissions issue. The image there at:
http://you-can-fight.com/wp-content/uploads/2012/08/YOU-CAN-FIGHT1.jpeg
certainly does exist, as I can load it up in my browser. The PHP script is having some trouble accessing the image file, and that’s what’s indicated in the error.

If the file permissions are okay, it may be that the server configuration has changed.

One thing that I would try would be updating the logo image.


Chris

November 23, 2012 at 4:20 pm

I updated the image. Nothing changed.
file permission is 644.
We didn’t change anything on the server.


Chris Reynolds

  • Support Staff

    •

November 27, 2012 at 4:23 pm

2 things you can try:

  1. Change the filename of the image from YOU-CAN-FIGHT1.jpeg to YOU-CAN-FIGHT1.jpg.
  2. Set the permissions on the file to 755 (I don’t really expect this to make a difference as 644 should be sufficient, but different servers react to permissions differently).

It may also be worth uploading the file manually via FTP. The theory behind that is that since the image exists in your /uploads directory, I’m assuming you used the WordPress media uploader to upload it to the server. This makes the webserver the owner of that file. It may make a difference if the owner was different, e.g. your FTP user.
Viewing 3 reply threads

The support post ‘Strang warning on ticket’ 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.

Status: closed

Updated by Chris Reynolds 12 years, 1 month ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server