Thread Starter
416BC
(@416bc)
I’ve uninstalled this plugin, please ignore this question, or answer it for others searching. Thank you.
That means the /wp-content/plugins/wp-post-to-pdf/tcpdf/cache/ directory is not writable. Please change its permission so that it can be writable by script. That will solve your issue.
Neerav, I get the same error but without the image file location.
Only looks like this:
“TCPDF ERROR: [Image] Unable to get image:”
I didn’t have this problem with this plugin before
UTF8 filenames (images) creates a TCPDF error as mentioned. This is a problem where wordpress saves images and stores the filename with utf8 but the server does not. This makes the function _parsejpeg($file) to fail in tcpdf.php
I’m actually getting this error in the admin, when I create or delete a post. The post is still created or deleted, but the error shows up systematically. The cache folder is writable. The PDFs download just fine.
ideas?
thnx!
-jennyb
So I’ve narrowed it down to images with a file path that leads to to wp-content/uploads. All images that are in the theme do not cause a conflict.
The weird thing is that the images in question aren’t even uploaded yet. And I’m experiencing this in the back-end. Changing permissions on the cache folder only changes how the error displays, with or without an image file path. I’ve also tried creating a conditional statement so that if the image is empty, the image doesn’t display at all, but that doesn’t seem to help.
Again, my PDFs were being generated just fine. But I had been working with an example CPT that was already compiled. We discovered this problem when going to create new posts. Obviously, deactivating the plugin every we create a post is not an option! 🙂
TLTL: did you come up with a fix for your encoding theory?
Am also looking into the possibility of some kind of hot linking problem…waiting on a host response…
thnx,
-jennyb
Ok, got it sorted. It didn’t like me having my <img> tags in the template when the images weren’t defined (even though it worked on some). So I put them directly into the variable and it resolved the error *whew*!
