It seems that since the outage and upgrade, it is no longer possible to print out an entire thread?
I had been doing this for the Iron ChIF working groups in order to save them as PDFs for offline reference. Now a PDF is created, but only a handful of posts appear (whichever were most recently loaded) – the rest of the docuemnt is only blank pages.
Is there some other way to print entire threads?
Are you using ctrl + p to print? It seems to work for me.
Ctrl+P seems to do the same thing as the normal print command from the dropdown menu, which is what I was using before. It may just be a browser/version compatibility problem affecting me.
I did discover that adding “/print” to the end of the URL for a topic allows saving the whole thread, so my immediate problem is solved. Thanks for confirming the way that it’s supposed to be working, Dannii – it looks like my issue and not a site issue.
This is what I get on MacOS Safari by closing the sidebar (so it doesn’t print) and choosing File>Print>[to PDF]
Printing entire threads - Site Feedback - The Interactive Fiction Community Forum.pdf (88.7 KB)
HanonO, my PDF output would be similar for a short thread like this one. The issue of blank pages only happens when the thread is long, as in tens of posts or more. In that case only some of the actual posts are found in the PDF, though the document includes blank pages where the rest of the posts would be expected.
Previously, scrolling through a long post would load all posts into the browser, making it possible to print the whole thread. It now appears that only a subset of posts (capped by number of posts?) remain loaded while scrolling.
If you are affected by the same issue, it should show up for threads that have 50+ posts.
Ah, gotcha. That is likely because as you scroll, Discourse is live-loading the content - basically is like a curling team ahead of your position loading the thread for your to read it.
Adding /print to the URL is the way to go. Per Discourse Meta: