Check image file type #
The following are the compatible file types, if all server requirements are met:
- JPEG
- JPG
- PNG
- WebP
A good and quick test involves changing the logo’s source to a different file that has a different file type (or file extension), in order to see if your server lacks support for a particular file type.
Temporarily disable any CDN #
You may be using a CDN (content delivery network) in order to have access to images. There are various ways to temporarily disable this, depending on your website host. Please contact them for assistance.
Alternatively, you may give this code snippet a try.
add_filter( 'wpo_wcpdf_use_path', '__return_false' );
If you haven’t worked with code snippets (actions/filters) or functions.php before, read this guide: How to use code snippets.
We also have a blog post here that you may find helpful about adding custom code to your site.
Check server requirements #
Path: WooCommerce > PDF Invoices > Advanced > Status > System Configuration.
The table that appears indicates red items as missing required items from your server, for proper functioning of our plugin.
Check our article for more: All server requirements
Deactivate plugins, code snippets and custom integrations #
Temporarily deactivate any plugins, code snippets that target images or any custom integrations in order to see if there is a difference.
Translation plugins like WPML, Polylang, TranslatePress, could be a possible culprit, as we have media translation as a compatible feature. Temporarily deactivating them in order to observe the logo/image is a test that should be performed.
Check woocommerce error logs #
Path: WooCommerce >Status > Logs.
Check the WooCommerce logs to see if there are errors with the wpo-wcpdf or fatal-errors that may mention any useful information.
Test without cache #
Disable any caching plugin or plugin that may implement cache for a feature, in order to eliminate caching as the culprit. Some of these plugins may contain an option to disable cache.
After successfully disabling or deleting the cache, other troubleshooting steps should be repeated.
