[Owncloud] updater.php error: Access to undeclared static property: OC::$APPSROOT
chymian
chymian at gmx.net
Fri Nov 16 23:51:34 UTC 2012
hi all,
Am 15.11.2012 16:12, schrieb Michael:
> Maybe we should add a ticket to update the updater - I think it is
> important that configs are backed in when updating(because it is
> automated, inexperienced admins don't think about doing their own
> backups).
I've opened ticket #498:
Issue:
updating an installation with updater.php moves the existing config out
of the way & creates new, empty one and therefor loses i.e. access to
the mysql-database, ...
happend on 4.5.1a
updater.php taken from 4.5.2
doublechecked on pristine 4.5.1 installation
workaround: copy your old config from
[OC-installdir]/backup/4.90.2*/core/config/config.php to
[OC-installdir]/config
change owner to your webuser: i.e. on debian: chown www-data.
[OC-installdir]/config/config.php
greetings,
günter
> Maybe a warning with a link on making a backup and how important it is?
> Mike
>
> On Thu, Nov 15, 2012 at 8:47 AM, Johan Hendriks
> <joh.hendriks at gmail.com <mailto:joh.hendriks at gmail.com>> wrote:
>
> Just a thank you for all the work.
>
> I think owncloud is doing well, but it needs to mature a bit more.
> Mature in the department off releasing, documentation and so on.
> If things settle down in the future there is more time to do more
> testing.
>
> If users are getting angry it is not a good sign, but people need
> to test it first.
> Even debian quality software needs testing on a test machine or a
> test environment before you run an upgrade.
> running a upgrade over an installation without testing could get
> you in trouble.
>
> Well we all learned something :D
>
> gr
> Johan
>
>
>
>
>
>
>
> Victor Dubiniuk schreef:
>> Hi Günter,
>>
>> I spent some time writing README. It is available in the app
>> directory and on the github
>> https://github.com/owncloud/apps/tree/master/updater
>> In short:
>> - If it is not possible to create a valid backup of the files the
>> upgrade process won't proceed;
>> - Database connection detail are stored inside *config.php*. It
>> is not deleted on upgrade;
>> - All the files of the previous instance are stored inside your
>> backup.;
>> - Many 3rdparty apps won't work with the new version anyway since
>> they have maximal core version they are compatible with. So there
>> is no reason to leave them, moreover it may cause various issues
>> right after upgrade;
>> - There are good chances not to have 3rd party apps compatible
>> with X.Y.Z in the same day X.Y.Z is released;
>> - I have a full-time job and family and I spend evenings
>> upgrading different versions of numerous ownCloud instances in
>> order to make the upgrade process smooth enough.
>>
>> Please accept my apologies for all the inconveniences you had.
>>
>> ---
>> Victor
>>
>> On Thu, Nov 15, 2012 at 4:14 PM, Jan-Christoph Borchardt
>> <hey at jancborchardt.net <mailto:hey at jancborchardt.net>> wrote:
>>
>> How can this be fixed to not happen in the future? There
>> should be an
>> upgrade path for the config, and in the worst case just
>> automatically
>> a backup be made, right? Also the LDAP config needs to be
>> preserved (I
>> presume it should already, maybe that’s a bug)?
>>
>> Can you please file these issues in the tracker at
>> http://github.com/owncloud/core/issues – that way we can not
>> only help
>> single people via the mailing list, but fix it for everyone.
>> Thanks!
>>
>>
>>
>> On Thu, Nov 15, 2012 at 2:00 PM, chymian <chymian at gmx.net
>> <mailto:chymian at gmx.net>> wrote:
>> > Am 15.11.2012 13:48, schrieb Mark Ziegler:
>> >> Am 15.11.2012 13:28, schrieb chymian:
>> >>> propbably, there came a new config with the update, which
>> destroyed
>> >>> the old one. and the updater did not make any backup of
>> the config file.
>> >>> WTF!
>> >>>
>> >>> I'm not very happy with this!!!
>> >> Who would be happy? But I am sure you made a backup
>> before, so no need
>> >> to be rude ;-)
>> >
>> > your right, I'm sorry about the WTF!
>> >
>> > but software, which destroys itself is not very nice
>> either! and
>> > produces a lot of work and debugging at the admin side.
>> > and should definitely be marked as alpha-state!
>> >
>> > [rant on]
>> > as I'm used to debian-state of quality, this is very
>> unusual behavior.
>> > but that seems to be normal with KDE!
>> > sorry, I'm a bit pissed
>> > [rant off]
>> >
>> > günter
>> >>
>> >> Mark
>> >>
>> >> _______________________________________________
>> >> Owncloud mailing list
>> >> Owncloud at kde.org <mailto:Owncloud at kde.org>
>> >> https://mail.kde.org/mailman/listinfo/owncloud
>> >
>> > _______________________________________________
>> > Owncloud mailing list
>> > Owncloud at kde.org <mailto:Owncloud at kde.org>
>> > https://mail.kde.org/mailman/listinfo/owncloud
>> _______________________________________________
>> Owncloud mailing list
>> Owncloud at kde.org <mailto:Owncloud at kde.org>
>> https://mail.kde.org/mailman/listinfo/owncloud
>>
>>
>>
>>
>> _______________________________________________
>> Owncloud mailing list
>> Owncloud at kde.org <mailto:Owncloud at kde.org>
>> https://mail.kde.org/mailman/listinfo/owncloud
>
>
> _______________________________________________
> Owncloud mailing list
> Owncloud at kde.org <mailto:Owncloud at kde.org>
> https://mail.kde.org/mailman/listinfo/owncloud
>
>
>
>
> _______________________________________________
> Owncloud mailing list
> Owncloud at kde.org
> https://mail.kde.org/mailman/listinfo/owncloud
More information about the Owncloud
mailing list