-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error sharing a Shared Folder #25464
Comments
owncloud/ios-legacy#704 could you check it @mcastroSG ? thanks! |
It happens to me on a 9.0.3 server upgraded from 9.0.2 in web ui, not tested on mobile clients. |
Maybe try setting "loglevel" to 0 and see if you get more messages in owncloud.log |
Is the shared file/folder originally on an external storage ? |
Hi @PVince81, the original folder is on external storage, sorry i forgot to mention it. |
@daorte please also give us more details about that external storage. The more info the better to be able to reproduce this. |
Ok Ok, 1- In filesystem i have a folder with this structure: The folder is owned by www-data and the group is www-data 2- With the admin account, configure an external storage with this params: 3- Log on with userOne, and can see the DATA folder, select it and share with UserTwo with all privileges 4- Log on with userTwo, and can see the DATA folder too (with the shared icon) I did change the log configuration and the message is the same: |
Hi! |
Just upgraded my test server to 9.0.4 and got the same bahavior. regards |
Server upgraded to 9.1 and still the same issue, i think it could be related to the ownership of the file, because it happens with a shared external storage. This is the log message in 9.1
|
More information: When sharing a link on a shared folder, the uid_owner and displayname_owner is the orginal owner of the file/folder, in this case userOne and then, when looking the node over user folder If i create a link with userTwo in a regular file/folder (not shared) the the uid_owner and displayname_owner is userTwo and then it can find the nodes correctly. |
Also observed here: Steps to reproduce
|
Follow-up: this is reproducible with Database users as well and not only LDAP ones |
this was working in 9.0.2 - stopped working in 9.0.3 |
@SergioBertolinSG may I ask you to write an integration test for this?
|
@daorte @nasli @mcastroSG please help testing #25703 |
* getJailedPath expects $path to have a trailing / - fixes #25464 * Adding test case for getPathById including a jailed cache where root is just empty
* getJailedPath expects $path to have a trailing / - fixes #25464 * Adding test case for getPathById including a jailed cache where root is just empty
* getJailedPath expects $path to have a trailing / - fixes #25464 * Adding test case for getPathById including a jailed cache where root is just empty
* getJailedPath expects $path to have a trailing / - fixes #25464 * Adding test case for getPathById including a jailed cache where root is just empty
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. |
Hi!
I think this issue is related to 704 on iOS project (don´t know hot to relate this with an issue located on other project) @nasli
After upgrading to 9.0.3.2 there is another problem sharing shared resources.
Steps to reproduce
Expected behaviour
The link of the shared resource should be created
Actual behaviour
Server configuration
Web server: Apache 2.4
Database: MySQL
PHP version: 7
OwnCloud: 9.0.3.2 upgraded from 9.0.2.2
Client configuration
Browser:
Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:47.0) Gecko/20100101 Firefox/47.0
Operating system:
Windows 8.1
Logs
ownCloud log (data/owncloud.log)
{"reqId":"sS6ysMKz2\/KHpqweRGG3","remoteAddr":"192.168.1.73","app":"PHP","message":"OCP\\Files\\NotFoundException: at \/var\/www\/owncloud\/apps\/files_sharing\/api\/share20ocs.php#110","level":3,"time":"2016-07-13T07:27:34+00:00","method":"POST","url":"\/owncloud\/ocs\/v2.php\/apps\/files_sharing\/api\/v1\/shares?format=json","user":"userTwo"}
The text was updated successfully, but these errors were encountered: