I also commented on your Gemini post but will address this here as well: The DnnGrid automatically localizes its column headings using the HeaderText with ".Header" appended as the key into the parent control's localization resource file. Without providing a local resource file from which to pull the localized heading text, the column headings will indeed be empty.

I "think" (but have not verified from looking at the code) the reason this works when AutoGenerateColumns=true is that the setting of column header text to be the names of each column's DataField occurs during the databind after DNN's own localization of header text whould have occurred. If you create columns in the HTML markup and set a column's HeaderText to say "Name" but do not provide a localization resource file having a key of "Name.Header" and corresponsing value of "Name" you will also see that no header text is displayed for the column.

So, I don't see this as a "bug" but rather a design decision. It would be good if the DnnGrid would expose a property such as Localize to disable this automatic header localization in cases where the developer does not wish to provide a localization resource file.

 

---

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

I just ran into this issue too. There definitely needs to be a way to programatically override the localization feature.

---

David O'Leary
Efficion Consulting