Hiding the error message would be nice. Then you can create a left navigation structure with including navigation points that can only be seen by special users.
For example:
"Navigation" describes the navigation site in the left menu. With the include macro you can include a "Navigation2", which can be only seen by a special group or user. Actually you can't use this, because users, that are not logged in will see the error message.

Thanks for adding me to that issue as Watcher - I see that this one is as old as the mentioned other duplicate (more than two and a half years); after several new versions of Confluence - we use 2.7.1 Enterprise - nothing has been done on this.

Because I suggest, that this feature is a basic feature of a WIKI, I can't imagine that adding the capability (of optional invisilibility) is as difficult. When will this one (besides other very annoying errors) be fixed?

In general - placing error messages might be a good idea for managing the page, but it must be possible, if I could not edit the page, that no error occurs and the misleading content is simply invisible

A note on trolling

As a customer and user, I've found that 'trolling' or 'complaining' doesn't really help get things changed by Atlassian, but spending time and money does. If you don't like confluence, don't use it. If you like it, suggest how it can be improved, or invest in improving it in some way. It's that simple. I've seen many of my suggestions eventually implemented by Atlassian or 3rd party vendors, when I take the time to make a strong case, connect it to other issues, connect it to other customers, suggest technically feasible solutions (or pay someone to do it). (I should also admit, I've done my share of 'trolling' atlassian issues in the past, so I'm not trying to preach from a haughty position, but just sharing my experience.)

This feature request can likely be accomplished out of the box in several ways with just a touch of configuration:

Using CSS

• re-style the global 'error' style to hide all error messages.
• re-style the 'error' style on just the navigation page, to hide all error messages.
• re-style the global 'error' style, when it is contained in another arbitrary style such as "mynavigator", and use {div:class=mynavigator} ... {div} around your 'navigator' blocks

Using User Macros and the internal renderer

• use a user-macro wrapper, such as was done with 'edit-include', which gives you control over the output of an include. (slower, using internal renderer)

If you get it working, please consider contributing it as a confluence extension

Hi James,

please note, that not every confluence customer/user/administrator is a programmer, who can easily change the behavior of confluence or can write plugins, macros etc or has the budget to pay someone to do this. There are customers who use confluence (mostly) out of the box with a few plugins.
For me, asking for an improvement is not 'trolling'. By the way, the issue was opened by Atlassian itself. So if you have some information or a workaround, just type it here or link some resources to help us.

Re-Styling the 'error' style with CSS on just one page can be a solution.
How can I re-style the error message for one page? Is it necessary to create a new theme? Or is there another smart way to get rid of the error message by including CSS only for the navigation site?

Thanks for your help.

• My appologies, Jochen. You're report was not at all a troll, and is very helpful. My note was not at all directed at you. My comment was intended to suggest alternative courses of action for anyone who decides to write about how ineffective Atlassian is at addressing a particular issue, such as seems to be implied by Wolfgang above. I've simply noticed that, for myself, writing statements to try to invoke guilt does not encourage Atlassian to develop something new. However, building a case, collecting examples, linking together ideas and people, does work.

• I'll refer you to atlassian support, the atlassian forums, or the help documentation for CSS restyling help.
• check out the 'style' macro extemsion for page-specific styling.
• also, check the 'show-to' and 'hide-from' confluence extensions for showing / hiding content to/from specific users.

First of all I've to thank Jochen for his comment - its that, what I feel and would sign fully.

"Trolling" as you, James classified my words, is no sort of action or participation on any type of software, I use, but I'm a bit frustrated about what is coming back as support from Atlassian and our IT support says the same regarding support requests, they asked. Besides that, most requests (about error fixing, not only feature requests) I researched, I saw on very old versions detected and while new versions of Confluence gets a lot of new features, questions on this are generally answered: No time to fix or to complex to fix.

Regarding Confluence, I'm a normal user. It has been set in our company and I've neither control over what to install for my needs, because all this could only be done by confluence system administrator. I'm only a space admin of one space in the confluence world. Also user macros (why they are named USER macros), changing css or further tipps you mentioned are under only control of the system administration. I could suggest changes in our installation, which I do, but to get them fullfilled I often have to give them a lot of technical and background information I do not have and I have no time to research, because of my normal job, I've to do - which is not managing our Confluence.

Because this issue has been opened by atlassian themselves and another issue I found regarding same topic does last point to this one and because I was put automatically? on the watchers list, I saw the chance to get more feedback by issuing a comment with words, showing the importance - obviously not only for me (on counting the number of similar issues in the different versions).

James,
if you have another focus on Confluence and/or the knowledge, how to circumvent the several problems and errors (e.g. as this one), which gives me the problem, that I could not share my space with viewers with different rights, I'm very very interested in a detailed description, what I could the forward to or IT for integrating. Thanks in advance and have a nice weekend.

In a similar vein, I'd like to be able to include content without bringing links along. Sometimes I want to include content from another space, but customers in space A can't access pages in space B, do they get error messages when they click on links that have come along fr the ride.