New Library in Web-Frontend (Seafile 12.0)

Hi there

I am unable to create new libraries by a user. Can’t find a button or menu to create one. Is it me or is there something wrong? :wink:

Cheers

You can find the menu for creating library at:

We will improve the design in a later release.

2 Likes

I just migrated to v12 today and this may be user/config error @daniel.pan but I’m not seeing that drop down option on Safari Version 18.1.1 (20619.2.8.11.12), or the drop down on the Create Wiki. It shows fine in Chrome though.
I disabled safari extensions to verify. I’ll follow up if I find problem.

Updated to v12, Wiki, Seadoc & OnlyOffice integrations are all working fine behind directly Traefik. Thanks for the comprehensive docs and support @daniel.pan
I can confirm I still dont see the drop down on new Library or new Wiki though which I think is related to Safari as i see them fine on Chrome.

Thanks for reporting the issue. We will check it.

Thanks for reporting the issue. Thank you for your support for Seafile 12.0 version.

I checked and did not reproduce this issue. I did not reproduce this issue when accessing cloud.seafile.com on the Safari browser. (My Safari version 17.4.1 (19618.1.15.11.114))

There may be the following reasons causing your problem, please check your browser:

  1. The default user role can create wikis, but Guest users cannot create wikis. Please check if the user roles in your Chrome and Safari browsers are the same.

  2. I saw in your screenshot that the font size in the upper left corner is too large (This font size is larger than cloud. sefile. com). Is there a custom CSS style available? If you customize CSS styles, it may affect the icons here. You can try removing the custom CSS styles and clearing the browser.

If there are still any issues, please provide your browser version and operating system type so that we can further investigate as soon as possible.

This user can create Wikis, verified in Chrome. The icon functions, and the Wiki works as expected, it just the drop down icon doesn’t display. See screenshot below. There is no custom CSS on this server.

OSX Sequoia 15.2
Safari Version 18.2 (20620.1.16.11.8)

I’ll sign up on cloud.seafile and verify in a moment

I can verify it displays correctly on cloud.seafile. Thanks for the suggestion/link.

Ok, I will test the display of the drop down icon in Safari 18.2 (20620.1.16.11.8) soon.

I think this was an error introduced by polluting some safari cache as part of my migration work towards v12. Since clearing my caches things are working as expected. Thanks for support here.

You’re welcome, thank you for your support of the new version of Seafile 12.0.

You have used Traefik. Could you help me with Nginx? Seadoc does not work for me. It can open a new sdoc file, but not write them because of http status code 403.

Heres my traefik section related to sdoc

    #seafile documents
    seafile-seadoc:
      rule: "Host(`seafile.xxxx.org`) && PathPrefix(`/sdoc-server`)"
      entryPoints: ["web-secure"]
      middlewares: ["seadoc-strip-prefix"]
      service: seadoc
      tls:
        certresolver: mydnschallenge
        domains:
          - main: "xxxx.org"
            sans: ["*.xxxx.org"]

    seafile-seadoc-socket:
      rule: "Host(`seafile.xxxx.org`) && PathPrefix(`/socket.io`)"
      entryPoints: ["web-secure"]
      service: seadocsocket
      tls:
        certresolver: mydnschallenge
        domains:
          - main: "xxxx.org"
            sans: ["*.xxxx.org"]

Thank you very much. I just noticed that the configuration of one reverse proxy cannot be transferred to that of another. In any case, I cannot find the error in the code for Traefik that crept into the Seafile documentation. The problem was the correct use of the slash.

I followed these instructions: Use other reverse proxy - Seafile Admin Manual and copied the code for Seadoc with copy&paste.

Later I looked here SeaDoc Integration - Seafile Admin Manual and saw that the line proxy_pass for the location /socket.io does not ends with a slash, unlike in the first link. I applied this and hey presto, what had previously simply not worked for hours suddenly worked.

While writing this answer I saw that the documentation had been adjusted. At this time, the instruction in both documents is exactly the same and correct.