Open raxx0r opened 8 years ago
I am having the same problem. Kind of a deal breaker for me.
This issue is known and logged in resume-cli. After two years of paying I had to shutdown that section of the API and haven't had the time to implement a non service version of the pdf export.
In the interim I should update the docs/homepage to reflect that PDF conversion doesn't work.
There should be services out there though that you can use for free to convert your html output to pdf.
Ah makes sense. Didn't realize it was using a pay service.
Thanks for letting me know, @thomasdavis
This is caused by the following code: https://github.com/jsonresume/registry-server/blob/master/server.js#L77. Currently, the pdf encoding is handled by pdfcrowd
, an freemium online PDF converter. Here are some alternatives:
There are a lot of html to pdf converters out there, I personally tried 18 of them and the most accurate was wkhtmltopdf. It still has a lot of issues, but it looks like the most popular tool out there.
I'd recommend disabling the pdf feature from the cli and providing help text instead of the following misleading message:
ERROR: No API conversion tokens available
Also note that browser's print to pdf functionalities could be used instead and everybody can do this without the need of yet another cli tool, it's not cool, but it works ™ ;)
I'm using the resume-cli to generate a pdf version of my resume, but the generated file is corrupt when I try to open it.
As far as I can tell the pdf conversion logic is located on the registry server, with an endpoint for the cli to connect to, so the error is likely on the registry server.
Navigating to http://registry.jsonresume.org/thomasdavis.pdf is responding with "ERROR: No API conversion tokens available", and not with the actual pdf. Could it have something to do with pdfcrowd? Perhaps a missing or invalid API key/token, the error message seem to suggestion something in that manner.