Skip to Content
Menu
This question has been flagged
2 Replies
1767 Views

Hi,
after pressing 'Print' Google Chrome presents me a 'Save as Dialog' with 'download' as the filename to use!?
Discarding this dialog and pressing 'Print' again, gives me an automatic download with the correct filename as expected.

A couple of days before it was just the automatic download.
I've no clue what I have changed or what causes that strange behavior.

Firefox just downloads the PDF file as usual after the first click on 'Print'.

Any Guess what I need to fix here?

Cheers
Stephan

Avatar
Discard
Best Answer

Hi Stephan, 
This is a browse configuration and not a server side problem. 
I would say that  google added it for security reasons. 

but if you insist on disabling this feature, go to chrome settings then In Downlaods side, disable "Always ask where to save the files".

Upvote if this helps.

Regards.

Avatar
Discard
Author Best Answer

...
This is a browse configuration and not a server side problem. 
I would say that  google added it for security reasons. 

but if you insist on disabling this feature, go to chrome settings then In Downlaods side, disable "Always ask where to save the files".
...

Thx for the hint, but this option is already disabled.
And if I enable it Chrome asks me the first time where to save 'download' and after clicking print the second time it asks where to save 'Quotation - A19026.pdf'.
So where does it gets the suggested filename 'download' from and why is it changed to 'Quotation - A19026.pdf' at the second click.
And that behavior continues with all odd / even succeeding clicks.

1st Click -> download
2nd Click -> Quotation - A19026.pdf
3rd Click -> download
4th Click -> Quotation - A19026.pdf
5the Click -> download
...

If I try to save the file 'download' as a pdf file it is corrupted ('server error').
This behavior started to appear about 3 weeks ago with no change on the odoo or browser side that I have incurred as a developer.
Odoo runs on my synology and there has been an updates around that time from synology.
Windows 10 got some updates as well around that time.
But reading the releases notes did not surface any hints to solve that issue.

Any other guesses?
Anybody else out there with the same issue?
Anybody able to reproduce that behavior?

Cheers
Stephan

Avatar
Discard