Issues on the Wiki (Pro 6.3)

I get an error

On Page unavailable
Sorry, but the requested page is unavailable due to a server hiccup.

Our engineers have been notified, so check back later.

but no log

tail - 100 gunicorn_access.log
==> entrée standard <==

tail - 100 seahub.log
==> entrée standard <==

tail - 100 seafile.log
==> entrée standard <==

Can you add DEBUG=True in and try whether the detailed error will be printed in the web interface?

Here is the debug trace on differents urls

note that the request url is on HTTP (not S)
Request URL:

SearpcError at /wikis/wiki-public/
Invalid user
Request Method:	GET
Request URL:
Django Version:	1.11.11
Exception Type:	SearpcError
Exception Value:	
Invalid user
Exception Location:	/etc/seafile/seafile-pro-server-6.3.0/seafile/lib/python2.7/site-packages/pysearpc/ in _fret_string, line 25
Python Executable:	/usr/bin/python2.7
Python Version:	2.7.13
Python Path:	
Server time:	mer, 4 Jul 2018 15:33:42 +0000


Request Method: GET
Request URL:

Django Version: 1.11.11
Python Version: 2.7.13
Installed Applications:
Installed Middleware:


File "/etc/seafile/seafile-pro-server-6.3.0/seahub/thirdpart/django/core/handlers/" in inner
  41.             response = get_response(request)

File "/etc/seafile/seafile-pro-server-6.3.0/seahub/thirdpart/django/core/handlers/" in _legacy_get_response
  249.             response = self._get_response(request)

File "/etc/seafile/seafile-pro-server-6.3.0/seahub/thirdpart/django/core/handlers/" in _get_response
  187.                 response = self.process_exception_by_middleware(e, request)

File "/etc/seafile/seafile-pro-server-6.3.0/seahub/thirdpart/django/core/handlers/" in _get_response
  185.                 response = wrapped_callback(request, *callback_args, **callback_kwargs)

File "/etc/seafile/seafile-pro-server-6.3.0/seahub/seahub/wiki/" in slug
  50.             request, wiki.repo_id, '/') == 'rw':

File "/etc/seafile/seafile-pro-server-6.3.0/seahub/seahub/views/" in check_folder_permission
  107.     return seafile_api.check_permission_by_path(repo_id, path, username)

File "/etc/seafile/seafile-pro-server-6.3.0/seafile/lib/python2.7/site-packages/seaserv/" in check_permission_by_path
  682.         return seafserv_threaded_rpc.check_permission_by_path(repo_id, path, user)

File "/etc/seafile/seafile-pro-server-6.3.0/seafile/lib/python2.7/site-packages/pysearpc/" in newfunc
  112.                 return fret(ret_str)

File "/etc/seafile/seafile-pro-server-6.3.0/seafile/lib/python2.7/site-packages/pysearpc/" in _fret_string
  25.         raise SearpcError(dicts['err_msg'])

Exception Type: SearpcError at /wikis/wiki-public/home/
Exception Value: Invalid user

Thanks. It will be fixed in the next release.

1 Like

Hi Daniel,

There is also an old bug mentionned here


HI Daniel

I just tried the 6.3.1 Pro beta version uploaded this morning

Here are the results of my tests

The wiki is now public

But the “Wiki” links on top of the UI links to the login page

I could link to a front page where all the public wikis are listed : what do you think ?
Could you also provide search capabilities here ?

Once logged in In the new Wiki interface (in the LIbrary context) :

  • we can see all files from the library
  • we can drag and drop, files from left to right
  • it creates links to the files :yum:

But :

Also, could this feature be improved to provide image inclusion ?

I also wonder if the co-existence of two editors (Library and wiki context) is still accurate :thinking:


Thanks for testing. Actually we are working on improving wiki feature, but it is not done yet and not included in 6.3.1.

I think you mean 6.3.1

Yes. We will need another month to make the Wiki feature ready.


@daniel.pan I noticed another limitation.

Wikis can not be renamed from the library scope.

If i rename the library “Wiki Public” to “Wiki Seafile”

The wiki is still named “Wiki public”

and the url remains /wiki-public/

The only workaround is to

  • create a new wiki
  • paste the original content
  • delete the old wiki

Could you resolve this issue ?


If i delete the wiki, the library is not deleted
Is it a normal behaviour ?

@daniel.pan Another Issue in the new wiki editor

You canot not add relative links (/link/), http or https is required

I remenber that it was possible in the old editor


I wonder how users can access wikis acdessible to logged in users

In the wiki view (admin logged in), i see all wikis the admin has created

But when logged in as a normal user, i only see my wikis.

How can i access wikis created by the admin ?



Another issue related to images inclusion

Previously i included screenshots with this tag


Images are located in a sub folder “images”


But they are not dispayed in the public wiki

The wiki name is displayed in the URL. It need to be unique globally. So it need to be different from the library name. An improvement will be that when you change the Wiki name, the corresponding library will be changed, but not vice verse.

This is a normal behaviour.

This will be fixed in a version released at the end of August.

Currently, the admin need to send the wiki links to users. In a future version, we will list all wikis one can access.

It will be fixed too.

1 Like

Hi daniel,

Glad to see that you have quick answers to all my questions and remarks. :wink:
Hope these tests will help you improve the wiki feature, which some of us are very intersted in.



1 Like


There is a Home page Link missing in the wiki (edit) view

From the wiki view, you can browse to the home page

But you can not access the home page anymore when you are in the edit view (except if you switch to the view from the right, wich is not convenient)

You can not quit the edit view easily neither come back from the home page of seafile webui


on 6.3.4 version, it seems that this behaviour is still confusing.

When accessing the wiki, the url is /wiki/*
When editing the wiki, the url is /lib/*
When switching to view from te editor, the url is still /lib/*

The location of the wiki between /lib/* and /wiki/* seems to be the cause of many probklems, such as :

  • lost of public acess (from /wiki/*)
  • difficulties to link to pafes and files
  • invisibility of other files (*.pdf) in the wiki view (see below)

From the /lib/* url, the tree shows files in a subfloder


From the /wiki/* url, the tree does not show files in a subfolder


A button back to the wiki page will be added in the next release.

In our design, the tree in wiki view only show the “pages” of a wiki instead of all files. In the edit view, you can add links of files to a wiki page, and the files can be downloaded via the links in the page.

This is because you are editing the underlying file of a wiki. Maybe we can hide the button of switching to view mode.

Thank you. The button should ask for saving before browsing back, shouldn’t it ?

I think it’as pity because most of wikis give access to files and seeing the files in a tree view is a +.

But without a button to add files (which existed in the previous wiki editor), you have to switch between different windows.

I don’t really understand, but switching to view mode is not really useful if you cannot do anything…
By the way, i did not find any string to translate in Transiflex about he new wiki. WIll you add it in the future ?

Hi Daniel,

Can you tell us the next release version (or the delay) in which you consider the wiki feature to be ready, according to the test and comments i made in this thread ?

I’m on 6.3.4 and there are still major problems (and regressions from 6.3.2 to 6.3.4 / rights and public wiki feature)