It’s working for me in v2.3.2, but I believe it was also working in 2.3.1 as well. However, PDF generation in the staff webapp is dependent on the resource producing valid EAD that gets piped to XSLT-FO stylesheet, so if you are having problems, it’s a good idea to export EAD first and try to validate the xml.
I know of some cases where mixed content in a resource note will generate invalid EAD. — Steve Majewski > On Apr 10, 2018, at 4:40 PM, Prestinary, Patricia > <pprestin...@exchange.fullerton.edu> wrote: > > Hello AS users group, > > I searched the tech support archives and haven’t found this issue posted yet. > > We have been unable to Export Finding Aids pdf’s since the last update > (v2.3.1) . The system generates a job and creates a pdf with some of the > finding aid data, but most of the pages are blank. > > Does the latest update fix this particular issue? I am hesitant to do any > additional updates until we can address this issue. > > Best, > Patricia > > Patricia Prestinary > Special Collections Librarian & Archivist > CSU, Fullerton | Pollak Library | PLS-352 > University Archives & Special Collections > (657) 278-4751 > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > <mailto:Archivesspace_Users_Group@lyralists.lyrasis.org> > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>
Description: S/MIME cryptographic signature
_______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group