Set publishing date when creating blog post

[martin]

I have seen a lot of buzz around this topic before. Some people seem to want to go back and set the date of an already published blogpost. Some would like to set publishing times in the future. All sources tells me that I cannot set the date on an already published post, but I'd be very happy to be able to set it when creating the post.

However I cannot find out how to do it, much less if it is possible at all.

I'd like to move my blogposts from a server instance to our cloud instance. And I'd like to keep the history of the old news feed somewhat intact. Hence the question. 

Are there any workarounds at all? 

Cheers,
/Martin

[Sven Schatter _Lively Apps_ · Accepted solution]

Hi @martin,

On Server this is definitely possible. There we are providing a feature like this in our app Lively Blogs:

In the Cloud, your only chance would be the REST API. Looking at the Create Content Endpoint, it doesn't seem like there's a creation date parameter or something like that, so it doesn't look like this possible through something like an app.

But since you are talking about a Server->Cloud migration, can't you just do a space or site export/import? Haven't tried it myself but my expectation would be that this retains creation dates/history, just as it does with content, attachments, etc.

Cheers,
Sven

[martin]

Thanks Sven, that is pretty much the same answers I've gotten from searching around on the forums and issue trackers. I wanted to know I wasn't missing anything before migrating a lot of pages. 

I have been told not to use the export/import tools. I believe they would mess with our instance somehow. Not sure exactly why. Could be something with the new editor not being supported.

[Sven Schatter _Lively Apps_]

From an app developer perspective I can tell you that imports can definitely mess with your instance, you're right. If you do a site import, your instance gets a new "clientKey" and that definitely can break apps and possibly other stuff as well. However, for space imports that shouldn't be the case I think. But it's probably a good idea to do more research in that regard as I've never performed a space import on a productive Cloud instance and can't guarantee for anything. 😅

EDIT: And yes, there's a lot of stuff that works on Server but isn't supported in the new cloud editor so that could also cause problems

[martin]

Yes, I have dabbled in the world of app development myself so I feel the pain. :)