The fork list are not displayed when accessing fork option within a Bitbucket repository
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
The view repository fork list is blank when clicking on fork option within a repository:
Environment
Bitbucket DC/Server 7.17.1
Diagnosis
Logs may throw errors similar to the ones below:
1
2
3
4
2022-01-04 15:56:17,616 ERROR [https-jsse-nio-10.10.10.171-8443-exec-1] o.a.c.c.C.[.[.[/].[plugins] Servlet.service() for servlet [plugins] in context with path [] threw exception
com.google.template.soy.tofu.SoyTofuException: Attempting to render undefined template 'bitbucket.internal.feature.repository.repositoryTable'.
at plugin.page.repoForks(all-forks.soy:20)
at com.google.template.soy.tofu.internal.BaseTofu.renderMainHelper(BaseTofu.java:369)1
2
3
4
5
2022-01-04 15:56:43,052 ERROR [https-jsse-nio-10.10.10.171-8443-exec-2] @1514Y11x852x10547x9 1f3ypg2 10.10.10.14 "GET /mvc/error500 HTTP/1.1" c.a.s.i.web.ErrorPageController There was an unhandled exception loading [/plugins/servlet/forks/project/TEST/repo/test]
com.google.template.soy.tofu.SoyTofuException: Attempting to render undefined template 'bitbucket.internal.feature.repository.repositoryTable'.
at plugin.page.repoForks(all-forks.soy:20)
...
at com.fernferret.bitbucket.forklist.AllForksServlet.doGet(AllForksServlet.java:98)Cause
There are some known plugins that may cause this issue which are:
Commit Graph for Bitbucket Server
ReadMe Parser plugins.
You can make a simple test attempting to access the fork list page after enabling safe mode and check if the issue will go away.
Solution
The solution is to disable the offending plugin.
Was this helpful?