All,
Finally with the release of DNN 3.0.13, the last bug was fixed in my content links module (which turned out to be a bug in DNN and not in my module).
Content Links 1.0 is a module based off of the Links module in the Core framework.
http://www.registrars.kent.edu/home/ContentLinks.zip
It allows you to not only open a link in a new window or existing window, but not in any of the available panes in your skin. When adding and editing links, you will have a drop down which dynamically pulls from the available panes for the current skin, then you can select a pane. When you click on the link, it will look and see if a pane has been selected, if so, inject an iframe into the pane with the same height/width/frame of the pane so it looks like it belonged there. And unlike previous beta versions I have released for DNN 2.1.2, and 1.0, this new version does not require any modification of your skin with javascript.
Included in the zip file is the source code for the module and a PA to install.
I created the PA with the help of the new Create PA function in DNN and added the
SQL scripts manually to the zip file.
It currently piggybacks off of the existing Links table, and modifies it to add a ViewPane column for this module, which is removed when the module is uninstalled.
Let me know what you think. And it does need DNN 3.0.13, DNN 3.0.12 would re-render the entire portal inside the pane instead of just the page you requested, whereas DNN 3.0.13 fixes this.
Nathan