Great : nomore pics ! :( (Upgrade 1.3.1 > 1.3.2)

[Rodinou]

Only things done

1. I have downloaded 1.3.2

2. I have backuped config.inc.php and anycontent.php and don't erase the album dir

3. I have all uploaded

4. I have run update.php

5. All seemed to work well

6. I go on Coppermine and NO MORE pics are available !!!



What's wrong ? The first time I upgraded Coppermine (1.2.x to 1.3.1) all worked fine

[Rodinou]

OK : update has erased all the cpg11d_pictures

great.

[Casper]

Please explain exactly what has been erased, the database tables, are they erased, or empty.

This should certainly not happen.  Are the pics still in the albums directory?

[Joachim Müller]

temporarily remove the blocking of folders to be browsed, I was trying to look at your files, but when entering a location where pics should reside (e.g. http://www.sortons.net/photos/albums/userpics/10010/ ), I get an empty screen (which is normally OK, but for trouble-shooting the htaccess policy should be disabled).

Joachim

[Rodinou]

I have erased my .htaccess but you cannot however browse ... it's weird

simply : the cpg11_pictures is ...

Espace utilisé :
Type    Espace
Données    0    Octets
Index    3 117    Ko
Total    3 117    Ko
        Statistiques :
Information    Valeur
format    dynamique
Enregistrements    0
Suivant Autoindex    38 318

Of course ... I cannot "surf" on this table, because the function "BROWSE" is not available on this table ...

I'm very sad (of course I have no backup, otherwise it would be not funny !!!)



PS : even if you can't see the pic (me too !!!), all the directories, pictures, thumb, normal pics are safe ... it's the database which has not appreciated the update ...

[Rodinou]

My host has made a recover, and all works fine again ...

but ... a lot of people can have THIS problem : try to see how it's possible !

[Casper]

This is the first time this has been reported, and there is nothing in the update that would empty or drop the pictures table.
Please explain exactly what you did, all the steps, so we can try and replicate it.

Having said that, I think we should make it clearer in the upgrading section of the docs, that a creating a backup of the database is essential in case the database breaks during the update.

EDIT, I have added an extra warning to backup the db in the docs, committed to stable and devel (the devel will need re-writing before release of 1.4).