[Solved] Issue with Gallery 1.6 + CMSMS 1.11.2

[curlypinky]

I am having a weird issue with the Gallery 1.6 module and CMSMS 1.11.2.

Gallery works great in the backend but when I attempt to embed a gallery on the page and view it on the front end it is breaking the template. The content is displayed unformatted and no images are displayed. Looking at the source all the stylesheet and header data is gone. When you get to the part where gallery is called it starts out displaying the template and gets to the first image's link where it just cuts off at the href entry.

Code: Select all

<div class="gallery">
<h3>gallery name</h3><p>2 images</p>
<div class="pagenavigation">
</div>

	<div class="img">
	   <a class="group" href="

This is only happening in CMSMS version 1.11+ and is affecting 2 completely separate sites on a common server. Works for me in v 1.10.x. It doesn't matter what page template (tried NClean and my own) or Gallery template is used. Debug is giving me no clues.

Are there any requirements that Gallery needs beyond CMSMS 1.11.2 requirements? Does Gallery require php 5.3+? This server having issues is php 5.2.17.

A site on another server with php 5.3 is running cmsms 1.11.2 and latest gallery just fine (unfortunately I can't move this site).

Thanks!
Alane

[Jos]

Are there any requirements that Gallery needs beyond CMSMS 1.11.2 requirements? Does Gallery require php 5.3+?

I have never heard of any issues with Gallery running on php5.2 sofar... so it should run just fine.

I'd be happy to take a look at your site because of you know why thx for that...
Just provide me a temporary admin login via PM

[Jos]

Thanks for letting me take a look. It's a very strange issue, but I solved it

The gallery-templates contain smarty tags with escape modifier like
{$image->thumb|escape:'url'|replace:'%2F':'/'}

This was done to make Gallery compatible with the SuperSizer plugin. But yours site goes blank on it.

So I removed the |escape:'url'|replace:'%2F':'/' part everywhere from the default template.
I copied a page (not included in menu) where you can see it work.

I don't know why your site can't handle the escape/replace modifier, but why bother... it's working now

[curlypinky]

Thank you so much!! I really appreciate you taking a look at it and finding the solution for our particular issue!
Thanks,
Alane

[Jos]

you give some, you get some