I'm afraid I don't have a good answer for you on that one as the problem is not that the image file has not been "approved" but rather a logic error in the module's legacy code for populating an album with an internal lists of both "approved" and "unapproved" media files. In both the case of an image file that has been given a title of "icon" and one that has been given a title of "watermark", these files are added to the list of "unapproved" media files even when they have been approved - apparently to prevent them from displaying along with an album's other content.

It is possible to re-edit the title of the file (by navigating to Edit Album which does include these "special" files in the list of files). Once the title has been changed from "icon" back to its original value or an empty value, the file will again appear among the thumbnails, the "(1 unapproved)" will disappear from the statistics, AND this same image will continue to display as the album cover icon.

Apparently that issue had existed in the old v 3.00.12 gallery but I and other team members were unaware of it. I had even forgotten that the capability of "manually" setting the album cover image had existed and when I had done a major refactoring of the album folder population code, that was one section of code I had not touched.

Now that I know that this capability is important to some users, the Gallery team will be sure to consider the need to implement it properly - in the next version.

---

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

Sorry . . . I have no trick for custom sorting or different sort orders for albums vs files. You use of a number or prefix before the album name is about the only one I can think of.

Custom sorting and being able to have the albums appear either at the beginning or end of the gallery thumbnails is in the roadmap for a later version. We had considered implementing it for this version but it would have required major alteration of the legacy code the team inherited and can be more easily undertaken once we move from the current xml based metadata storage to a DAL using the site's database.

---

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