Hi Brendan

Something of the back of my mind tells me that I've seen other people have this issue before but can't remember if it's something I've seen in the issue tracker or on a post here on our.

If it's possible I think the best option is to upgrade to latest stable version of v4.11 since there unfortunately also are som nasty bugs in this version not to mention the newly discovered security issues. Even though there is a patch specifically for 4.9.0 some of the bugs in this version justifies an upgrade I think. But I also know that it's something you need to clear with your client since it probably involves some economy.

Hope this helps.

/Jan

Thanks Jan. I hope the client goes for the upgrade, fingers crossed it would fix the issue.

Thanks again for the help.

Brendan

Hi Brendan

Yes I really think it's the best solution in this case - let us know how it turns out.

/Jan

Idk, I've had something like this issue in 6.1.1.

It requires a republish of the entire site, clearing the browswer's cache and sometimes even restarting the site to fix (and even then it will pop back up sometimes).

I'm sort of thinking its a caching problem with umbraco.

VERY late to the party here but I had a Client who couldn't upgrade but had this issue.  I created a rest extension and hit my method via ajax like so.  The key is to delete the XML record from the DB:

public static string UnPublish(int contentId)
        {
            bool success = false;

            var doc = new Document(contentId);

            if (doc != null)
            {
                doc.UnPublish();
                RemoveXmlFromDB(contentId);
                umbraco.library.UpdateDocumentCache(doc.Id);
                umbraco.library.RefreshContent();
                success = true;
            }

            return jss.Serialize(new { success = success });
        }

private static void RemoveXmlFromDB(int nodeId)
        {
            var sqlHelper = Application.SqlHelper;

            var sql = @"
              DELETE TOP(1)
              FROM cmsContentXml
              WHERE nodeid=@nodeId
            ";
            sqlHelper.ExecuteNonQuery(sql, sqlHelper.CreateParameter("@nodeId", nodeId));
        }

is working on a reply...