Pages are incomplete or contain many garbage characters, regardless of content in the record. May be due to a missing or incorrectly loaded gem. This appears to affect both Print-to-PDF and reports in PDF format for those with Windows servers.
We'd be interested in testing a fix. Our IT admin hasn't had a chance to upgrade us to 2.5.0, but I was told it would happen soon.
Pull request updated with:
All external command output shows in log
-Fix now works with ArchivesSpace installed in a directory name with spaces
- we have a build with the PDF fix that is downloadable at https://drive.google.com/file/d/1Plau83HLlHS6YwwfVvy_f-_ZhfKHtgrG/view?usp=sharing (it's a big file, so your browser and Google Drive may give you some extra warnings). You will need to install this on a Windows machine – any windows desktop or laptop would be fine, or you could ask your system admin to try it out on the server where you use ArchivesSpace. If you need any help with this part, please let us know.
Once you have it installed, add some test (or real) data and then see if the staff side PDF runs and is legible. It's the same PDF as is produced on Linux and Mac servers, but just uses a slightly different process.
Sorry that I am just now responding to this, Christine.
I've sent the files and instructions along to our IT administrator, and I'll let you know when/if she gets it installed and if I'm able to run the reports.
Do we need to be upgraded to v.5.1 before we try to install this?
- thanks for testing! You do not need to upgrade since the version above is what has the fix. (Definitely don't do this with your production version of ArchivesSpace. If you're using an older database for your testing, just be sure to using the setup-database script to get it to a more current version.) Please just let us know how it goes.