• Windows 7 / Windows 2008 R2 SP2, 64-bit​
• IIS7
• PostgreSQL version 9.2.3, 64-bit
• ​.NET 4.0
• mojoPortal 2.3.9.8

Using the Feed Manager feature, I have activated one of the "Show Feed Name..." settings. This issue is the same whether the setting is "Before Content" or "After Content."

The Feed Manager is on the Home page. The URL of the Feed Name link for every story excerpt is "~/home.aspx," rather than the page actually entered.  I do not know if this is pointing at the home page specifically, or at the page on which the Feed Manager is posted.

I have three feeds in the manager, all pointing at the Blog feature on different pages. In some, it is being used for news articles, and for blogs in others. In the Feed Editor page, the feeds are entered as:

• ~/acs-blog.aspx
• ~/intern-blog.aspx
• ~/cva-news.aspx

All these addresses are correct, and their entries are appearing in the Feed Manager correctly. But all the "Feed Name" links are pointing at "~/home.aspx."

OK. On the demo site, home page, at the bottom of the center column.

The "Feed Name" link, "Blog Feeds," is pointing at https://demo.mojoportal.com/home.

On the Add/Edit Feeds page:
   Web Site URL:  ~/blog.aspx
   Feed URL:  ~/Blog/RSS.aspx?p=5613~9280~-1

The reason I am using the "~/" format for the URL's is because we are setting up as new web site. Doing that, we do it on a a test site, then deploy it live. In this case, the test site, visible only to internal computers, is http://uat.cvacoop.com. It is loaded and operating off of the external web server, but can only be accessed through our DMZ from inside. The IIS of the machine is set to route both "uat.cvacoop.com" and "www.cvacoop.com" to the same binding. Also, the mojoPortal site is set to display the same site under both address names.

To make it go live this week, all we will do is change the routing of the outside recall using our firewall/router, to send "www" requests from the old server running DotNetNuke to the new server running mojoPortal. The change to the outside world will be instantaneous. The news/blog feeds only exist on the "uat" site now. Once we switch, they will only exist on the "www" site.

By using "~/" format for the URL's, then we won't have to make changes to any settings, anywhere in the system, when we switch the outside router.

BTW -- Unrelated to the issue--
I was a core developer for DotNetNuke back when it was new. I was the primary developer who made DNN skinnable, and 90% of their skinning code is still the code I wrote 10 years ago. It's said (though there is no proof), that Microsoft took the DNN skinning code and used it to build the layout.Master methodology. Cool to think about, but that's not where I'm going with this. Just a way to tell you how familiar I am with DotNetNuke.

The point I'm making here is that DNN leaders have gone way, way wrong with that framework-- Their focus on money more than quality, their poor customer service, and their slow development and bug fixing-- All of that made me quit them with disgust. And it has only gotten worse every year since.

I think mojoPortal is far superior to DNN, and that's why we're changing our web site to mojoPortal. You have proven that to me three times, with two bug reports and a feature suggestion that I submitted. You fixed or implemented all of them within one day, and I can't express my gratitude sufficiently. Thank-you so much!