Quote Originally Posted by lhungil View Post
Perhaps a long term solution would be to change the code where a page is added to the navigation?
That's basically what my proposed change does.

I agree that a better solution is desirable, but the goal of any fix to share for v1.5.4 needs to be as brief and simple-to-implement as possible. Any broader architectural changes would go into a new version. I know you understand this. I'm just writing it for the sake of others who read this discussion.

At present the class is instantiated via the auto-loader system, and there's no interception option there to say "do or don't do based on XYZ conditions".


I personally never use those "go back to the previous page" navigation buttons, because I always just use the browser's "back" button ... it's a lot faster than having to find something to click on. If I had my way I'd remove all such buttons from all templates, as I feel they just clutter the page. But, I know some people swear by them and don't even realize that the browser has a "back" button. Sigh.