nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Someone's unpublished draft created a ghost child page - how can I find that page and remove it?

Arezou Seifpour_5whve6

I have a page that has a child dropdown but when I click on the dropdown, no page exists. I can recreate this situation by opening up an unpublished draft which creates a child dropdown carrot that in another browser I can see has nothing underneath it. When I delete the unpublished draft, that dropdown goes away. So how can I figure out who has an unpublished draft in my docs?

Accepted answers

All comments

Andrii Maliuta

Hello @Arezou Seifpour ,

You can try to use REST API to get the DRAFTS:

https://developer.atlassian.com/cloud/confluence/rest/api-group-content/#api-wiki-rest-api-content-get

ALL - https://MY_CONFLUENCE.atlassian.net/wiki/rest/api/content?status=draft

SPACE - https://MY_CONFLUENCE.atlassian.net/wiki/rest/api/content?status=draft&space=MY_SPACE

It will show the drafts and you can further extract the history/author/etc. data

You can use API parameters to configure the results you need.

Mia Cheeseman

Has anyone translated that suggestion into English? I have the same problem. My categories have arrows as if there's something under them. They should just be bulleted child pages.

CHopper

You can see your unpublished drafts using the menu bar at the top of a Confluence page.

From the top menu bar

Click on Recent to show recent pages you visited
Under Recent, click on Drafts to show your recent draft pages
At the bottom of that recent drafts list, click on View all drafts to show all the unpublished draft pages you have created

Unfortunately this does not show me the ghost draft page causing my Confluence menu to show an arrow instead of a disc. I have the same problem as the original post.

My solution was to recreate the page. I created a new page. I copied all the information from the old page. I then published the new page and deleted the old page that had the ghost child attached to it.

-Christopher

Matthew Scott_sbp36w

So I've investigated this issue and fully understand what's going on here. It's 100% replicable and incredible that the development team haven't picked this up yet, because it's a major problem.

This problem occurs when somebody hits the "Create Child Page" plus button in the side panel, and then quickly clicks "Close Draft" without making any changes. Specifically, it occurs when you don't set a page title before closing the draft.

It creates a phantom page which is still recognised as a child by the parent, but is not returned in the list of children because it doesn't have a name. This causes 2 issues. The first is that the little icon next to the page title is a drop down arrow when it shouldn't be. The second is that the draft does not show up in "Recent Drafts" where you'd normally be able to retrieve it.

I wrote an integration with the API just to test this to make sure, and the API doesn't return any data relating to these phantom pages. Basically, if a page doesn't have a name, it's there as a draft but it's not visible.

This is some classic Australian programming by the looks of it. If it doesn't have a name, just filter it out 🙃

In order to determine what was going on, I tested a few potential fixes. First I created pages on other layers and dragged them into the page with the phantom child. Then dragged it out. I thought that might reset the icon at first. Then I tried creating new children in that same page and then deleting them after, still no good. And this essentially confirmed to me that the draft is still there, it's just not being listed (either on the web UI or in the API).

There's only one solution guys. You have to delete the page with the phantom child and recreate it. It's incredibly inconvenient when you've done a bunch of work linking it up with the rest of your wiki.

I'd submit a bug report but I've read a few on other issues already that were closed on reasoning along the lines of, "we're going to use our resources to make new features instead of fixing this bug, maybe we'll come back to it in a few years but we closed it so probably not." So yeah, I'm not 100% confident with my choice to use Confluence for our project right now. I hope this is the last bug I run into.

Cristiano Rastelli

The solution suggested by @Andrii Maliuta above worked for me:

visit https://MY_CONFLUENCE.atlassian.net/wiki/rest/api/content?status=draft (logged in, and replace "MY_CONFLUENCE" with your instance name)
you will see a list of draft in JSON format each one with its own ID
for each ID
- visit https://MY_CONFLUENCE.atlassian.net/wiki/pages/viewinfo.action?pageId=DRAFT_ID
- click on the "Visit page" button on the top right of the page
- now you can see the draft and see if it's a valid draft
- if it's not a valid draft that you want to preserve, you can delete it using the three dots menu

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud