Archiving blog posts

Avatar
Levente Szabo
Follow

See the discussion: https://jira.atlassian.com/browse/CONF-2455

Have more questions? Submit a request

39 Comments

Date Votes
  • 0
    Avatar
    Aron Gombas

    UPDATE: We have released the Better Content Archiving app's cloud version just a few weeks ago. It addresses many points criticized in the Data Center version, including also this one.

    (Our plan is that, if there is interest, we will back-port the most valuable changes from the Cloud version to the Data Center one.)

    It tracks every types of contents in the same way. Thereby all features work on blog posts just like they do on pages. 

    In the screenshot above, for example, you can see one of our internal blog posts with its status displayed in the top!

    🔥 Try this in action now!

    Edited by Aron Gombas
  • 0
    Avatar
    Constantin Lotz

    When this is planned in the data center edition? +1 Need it :-)

  • 0
    Avatar
    Constantin Lotz

    @Aron Gombas

    any news on this?

  • 0
    Avatar
    Joe R

    This would be so helpful in data center, any update on this being brought from cloud?

  • 0
    Avatar
    Levente Szabo

    There are no updates yet that we could share regarding this. Please keep monitoring this space as we will share news here first.

    Thanks for your interest!

  • 0
    Avatar
    Constantin Lotz

    any news here on this? Still want it for Datacenter :-)

  • 0
    Avatar
    Beate Odrig

    Schön, dass ihr seit zwei Jahren in der Cloud auch Blogs archiviert, wann kommt es für DataCenter? 
    Blogs haben eine kürzere Aufbewahrung und "müllen" Confluence zu :(

     

  • 0
    Avatar
    Constantin Lotz

    Well I think midori isn't doing here anything. We're going to switch to other tools like mft and archiving the blog posts via the api themself. Works nice :-)

  • 0
    Avatar
    Aron Gombas

    Dear everyone,

    I just wanted to leave a reply on this thread.

    The hash reality is that over the recent years, Atlassian kind of "pushed" ("forced"?) us to rewrite the app for Confluence Cloud, which turned out as an enormous effort. It has been enormous, because their REST API lacks critical endpoints, there are unreliable mechanism on Cloud (CQL indexing latency is crazy), there are unexpectedly low REST API rate limits, they made breaking changes to the API from "v1" to "v2" and forced us to migrate, and so on. 

    On the top of this, just recently they started to aggressively push the app vendor ecosystem from the old Connect framework to their new Forge platform. It basically means another rewrite and migration -- while keeping the app functional for existing installations.

    On the Data Center side, they released multiple Platform versions (like P7), each of which broke existing apps. Although it may not be visible from the outside, they changed APIs, they removed components from the Java classpath, etc. We are busy to keep up with these changes, offer compatibility and also offer backward compatibility.

    Having said these, we don't know what are Atlassian's plans with the Data Center deployment type... Maybe the Team '25 conference will reveal some details, and we can adjust our allocations accordingly.

    It is not easy.

Please sign in to leave a comment.