I was not sure if this approach would work so I had to test it first. Because the ModuleSettings are heavily cached, for it to be successful it will require making the change to the the MaxThumbWidth and MaxThumbHeight settings in the database IMMEDIATELY followed by 1) deleting the image files from the _thumbs folder and 2) an application or IIS restart and clearing of the browser cache BEFORE revisiting the gallery page and resynching. If the gallery website is live, you should take it off line until after the resync is completed.

One other potential issue (and one of the reasons we decided to disable changing thumbnail size of a populated gallery): if you have more than 50 or a 100 or so images in the gallery or and particularly if the image file sizes are large, you may encounter an execution time-out server error. The processing time to resize each image and update the DNN files table with the new size information is very high. This operation really needs to be spun off onto a separate background thread but that introduces other potential problems.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner