I didn't know he was still working on it. Thank you, he should check on this forum post too, as he needs to update the wiki's and the reference documentation on the various sites to include up to date and easily followable structure for implementation too.

Properly archive content from here as it's quite out of date and irrelevant: http://www.dnngarden.com/Download.T87.aspx

As well he needs to better reference these two websites together as one living location for the documentation:  http://dnnddrmenu.codeplex.com/documentation and http://www.dotnetnuke.com/Resources/Wiki/Page/DDRMenu.aspx

I found these resources more helpful for implementation, than the original documentation:

http://www.dnnhero.com/Article/tabid/212/ArticleID/4/Beginning-XSLT-with-DDRMenu-Part-1.aspx

http://www.dnnhero.com/Article/tabid/212/ArticleID/12/Beginning-XSLT-with-DDRMenu-for-DotNetNuke-Part-2.aspx

http://www.dnnhero.com/Premium/Tutorial/tabid/259/ArticleID/28/Beginning-XSLT-with-DDRMenu-for-DotNetNuke-Part-3-3.aspx

Look at the Wiki page for info on  DDR menu, it's the best resource IMO.
http://www.dotnetnuke.com/Resources/W...

I have more info on the issue.
It's a bug and it's fixed in DDR 2.0.3, which is unfortunately only for DNN 7.0.3 as there are DNN 7 specific fixes in it too.
https://dnnddrmenu.codeplex.com/relea...

I came to that conclusion as well using XSL javascript and some ASP.

In the grand scheme it was only for one link so I managed to just hard code the target window for that specific link it into the XSLT file, and then wait to hear back if when the update for the DDR Menu would incorporate this.

That being said, can you please update the documentation for the latest version of DDRMenu for 7.0.3 (and also indicate that it is only for the latest version number that works on DNN 7.0.3) on the page below, so that it contains the information regarding the attribute name to test against when creating our conditionals in XSLT and the other language syntaxes here?:

http://www.dotnetnuke.com/Resources/W...