Hallo Tom
Thanks for reporting that, and for commenting on the documentation page too. It's very odd. I've just tested the PDF space export in Confluence 5.0-m9 and in Confluence 4.3.3, and it does not include the blog posts in either of those. Perhaps Confluence 4.3.1 is special!
Cheers, Sarah

A very, very nice "add" would be the ability to PDF export a range of blog posts by date.

We're an Atlassian partner and this is a recurring request from our clients. Project teams often want to provide "News Recaps" that are more "curated" than simple Watch updates, or to disseminate content to external audiences. The most common use case is to PDF export "Last week's news", or within a specified date range.

Exporting Blog posts via search filter and/or label would be extra special. (Please Santa! I've been very good this year!)

Thanks for making this into the Sprint!

I am doing a backup of all spaces as PDFs (as we want to cancel the license of a Confluence instance) but many useful resources are blog content!

It's disappointing, really.

Let me agree on premise but disagree on conclusion.

If you think that "Atlassian's business model is to charge a small licensing fees to a large number of customers", which sounds absolutely feasible to me than they should not care why I need this feature. The only thing the should care is how many customers need this feature i.e. how many customers they can loose (the level of frustration) and how many new customers they can get (the competitive advantage). Given this premise the only right thing to do to make this feature come true is letting Atlassian know that I do need it and hoping that all others do the same.

Anyway I believe it becomes kind of off-topic.

To sum it up I would really appreciate any feature that would allow me sharing content of the blog with those who do not have rights to access Jira/Confluence.
Thank you.

You're comments aren't offending me, they're just not serving any purpose. My point was that you're not adding anything more to the detail of this issue...you're just complaining.

The following part of your latest comment is hinting at something: "In a big company with all those restrictions and securities...". There is obviously something specific about your use-case that makes this a bigger problem for your organization than it may be for others. Why not spend a few minutes describing that in a clear and concise way, so that Atlassian can possibly use the information to re-evaluate the priority of this request?

Something that all of us need to remember is that Atlassian's business model is to charge a small licensing fees to a large number of customers, which means that any one customer (or possibly any 5) expressing "unhappiness" (i.e. without real use-case context) is unlikely to have much impact on their prioritization. If you really want Atlassian to address a request, they have to understand the requirements and, ideally, how the requirements might affect a larger set of customers.

This workaround is definitely worse than suggested by Jim (above). I would never send out anything such badly looking.

I am sorry if my comment offended you.
Still it is weird to me that after 6 years there is still no ability to share the content of the blog post in any straightforward way. The only thing you can do is sending a link.

Technology should support process. If it can't it is useless. In a big company with all those restrictions and securities what is the benefit of using Blogs if you still have to create document in Word then distribute it separately from posting it to Blog? I presume it is designed to save my time, not to introduce additional effort.

It's important not to hyperbolize when stating an impact, as it dilutes all other impact statements. For example, blogs are absolutely not useless without any one feature, especially for something as basic as exporting to PDF.

Also, the workaround here is simple: print the page to PDF using one of the many PDF printer drivers available. It's not a perfect workaround, but it mostly works.

If you want to emphasize the importance of this feature, provide some new information that no one else has included here, such as a description of your organization's specific use-case for exporting to PDF that others may not have considered. Otherwise, you're just spitting into the wind.

So after 6 years it is still not implemented?...
Without ability to export Blogs are useless.

FYI, an ugly workaround to make this work is to create a new page and use the include macro to include the contents of the blog post. Then you can use the Tools -> Export to PDF to export it.

Though it looks like there is also a bug in the include macro for blog post titles that contain a slash '/' character. The workaround to that is to rename your blog post and replace slashes with something else (e.g. dashes).

This makes me a sad panda. I would've thought most of the operations in Tools for pages were available for Blog pages.

I need to be able to "publish" blog entries in a forward or reverse chronology, with the option to select or deselect individual posts, very similar to the process for exporting a PDF. Why isn't this easy?

Hi, any updates to this issue?
We really would like this feature as well as CONF-14684 (export to HTML).

We use the blog post feature extensively for meeting minutes or any status updates. Being able to export to PDF/Word (as you can for a page) is essential as not all stakeholders have online access to our installation of Confluence.

this feature is very important. 期待the first half of 2010

This feature is something we'll consider adding in the first half of 2010, depending on other high priority feature requests.

If you would like to understand how we select features for our releases, please read:
http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements

We need this feature too; spaces containing only news items cannot be exported properly

I need this feature too.

Regards

Our lab now uses Confluence routinely in as an electronic notebook, where daily reports of experiments are filed in as news posts. This allows us to navigate the experimental data chronologically and intuitively using the wiki tree structure and blog-posts macro, which we find as one of the strongest aspects of the Confluence engine. I am now appaled to find that there is no mechanism to effectively backup this data..! It's surprising that the capacity to backup blog posts has not been implemented yet into Confluence given that this issue has been raised more than 3 years ago!
Right now I am backing up my news entries by forcing them to appear on a sigle wiki page using the blog-posts macro and then exporting the page itself with everything in it. This is NOT a sustainable solution since most of the attachment links, thumbnail pictures are either formatted incorrectly or still point to the server files! Atlassian, please implement a proper way to export news items either to PDF or HTML.

So Confluence3, great, but still there are basic functionality holes like this. Any comments from Atlassian?

Please make news posts exportable alone and with the whole project in PDF. This is a real nuisance and has reduced the benefit of Confluence. We need to share our news posts easily with non-Confluence users.

It would make a lot of 'sense' for blog posts to be exportable just like any other "first class" wiki document. We use blog posts for meeting minutes and it would be good to be able to send out a richly-formatted read-only copy to others as needed.

Yes please, make blog entries exportable as PDF!

We are implementing a space as a specialized blog for some of our internal corporate users. The space will only have a menu page and everything else will be news items. The users want to have a record of the blog to be accessible offline and a PDF is the best way to do this but we need a way to get the news into a PDF.

As of yet, our Confluence 2.2.9 does not have the option to export news-items to PDF. We would also like to export news to PDF, any idea when this will be implemented or if at all?

Kind Regards,
Eric Salonen
Ambientia

Thanks for the suggestion. Unfortunately having the file as an "uneditable" PDF when email is considered an important feature (which is why its so great that its available elsewhere in Confluence). In the meantime we are going to write the daily report in Word, export to PDF for emailing and then put it in Confluence for people within the company to read.

Thanks for the suggestion Paul.

For the time being, you could write an XML-RPC [1] script which could be run automatically every day and send the latest new posts to a list of users.

Cheers,
Jens

[1] http://confluence.atlassian.com/display/DOC/Remote+API+Specification