I would check things like SELinux and similar.
--
Sent from: http://owncloud.10557.n7.nabble.com/Users-f1.html
___
User mailing list
User@owncloud.org
http://mailman.owncloud.org/mailman/listinfo/user
> More details can be found in the server log.
I guess this note in the posted message could give you a hint where to look
for possible problems.
> I'm upgrade from owncloud 8.2.1 to owncloud 9 then owncloud 10.
Why not following the previously given advise to go from 8.2.1 to 8.2.11 and
then
You can find some background info here:
https://github.com/owncloud/documentation/pull/4171/files
--
Sent from: http://owncloud.10557.n7.nabble.com/Users-f1.html
___
User mailing list
User@owncloud.org
What about using the selective sync folder shown on the screenshot here and
only sync the folders you want to have synced?
https://doc.owncloud.org/desktop/latest/navigating.html#configuring-owncloud-account-settings
--
Sent from: http://owncloud.10557.n7.nabble.com/Users-f1.html
In the last few weeks you got multiple times the information to not use the
updater app and to do the manual upgrade instead:
https://mailman.owncloud.org/pipermail/user/2018-April/002953.html
https://mailman.owncloud.org/pipermail/user/2018-April/002959.html
> mark them as explicitly unsigned and not to be checked?
Seems this will be possible with the upcoming 10.0.8:
Added config.php option to select apps to ignore missing signature file
(mostly for themes) - #30891
-> https://owncloud.org/changelog/server/
--
Sent from:
> I just wold like to upgrde from owncloud 8.2.1 to owncloud 10 but when I
want to start the ugrade to owncloud 10 I get this message :
You need to first update to 8.2.11 before you can upgrade directly to
10.0.7.
mod_fcgid: stderr: PHP Fatal error: Call to undefined function
> Otherwise you'll have to download and install the paket by hand.
This should be the recommended way as the updater app wasn't that reliable
back in the old days.
--
Sent from: http://owncloud.10557.n7.nabble.com/Users-f1.html
___
User mailing list
I think i had provided the required steps a few weeks ago in:
https://mailman.owncloud.org/pipermail/user/2018-March/002942.html
So follow this steps:
- Delete all files and folders in your existing ownCloud directory
(/var/www/owncloud) - except data and config.
- Don’t keep the apps
If you want a successful update of any pre-ownCloud 10 release you really
really shouldn't use the updater app and follow the manual instructions
pointed out previously:
https://mailman.owncloud.org/pipermail/user/2018-April/002956.html
--
Sent from:
I don't think that you need to search for an issue in the ownClouds code. The
message means that something (maybe old and not deleted code or apps or
stuff in your redis/memcache etc.) is declaring a class which already
declared previously.
It might help if you explain in detail which steps you
Hi,
the most common reason for such update/upgrade issues are that people
leaving old files left during the process. Did you
make sure to follow all steps provided in
https://doc.owncloud.org/server/latest/admin_manual/maintenance/manual_upgrade.html
and especially this one:
- Delete all files
And shortly after the previous mail i've noticed:
> owncloud core-stable9
The github releases are not meant to be run by users as there is more then
just downloading this branch required to
run ownCloud. I strongly suggest to switch back to the official releases
from
There is a files:transfer-ownership occ comand available you could use:
https://doc.owncloud.org/server/latest/admin_manual/configuration/server/occ_command.html#the-files-transfer-ownership-command
Might be possible that the outdated 8.2.11 doesn't provide this
functionality yet. But this
Doing the same on my ownCloud 10.1.0 installation shows an "internal server"
error page of ownCloud instead of the stack trace like happening at your
setup.
--
Sent from: http://owncloud.10557.n7.nabble.com/Users-f1.html
___
User mailing list
No special configuration in the config.php, just the plain one after the
ownCloud installation.
Shutting down the database is not possible as this is a live / productive
system but i guess i will also get the same generic/themed internal error
message of ownCloud without the full stacktrace.
IMHO upgrading to a recent version is the way to go here. 7.0.4 is way too
outdated to offer help for (if there is any help possible for 7.0.4 at all).
--
Sent from: http://owncloud.10557.n7.nabble.com/Users-f1.html
___
User mailing list
17 matches
Mail list logo
