Stuart,  

This is a great question; and sadly, it is a great question because the use of "Display Page Options" isn't very intuitive. Hopefully, I can explain its use and we'll work toward making this more intuitive.

Setting an article to use "Current Page" will allow the article to be displayed on the page of any list that links to the article. This setting only works in tandem with instances of Publish set as "Overrideable." The way I typically think of using "Current Page" is that the article's display page is determined by the display setup at a specific module.

Setting an article to use "A Specific Page" tells Publish where to display the article if a system generated link points to it. For example, if you have a Custom Display set to show articles from a Category. The list of articles for the given category may display on one page, but when the article link is clicked, the article determines where it should be displayed.

By "Forcing the display," the article starts to get stubborn about where it will render. This is particularly useful if you have permissions set on a page so that only people in a specific role can view the articles on that page. Force display restricts someone from manually passing in the itemid for an article they are supposed to be restricted from seeing on a page for which they do have permissions. I tested this on my personal site and there may be a bug.

After I had loaded in a bunch of content, and started to figure out how I wanted to display things, I ended up using a common page, and the 'force display' option.  Not sure why, but it just seemed to be more consistent.

Rather than go back into each article, here is some SQL that I used to fix up the items/articles to display on that common page:

UPDATE Publish_ItemVersion
SET DisplayTabId = 158
WHERE ItemId IN (SELECT ItemId From Publish_Item WHERE ItemTypeId = 1)

DELETE 
FROM Publish_ItemVersionSettings
WHERE ControlName = 'ArticleSettings' AND PropertyName = 'ForceDisplayOnPage'

INSERT INTO Publish_ItemVersionSettings
SELECT iv.ItemVersionId,'ArticleSettings','ForceDisplayOnPage','True' 
FROM Publish_ItemVersion iv 
WHERE iv.ItemId IN (SELECT ItemId From Publish_Item WHERE ItemTypeId = 1)

aapubs, can you post what the errors are that you're seeing when this occurs? If you login as host you should be able to get detailed errors in the Event Viewer (event log) that might help us track this down.

dunmcl can you confirm you're using Publish 5.1.3? I'm trying to test this out and see what I see here.

Did you have any luck replicating our problem Chris?

• We have a page set up showing a specific category. The category is configured with this page as the display page.
• An article is entered with that category selected, and 'Display on Current Page' is ticked ('A Specific Page' is not ticked, the drop down is thus disabled - but our homepage is selected in the disabled list).
• When accessing the article from the page via category display or (custom display) the article doesn't load on the current page, it loads on the homepage.

The only way we can get the article to appear on the current page is to not use the 'Display on Current Page' feature and use the 'A Specific Page' instead. Though we're rather not do this, as we have a lot of articles which we want to display though multiple categories/pages.

Any advice you can give will be most appreciated!

Cheers
Duncan