Coppermine 1.3.1 has been released and is recommended for usage as stable version. Compared to cpg1.3.0, it doesn't contain any new features, it only fixes some known issues and has some additional language files.
All users who experienced issues with cpg1.3.0 are recommended to upgrade to cpg1.3.1
Get the package from the download section (http://sourceforge.net/project/showfiles.php?group_id=89658)
CPG1.3.0 Issues that were fixed in CPG1.3.1:- On batch add check filenames for non-permitted characters (http://forum.coppermine-gallery.net/index.php?topic=7249.0)
- Maintable bug ? (http://forum.coppermine-gallery.net/index.php?topic=7924.0)
- mistake in one of the sql files (http://forum.coppermine-gallery.net/index.php?topic=7927.0)
- wrong indented text at mainpage for "guest" (http://forum.coppermine-gallery.net/index.php?topic=7698.0)
- Last additions (http://forum.coppermine-gallery.net/index.php?topic=7462.0)
- Bugfix for theme RainyDay theme.php (http://forum.coppermine-gallery.net/index.php?topic=7017.0)
- E-card : missing internationalization (http://forum.coppermine-gallery.net/index.php?topic=6946.0)
- Unescaped variable used in SQL query in exif_php.inc.php (http://forum.coppermine-gallery.net/index.php?topic=7721.0)
- Lost user album thumbs on cat page (http://forum.coppermine-gallery.net/index.php?topic=6973.0)
- Strange handling of TIFF files (http://forum.coppermine-gallery.net/index.php?topic=4734.0)
- bug with "toprated" section in album view (http://forum.coppermine-gallery.net/index.php?topic=7315.0)
- Anonymus user can see Private album pictures (http://forum.coppermine-gallery.net/index.php?topic=6837.0)
- SMF Bridge problems (http://forum.coppermine-gallery.net/index.php?topic=5727.0)
- slash bug (http://forum.coppermine-gallery.net/index.php?topic=7128.0)
- Server side fav bug (http://forum.coppermine-gallery.net/index.php?topic=6974.0)
- Email password BUG (http://forum.coppermine-gallery.net/index.php?topic=6796.0)
GauGau
I just noticed that sf.net seem to have trouble with their download section - the release file hasn't been propagated to all download mirrors yet. Currently, the download results in a "404 not found" page. Please be patient and try to download later - hopefully sf.net will fix this issue soon.
[edit] Has been fixed, downloads are working [/edit]
GauGau
silly question ...
I have 1.30 installed and my gallery is active.
To install this new version of 1.31, all I do is overwrite the files thru FTP?
yes upload the new files and then run update.php for a good measure
GauGau,
I have miraculously succeeded committing a patch through the CVS. I've found out that the UTF-8 Hebrew file was not saved correctly so I committed a correct version. First of all I'd like to know if I *really* succeeded, and second is it included in 1.3.1?
By the way, CVS is acting up on me again and wouldn't check out. This is really strange because I can consistently check out from other SourceForge projects (that provide no-password read-only access). Ah, the hardships of life.
EZ.
you can easily find out if your modification has made it into the package: get the package, unzip it and look at the cvs version info (starting with $Id) - that's where the version, date and username of the last commit shows. In this case, the last commit was done by Tarique, this is what the line looks like:
Quote// $Id: hebrew-utf-8.php,v 1.7 2004/06/11 09:20:06 tarique Exp $
Apparently, the hebrew-utf-8.php has been tampered with, it will not work (*grr*).
Another way of checking the successfull commits is to browse the stable branch of the cvs with webcvs: http://cvs.sourceforge.net/viewcvs.py/coppermine/stable/lang/hebrew-utf-8.php?rev=1.7&view=log
OK, this means trouble: the utf-8 version of the hebrew language file is f*** up in the cpg1.3.1 package, will need another repair...
GauGau
GauGau,
Thanks. Of course I know that I can download 1.3.1 and check. Anyway my CVS rollercoaster is once again top side, so I managed to checkout and verify that my commit of hebrew/utf-8 was indeed accepted.
Eyal.
EZ, sorry, but your modification doesn't appear in the CVS stable: http://cvs.sourceforge.net/viewcvs.py/coppermine/stable/lang/hebrew-utf-8.php?rev=1.7&view=log , only in the devel branch: http://cvs.sourceforge.net/viewcvs.py/coppermine/devel/lang/hebrew-utf-8.php?rev=1.8&view=log
That's why I didn't go into cpg1.3.1
I'll have to look into this...
GauGau
0 bug for me !!! (... only One : the Pic Editor ... but if I want to edit my pics I use Photoshop ... so no problem for me)
What a lot of modifications !!!
However, you have not put my CSS hack on LONG TEXT description albums ... Shall I post again ? or include this in a XHTML version (tarique ?)
It might be useful if you update the link on your sourceforge home page, I've just spent the day customising 1.3.0 just to find 1.3.1 is out.
Cheers.
Quote from: Tarique Sani on July 16, 2004, 06:58:28 AM
yes upload the new files and then run update.php for a good measure
i just delete ALL files without the ALBUMS folder or ? what about those 2 config files which were created ? how i can tell cpg131 where my sql and password login is located blabla ? .
what does update.php exactly do . i did for testing reasons yesterday jsut for fun in cpg130 the update.php .. isnt dangerous or ? it doesnt delete something or when i run it while already using 130 ?
i just want to know how i can upgrade to 1.31 without loosing too much,i mean, i have to change after that my theme.php and my german language php .. nothing more . i compared my pending files with the orig. 130 files and only a few php files were changed.. mainly the ones (style.css, theme.php)which i edited myself .
i just want to be sure. cause i dont want to sit severals days again until the gallery works like i want hehe ;-)
hope you can help me
cu
raum
update.php will run the mySQL queries needed to reflect database changes. They are not grave. You would be able to run a cpg1.3.1 database with cpg1.3.0 files.
Like the instruction says: replace all files on the server with the files from the package. As the two files the installer creates don't exist within the package, they won't get replaced - the original ones will persist.
It's always advisable to do a backup before updating (both files and database).
GauGau
Nice to meet you.
I'm access from Japan.
CPG1.3.1 is running without any problem with in my personal computer (Windows2000).
I thank for very excellent CPG and this creator.
Thank you.
If you have installed the permanent watermark and you run this update is there still the automatic watermark or do I have to install that mod all again ?
I persume that the file information in the desdcription is stil there after you have installed the update?
since all modified files will be overwritten in order to perform an upgrade: you will lose all your mods that needed modification of core files.
GauGau
I updated to 1.3.1. but...
If I go to "Config" .../config.php
I see: "Configuration - Coppermine Photo Gallery 1.3.0"
Great I have updated the new version and yes the language thing is also fixed.
I notoced that the bug is still there regarding the Mod of the watermark.
It leaves red things in the picture.
The Deep link http://www.persfoto.com/database/displayimage.php?album=62&pos=1
can this be fixed in an other update or stays it stil mod releated
@Makc666: you haven't uploaded all files from the cpg1.3.1 package then.
@tqam: a mod is a mod. The standard package works, there's no guarantee for mods. Post on the mod's thread.
GauGau
Yes. I forgot to upload include directory.
Thanks!
Quote from: GauGau on July 23, 2004, 06:41:23 PM
@Makc666: you haven't uploaded all files from the cpg1.3.1 package then.
I have highlited show FAQ but it does not show up in the header.
Also the ITPC and EXIF does not show up. the buttons in the config are marked yes
@tqam: don't try to hijack this thread: it's an announcement of cpg1.3.1 being released, not your personal trouble-shooting thread. Do this the usual way: post in a separate thread (and only one question per thread please). Search the board first, maybe this has been answered already.
GauGau
I just upgrade from 1.3.0 to 1.3.1, but i still have the following problem:
If I start the browser (no matter Mozilla or IE) and login, the server always reply
"Site does not exist".
The problem is the following.
This is my Address:
mysubdomain.provider.com
coppermine is in mysubdomain.provider.com/gallerie/
so when i start the browser and login, coppermine want to forward me
to
mysubdomain.provider.com/mysubdomain/gallerie/
instead of
mysubdomain.provider.com/gallerie/
This fault only happens after the first time the browser is started.
If I logout and login again it will work properly.
:|
Read the previous post....This isn't a bug thread, it's a release thread. Start a new thread. Make sure you put a LINK to you site, at least.
-omni
I am still running 1.3.0. Is it possible to know what file changes were made instead of replacing the files? I have so many mods installed. :(
you could use a diff viewer to find out what actually changed. If you're on windows, I recommend Winmerge (http://winmerge.sourceforge.net/). That's one of the drawbacks of applying mods: upgrading becomes very hard, or nearly impossible, unless you're ready to lose all mods. I recommend putting comments into the code if you actually apply mods, so you can later find out what has been changed. You can however use your cpg1.3.0 theme with cpg1.3.1
GauGau
Cool. Thanks, I ll try winmerge. Any idea of which files were changed? I assume not all? :-\\
all of them were changed, but for some only the headers changed (so you could leave the old versions in place). Like I said: to see what files actually changed, you will have to use the diff viewer. We (the developers of coppermine) don't have a list of files where all changes are being noted, we use a software called "CVS" to do keep track of changes.
GauGau
I upgraded to the latest version. E-card issue is not fixed as well. Good work.
Btw, I went through each file in winmerge. Took me good hour or so but preserved the mods. Thanks! ;)
Quote from: DefenceTalk.com on August 09, 2004, 03:12:01 PM
E-card issue is not fixed as well. Good work.
Do you mean
QuoteE-card issue is not fixed as well.
or
QuoteE-card issue is now fixed as well.
?
GauGau
oh crap! :o
Sorry. big typo! I mean its fixed now.