try to fix regression with public file upload button

[szaimen]

On public link shares where files are editable, there the add button is broken after #39884. Fix this:

Before	After

[szaimen]

/backport to stable27

[szaimen]

btw @susnux the file/folder picker does not seem to work on public link shares currently... Or is it not merged yet?

[szaimen]

/compile amend /

[susnux]

@szaimen

the file/folder picker does not seem to work on public link shares currently... Or is it not merged yet?

Not merged for master currently.

[szaimen]

@szaimen

the file/folder picker does not seem to work on public link shares currently... Or is it not merged yet?

Not merged for master currently.

all right 👍

[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

[susnux]

/backport to stable27

[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

[susnux]

/backport 6226765 to stable27

[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

[szaimen]

#39921

[nickvergessen]

@susnux@szaimen

If there is compiled JS backporting mostly never works.

You can help yourself by having the compiling in another commit, by using /compile / (without the amend) and then only requesting the backport bot to backport the source code change only /backport <commit sha> to stable27. After the backport is done, you do /compile / there again.

[susnux]

@nickvergessen the last of my requests did not contain any compiled assets but still failed.

[nickvergessen]

Yeah sorry, it contains compiled CSS not JS. but same problem. all the scss files are reduced to a single line. so conflicts are just going to happen.
But also for compiled CSS the mentioned "trick" works.