Fix invite guest for new sharing flow

[nfebe]

Resolves : #40172
Resolves : #40299

[nfebe]

/compile amend /

[AndyScherzinger]

Important point here is the backport then, which from what I understood will differ from the main branch one.

[nfebe]

/backport to stable27

[nfebe]

Important point here is the backport then, which from what I understood will differ from the main branch one.

I did this on stable27 and realized it would work on master so decide to send the PR here at once, would backport to stable27 from this. (If your comment is related to this)

[blizzz]

conflicts and red cypress

[nfebe]

/compile amend /

[nfebe]

/compile amend /

[juliusknorr]

Tested and works

[artonge]

Rebased

[nfebe]

/compile amend /

[nfebe]

Threw in a commit to fix share entry alignments

Before	Now

[nfebe]

/compile amend /

[artonge]

Threw in a commit to fix share entry alignments

This commit will need to be backported as well, as the rest is already merged into stable27

[nfebe]

This commit will need to be backported as well, as the rest is already merged into stable27

Exactly! already did :)

[nfebe]

/compile amend /

[AndyScherzinger]

This commit will need to be backported as well, as the rest is already merged into stable27

Well this one is too late for 27.1.0 but would then go into 27.1.1 - it that a problem? @artonge @fenn-cs ?

[backportbot-nextcloud]

The backport to stable27 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable27
git pull origin stable27

# Create the new backport branch
git checkout -b fix/foo-stable27

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable27

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

[nfebe]

Well this one is too late for 27.1.0 but would then go into 27.1.1 - it that a problem? @artonge @fenn-cs ?

It went in via this backport : #40415 thanks to @artonge the only thing that didn't go with that is the alignment commit which is non critical and is already back-ported now too.

cc: @AndyScherzinger

[AndyScherzinger]

The backport et alignment we will probably need to dig in a bit deeper so it is also aligned with related resources (if present).

So I expect the alignment will see a further small update.

Do you happen to have a screenshot with shares and related resources?