Is it possible to target the print version of a specific topic with CSS? For example, if I have one topic that is a manual (ie. not just the first post but the entire topic is the manual, with different posts containing different sections of the manual), I’d like to hide post number, user names and post date (and possibly a few other things) from the print layout.
A workaround seems to be that I put that topic into its own category and then target the category, but maybe there is a better way?
When printing it would also be nice if the entire topic, rather than just the first 20 posts, we loaded.
What’s the use case for printing a 100 reply topic, exactly? Or a 1000 reply topic? Surely there has to be a limit.
I’m working with researchers who want forum data for offline analysis. One forum that I scraped recently included a print option which gave whole threads rather than splitting into multiple pages,which made the job much easier. In the particular instance it was scraping a public forum, but it’s often useful for those who want to analyze their own forum data.
I agree that some limit of posts would make sense (1000 perhaps?)
Why are you scraping when you can use the JSON API?
On the site I scraped recently there was no api.
I’ve written a discourse scraper before, but it’s nice to be able to easily reproduce formatting stuff that a scraper would need to handle from scratch.
I helped work on a print.css quite a while ago. By eliminating useless navigation, post and topic actions, reducing print size, margins and padding, etc. we were able to get the twenty posts down to around, IIRC, 4-5-ish print pages. Dependent on post content of course.
Perhaps it isn’t as expensive to run off reams as I think it would be. But in any case it would be extremely unlikely that I would want an entire discussion. And if I did I would want it bad enough that I would be willing to print the paginated posts in a repeated process.
We do this already! Just press CTRL+P.
And I’m pretty sure the print view is limited to exactly 1000 posts already…
Oh. I think I remember that now that you say it! Sorry about that.
Oh, and this is what I don’t like about suggested topics. I didn’t realize that was restarting a topic that was half a year old.
Maybe a stupid question, but how to implement this ?
When I put it in theme CSS I get:
ember and .ember-view error