Using 7.0.3 CE Version (compiled to raspberry pi)
FILE_SERVER_ROOT = 'https://xxxxx.xxxx.xx/seafhttp'
SERVE_STATIC = False
MEDIA_URL = '/seafmedia/'
COMPRESS_URL = MEDIA_URL
STATIC_URL = MEDIA_URL + 'assets/'
SITE_ROOT = '/seafile/'
# Since version 5.0.4 we need to define this as well:
LOGIN_URL = '/seafile/accounts/login/'
The config was not changed. Seahub cache (in my case memcached) was empty. I tried deactivating memcached as well, and flushing seahub_cache.
The feature request has been out there for quite a while… but there are also reserverations.
I, personally, am lukewarm about the combo link (up- and download). I think sensible use cases are rare. In any case, it can be emulated by two separate up- and download links.
What do you meen by “it can be emulated by two separate up- and download links”? In the pro version, if you enable write on share links, you can use onlyoffice with non existent seafile users via sharelink which is very convenient. You cannot emulate this by adding a different upload share link.
First off, I am talking share links for folders, because that is what @maweber inquired.
You seem to focus on file share links. That’s not what I was talking about.
Second, what I mean is very simple: You can create an upload and a download link for one and the same folder (or library for that matter). As a consequence, you can upload into and download from one and the same folder/library. Other sync & share solutions offer a combined / combo link feature for that purpose - which is more convenient. Does the convenience aspect make it a high-priority development? I don’t think so and that is why is it a nice to have at best.
The Share to User Menu has a little bug.
The list doesn’t show existing Users that a folder is shared to. Adding a user share works without problem, but the displaying dosn’t.