@Joffrey
Thank you so much for the minor upgrade. You were right about django-picklefield and this update essentially fixed the issue since you bundled it with the release.
Seafile is working for me once again, thank you :)
Git Clone URL: | https://aur.archlinux.org/seahub.git (read-only, click to copy) |
---|---|
Package Base: | seahub |
Description: | The web frontend for seafile server |
Upstream URL: | https://github.com/haiwen/seahub |
Licenses: | Apache |
Submitter: | eolianoe |
Maintainer: | Joffrey |
Last Packager: | Joffrey |
Votes: | 7 |
Popularity: | 0.000000 |
First Submitted: | 2017-07-03 09:48 (UTC) |
Last Updated: | 2024-05-09 09:15 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 13 Next › Last »
@Joffrey
Thank you so much for the minor upgrade. You were right about django-picklefield and this update essentially fixed the issue since you bundled it with the release.
Seafile is working for me once again, thank you :)
Hello @all,
For Seahub v7.1.4-2 you should to upgrade seafile-server directory with /usr/share/seafile-server in your instances, as a release change and execute minor-upgrade.sh after.
Best regards.
@kuzalj, It's Django-picklefield. The support of Django v1.11 was dropped, a downgrade to python-django-picklefield-2.1.1-1 temporarily fixes the problem. I'll look for a viable solution.
Not sure what I am doing wrong, but after running pacman and getting some python updates, I am getting an error on 7.1.4
TypeError at /
from_db_value() takes 4 positional arguments but 5 were given
Request Method: GET
Request URL: https://x.com/
Django Version: 1.11.25
Exception Type: TypeError
Exception Value:
from_db_value() takes 4 positional arguments but 5 were given
Exception Location: /srv/seafile/x.com/seafile-server/seahub/thirdpart/django/db/models/sql/compiler.py in apply_converters, line 832
Python Executable: /usr/bin/python3
Python Version: 3.8.3
Python Path:
['/usr/bin',
'/srv/seafile/x.com/seafile-server/seafile/lib/python3.6/site-packages',
'/srv/seafile/x.com/seafile-server/seafile/lib64/python3.6/site-packages',
'/srv/seafile/x.com/seafile-server/seahub',
'/srv/seafile/x.com/seafile-server/seahub/thirdpart',
'/srv/seafile/x.com/seafile-server',
'/usr/lib/python38.zip',
'/usr/lib/python3.8',
'/usr/lib/python3.8/lib-dynload',
'/usr/lib/python3.8/site-packages',
'/srv/seafile/x.com/seafile-server/seahub/seahub/api2/endpoints/../../../../../conf',
'/srv/seafile/x.com/seafile-server/seahub/seahub/api2/endpoints/../../../../../conf']
Yes, either of the change should be enough to fix the issue.
@yuyichao, I have make a test and I think this patch is enough :
- <form action="{% url view_name token %}?p={{ path }}" method="post" id="share-passwd-form">
+ <form action="{% url view_name token %}?p=/{{ path }}" method="post" id="share-passwd-form">
Thanks for debugging.
Glad it works.
..., you got the white space correct right?
Nah, you were right. That was wrong.
Oh, that repo.py
. I thought you are talking about some code you use... Whatever....
Just to state the obvious (if you are a python users), if you applied the patch manually, you got the white space correct right?
The way I found the error last time was to just put something like a
raise ValueError()
in seahub/thirdpart/django/views/defaults.py
at the beginning of server_error
. That either cause the server to quite or otherwise cause a full backtrace to be printed. The message from there should tell you what kind of error you got. I don't really see how the new code, with the only addition beting basically a comparison to empty string, should cause and error in this case....
Line 19/20
https://github.com/archlinuxcn/repo/blob/3844a0e73eff940e25e5d138f4d379d43ffbdb0a/archlinuxcn/seahub/fix_shared_link.patch
or
https://github.com/haiwen/seahub/issues/4440
Yeah, I don't know why the problem exists, I tested it before the update, after the update and after the patch. It only works with your patch.
Pinned Comments