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
Logo file and size issue | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Logo file and size issue

Logo file and size issue

Posted: September 27, 2013 at 7:34 am

Viewing 2 reply threads


B D

September 27, 2013 at 7:34 am

While my EE accepts jpeg files, it doesn’t accept png files. The error message is: “FPDF error: Alpha channel not supported:”, followed by the url of the png file.

And what is the exact size of the logo to be uploaded? The jpeg files that I have uploaded, in different sizes, show up pixelated.

Thank you in advance,

B D


Josh

September 27, 2013 at 3:17 pm

Hi there,

The key with getting a png image to load up in the invoice is to make sure it’s exported with no alpha channel when you save it from your image editor. If you later edit it in WP it will get an alpha channel though…

The invoice will accept a variety of logo sizes. Generally something around 100 pixels tall will work well. So for example a logo that’s around 250px wide to 300px wide by 100px tall could be used.


B D

October 1, 2013 at 2:16 pm

Thank you.
Viewing 2 reply threads

The support post ‘Logo file and size issue’ 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.

The original Forum description...

Status: closed

Updated by B D 11 years, 4 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server