The API page still appears in the navigation links even if I uncheck the option while editing in staging. Has anyone else faced similar issue?
Hi again Sonalee,
I am writing to confirm for you that this development incident has been submitted and is under review by our development team. It will be carefully considered when fixing bugs for future versions.
This development incident was filed as ADP-1179.
For your reference, the development incident number is always noted in the release notes of every version that is released, including its minor updates, so that you can confirm when a fix or new feature has been implemented from your request.
Support Engineer, CA Technologies
Phone: +1 800 225 5224
Outside of North America - http://www.ca.com/us/worldwide.aspx
Anyone able to help with this question?
I just want to clarify... which option specifically are you unchecking to prevent the page from appearing in navigation? Are you referring to the "Include Page in General Site Navigation" checkbox while editing a page such as a Documentation page? Are you making this change somewhere else?
Are you deleting the page at all, or just modifying it?
What kind of page is this - is it a header page or a sub-header page (which represents itself as indented from a parent page in the side navigation bar)?
Where are you expecting this link to be removed from... the side navigation bar or the top navigation bar?
Sorry for all the questions, but I need to ensure I fully understand what you are trying to achieve and how before I can troubleshoot much further. Also, which version of API Portal are you running? I can check for any known issues around navigation in that version.
Yes ,I am referring to the "Include Page in General Site Navigation" checkbox.I am trying to remove a page documentation link from side bar since I am including it's URL in another documentation's description. But when I uncheck this option, it still appears in side navigation bar.I am using portal version 2.6 .
It seems I am able to reproduce this issue specifically with top-level Documentation pages. However if modifying a sub-documentation page, it works as expected.
I will be doing a bit more troubleshooting and perhaps filing a development incident report for a fix in an upcoming version if the issue is indeed a bug at all.
I will keep you posted with the development incident number if I file it, or any further progress I make. Please bear with me.
Retrieving data ...