Thanks for your replies. I didn't form my question correctly.
What I meant to ask was: when using DDR menu inside a skin file, can I reference TabIDs from different portal? I have many portals under one DNN instance. I've place d a DDR menu in my skin file:

< dnn:MENU MenuStyle="sccDeptNav" runat="server" NodeSelector="3452,0,2" IncludeHidden="false" >

However, if I place a TabID into the NodeSelector that refers to a Tab which is in a different portal (has a different PortalID) that the page which is using this skin, the Menu doesn't show anything. Is there a way to reference/ or specify a different portal in this case?

Thank you again

Also, thanks for the information about the "Open in New Browser" fix. In what version of DNN did that first get fixed?

Thanks. Time has passed but I'm still interested in this question if anyone knows.





Again the question is: Using DDR Menu, is there a way to specify a different portal than the one in which the menu is called. Something like adding a variable which specified Portal Id when calling  the menu on a page, and then showing pages from the Portal Id which was specified (as opposed to the current Portal)




Thanks, Tom

Hi Tom, I'm interested in this too today... it just goes to show that there are never any old questions that go out of date... they're just waiting around for the next person that needs the same information!

For the record for others that follow, I don't think this is possible, at least not within the core settings that you set in the skin with the DDR menu.

What we're going to do for a client is have that spot in the skin be a Pane and we'll place an XMod Pro module in the spot. From there, our XMod Pro Template will do a SQL query to get the menu pages for the other portal and will display there. That way, too, we can control the full URLs/domain that's displayed for the links (and of course all the style, etc).