News:

CPG Release 1.6.29
During HTML5 upload, keep pseudo blank code 200 messages from triggering error condition
added Russian language
correct failure to use theme menu icons in album manager
minor vulnerabilities mitigation

Main Menu

Upgrade went okay but....

Started by WarpGate, March 14, 2004, 12:11:38 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

WarpGate

Just a quick note to say I upgraded from 1.1 to 1.2 with no problems, it went as per documentation...

However.... (there is always a but...)

in displayplayimage.php I had to add back

{$image_size['geom']}

To stop the image being displayed wider than what was stated in the admin config screen ????

$pic_html .= "<img src=\"" . $picture_url . "\" class=\"image\" {$image_size['geom']} border=\"0\" alt=\"{$lang_display_image_php['view_fs']}\" /><br />";

Not sure if this has been said before, but without it the hardwired template went crazy if the images was wider than 700 pixels...

Anyway, thanks for an excellent script.......

See it @ http://www.warpgate.co.uk - A site for belly button lovers..

Joachim Müller

yes, hardwired sucks on larger images, as it uses a fixed absolute value (in pixels). If you're going to have larges images as intermediates, I recommend not using hardwired at all.

GauGau