sharing:list does not show circles shares and filter doesn't show public shares

Offen
  • Stimmt etwas nicht?
#461 1 Kommentar 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
42/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Veraltet
Tech-Stack
php
Bereich
backend, cli

Rechercherichtung

Beginne damit, die gemeldeten Befehle occ sharing:list -o csv -u Admin_ShareA sowie die ungefilterten CSV/JSON-Befehle zu reproduzieren, und vergleiche anschließend ihre Ergebnisse mit dem in der Meldung beschriebenen Workaround für die Datenbank. Die Arbeit ist abgeschlossen, wenn nach Benutzer gefilterte Auflistungen die relevanten Public-Link- und Circle-Shares enthalten und mit den erwarteten vier Ergebnissen im Beispiel übereinstimmen.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Using Nextcloud 27.1.8 and Sharelisting 1.2.0.

When I run "occ sharing:list" I do not see any shares related to circles.
When I run "occ sharing:list -u username" to find any shares related to user, I just see direct share to/from this users, not public links generated by this user or related to files owned by this user.

So share:listing report misses a lot of relevant information!

Below a more complete example with command outputs.

  • My user Admin_ShareA has folder called /Espai_ShareA shared with Circle_ShareA. There's a subfolder called "probando subcompartir", with a file called "asdfasdfasdf.md".
  • User "gonzalo" is member of "Circle_ShareA". He shares asdfasdfasdf.md with user "gcc2", with circle "gonzalo_circle". All shares are configured, tested and work properly.

Getting all Admin_ShareA related shares should be as simple as # occ sharing:list -o csv -u Admin_ShareA, and it should show 4 results:

  • Share of Admin_ShareA with Circle_ShareA
  • Share of gonzalo with user gcc2
  • Share of gonzalo with circle gonzalo_circle
  • Share of gonzalo with public link

But when I run:

# occ sharing:list -o csv -u Admin_ShareA
id,file_id,owner,initiator,time,permissions,path,name,is_directory,type,recipient
206,72420,Admin_ShareA,gonzalo,2024-04-30T12:36:10+00:00,19,"/Espai_ShareA/probando subcompartir/asdfasdfasdf.md",asdfasdfasdf.md,0,user,gcc2

No public share, no circle shares.

I tried again without filtering by user but using grep:

# occ sharing:list -o csv | grep  Admin_ShareA
205,72420,Admin_ShareA,gonzalo,2024-04-30T12:30:07+00:00,1,"/Espai_ShareA/probando subcompartir/asdfasdfasdf.md",asdfasdfasdf.md,0,link,G2yRQeBqSiYtZmz,"2024-05-06 22:00:00",
206,72420,Admin_ShareA,gonzalo,2024-04-30T12:36:10+00:00,19,"/Espai_ShareA/probando subcompartir/asdfasdfasdf.md",asdfasdfasdf.md,0,user,,,gcc2

Now I see the public link but not the circles shares. Also, this method is not valid for my productions system as I need to generate multiples report for users that have multiples shared spaces, links...
(using CSV just to make it easier to parse, but Json has the same results).

Sharelisting command is exactly what I need as I want to generate reports for a group of users that are acting as Share-units and I want to audit the sharing activity on those files. But is not possible if it's missing that public and circle shares. Currently I'm using a workaround querying directly database but I really would like to use this tool.

Is it possible to fix this stuff, or I'm doing anything in a wrong way?

Vorherrschende Sprache
PHP
Sterne
20
Forks
8
Ø Merge
7 Min.
Gemergte PRs (30 T.)
1

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus nextcloud/sharelisting

Alle Issues in nextcloud/sharelisting

Ähnliche Issues

Weitere Issues zu PHP

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.