Welcome to our Support Portal › Forums › WooCommerce Personalized Product Options Manager (PPOM) › File upload download problem
February 8, 2021 at 8:13 pm #22283nunameParticipant
Hi there, I have a PPOM File upload field in a Woocommerce Product. File types jpg and pdf are enabled.
jpg files upload and display as large thumbnails, and pdf files upload and display as generic documents.
In the back end, once the product has been purchased, the same thumbnails appear with a download button. The jpg’s download button results in the jpg being opened in that tab, not downloaded. The pdf’s download button results in a 406 error.
The most important query I have is how to download the pdf. What do you think is blocking it?
I’d also like to reduce the size of the thumbnails, which appear all over the place and look odd.
Many thanks.February 9, 2021 at 1:24 pm #22321nmediaKeymaster
it seems that your server is not configured to accept PDF files, please contact your hosting company with the PDF download link and they will assist you or fix it.
And you can use CSS to reduce the thumb size.February 28, 2021 at 10:12 am #22852nunameParticipant
I have investigated a bit more. It seems that the formation of the download path is triggering firewalls. When I first reported this, I was using Sucuri and no other firewall, and the blockage was triggered for pdfs but not jpgs. Currently I am using Cloudflare WAF proxy and 7G Firewall on the server itself. The problem does not trigger Cloudflare, but it does trigger 7G.
The request is apparently breaking rule 24 of the bad_request ruleset. It looks like it is picking up on the word “confirmed” in the path thinking it is “conf”.
So while I can fix this for myself with a rule customisation, I’d suggest you rename /confirmed/ if you do not want to cause problems for other people using firewalls.
I also have another problem with the thumbnails, which is that they increase Spamassassin score for Woocommerce transactional emails if they contain images, so it would be much better if we could just have a download link instead.
Specifically, when attaching non-image files, the thumbnail file is just named “file.png”, which might be what is triggering HTML_SHORT_LINK_IMG_1. But generally, it would be better for transactional emails to have no images, in order to have maximum deliverability.
Thank you.March 1, 2021 at 5:33 am #22859nmediaKeymaster
Thanks for this valuable information, we will try to control this via our updated features.
- You must be logged in to reply to this topic.