Hi,

To try and find out which node it thinks isn't published can you go to the info tab and see if it says under the Links section?

If you don't have any luck with this then you can try going to the root of your content tree and publishing with descendants (I can see you've tried this) and make sure to tick include drafts (assuming that you don't mind everything being published).

HTH, David

For me, it shows like this.

I face this issue while copying the node from one node to another.

I found the solution

1. I move the parent node(case-studies) to another node.
2. Then give publish with descendant to case-studies
3. Again back to visiting and give publish with descendant then right click on visiting and give reload
4. Copy the case-studies to visiting.
5. in visiting give publish with descendant then right click on visiting and give reload
6. then go to case-studies under visiting give publish with descendant to case-studies then right click on case-studies give reload

It solved

Glad you have this sorted.

With v7 it was always best to unpublish and republish when you got issues like this. With the new caching in v8 I'm not quite sure what the best way is to remind Umbraco when nuCache gets confused!

The published issue has fixed in 8.0.2 version here

is working on a reply...