I have expanded the article content type to include a few more fields and want to display an article node as a page. Each article node (content) I give an alias with the following pattern: press-releases/[name-of-article]
I've set up A "Press Releases" view which has three displays. Two of the displays are block displays and these work perfectly. I also want to make a page display with this view, and that's where I'm running in to problems. I want this view to be active for any node (content) that has the url press-releases/[name-of-article] and so I set up the view like this:
And the Contextual Filter has these settings for the Node ID:
But when I visit any press-releases/[name-of-article] it's like the Contextual Filter is completely being ignored and I just get the node spit out all the default fields as determined by the content type, and not according to the View's Page display. Why is this, and how can it be corrected?