Skip to content
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

"Exclude groups from sharing" checkbox broken on master branch #31739

Closed
jvillafanez opened this issue Jun 12, 2018 · 9 comments · Fixed by #33442
Closed

"Exclude groups from sharing" checkbox broken on master branch #31739

jvillafanez opened this issue Jun 12, 2018 · 9 comments · Fixed by #33442
Assignees
Labels
bug-analysis feature:sharing p2-high Escalation, on top of current planning, release blocker regression settings:admin
Milestone

Comments

@jvillafanez
Copy link
Member

Steps to reproduce

  1. Install ownCloud from github, master branch (9edd97a)
  2. Create several groups
  3. Go to the settings page, sharing section
  4. Mark "exclude groups form sharing" checkbox
  5. Try to exclude an specific group

Expected behaviour

Groups can be selected

Actual behaviour

The selection loads forever

screen shot 2018-06-12 at 18 02 09

It works fine on stable10

Server configuration

Operating system: ubuntu 16.04

Web server: apache 2.4

Database: mysql

PHP version: 7.0

ownCloud version: master

Updated from an older ownCloud or fresh install: fresh install

Where did you install ownCloud from: github

@PVince81
Copy link
Contributor

PVince81 commented Jun 12, 2018

@jvillafanez as discussed, please have a look if you can fix this as you're already in the topic.

Scheduling for 0.5md to find out

@ownclouders
Copy link
Contributor

GitMate.io thinks possibly related issues are #10307 (Exclude Groups from Sharing), #12824 (CI broken on master), #13402 (... broken), #7272 (Exclude subfolder from sharing), and #18512 (Master broken).

@phil-davis
Copy link
Contributor

I thought I had seen this problem a little while ago. Maybe there is another issue raised, but I can't see it.
Sharing autocomplete does queries like:

/ocs/v1.php/apps/files_sharing/api/v1/sharees?format=json&search=longname&perPage=200&itemType=file

The settings box uses:

/index.php/settings/users/groups?pattern=longname&filterGroups=1

In stable10 the query returns status 200 with happy data.
In master the query returns 302 - redirect ???
The problem is there with user_management app enable or disabled.

@jvillafanez
Copy link
Member Author

Confirmed the problem: the target route has been moved to the user_management app. It should be /apps/user_management/groups instead of /settings/users/groups.

Quick fix would need to install the user_management app and modify the "settings/js/settings.js" file so the ajax request goes to the new url.

We'll need to schedule time for a proper solution as this would create a dependency between 2 apps.

@PVince81
Copy link
Contributor

@jvillafanez thanks for the research, let's stop here for now.

@DeepDiver1975 seems we'd need to either move back the endpoint or add a second one.

@PVince81
Copy link
Contributor

this could be a blocker for moving out user_management as we cannot assume the app will always be enabled

@PVince81
Copy link
Contributor

setting to p2 as I think we should not release OC 11 without fixing this regression

@sharidas
Copy link
Contributor

sharidas commented Nov 6, 2018

A rough idea I have is:

  • Move lib/MetaData.php of user_management to core.
  • Also move the GroupsController from user_management to core, and adjust the routes.

@sharidas
Copy link
Contributor

sharidas commented Nov 6, 2018

Created PRs

@PVince81 PVince81 modified the milestones: development, QA Jan 11, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jan 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug-analysis feature:sharing p2-high Escalation, on top of current planning, release blocker regression settings:admin
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants