We are almost ready to launch, but still working through the development process. There is a lot to love about GSP. At this juncture, I'm wishing for a setup routine to restrict the data which the search function operates. As it operates now, information not intentionally placed in metadata yields a false positive. If the setup could allow a selection of fields to restrict the search, it would be a more useful function.

Overall, this module is delivering the results I had hoped and MORE!

The dev site (again, not ready for prime time) is at:

http://st.swifttechdesign.com/Home.aspx

When ready (hopefully Tuesday 10/4/2011), the URL will be:

http://shadetree-imaging.com/

TIA,
Jack

Paraphrasing Leonard H. "Bones" McCoy, "I'm a photographer, not a programer", so "Yes" I do mind hard coding a 'fix'. The attractive aspect of GSP and the modular approach to building in a dotNetNuke environment is the tools that allow me to 'make it my own' (so to speak). Hard code would mean that it could break in any upgrade I may wish to do in the future.

I do find it hard to believe that it would not be useful to *ALL*. Perhaps it just hasn't been noticed before. The administration tools already allow a selection of what Metadata to display. It seems a natural thing to add a property to the class (assuming OO design) and clean this up.

One of the downsides of the dnn modular approach is the need to 'settle' for the features offered. This appears to be another example of 'settling'. I regret that you don't feel any urgency to address this feature.

I read through the list prior to posting my 'suggestion'. Being that I'm late to the show, its hard to evaluate the impact of each of the items you placed up for the vote (though I did cast a vote for "Editable metadata/tagging"). The reason I did not vote for the skin, is that we found a work around (more 'settling'). It would have been nice to have some css interface for font colors that would show up better on something other than a white background.

Be well,