| Commit message (Collapse) | Author | Files | Lines |
|
new: upgrade script from 1.7.0. Instead of previous upgrade scripts, I call
directly the "unit" upgrades from 61 to current. Previous upgrades not in
the database are inserted but not applied (and have an explicit description
saying so).
git-svn-id: http://piwigo.org/svn/trunk@2768 68402e56-0260-453c-a942-63ccdbb3a9ee
|
|
git-svn-id: http://piwigo.org/svn/trunk@2516 68402e56-0260-453c-a942-63ccdbb3a9ee
|
|
bugged (r2297 was repeating new and old header).
By the way, I've also removed the replacement keywords. We were using them
because it was a common usage with CVS but it is advised not to use them with
Subversion. Personnaly, it is a problem when I search differences between 2
Piwigo installations outside Subversion.
git-svn-id: http://piwigo.org/svn/trunk@2299 68402e56-0260-453c-a942-63ccdbb3a9ee
|
|
git-svn-id: http://piwigo.org/svn/trunk@2297 68402e56-0260-453c-a942-63ccdbb3a9ee
|
|
o use of l10n_dec
o normalize file header
git-svn-id: http://piwigo.org/svn/trunk@1932 68402e56-0260-453c-a942-63ccdbb3a9ee
|
|
git-svn-id: http://piwigo.org/svn/trunk@1931 68402e56-0260-453c-a942-63ccdbb3a9ee
|
|
install/upgrade_1.6.2.php is really new, upgrade 60 was taken into
account. Detection of 1.6.0 or 1.6.2 data model in upgrade.php. Release
upgrade scripts added on trunk to be kept in a safer place.
git-svn-id: http://piwigo.org/svn/trunk@1927 68402e56-0260-453c-a942-63ccdbb3a9ee
|