Hi Ryan,

Once user trash a blog post it will stored in the trash filter (and here you still can restore back the blog post)
However, if you've delete/empty the trash the blog post is completely deleted in the database. (in other word you no longer can retrieve/restore the blog post)

I have a back up of the entire site and DB...

-> If you already backup the site before the blog post completely deleted in the trash. You can restore the site back

But I only want the one post.... I do not want to restore the entire site.... How do I restore or rebuild just the one?

Remember there were attachments as well would the have also been deleted?

Hello Ryan,

Did you trash the post or delete it altogether? There is no way to restore it from EasyBlog if you have deleted it altogether after trashing it. If it was only trashed, it's as simple as filtering by "trashed" and publishing the post again.

If it was deleted, your best bet is to restore a backup of the site on a subfolder and try to re-post the blog post again.

A user deleted so I am not sure the steps they took... I checked trash, archive and unpublished and I am finding nothing. I doubt the user trashed and then deleted the trash.

To restore and repost can you please give me specific instructions?

Hello Ryan,

There is no way for anyone to automatically delete the post without it being in the trash first. As the data could be mismatched, I strongly advise you to restore it on a different (staging) site and manually post the post again.

So restore the full site... and then just rebuild the post??? Is there any way to export and then import the post???

Hey there,

I am really sorry for the delay of this reply as it is a weekend for us here.

Yes, but you have to make sure you restore your full site from your development site, then edit that blog post from your development site and re-create again the blog content into your live site.

Is there any way to export and then import the post???

Unfortunately that was no easier way to import 1 post into your site, because the post id could be different already, since your live site have multiple blogger compose new blog post on your site everyday.