-
Notifications
You must be signed in to change notification settings - Fork 663
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
Provide space_ref to share requests when using spaces #10845
Comments
Ocis responds with an error and we fallback to "displaying the share ui" which with ocis is the web.
|
On the same space, some files work others not. |
Where is the error? |
|
@individual-it @ScharfViktor please re-test with the oCIS 3.0-rc2 later today. (rc1 had a caching issue) |
retried with ocis 3.0 rc2 and client 4.0 rc2 and the issue persists |
We noticed that using the I only see /01.jpg in the request but how should the server know which space is meant? Web now uses a I'll take another look Tomorrow... |
This is definitely a missing |
@butonic how can clients know? oCIS announces oC10-style public links in
|
Well, how do they detect that spaces are available? Space support makes it necessary to send a space in addition to the path so the server knows which space the path belongs to. |
Conclusion: not a blocker because the user experience does not break. Opening the WebUI is a good fallback. To achieve creating a public link on the client side would need client side changes. |
@michaelstingl Can you transfer the issue to the client repo? |
Addition: needs to be documented -> Server Team |
@TheOneRing @fmoc so, we'll send the |
To check for spaces support: client/src/gui/accountstate.cpp Line 552 in e4ae053
|
When I send a get request with the
Note: I created a new space called "New space", and put a file "README.md" in it. |
Oh the old code performs two requests, it lists the existing shares and creates a new one if it didn't exist. |
Can you point out where the two requests are made in the old code? |
( client/src/gui/socketapi/socketapi.cpp Line 615 in 92f5d98
client/src/gui/socketapi/socketapi.cpp Line 570 in 92f5d98
Please don't use the deprecated ShareManager |
Could you please provide an example query? |
@micbar ^ |
What we did before:
Now, we ask for existing Shares, and the response look sane:
(no existing share ✅ ) |
Creating the Share with
@micbar @butonic how should the request look like? Link to docs? Full HTTP:
|
Web does this:
Copy as cURL from Web Inspector:
Tested with:
|
Seems
What exactly does cs3org/reva#4004 fix? |
Conclusion
oc10 compatibilityThe ocis (bad ocs API experience, will be replaced by graph ASAP)On the backend, we identify resources by a Reference (https://cs3org.github.io/cs3apis/#cs3.storage.provider.v1beta1.Reference) Easiest solutionUse the So the easiest way to go, is to use the OptionalLike in the mentioned CS3 Api docs, you could also use the id and a relative path. |
@micbar thanks for the recommendation. I'll coordinate across clients. Desktop client team decided to kill the |
@erikjv please disable the context menu entry if account->supportsSpaces is true. |
Resolved by and tested in #11079. |
Pre-submission Checks
Describe the bug
When clicking on "Create and copy public link to clipboard" from the context menu the user is lead to the webUI of ocis instead of a link being created.
This happens only after the first start of the client after connecting a new space, after a restart it works fine.
Expected behavior
I expect to get a public link in my clipboard
Steps to reproduce the issue
OCIS_URL=https://192.168.56.1:9200 ./ocis-3.0.0-rc.1-linux-amd64 server
ict
)Create and copy public link to clipboard
=> browser opens and leads to the webUI
If the desktop client is restarted, the action works as intendedScreenshots
No response
Logs
ownCloud.log
Client version number
ownCloud 4.0.0.10732-rc1
Desktop environment (Linux only)
No response
Client package version and origin (Linux only)
No response
Installation path (Windows only)
c:\Program Files\ownCloud\
Server information
ocis 3.0.0-rc.1
Additional context
No response
The text was updated successfully, but these errors were encountered: