You know that if you edit a file of NodeBB itself it may refuse to update by git pull because a merge would be needed?
So it may be that you're working with an old version of NodeBB o_O
If you are able to delete a post you have the permission to also restore it. Because of this the post doesn't get removed but only gets less opacity (within the official themes).
I just don't know in which case the post could be removed from DOM after reload, may be an inofficial theme or an old version of NodeBB (maybe because of the reason above).
If you've forked the Lavender theme, just add the original source as another remote:
$ git remote add upstream git://github.com/NodeBB/nodebb-theme-lavender.git
Then every time you want to merge the latest changes in:
$ git fetch upstream && git merge upstream/master
I realize this is an old topic, but given that I'm dealing with exactly the same problem, I figured it would be sensible to reply here. Essentially, I've followed the advice of @pichalite and created a simple IIS forward proxy for my NodeBB server. Unfortunately this solution does not yield the desired result, as many requests for resources are not being made to the correct directory - instead, requests are being made to the root level of the IIS Web server (e.g., GET http//website.ca/stylesheet.css?4210ebb0-9225-4237-b2ad-87d88b61756b), and not to the specified port where NodeBB is being hosted (e.g., http://website.ca:4567 or http://localhost:4567).
Any ideas? I've played around with reverse proxies and outbound rules to route all outgoing traffic from http://localhost:4567 to the same URL I've specified for the proxy rule (e.g., http//website.ca/associates-hub) to no avail... If more info or screenshots are needed, they can be provided. I've been banging my head against the wall trying to cycle through all possible solutions to this problem. Any insight would be GREATLY appreciated.