iFinity

One of the new features you’ll find in the recently released DotNetNuke 5.3.1 version is the ‘User Profile’ page.  This page is created by default in new installations, and is part of the continual move towards more ‘social’ features in the DotNetNuke core.

The new User Profile page contains details from the existing DotNetNuke user profile, and includes the new messaging system newly built into the DNN core.



Shown Above : DotNetNuke 5.3.1 User Profile Page

Vanity User Urls It’s a funny term, ‘Vanity’ Urls, but it denotes the use of a short, simple Url, usually based...

File this one under ‘you learn something new every day’.

I may be the last person to know this, but example.org, example.com and example.org are domains reserved for use in documentation.

I tend to use ‘mysite.com’, ‘domain.com’, ‘yoursite.com’ and anything else.  I usually try and remove automatically generated hyperlinks because I don’t like to feed link juice to the owners of these domains.  But it still happens.

Then today I accidentally clicked on an automatically generated example.com Url, and found out it’s reserved for documentation.  No more link-juice bleeding from documentation and discussions about Urls.  Try it! http://example.com

I’m off to do some find/replace.

With DotNetNuke 5.2 a new change was introduced, where a specific GRANT EXECUTE statement was run for all the objects on the database.  This caused plenty of problems with shared hosts, where a specific database user is used to run all of the Sql for a specified database, and those users don’t have permission to use ‘grant execute’.

The change was to tighten up security, but unfortunately it tightened things up to the point where many users could not run them.  I know I personally burnt many hours trying to figure out where these errors had suddenly come from.  I was genuinely bewildered when first hit with this problem after providing someone some script to run to correct an error in their database.

Typically, you’d get something like this, either as a result of using the ‘Host->Sql’ screen, or by installing a module.

System.Data.SqlClient.SqlException: Cannot find the object 'dnn_DeleteLanguage', because it does not exist or you do not have permission. Cannot find the object 'dnn_GetUserByUsername',...