First of all I never implied it was simple.  Second of all, it IS quite simple. Some of code to provide this ability is already in the module, some of it has been removed. There doesn't have to be any confirmations, its just another one of the options for configuring the module.  I changed like 5 lines of code in my copy and now I can switch whether source is kept or not. I have to change the setting in the database directly as I did not take the time to add it to Settings.ascx, but I can control it now.

But, thirdly and my main point is, that Tam's post seemed to be implying that a user merely has to make a choice on whether or not to keep the source file and that is not correct. There is no config option for a user to decide whether to "keep source" or not and cannot switch it by editing settings in the database either. Its hard coded to always keep source (the third, pehaps un-needed copy) which is what the original post was commenting on.  But the option used to be there back when it was TTTGallery.

And lastly, I would have to say that storing metadata in a database about disk files has always been a bad experience for me. The code to keep disk vs. tables in sync is always a pain. Its far too easy to move, add, rename or delete a disk file and then the database is out of sync. At least as how the metadata is currently stored in the same folder as file, then when files are moved the metadata can travel with it.

I would much rather have the project team spend its time making features that are ABSOLUTELY required, such as the settings.ascx issue work and be available in a download than have the team write a bunch of sync code that may never be right and very easy to break.  I find it very irritating that a software product exists where the most basic function such as configuration flat out doesn't work as delivered when it takes all of 1 hour to change the code and make a new download package. And yet this known to be broken download is the only version that is available and every single user of it has to spend their own hour trying to figure out what is wrong, research the fix and apply it.

I have inadvertantly changed the topic here and I failed to make my point. I was trying to say that the "configuration" feature is what I would deem "absolutely required", not this "keep source" feature. You would agree that having the settings.ascx screen to set the options should at least open, right? I'd be surprised to learn of a user who wouldn't agree that in 100% of the cases that this basic ability should work.  Yet in the 3.0.11 download the first thing I do after adding the module to a page is go to "Configuration" and boom, error. Hmmm. it was OK in 3.0.10.

So, what me set off was that the most basic feature is broken and the time I wasted trying to figure out what I was doing wrong.  I eventually learn that someone has figured it out and that the fix doesn't even require a recompile. Yet, the 3.0.11 has existed for weeks with this serious flaw in it that affects all users who wish to even change just the title of their gallery. And a fix exists which requires very little regression testing and a new download could be built (changing only 1 file from 3.0.11) and save the entire community untold wasted time.   But instead the team is working on moving all the data into the database, which in the long run may be needed and a good idea, but in the short term seems to work just fine.  And I don't recall much discussion on this board about how painful its been without this and how much trouble the XML metadata solution is causing. I am doing DotNetNuke websites in my spare time as well and I would think you would want to spend your time on the most "bang for the buck" items.

tclaffy, if you're still reading, I'll post the code changes I made to allow the ability to choose not to keep the _source files. These are the largest of the three files. They are only needed if you want EXIF data to display completely (it displays only partial data without having access to the source image) and to allow "download" of large resolution source files. If the source is missing, then "download" delivers the resized file. My solution requires direct database editing to change the option as I didn't want to get into editing the UI.