Hi,

In the next version of my Smart-Thinker Wall module I want to move images to portal level instead of under DesktopModules (effectively Host level). This will allow image customizations to be done at portal level (for example, if you have a set of flags that all modules can use but needs to diffe by portal). 

My plan is to use the format:

Portals\CompanyName\Images\

eg.

Portals\Smart-Thinker\Images

The problem is that when I install a module I need to add the images to any portal that will use the module. So if you are installing it on a server with 10 portals then it really needs to create and write the image files to each one. I don't think there is any other way other than instructing the installer to create the folder under each portal and copy the files manually? From the looks of this post, the DNN installer can only write under the Desktop folder module when it comes to install resources.

I could of course check for it the first time it is used on the portal and create/copy/unzip it from the desktop folder, but this seems clunky - is there a better way?

---

Thanks,
Rodney
Smart-Thinker - Social Networking modules for DotNetNuke
The DotNetNuke Directory - Are you listed?
PokerDIY - Example Implementation of DNN Social Network
Do use DNN a lot? Try the DotNetNuke Toolbar to save you time!

Rodney,

IMO, if there is a larger number of images, you should consider to place shared images inside /portals/_default/company_images and portal specific ones inside /portals/[portalid]/company_images, which shall be searched first when retrieving the image (if done by path, not by id). You should not create folders in \Portals root directory, this shall be reserved to the core.

For further discussion, you need to point out the background a bit more.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

I like Sebastian's suggestion which also has the benefit of of only one instance of the default image used by all portals, and only create a portal-instance of an image by the same name when a portal chooses not to use the default. I know disk space is cheap but still it makes sense. Not only that but simply by existing, a portal-level image would provide an audit on which portals use the default images and which have their own.

---

pmgerholdt