Seafile server 7.0 is ready! (Including the CE and PRO edition)


#22

Have some UI issues after upgrade from 6.3 CE to 7.0.2 CE

ICON Display Issues on Toolbar

SOLVED: thanks to Cisco A simple delete of browser cache solved it. had to do ti on all browsers


#23

It is a feature like the OAuth feature via Google and it is turned off by default.


#24

Hi @daniel.pan

I have been testing Seafile Pro 7.0.3 for a week now.

On mobile devices (like iPhone 8) your rewritten UI seems not quite production ready.

I also noticed that saving markdown files after editing them in the WebUI works but users get an error.
I am getting the following error in nginx:

2019/06/21 07:11:11 [error] 22352#22352: *20361 upstream prematurely closed connection while reading upstream, client: XXX.XXX.XXX.XXX, server: XXXXXX, request: "POST /seafhttp/update-api/c0889161-8950-410d-8ea6-9bf6851c6d2c HTTP/2.0", upstream: "http://127.0.0.1:8082/update-api/c0889161-8950-410d-8ea6-9bf6851c6d2c", host: "XXXXXXXX", referrer: "https://xxxxxxxxxx/lib/dc26e32b-71b9-4273-bc64-202af6fb6ba8/file/test.md"

Furthermore I am not able to replace an existing file using the WebUI. I am able to upload a file once. If I reupload the same file and choose to replace the first one I am getting the following error.

I am using Firefox for testing. Seafile runs on Debian.

Thanks a lot for your constant development.


#25

Found an issue:
Server: CE 7.0.2, Client: WIndows 7.0.0
When i select a library in the client and go to -> view on cloud, the link just takes me to the library overview of all my libraries rather than the library i wanted to see. Url seems to be valid tough.

URL: #common/lib/326c1496-ea18-47ff-bfb4-9f483376fb44/
Looks like a seahub issue


#26

The URL for libraries is changes. We will look into the problem.


#27

Thanks for the new features and Seafile version 7.

Can you please provide change logs with every release? With every update something changes.
Old features are dropped or new added, sometimes without documentation anywhere. Changes like different URLs are no minor change and break many things.
Generally speaking even if this doesn’t apply to 7.0.0:
Minor updates shouldn’t contain any changes at all, they are supposed to fix bugs or close security holes. The community said this several times over the last years, but nothing seems to have changed. This is one of the big points that keeps customers from using Seafile: there seems to be no defined way how you develop Seafile and it seems that you don’t work with any know release cycle standard. It’s more like you release whatever is ready or what you can squeeze into a new release.
I am very sad that there are no changes at all regarding this. Don’t you want to sell more Seafile licences?


#28

After upgrading from 6.x to 7.0.1, seafdav wouldn’t start anymore. The reason was a new dependency, sqlalchemy, which is not documented. Things like this are also hard to debug, because startup errors don’t appear in any log file.


#29

The newest version is 7.0.2. 7.0.1 is a beta release.


#30

I know, and I upgraded before 7.0.2 was out. I’m just assuming that the stable release still depends on sqlalchemy and when I checked the manual before writing this post yesterday, I wasn’t able to find a reference to it. It would be great if you could update the manual!

Thanks,
Markus


#31

THIS!!! 100%!!!


#32

Thanks for the UI upgrades with v7.

Unfortunately the MEDIA_URL setting is now ignored, which breaks installations that do not run at web root. Seafile now uses the /media folder again instead of the MEDIA_URL setting, breaking existing reverse proxy setups.

Also Avatars are somehow served via HTTP url instead of HTTPS, even if every single root setting is set to HTTPS. This breaks my setup due to restrictive CSP that forbids non-HTTPS items.


#33

Hi @Manuel , have you found any workaround for this?


#34

@jobenvil Yes, I have updated my Nginx config to fix the MEDIA_URL setting temporarly and I am living with the broken avatars as it’s not critical for operation (allowing plain HTTP is a no-go for me)


#35

The avatars problems should have be corrected in 7.0.4.


#36

Hi @daniel.pan, thanks for the update. I can confirm that 7.0.3 fixes the avatars. Any news about MEDIA_URL settings? Is a fix for this regression planned?


#37

If you use a non-root, you can set SITE_ROOT. Please try if this can solve your problem.


#38

@Manuel Strange, do you really mean “7.0.3” or 7.0.4? For me 7.0.3 (which is the highest release for CE) is not solving the avatars issue.


#39

@jobenvil No, I mean 7.0.3 CE. I haven’t checked the profile page, it’s inconsistent.

The small avatar at the top right now loads correctly from a relative URL, but it’s using the root path - so it’s ignoring MEDIA_URL settings which I fixed by updating my Nginx config.

The profile page on the other hand is still using the MEDIA_URL setting which is now broken because my updated my Nginx config. :woman_shrugging:

@daniel.pan The value of SITE_ROOT in seahub_settings.py is already set to /seafile/

I will wait for 7.0.4 before I touch anything again. It’s not worth to me to fix this small inconsistency if an update will fix it soon.


#40

I have the same configuration inside of seahub_settings.py for non root domain.
Yes, it’s not worth to me too. I can live with broken avatars until 7.0.4.


#41

Have you tried to remove Seahub cache? The problem should have already been fixed in 7.0.3.