How to fix failed to retrieve directory listing error

Sometimes when using Filezilla FTP Client to connect a FTP location you may experience following error:

Server does not support non-ASCII characters.
425 Can't open data connection.
Failed to retrieve directory listing

To fix this error you will probably need to visit Site Manager of Filezilla Client application and for the FTP site in question, click to Transfer Settings Tab and change Transfer mode to Active. Click OK and try to connect again.

Upon applying new settings connection should work again.


Host Header Issues When HumanFriendly Urls Applied

Many hosting providers do not allow you to install your web application into your hosting account's root path. However, you can overcome this limitation by several ways. Specifying a host header in web.config and modifying Portal Alias table is one of the useful methods.

Although it can be a good workaround, using host header in DotNetNuke has its own limitation with SEO Friendly URLs. If you are in a rush, you can see the logged issue here >>

I had some time to test DotNetNuke 5.6.2 release against the goal of removing sub directory name from URL, i was able to do it. But, URL structure where Human Friendly (SEO Friendly URLs) used, gave 404 errors.

For instance, if you install your website in a folder called portal, your host header value should be following as demonstrated in DotNetNuke Wiki.

<add key="HostHeader" value="portal/" />

After using this and adding a naked portal alias into Portal Alias table for desired domain, you will be able to access your website. Partly!
Login, Registration and some of Host pages will work, while others won't!
So, the only way to overcome this problem is to remove urlFormat="humanfriendly" from following section in web.config.

<add name="DNNFriendlyUrl" type="DotNetNuke.Services.Url.FriendlyUrl.DNNFriendlyUrlProvider, DotNetNuke.HttpModules" includePageName="true" regexMatch="[^a-zA-Z0-9 _-]" urlFormat="humanfriendly" />

After using this workaround, you will be able to access the pages in your website with no subfoldername in urls. However, you will have no benefit of using SEO Friendly URLs.

Maybe it's by design, or a bug in core needs to get fixed. Issue is logged below:
Human Friendly URL's With Host Header in web.config

If interested in solution, you can click on Watch button at bottom left corner.

DotNetNuke 6 beta 1 released

I was expecting to see the release of DotNetNuke 6 Beta 1 after WebConnections conference. I guess, I'm right since checking DotNetNuke library on Codeplex brings list up new items for DNN 6 Beta 1 (install, source, web platform installer, upgrade package etc...)

DotNetNuke 6 will be released very soon, so if you haven't done yet go ahead and test the BETA releases. Report issues you find under Support Tracker and help the team to improve it for community.


DotNetNuke 5.6.3 Will Be Released Next Week

My resources (erikVB from Twitter) has just announced that DNN 5.6.3 will be released next week after Web Connections Conference. I guess, the new release will handle core permission provider issue and add some extra improvements to DotNetNuke Core....

Monitor Your Paypal Accounts Against New Vulnerability

This morning, i was checking my Twitter account and noticed a tweet regarding a vulnerability in Paypal's system. The vulnerability in question allows an unauthorized people to access your account details. Once a password reminder request sent, system sends password reset tokens to a random email address instead of yours.

Since we use Paypal for purchasing stuff for our DotNetNuke installations or any other personal needs, i strongly suggest monitoring your accounts until we hear from Paypal Staff.


Web Connections Time

Web Connections Conference time... Tomorrow will be great opportunity for DotNetNuke Community. Unfortunately, i will not be able to attend for several reasons.

Anyway, if you want to learn more, you could take a look at Will's latest post on DotNetNuke Blogs.
Are You Ready for Web Connections 2011? >>


Scheduling DNNScheduling ProcessGroup Run

I'm using DNN for one of my clients at a hostel booking website. You can browse the hostel booking website by following this link >> While checking Log Viewer for error logs I've noticed the following error:

Method: DotNetNuke.Services.Scheduling.DNNScheduling.ProcessGroup.Run StackTrace: Message: System.Threading.ThreadAbortException: Thread was being aborted. at DotNetNuke.Services.Scheduling.DNNScheduling.ProcessGroup.Run(ScheduleHistoryItem objScheduleHistoryItem)
It seems DNN Scheduler has a problem with items in ScheduleHistory table. While searching this on DotNetNuke forums i only found old posts from 2007.  Maybe a bug appears again after a long break.