Here is a quick tip to display one of those cool pages to people when they either try to get to a page on your site that doesn't exist or when something happens and an error occurs on your site.

Open up your web.config file Locate the line that starts wtih Set the mode equal to "On" Then create another attribute in the tag labeled "defaultRedirect="URLOfErrorPage" The tag will end up looking something like this Note: This only works for pages ending in aspx, for pages ending in something else you will need to either configure IIS or see if your web host provider offers the ability to configure custom error pages.

Or you can check out this great article by SEABlick Consulting regarding 301 redirects which you can easily use to setup 404 redirects http://seablick.com/blog/articletype/articleview/articleid/114/understanding-301-redirects.aspx

You can add mandatory fields by doing the following:

1. Login as a user with at least admin privelages.
2. In the Admin menu click on User Accounts.
3. In the Module Settings menu for User Accounts click on "Manage Profile Properties"
4. In this window you can create new profile properties, specify their order and mark them as required.
5. Once done click the Apply Changes button.
6. Back at the User Accounts main module go to the Module Settings menu for User Accounts click on "User Settings"
7. Put a check next to "Require a valid Profile for Login".

That should do the trick.

 

Well after a year plus same change of being in business we finally got a logo.  Look up and to the left.   Do you like it?  We sure do, it makes us feel like we have entered into a new space age, of the Internet.....

Anyway, with a new logo, comes new things.  One big new thing is that we are looking for some help with our DNN projects. 

Are you a Dotnetnuke developer, or a wanna-be Dotnetnuke developer?  If, so drop us a line at jobyjobs@hilbertsolutions.com and let us know your experience and what you charge an hour, as well as your availability.

 

Animated Gifs seem pretty antiquidated now, but there is still a time and a place for them.  When that time and place comes here is a good one to use.

http://gifmake.com/

Here is a stored procedure you can use to delete users from Dotnetnuke. This also has a procedure to remove a user from DNN Master's multi-portal sharing.  It won't hurt anything if you leave it in there.

To delete the user just call DeleteUserByUserName 'SomeUserName'

 

 

ANSI_NULLSONQUOTED_IDENTIFIERON Create

@Username

 procedure [dbo].[DeleteUserByUserName]asnvarchar(100) as

 

EXEC

 

aspNet_Users_DeleteUser 'DotNetNuke', @Username, 15, 0deletefrom Users Where

Username = @Username delete

from DNNMasters_MPUS_X_UserInSharedArea WHERE

Username =@Username

go



set

...