[fix] Fix a bug in multiple storage backend support
There is still a bug with multiple storage backend support in Seahub. I have ENABLE_STORAGE_CLASSES = True and STORAGE_CLASS_MAPPING_POLICY = 'USER_SELECT' in seahub.conf but there is no way to define the backend while creating a new Library and the Backend Column in Library-View is still empty. See Screenshots.
Still getting many warnings in seahub_email_sender.log and file_updates_sender.log: /home/seafile/seafile-pro-server-7.0.7/pro/python/SQLAlchemy-1.1.3-py2.7-linux-x86_64.egg/sqlalchemy/dialects/mysql/base.py:1496: Warning: (1287L, u"'@@tx_isolation' is deprecated and will be removed in a future release. Please use '@@transaction_isolation' instead")
No clue what I’m doing here (no experience w/ Python) but I created an .egg from SQLAlchemy 1.1.18 (the last one ín the 1.1.x branch) and use that instead of the old one (keeping the 1.1.3 naming as there was another dependency I couldn’t find).
The log spamming has stopped now. Let’s wait for unwanted side effects but maybe @daniel.pan should just upgrade SQLAlchemy in 7.0.8?
@marcusm@upD8R think this is a matter to wait for upgrade SQLAlchemy in seahub_thirdpart. In Raspberry Pi CE Version, this doesn’t happens since we are using SQLAlchemy 1.3.5.
I’m having problem with docker in pro edition, when I try to access library said access denied … I’m lost searching some configuration or value to fix that … If you want I can post picture about but is trying to access to any library in any user say access denied, even I can create new library successful but can’t access