It could be that this fix will only work with DNN 3.2.  That's all I've tried it on in any case.  Some nice kind soul who was good enough to leave their IP address did manage to take down the Gallery I've had running on my site for the last three months or so. :)

I'm not sure if making the changes to the settings.ascx file will fix it if you are running DNN 4.

Yep, its dnn4 i'm getting the same error with too.

I only wanted dnn for its txt/html, forum and gallery... 6 weeks down the line, gallery still dead :(... time to delete it all i think.

(and install dnn3.2... *sob*... I wanted to play with dnn4+net2 over the hols)

I didn't test the gallery on 4.x aside from a single install which was based on 4.0.1.  Since the module is STILL beta, I thought it more important to just get a release out.  If you are using this on some mission critical site without really testing it, I think you are nuts anyways.  I would say the same for any module even if it wasn't in beta.  I don't think you should be switching to dnn 3.2 just because gallery.  If you need a gallery that bad, I don't think you should be using this one then considering it is STILL beta, unless you are willing to get your hands dirty in the code.  With all module available from core now, the only development enviroment is still in 1.1 framework, so its not like you will be truly getting your hands dirty in 2.0 unless you are working on the core or webcontrols projects.