I don’t understand you.
I am using since years Centos - in all Versions 7, 8 , 8-stream
I’ve told you x times that WKHTMLTOPDF 0.12.4 is outdated.
Yes you create under _lib/prod/third/wkhtmltopdf a directory named centos8 with the actual version WKHTMLTOPDF 0.12.6.
Wonderful but scriptcase does not recognize centos.
WHY don’t you switch to the current version 0.12.6 in …/linux-amd64? - and the problem is solved.
WHY???
Hola Sr. Gomi, quería saber si tiene una solución a este ERROR (WKHTMLTOPDF) de scriptcase, agradezco me lo indique si tiene la solución. mariocodina03@gmail.com
Hi Mr. Gomi, I wanted to know if you have a solution to this scriptcase ERROR (WKHTMLTOPDF), thank you for letting me know if you have the solution. mariocodina03@gmail.com
Does it work fine in Ubuntu? Or is this just a Centos issue?
Hello mariocodina.
The only way is to change the version in _lib/prod/third/wkhtmltopdf.
Or you change the version in scriptcase. But every Update changes the version…
Don’t know - i am using always centos.
i also had to manually install it, from the internet find the right version.
anyway, what is the path to update production environment ?
i miss this option in the deployment dialog, only by the initial deployment you can upload the libraries.
you update sc on dev but it does not update the production, libraries etc
Hello Maxim,
As i wrote before…
tld/_lib/prod/third/wkhtmltopdf/centos8/ ← 0.12.6
cp wkhtmltopdf-amd64 …/linux-amd64/wkhtmltopdf-amd64
In SCRIPTCASE you find it at …/scriptcase/prod/third/wkhtmltopdf/…
The correct version is available. But scriptcase can not recognize centos 
Hi gomi,
Based on what u say, looks like even if you deploy the correct version, it is still a problem.
So pdf’s just do not work with scriptcase applications on centos i.e there is no workaround?
-Ken
Hi Ken,
Because of my complaint scriptcase has installed the Centos version 0.12.6. But I don’t know why they don’t use 0.12.6. in general but still the outdated 0.12.4.
There was an update since scriptcase recognized Centos. But now again not.
The workaround I have already described - copy
I have no idea why netmake does not finally update the version for linux-amd64…
I wonder why SC puts all this third party software , which is not SC responsibility, wkhtmltopdf is not even used in SC i believe , pdf app type is hooked up in another pdf library.
you find a right version and plug it in.
I guess it is time SC cleans up the installation,
it is so huge , it is unbearable . also the update of the production env should be addressed,
how come there is no option to update it from the deployment center after the initial deployment
there is production environment , it is another place SC may consider to add upgrades such that a right version of the production libraries is pulled from the SC server.
Of course wkhtmltopdf is used in SC. How else do you think pdf are created.
It’s not a big problem either. You just don’t get it done.
Yes, the update routines are somewhat deficient.
I see a number other pdf libraries in prod/third such as qpdf, tcpdf
I make only custom pdf from html , therefore i use wkhtmltopdf, this requires a lot of customization
for headers, footers, TOC, quality.
but i think the standard export to pdf uses something much simpler
i was surprised that wkhtmltopdf is like the half of all PROD library
it seems that the best practice to update PROD is to go Typical deployment ,
generate zip with option Include PROD libraries enabled, and copy PROD folder from the ZIP to your production environment.
You might delete unused or customized third party libraries from ZIP before making an upload to your production. (such as wkhtmltopdf, otherwise SC files will overwrite your customizations).
#thirdparty #applications:prod-environment #deployment #wkhtmltopdf
by the way , I am using version 0.12.6 of wkhtmltopdf. previous versions had bugs.
you need wkhtmltopdf-amd64 for CENTOS
(centos is discontinued from 2022, you need to step over to Alamalinux. )
we run now dev and few production on #almalinux on Azure VM , works good except some #Azure limitations that are already solved.
@maximnl
I do not quite understand what you want.
I have previously written what is necessary.
You just change Centos8 to stream. It is the same and binary compatible with RHEL.
We’ll see how it goes with Alma.
no big deal, i was wondering if the standard export of scriptcase to pdf and pdf app are using wkhtmltopdf from the third parties lib at all. Cause if so , which functionality is using it and why they are using an old buggy version?
this was my point, we do not know what PDF library is here used for?
and if it is WKHTMLTOPDF , it requires execute rights on the hosting,
as it is just executable file and not a php library.
many shared hostings won’t give you that
As we can see, Scriptcase doesn’t even respond to this.
Now the whole creation doesn’t work anymore.
Links are written into the html file that do not exist.
Everything tested.
Perhaps it would be the time where we should ask scriptcase for a refund of the license costs.
Their support is really poor even paid support.
Many third party tools are outdated.
Not only WKHTMTOPDF.
Tcpdf is outdated , as well as AdoDB on which database access depends is far behind latest stable version.
