Is there a way to disable the News Link in the Global Navigation for Anonymous users?

[Roxana-Otilia Ciuhat]

Hi and and first of all thank you for creating this app!
I am using it in the Lite version for now and I have the following behaviour which I don't know how to correct:

Context and what I did:
- Confluence instance is accessible to Anonymous users
- I added and featured blogposts,  thus publishing them the "News"
- in the app Configuration I disabled the Confluence global navigation link

What I expected this will trigger:
- disable the link to "News" in global navigation for all users

Actual result:
- link was disabled for logged in users 
- link was not disabled for anonymous users. no content was displayed though (so that's good :), fits my use case )

So, the question is, if there is a way to disable the link in the navigation for Anonymous users as well? I do still need to keep the instance Public because of other spaces, but I need to keep the "News" part internal. And having the menu item in the navigation may confuse users who might expect to receive content there.

Thanks a lot!

Otilia

[James Dellow]

I've deployed a work around, however, Atlassian support have now logged a bug report on the cause of this.

If you are interested in the technical detail, see:

https://ecosystem.atlassian.net/browse/AC-2554

[James Dellow]

Hi @Roxana-Otilia Ciuhat - I'm the developer of the News Board apps.

Thanks for raising this - I would expect that when you disable the link, it removes this for everyone including anonymous users as well. Leave it with me and I'll investigate.

[James Dellow]

@Roxana-Otilia Ciuhat I've confirmed the issue and as result I've logged a support ticket with Atlassian, as the underlying problem is how Confluence is processing a configuration rule to hide the link.

In parallel, I'm also working on an alternative fix, however, this requires some backend and frontend development so may take a few weeks before I can release the update.

[James Dellow]

@Roxana-Otilia Ciuhat Atlassian haven't responded to my bug report yet, but in the meantime I've deployed my own work around. Once your version of the app updates to version 1.0.21-AC you should find this issue is resolved.