Hi,

I've recently upgraded a site from DNN 4.9.0 to DNN 5.6.x.  Users can make donations on the site via an external payment gateway. The gateway calls back to a control within the DNN file system - http://www.domain.com/physicaldirecto.... <- this is not a DNN page but a specific callback script.

This worked perfectly at DNN 4.9.0 but when testing with the upgraded site I get the following message:

Domain Name domain.com/physicaldirectory Does Not Exist In The Database 

DotNetNuke supports multiple portals from a single database/codebase. It accomplishes this by converting the URL of the client browser Request to a valid PortalID in the Portals database table. The following steps describe the process:......

If I add domain.com/physicaldirectory  as a portal alias, I simply get redirected to the homepage.

Any ideas how I can achieve this simple task of calling callaback.aspx?

THanks

Phil

Thanks for the reply Wes....that the sort of thing they don't tell you in the docs.

Moving the callback program to the /desktopmodules folder did the trick and the callback is working.

We're using DNN 5.6.1 in this case and I'm wondering if there is a way of placing the callback program somewhere other than /desktopmodules so that I can apply security independantly ?

Is there any way a subfolder can be excluded from the the 'dnn domain'?

Rgds

Phil