Hi guys

(Sorry for cross-posting, I didn't realise that the old topic I asked about this was in the now-closed Alpha Club)

As we're in Beta phase, I wanted to raise this topic again and see if there has been any more thought given to this? It'd be great to keep an archive of status updates somehow instead of simply disappearing them; if there's no plans then I'll need to look into a third party solution, so it'd be good to know the first-party plans so I can arrange things on my side accordingly. Thanks!

Nothing has really changed from what Matt mentioned in the post you link to there. At present there isnt any plan to convert these to any other type

What do we want to see? Converting status updates into a specific forum with one topic per person and each status update a comment, and each reply to that status update a quoted reply?

 

What do we want to see? Converting status updates into a specific forum with one topic per person and each status update a comment, and each reply to that status update a quoted reply?

That could work, yeah!

I was thinking, personally, that each status update would be its own topic in a specific forum (rather than a single topic for all of one user's statuses) and every status update comment would translate to a (quoted) reply within that topic. But I'm happy for a solution like you suggested as well, it might actually be cleaner that way!

Let me know if something like either of the above is possible at all on the Invision side. Thanks @Matt! 😀

Edited November 2, 2024Nov 2 by Dreadknux

There is a solution though it's not gonna work in bulk but rather individual statuses.

https://www.sosinvision.com.br/index.php?/file/146-convert-status-updates-to-topics/

 

There is a solution though it's not gonna work in bulk but rather individual statuses.

https://www.sosinvision.com.br/index.php?/file/146-convert-status-updates-to-topics/

Yeah, that's a nice solution for people who want to save specific statuses, but that's not gonna work for me, lol. Trying to archive 13+ years worth of status updates one by one will take me an ice age. 🙂

Hopefully the solution Matt proposed could be looked into as I can definitely work with something like that.

Our site has just been upgraded to 4.7. We use the Status Updates a lot so when the time comes to look at V5, we will be reaching out to a 3rd party developer to create an application to mimic the existing Status Updates.  

That's just my input.  

We need the same solution for tickets as well... we can't loose the ticket history for audit perspective. If we can convert tickets to private category -> Topics and posts, would be perfect. 

 

That could work, yeah!

I was thinking, personally, that each status update would be its own topic in a specific forum (rather than a single topic for all of one user's statuses) and every status update comment would translate to a (quoted) reply within that topic. But I'm happy for a solution like you suggested as well, it might actually be cleaner that way!

Let me know if something like either of the above is possible at all on the Invision side. Thanks @Matt! 😀

Seeings as we're (seemingly) inches closer to a final release for 5.0.0, wanted to just check in on this @Matt and get your thoughts on this and whether it is possible? If it's not something in the scope of 5.0.0, that's fine as I don't plan on upgrading for a couple months yet (lot of testing to do, particularly with custom CMS Pages...) but if there's an idea of implementing something, no matter how basic it is, knowing when that might drop would be helpful for me in order to make the jump to v5. :)

There are no further additions to 5.0.0 that are not already in the latest beta. We are feature locked for that version now. Of course there will be many many more updates to come 😊

 

Seeings as we're (seemingly) inches closer to a final release for 5.0.0, wanted to just check in on this @Matt and get your thoughts on this and whether it is possible? If it's not something in the scope of 5.0.0, that's fine as I don't plan on upgrading for a couple months yet (lot of testing to do, particularly with custom CMS Pages...) but if there's an idea of implementing something, no matter how basic it is, knowing when that might drop would be helpful for me in order to make the jump to v5. :)

Our plan is for a fairly soft and quiet 5.0.0 release and then focus on the needs of those moving from v4. We keep all the status data, so it's trivial to convert it into a forum, or whatever if/when we wanted to do that. If the need isn't huge, I might just do a one-off app or something that does it rather than bake it into the product, but we won't know until more people start upgrading.

This is already available to a third-party developer

https://ipsappzone.com/file/47-ustatus/

Although I do not plan to use it because I see that this feature has already become old from the last century

 

This is already available to a third-party developer

https://ipsappzone.com/file/47-ustatus/

Although I do not plan to use it because I see that this feature has already become old from the last century

Thanks for sharing, I'll keep it bookmarked but for now I think I've made my peace with Status Updates going completely and want to explore how my community interacts with the site without them... but if I hear too much complaining I may run to something like this for protection! 😂