Save configuration XML differently so it can be used in multiple modules & portals


Change the location the configuration XML is saved in, so that two modules can display different lists of files, and so that two DNN portals can display different lists of files.
With the XML saved in the DesktopModules folder, it limits the use of this module. (http://localhost/dnn/DesktopModules/FlashImageRotator/Flash/ImageList.xml)
  • It could be in Portals folder for each site.
  • Or, It could be saved as a varchar string in a table, with columns for PortalId and ModuleID, so that it would be useable by multiple portals and modules in a portal.
    Where it stores the XML now, means that it can be used only once, which really goes against the DNN principle concepts.


734353 wrote Jan 24, 2011 at 1:24 AM

Anyone interested on working on this with me? I have limited time now, but later in Feb. I may have a little time.

m2land wrote Jan 24, 2011 at 2:15 AM

Hi, I can added you as "Developer" and I can share some codes to finish this function.

wrote Jul 16, 2011 at 12:19 PM

MikeKilby wrote Feb 8, 2012 at 11:25 AM

I would find this function incredibly useful. Looking at database, I can set the folder location I want by editing the row in SQL but as soon as I save from the UI, the value is overwritten, so it's probably a fairly simple change to pick up the portal or prompt the user for a save URL?

If I can I will help to implement this.

wrote Feb 13, 2013 at 5:29 PM