Thanks Sebastian,

I tried that but this only resolves my issue if users check the Track option when inserting the link. I can't expect them to do this every time.

What kind of workflow do people use to develop and test their website upgrades? I do my development and test upgrades in a sandbox. What do people do if they change domains? Is their entire DNN installation hosed?

But sandboxing becomes difficult with this design. If I copy the production site down to a local address, make major enhancements to it, every link in the entire site references the production server's URL. I wouldn't even be able to navigate the site without ending up on a production server. I realize I could modify my hosts file, but that isn't a workable solution for others that are helping with development from remote locations. Its also scary because what if you forget? What if you want to look at the old site and the development one at the same time?

Moving the site to a new domain is still problematic, since once again, every link references the old web address and every request to the server will require a redirect. I don't see this as a solution but instead a giant kludge.

Am I alone in thinking that this is a design flaw?

>DNN was not designed for a staging and production server Translation: We didn't design DNN so that it could be moved to a different server or domain. You can move your installation to a new domain, but you have to pay for that. Well put in a feature request for me. My only choice is to take our existing website down, publish a website with broken links and then go out and repair each link by hand manually for the next 3 to 4 days. This is embarrassing. I think its time for me to go in a different direction. I think its pretty clear the DNN is no longer a very good choice for our needs, nor for small organizations. Considering that you are the only one that has been providing support for my issue, it looks like many others in the community must have decided this a long time ago. Sebastian, take no offense to this. You've responded to every post I've made and have done an admirable job representing DNN. I am clearly frustrated, but that frustration is not directed at you. --Kevin