Federatedfilesharing application problem in apache2 log (OC 10.0.9)

[etienne-monier]

Hi !

My operating system is Raspbian GNU/Linux 9 (stretch).
My web server is Apache 2 v2.4.25.
Php version PHP 7.0.30.
Database is MySql MariaDB 10.1.

I used a OC version 10.0.3 stable but I have just upgraded to OC 10.0.9.

I followed the manual to upgrade OC. All worked very well until the end.

Arriving at the "Finalize the Installation" section, I realized that I could not reach the web interface. I have no web error, but just a blank page.

The OC log gives nothing at all, but the apache2 log gives

[Thu Jul 19 11:44:24.012790 2018] [:error] [pid 1090] [client x.x.x.x:x] PHP Fatal error:  Class OCA\\FederatedFileSharing\\FederatedShareProvider contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (OCP\\Share\\IShareProvider::updateForRecipient) in /var/www/owncloud/apps/federatedfilesharing/lib/FederatedShareProvider.php on line 958

I had a look on seach engines and I found that that could be caused by an app that is not up to date and that does not work yet wil the new version of OC. People tell to disable this app. But I understood that that app could not be disabled as that's a core app.

Help !

[ownclouders]

GitMate.io thinks the contributor most likely able to help you is @PVince81.

Possibly related issues are #23107 (New Install Problems (9.0.0)), #27778 (caldav/carddav syncing problem after upgrade to 10.0.0), #14683 (Problem with the email field (OC 8.0.0.7)), #23875 (Calendar: shared calendars have several problems after upgrade to OC 9.0.1), and #23925 (OC 9.0.1: Problems with the code integrity check).

[etienne-monier]

Well, I made it work. It seems I had a problem in the downloaded package. I downloaded OC 10.0.9 here, Resssources/Tarball/Production/10.0.9/Tar archive.

As I understood the Federatedfilesharing app caused the error, I downloaded the apps/federatedfilesharing folder in the github repo and I placed it in my OC folder located in my server.

After restarting apache2, it works.

Conclusion: close this issue, but look at the .tar.bz2 file I described before to be sure there is no problem ...

[PVince81]

I've checked the downloaded version and the md5 matches. It also matches the md5 from the tarball we used when testing.

Maybe you got unlucky and got a corrupt or aborted download. Strange that tar didn't tell you.
In any case, best is to always verify the md5/sha

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.