Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

All other Modules

Discuss all other Modules here.

Moderators: martimiz, Sean, biapar, Willr, Ingo, swaiba, simon_w

Gallery error in published site


7 Posts   887 Views


25 March 2010 at 8:47am Community Member, 11 Posts

Hello everyone

XML tolkningsfejl: ikke well-formed adresse: http://localhost/galleri/ linje 83, kolonne 10:            <h3><% sprintf(_t('ALBUMSINGALLERY','Albums in %s'),Galleri) %></h3>
This i my error -which i don't understand - i have installed the modules from Uncle Cheeses page - with succes - but the "button" i my admin page for the gallery (where i add albums, pictures etc) i get the same "text error" in the button. But the site works, and so do the button.
But i cannot go to the gallery page.
I have added a album, added pictures. but no go to the published site. :-(

Hope you can help me



30 March 2010 at 6:34pm Community Member, 101 Posts


Which version of SS are you using



12 July 2010 at 12:29am Community Member, 161 Posts

I'm having exactly the same problem.

I am using SS 2.4 and it only seems to happen on Firefox.

Does anyone know how to solve this?


12 July 2010 at 4:45am 4085 Posts

Try the ImageGallery module!


12 July 2010 at 11:22pm Community Member, 161 Posts

UncleCheese... I *am* talking about the ImageGallery module.

The albums tab displays

<% sprintf(_t('DataObjectManager.ADDITEM','Add %s',PR_MEDIUM,'Add [name]'),an Album) %>

instead of the usual. But it only seems to happen in Firefox.


13 July 2010 at 2:57am 4085 Posts

That's a bug that's been around for a while. I've never quite figured it out. As a temporary fix, I've moved the translation function off the template and into the controller. I just checked in the fix. Run an update and give it another try.


30 July 2010 at 10:26am Community Member, 161 Posts

Sorry I've taken so long to reply: that project was put on the backburner and other stuff came up.

I'm having a look at it this morning and the problem seems to be fixed, at least on FF running on Windows.

Thanks very much, UncleCheese! :D