No problem, Steve!

Enjoy!

Scott,

I have found an issue with he FURL. It does not "play" well with (4.6) DNN Search. With the FURL enabled the search returns no results. When disabled the search works as it should.

Attached is a fixed version.

I'll be adding a faster tabpath lookup and a fix so the login page appears friendly (again) as well.

Scott,

Will you also be adding SSL support to the next release?

Apologies Scott.. Yes your fix for search results works well.

Off topic question..news articles...its there a token for sending an article link via email? Like email a friend.

Danny,

I am currently running it on 5 sites. Various shared servers and VPS servers.

I have to say that a few of them have been a challenge to upgrade to DNN 4.6.2

My suggestion would be:

1. Backup your site and database
2. Make sure your current web.config file has two entries changed
   add key="AutoUpgrade" value="false"
   add key="UseInstallWizard" value="false"
   
   This will prevent a premature installation.
3. Carefully FTP over your new folders and files for DNN 4.6.2. Some installs required me to open every folder within the structure to make sure I got this part right.
4. Open the web.config, or release.config, file that is included with the DNN 4.6.2 build and transfer your database connection stings, Validationkey, and Decryptionkey values from your existing web.config file. Also change CustomError="RemoteOnly" to CustomErrors="Off". This change will allow you to see the errors during the install.
5. Save your current web.config onto your local machine (for safe keeping).
6. Transfer the new web.config file to the host server.
7. Run the following URL http://www.yoursitename.com/Install/install.aspx?mode=install or http://www.yoursitename.com/Install/install.aspx?mode=upgrade - depending on your preference.
8. If your install went smooth, I would then login, go to host settings, and clear cache and restart the application.
9. After you are sure that the site is performing properly, transfer the Ventrian.FriendlyUrl.dll to your bin folder.
10. Make the necessary changes, per Scott's instructions, to your new web.config file, transfer it to your site location and you should be good to go.
11. At this point, the friendly URLs might not take right off. I again go to Host Settings and clear cache and restart the application and friendly URLs should now be working.

I second that Danny. It will be a welcome enhancement to have core integration.

Scott,
Can you check the configuration on this forum for the ability to edit?

Thanks

One additional thought in preparation for an upgrade.

In step 4, above, if I think I might have a troublesome upgrade, (DNN 4.3 to 4.6.2 has become a diffiicult upgrade path for me), I will also restore the friendlyurl section, of web.config, to the original DNN code and, in the bin folder, replace Scott's  DotNetNuke.HttpModules.UrlRewrite.dll with the original one from the DNN build you are using.

I then test my site to make sure that everything is working and the URLs are resolving correctly.

Proceed to step 5

After a successful upgrade, you convert back using step 10 above.

Thanks Scott. I discovered that fact during install troubleshooting.

That is my reason for my addendum to the list:

(In step 4, above, if I think I might have a troublesome upgrade, (DNN 4.3 to 4.6.2 has become a difficult upgrade path for me), I will also restore the friendlyurl section, of web.config, to the original DNN code and, in the bin folder, replace Scott's  DotNetNuke.HttpModules.UrlRewrite.dll with the original one from the DNN build you are using.)

The procedure listed above is what has worked for me.

I find on the older builds of DotNetNuke that the upgrade path to DNN 4.6.2 goes smoother if the original urlprovider was replaced and tested on the site before the upgrade occurs.

I spent 24 hours trying to resolve an issue with a 4.3 to 4.6.2 upgrade. The higher admin functionality would not resolve their paths after upgrade. I don't know if it was a cache issue on the hosting server and I doubt it was caused by your module.

Common sense dictated that I should convert the URL provider to its original code prior to upgrade. 

I finally did a complete restore back to 4.3 and added the procedure above. It corrected the previous upgrade issues.