-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't view Wiki pages after upgrade from 1.11.1 to 1.11.2 #10681
Comments
I am also getting this message when creating a new wiki page, just upgraded from 1.10.3 to 1.11.2. |
A little more detail in my instance: In a repo with no Wiki pages, adding a new page loads the editor as expected. I get the error when saving the page, however when I go back to the Wiki page listing the page does appear to be created as it does show up. I get the template error again trying to read the new page. |
This should indeed be fixed by #10583, though that fix was for Go 1.14 and Gitea |
How did you get the binary for 1.11.2, did you build it yourself? What is the output of http://gitea.example/admin/config for the |
Downloaded "gitea-1.11.2-linux-amd64" from github.
1.11.2 built with GNU Make 4.1, go1.14 : bindata, sqlite, sqlite_unlock_notify
Will try shortly. |
Confirmed, using this line: |
I got the same kind of error clicking on a wiki page's Revision, and grepping around the source it looks like the same kind of change will need to be made in revision.tmpl (assuming that's the proper fix). |
Downloaded gitea-1.11.2-windows-4.0-amd64.exe from https://dl.gitea.io/gitea/1.11.2/ Gitea version is |
Should be fixed by #10684. Closing. |
[x]
):Description
When trying to view a Wiki page I've got this message
Upgraded from 1.11.1 to 1.11.2 this morning and the problem appeared.
When downgrading back to 1.11.1 the problem disapears.
I had a custom template (footer.tmpl for mermaid.js) even when removing the custom template the problem persists.
I tried on a repo without Wiki, clicked start wiki saved the default page and got the message.
The text was updated successfully, but these errors were encountered: