Web2pdf add-on conflicts with my Adobe CS3 PDF printer.
I installed the web2pdf add-on because I thought it was an idea with merit, particularly since creating PDFs without Adobe CS graphics software was an annoyance I routinely encounter (since Adobe restricts the number of devices that may be loaded with a given Adobe Creative Suite "purchase"). I downloaded the web2pdf add-on, and it would not create a PDF, instead presenting me with an error message.
"Adobe PDF Properties" tells me my PDF printer is working properly, but when I attempt to print a PDF, I get a pop-up window that informs me of an "error printing PDF." If I try again, the popup window tells me that my "Adobe PDF" is in "error status" until I remove the queued document.
I never had this problem before I downloaded print 2pdf, and now that I've uninstalled it, the problem remains.
How do I regain my Adobe PDF function? Any steps I can take to set my system back to its original operational state? Would reloading my Adobe CS3 solve the problem? Is there anything I should/can do before I resort to that (a very timely process)?
All Replies (3)
Have you uninstalled the web2pdf add-on?
https://support.mozilla.org/en-US/kb/disable-or-remove-add-ons
HI, edmeister. Thanks for your response.
Yes, I have uninstalled web2pdf. However, when I attempt to print a PDF, "Adobe PDF Properties" tells me my PDF printer is working properly, but when I attempt to print a PDF, I still get a pop-up window that informs me of an "error printing PDF." If I try again, the popup window tells me that my "Adobe PDF" is in "error status" until I remove the queued document.
I never had this problem before I downloaded print 2pdf, and now that I've uninstalled it, the problem remains.
Just tried to PDF again, with same result. Seems the only way I can create a PDF is to copy and paste onto another browser, unless I want to reinstall web2pdf which seems to be a pretty unsavory way to push an add-on.
I can't believe I'm the only person in the online community to experience this problem. Doesn't Mozilla care about this glitch?
More importantly, doesn't Mozilla care about user trust?
Modified