The situation was confusing, because some people could log in with their Windows credentials, but others couldn’t.

Either ask your user to change their password to something at least 7 characters long (which is obviously the right way to go), or change the default minimum password length in web.config.  The parameter there is “minRequiredPasswordLength”.

The default login page is shown at left.  I don’t like how the buttons are stacked, I’d like to add some hints for users about how to use the Windows Login, and I’d ideally like people to be able to hit <enter> when they’re using Windows Login.  I doubt I’ll figure that last one out before publishing this post.  Right now, you can hit <enter> when using the Standard login, but hitting <enter> with Windows Login causes a “Login failed” message.  I’m guessing that the <enter> is triggering a hidden Standard login button instead of the visible Windows login button.

Step 1: Create a new login page so that other content can be added more easily

Following the tips at dnngallery.net, I created a new page, added the Account Login module, and changed the Site Settings so that this page is the Login Page for the site.

Step 2: Reformat the login module

Since we’re allowing Standard and Windows logins, we need to edit two different Login.ascx files: one in DesktopModules\AuthenticationServices\DNN, and one in AuthenticationServices\ActiveDirectory.  I changed the table width to 240, aligned the Windows login parts to the left to match the Standard login, and added helptext = “” to the labels to get rid of the little help icons (I found that tip here).

I also wanted it to be more obvious when someone clicked on Windows Login, so I edited AuthenticationServices\ActiveDirectory\App_LocalResources\Login.ascx.resx to change the label on the User Name box to “Keynote User Name” and the label on the button to “Windows Login”.

Step 3: Add other content to the page

I added a text/html module to the page with some login tips.

Here’s the final result:

PhoneGap supports iPhone, Android, Blackberry, Symbian, and Palm!

Click here to view the embedded video.

The fix is pretty simple.  Just edit the .htaccess file in the blog’s root directory and add the line Options +FollowSymlinks. I put it after <IfModule mod_rewrite.c> because that was suggested by the article that I found on the interwebs.

I don’t know why I’ve only had to do this with Bluehost, but their tech support told me that they don’t have any plans to fix whatever the underlying issue is.

A little research revealed that you sometimes get this error when unpacking to a hosting account’s root folder.  You can get past this by unpacking to a subdirectory and then moving the files to the root.  It looks to me like my host, 1and1, wasn’t allowing the kickstart scripts to write to the logs folder.  I couldn’t figure out how to fix the permissions, so I used the subdirectory workaround.  After unpacking everything to a subfolder and then moving it to the root, I just needed to change two paths in configuration.php and the site was working.  I never was able to move logs/index.html to the main logs folder, but the site is working fine without it.

I did need to follow one important tip in the Akeeba Backup manual and force “binary mode” when transferring the site’s .jpa archive file down from the original host and up to the new site.