# In old version, if you use Single Sign On, the password is not saved in Seafile.
# Users can't use WebDAV because Seafile can't check whether the password is correct.
# Since version 6.3.8, you can enable this option to let user's to specific a password for WebDAV login.
# Users login via SSO can use this password to login in WebDAV.
# Enable the feature. pycryptodome should be installed first.
# sudo pip install pycryptodome==3.7.2
ENABLE_WEBDAV_SECRET = True
Why do you release a beta version for pro (as always)? You don’t keep your word regarding features first being tested for weeks in the community version (did you ever?).
This doesn’t even make any sense since you limit the functionality in CE.
You most probably will never experience “the” big customer wave doing it the way you do until now.
As asked a million times already, please fix that.
We have a testing/release workflow. Some bugs can’t be found in testing phase until under heavy usage in production. This is a normal scenario.
On the other hand, most of the releases are very stable, for example, the CE version 6.3.5 released on 2018/09/15 don’t have any major issue so far. The last Pro version 6.3.7 released two months ago also has no major issue.
It is very understandable that bugs cause frustration. On the other hand, even diligent testing efforts are no guarantee against bugs. Just as a reminder: It happens even in the best of families:
(I would argue that the world’s most valuable company in the world - at this point in time - cannot be doing it soo terribly wrong.)
This said, I have a question: The Seafile roadmap states that “A new minor version will be marked as beta for about 2 weeks. When no important bugs are found, we will remove the beta mark and consider it as production ready.”
Is this process still lived by? I think it makes a lot of sense.
The Pro version does not support SQLite as database.
Though in old versions, most features worked when using SQLite, as we are adding more features, the compatibility with SQLite will be harder to maintain.
Can you confirm something is being done with my API feedback? I’ve been asking this for months now. Zero communication on Seafile’s end is quite disappointing tbh.
This is #1 wished for:
Please expose the notifications that are already visible in seahub (this one is important for me)
This is #1 bug that would be in need of a fix:
Getting an OWA link seems to always return ‘path invalid’ although the path is valid (this one is important to me as it stands between a system with an online office feature or none at all, where the latter is disappointing)
Currently it is not implemented as an API in version 6.3. In version 7.0, as we rewrite the interface, it will be implemented as an API.
Getting an OWA link seems to always return ‘path invalid’ although the path is valid (this one is important to me as it stands between a system with an online office feature or none at all, where the latter is disappointing)
The API is used in one of our project. It should work. Have you encode the PATH parameter? On the other hand, it is designed for pro edition, if you are a customer, you can send a support email. Otherwise the support of the API issues is beyond our scope.
