Directory sharing breakdown between nextcloud and owncloud

hi,

I shared a friend in owncloud-times a directory, he imported it with the button on the top right corner about 3 years ago, so its in his oC instance.

I switched to NC and updated it as he stayed with oC and does sometimes some security updates or so.
I think is is still at version 7 or so in.

Today I got the following error messages in my NC instance: (I have my nextcloud still in the old owncloud directory because moving it is more a hassle than kepping it there)

call_user_func() expects parameter 1 to be a valid callback, class 'OCA\Richdocuments\Storage' not found at /var/www/owncloud/lib/private/legacy/hook.php#106

and

Error while running background job (GuzzleHttp\Exception\ServerException): Server error response [url] https://owncloud.DOMAIN.TLD/ocs/v2.php/apps/activity/api/v2/remote/SHARINGURI [status code] 500 [reason phrase] Internal Server Error
/var/www/owncloud/3rdparty/guzzlehttp/guzzle/src/Subscriber/HttpError.php - line 32: GuzzleHttp\Exception\RequestException create(Object(GuzzleHttp\Message\Request), Object(GuzzleHttp\Message\Response))
/var/www/owncloud/3rdparty/guzzlehttp/guzzle/src/Event/Emitter.php - line 108: GuzzleHttp\Subscriber\HttpError->onComplete(Object(GuzzleHttp\Event\CompleteEvent), 'complete')
/var/www/owncloud/3rdparty/guzzlehttp/guzzle/src/RequestFsm.php - line 91: GuzzleHttp\Event\Emitter->emit('complete', Object(GuzzleHttp\Event\CompleteEvent))
/var/www/owncloud/3rdparty/guzzlehttp/guzzle/src/RequestFsm.php - line 132: GuzzleHttp\RequestFsm->__invoke(Object(GuzzleHttp\Transaction))
/var/www/owncloud/3rdparty/react/promise/src/FulfilledPromise.php - line 25: GuzzleHttp\RequestFsm->GuzzleHttp\{closure}(Array)
/var/www/owncloud/3rdparty/guzzlehttp/ringphp/src/Future/CompletedFutureValue.php - line 55: React\Promise\FulfilledPromise->then(Object(Closure), NULL, NULL)
/var/www/owncloud/3rdparty/guzzlehttp/guzzle/src/Message/FutureResponse.php - line 43: GuzzleHttp\Ring\Future\CompletedFutureValue->then(Object(Closure), NULL, NULL)
/var/www/owncloud/3rdparty/guzzlehttp/guzzle/src/RequestFsm.php - line 134: GuzzleHttp\Message\FutureResponse proxy(Object(GuzzleHttp\Ring\Future\CompletedFutureArray), Object(Closure))
/var/www/owncloud/3rdparty/guzzlehttp/guzzle/src/Client.php - line 165: GuzzleHttp\RequestFsm->__invoke(Object(GuzzleHttp\Transaction))
/var/www/owncloud/3rdparty/guzzlehttp/guzzle/src/Client.php - line 150: GuzzleHttp\Client->send(Object(GuzzleHttp\Message\Request))
/var/www/owncloud/lib/private/Http/Client/Client.php - line 204: GuzzleHttp\Client->post('https //ownclou...', Array)
/var/www/owncloud/apps/activity/lib/BackgroundJob/RemoteActivity.php - line 89: OC\Http\Client\Client->post('https //ownclou...', Array)
[internal function] OCA\Activity\BackgroundJob\RemoteActivity->sendActivity('HISUSER@ownclo...', 's0IBEUWoI0FA412', '/ToA/Charakter....', 'file_deleted', 1507530884, 'MYUSER@cloud.r...')
/var/www/owncloud/apps/activity/lib/BackgroundJob/RemoteActivity.php - line 45: call_user_func_array(Array, Array)
/var/www/owncloud/lib/private/BackgroundJob/Job.php - line 59: OCA\Activity\BackgroundJob\RemoteActivity->run(Array)
/var/www/owncloud/lib/private/BackgroundJob/QueuedJob.php - line 43: OC\BackgroundJob\Job->execute(Object(OC\BackgroundJob\JobList), Object(OC\Log))
/var/www/owncloud/cron.php - line 124: OC\BackgroundJob\QueuedJob->execute(Object(OC\BackgroundJob\JobList), Object(OC\Log))
{main}

which went away, after he updated or patched his oC-instance, so it came to my mind when will it happen that Nc and oC are so far apart, that that sharing feature will stop working between both applications?

ownCloud and Nextcloud are following an Open Standard called: OpenCloudMesh https://wiki.geant.org/display/OCM/Open+Cloud+Mesh
Have seen commitments from both sides to adhere to the standard and the standard is developed under leadership of a European Union organization named Geant.
It is also adhered to by Pydio and others are welcome to join.

So as long as Nextcloud or ownCloud are not breaking away from the standard we and all of our users will be fine.

1 Like

thats nice to read, so that was a different issue, which gone away.