We just purchased the module and the module installation went fine.  We were able to add the module to the DNN page and select the option to "Setup Property Listing Template". We are able to see and edit the template but unable to save it.  We get the error

Could not find a part of the path 'C:\websites\websitename.com\wwwroot\Listing_Images\16_685.htm'.

ok, that fixed it.  but why wouldn't that folder be portal specific (put it under the portal specific folder instead of the root)?

I could see that being a real limitation in some cases;

For example Company XYZ has a rental division, a commercial division and a residential division.  The company has the main DNN site and each division is a portal with thier own listings... kinda seems weird that it would put all that stuff in the root folder instead of the portal's.

Second scenario Company XYZ sets up a DNN site and gives each of it's agents a Portal to edit/manage thier own listings..

Robb,

We only recently discovered this issue and are working on the fix. The problem is that the fix needs to include a patch where it will also copy files from that directory to the new directory in the portals home directory. Its an easy fix to changes this to be using the portals home directory but for upgrades this causes an issue. Also, you can use this on as many portals as possible and it wouldn't affect the installation. The filenames are specific to the moduleID and I believe even the portalID (at least the moduleID I know) and since the moduleID would always be seperate between portals you wouldn't run into any problems. This is a security/permissions issue though as most DNN installations shouldn't have write access to a folder within the root, only the home directory by design so its something on our list to get fixed.

-Chad