Wkhtmltopdf: got errors when upgrading from 0.12.5 to 0.12.6

[nixilb]

0.12.5:

E:DropboxNiSTomcat wwwwebappswwwnicbook>wkhtmltopdf --outline-depth 3 ECG-SCA-book_Cover.html ECG-SCA-book.pdf 1>ECG-SCA-book.log
Loading pages (1/6)
Counting pages (2/6)
Resolving links (4/6)
Loading headers and footers (5/6)
Printing pages (6/6)
Done

0.12.6

E:DropboxNiSTomcat wwwwebappswwwnicbook>wkhtmltopdf --outline-depth 3 ECG-SCA-book_Cover.html ECG-SCA-book.pdf
Loading pages (1/6)
Warning: Blocked access to file E:/Dropbox/NiS/Tomcat www/webapps/www/nicbook/materialize/css/materialize.min.css
Warning: Blocked access to file E:/Dropbox/NiS/Tomcat www/webapps/www/nicbook/style-mdcss.css
Warning: Blocked access to file E:/Dropbox/NiS/Tomcat www/webapps/www/nicbook/Images/ECGno1.jpg
Error: Failed to load about:blank, with network status code 301 and http status code 0 - Protocol "about" is unknown
Error: Failed to load about:blank, with network status code 301 and http status code 0 - Protocol "about" is unknown
Error: Failed to load about:blank, with network status code 301 and http status code 0 - Protocol "about" is unknown
Counting pages (2/6)
Resolving links (4/6)
Loading headers and footers (5/6)
Printing pages (6/6)
Done
Exit with code 1 due to network error: ProtocolUnknownError

[PhilterPaper]

Perhaps 0.12.6 turned off local file access (at least, on some platforms) by default? Try --enable-local-file-access and see if that works.

[nixilb]

This fixes the problem. Thanks for the turnaround!
Well this is a bug. default should remain the same.

[PerlTester]

Its not a bug, it was a well documented breaking change to fix a security hole.

P.