Login button on share links

[Darkassassin07]

When visiting a share link, there used to be a login button in the top left corner that would redirect you to the main login page.

I frequently used this as I would create a user with a limited scope, share it's entire directory, saving that share link on several shared computers, then when needed use this login button to modify the contents of the share at whichever computer I happed to be at.

It's a small convenience over editing the url, but can we please have it back?

[gtsteffaniak]

Thanks for opening this issue. The OG filebrowser has had many requests to remove that button, but I see it makes sense for some people to include. 0.8.0 will revamp sharing and I can add this for tracking.

I could make this customizable with everything else.

[Darkassassin07]

@gtsteffaniak
This login button, once used, currently returns you to the share page you were browsing.
From there, there doesn't seem to be an obvious way to get to the rest of the now logged in users files; and, while browsing via the share link, despite being logged in, there is no access to file options (upload, create, move).

From the share page; If you click on the username/settings icon, opening the settings page, then close the settings; you are returned to the path '<host>/files' which displays 'this location can't be reached'.

I think it would make more sense to redirect to the users files/homepage on login, perhaps navigated to the file path of the share (if and only if they have permission to access it while logged in). This would negate both issues.

[gtsteffaniak]

Part of this is intentional. I want to make shares as secure and independent from the reset of the dashboard as possible.

But like any difference in preference, it should be configurable per-share.

I created this to address your concerns: #1137

[Darkassassin07]

@gtsteffaniak

The login button (clicking the username 'anonymous') on shares is no longer working at all with v.0.8.8-beta

[gtsteffaniak]

Yeah thanks for mentioning, it has been fixed in 0.8.9 dev branch, be on the lookout, I hope to release today