Great news! We have upgraded cloud.seatable.io to SeaTable 1.5 today. This release brings with it a load of smaller and larger improvements of existing features to boost user experience and a few new features - these few are all the more exciting though.
Here a brief summary:
Improved table editor : You’ll feel the difference right away when working with the editor. The new non-modal menus are a lot smoother, the menu structure of the select columns has been simplified, the linked column wizard now has an edit function in addition to the existing display function and the number and formula columns provide a decimal precision setting.
Custom sharing permissions : Sharing a base to multiple users with different permission levels has become a piece of cake with SeaTable 1.5. A custom sharing permission consists of individual access rules for all tables and their views in a base. And you can define as many custom permissions as you want!
More flexible forms : The new release offers three more options to customize your form to your needs. You can add a form note above the form fields, you can word an individual message to be displayed after the form’s submission and you can specify a URL to which the submitter is automatically redirected after the submission message.
Time-trigger for Python scripts : You have a Python script that you want to run automatically in certain intervals? With SeaTable 1.5, just define the interval, and SeaTable does the rest for you.
For more details on these and the many other improvements packed into SeaTable 1.5, have a look at the Release Note.
For a detailed list of all major and minor changes in the new version, visit the Changelog.
In a few days, we’ll also update the docker image on Docker Hub. Check back soon!
Thanks. 1.4.0 was working fine. Updated to 1.5.0 and I just get a page that says;
# Page unavailable
Sorry, but the requested page is unavailable due to a server hiccup.
Our engineers have been notified, so check back later.
Only errors in the log I see are;
2020-12-14 22:23:05,334 [ERROR] django.request:135 handle_uncaught_exception Internal Server Error: /workspace/1/dtable/Home Contents/
Traceback (most recent call last):
File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/backends/utils.py", line 64, in execute
return self.cursor.execute(sql, params)
File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/backends/mysql/base.py", line 101, in execute
return self.cursor.execute(query, args)
File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/pymysql/cursors.py", line 163, in execute
result = self._query(query)
File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/pymysql/cursors.py", line 321, in _query
conn.query(q)
File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/pymysql/connections.py", line 505, in query
self._affected_rows = self._read_query_result(unbuffered=unbuffered)
File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/pymysql/connections.py", line 724, in _read_query_result
result.read()
File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/pymysql/connections.py", line 1069, in read
first_packet = self.connection._read_packet()
File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/pymysql/connections.py", line 676, in _read_packet
packet.raise_for_error()
File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/pymysql/protocol.py", line 223, in raise_for_error
err.raise_mysql_exception(self._data)
File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/pymysql/err.py", line 107, in raise_mysql_exception
raise errorclass(errno, errval)
pymysql.err.OperationalError: (1054, "Unknown column 'profile_profile.need_show_video' in 'field list'")
I tried with a fresh database and everything works correctly. Can anyone confirm they have 1.5.0 working without modifying their setup or if there’s any way to fix the errors so I don’t have to start with a fresh database? Thanks.
