Gallery v1.4 -RC2 and Gallery Remote v1.1-RC1 Available!
Submitted by beckett on Sat, 2003-08-30 21:10
The second *release candidate* for Gallery v.1.4, which fixes some critical bugs found in RC1, as well as the first release candidate for Gallery Remote v.1.1 are now available. This new version premieres some major new features: Gallery is now multilingual, and can be displayed in 18 different languages, with more on the way! In addition, we've completely overhauled the documentation and made it more accessible and more informative. Other changes include ownership of individual album items, not just of albums, and a slew of minor improvements and bugfixes.
Other changes for Gallery 1.4 include:
Download Gallery v1.4-RC2 and Gallery Remote 1.1-RC1 from the Gallery Download Page now!
Note: These are *pre-release* versions, and you should be sure to BACK UP YOUR GALLERY *before* installing and upgrading your current Gallery. Read on for information on how to back up critical data...
Other changes for Gallery 1.4 include:
- • Support for lossless JPEG rotation, and new "flip photo" options
• Image size and JPEG EXIF data can be displayed below photos
• Data loss prevented if disk space is exceeded
• Image dimensions and file size can be restricted
• Support for "*" wildcards in search field
• Add items to front or back of album
• Tons of other feature enhancements and bugfixes
Download Gallery v1.4-RC2 and Gallery Remote 1.1-RC1 from the Gallery Download Page now!
Note: These are *pre-release* versions, and you should be sure to BACK UP YOUR GALLERY *before* installing and upgrading your current Gallery. Read on for information on how to back up critical data...
We have provided a small PHP script with this version to assist you in making a backup. When you download and decompress this release, the script will be located in:
-
gallery/setup/backup_albums.php
The script gives you the option of backing up your entire albums ("All files") directory or just the Gallery database files ("Data files only"). While you should have a backup copy of all your photos, for most upgrades, it is sufficient to just back up the data files only. Note that backing up all the files could produce a *huge* file, since all of your photos will be included.
Finally, verify the contents of the downladed backup file to make sure the files were indeed saved. Once you have the data files backed up, you can confidently upgrade to this version.
Im getting-><br />
<br />
Fatal error: Call to undefined function: findinpath() in /home/httpd/vhosts/myhost.com/httpdocs/gallery/backup_albums.php on line 107<br />
<br />
after I copied backup_albums.php to my old gallery path. Do you copy all the files in /setup/ to gallery/ ? <br />
<br />
These notes only say to copy the one file.<br />
You need to install the latest version of Gallery, then copy that one file out of setup into gallery/<br />
<br />
Then run the backup. <br />
<br />
Then visit your gallery to upgrade.<br />
<br />
Sorry this was not clear.
Hi,<br />
<br />
upgrading from 1.3 worked fine, but no backups, i get the backup_albums.php alright (after reading the other comment, install first and then copy the file). But clicking on backup _does_ get me a 'safe file as'-box, but it fails (clicking either open or save-as).<br />
<br />
Apache (2)'s error log shows<br />
/usr/bin/tar: Removing leading `/' from member names<br />
<br />
indicating that indeed tar tried to do something, but no more ... maybe just overlooking something small, but it didnt work. Upgrading went smooth anyways so it's u&r on my site, but i didn't get it backupped properly (yeah, did a mysqldump and manually tarred some files, but not with the provided script).<br />
<br />
Cheers, (ow, and i can finally rotate pictures, using the old ones i could only do a '270' not 180/90, so thanx for the fix <br />
<br />
Tom
Are the font sizes in the style sheet fixed? In the previous versions of Gallery, the style sheet was using fixed size fonts rather than using relative sizes like percentages and ems. So the fonts wouldn't size bigger like I had set in my browser for my default font. It made it difficult to read. It was worse in IE where you can't resize fixed sized fonts at all.
Fatal error: Allowed memory size of 8388608 bytes exhausted at (null):0 (tried to allocate 12 bytes) in /var/www/slak/gallery/classes/Album.php on line 455<br />
<br />
This is the answer I get when I try to upgrade my albums. What should I change?
Ok, forget it The albums auto-updated themselves when i entered. Too bad i got like 200 of them :O
Next problem.. I entered a gallery with 465 pictures and got this:<br />
<br />
---<br />
snip<br />
---<br />
<br />
Upgrading item 465 of 465 . . . done.<br />
<br />
Fatal error: Allowed memory size of 8388608 bytes exhausted at (null):0 (tried to allocate 44 bytes) in /var/www/slak/gallery/util.php on line 1434<br />
<br />
---<br />
<br />
Something is weird..
Ehhh, how come RC2, view_photos.php around line 625 lost the addition of "array_shift($myExif)" in order to NOT display the server's filename? That's a security hole to give out the full filesystem info... or, you could just show the actual filename, stripping out the filepath.<br />
I'm just surprised because this was in cvs right after RC1.<br />
This is <a href="http://gallery.menalto.com/modules.php?op=modload&name=GalleryDocs&file=index&page=gallery1-install.faq.c.php#gallery1-install.faq.c.16">FAQ C.16</a>.<br />
Hrm... my guess is that code was transferred over from view_photo_properties.php and someone missed this important step. I've added the shift into view_photo.php for 1.4-RC3 and into CVS for 1.4.1, so this should be fixed.
To be honest, we still haven't sorted this all out. There was much migration to depend more on CSS, but some issues are still unresolved. For example, I believe specifying the "font" setting in an invididual album no longer has any effect, and it must instead be specified in the CSS files.<br />
<br />
Please file a <a href="http://sourceforge.net/tracker/?group_id=7130&atid=107130">bug report</a> with regard to what you think needs to be fixed and we'll be sure to have this sorted out for v1.4.1. To be honest, integrating the multilanguage capability has been our main focus for v1.4, and some other high priority tasks had to be bumped back.