github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

HTML/View Template is rendered twice #7728

New Issue
Closed
opened 2025-11-02 07:34:44 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 07:34:44 -06:00
Owner
Copy Link

Originally created by @PhoenixPeca on GitHub (Aug 22, 2021).

  • Gitea version (or commit ref): v1.15.0
  • Git version: not relevant
  • Operating system: Ubuntu (Gitee docker via mailcow setup)
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No -- the gitea server did not send me the activation link.
  • Log gist: not relevant

Description

I'm not sure if this issue has been reported already, but after researching the existing issues in this repo, seems like this is a new one.

Anyways... here's a bug that I found:

I'm using the latest release of Gitea (v1.15.0) and created a new empty repository. I opened the repository Settings and clicked on the "Add Push Mirror" button without any change to the other fields and somehow the webpage just reloads and renders two copies of the same template. Attached is the fullpage screenshot.

Screenshots

Fullpage PDF Screenshot: screencapture-mail-aspac-io-gitea-phoenix-testing-settings-2021-08-22-23_09_30.pdf

Fullpage PNG Screenshotimage
screencapture-mail-aspac-io-gitea-phoenix-testing-settings-2021-08-22-23_09_30.pdf

Originally created by @PhoenixPeca on GitHub (Aug 22, 2021). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq) 5. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): v1.15.0 - Git version: not relevant - Operating system: Ubuntu (Gitee docker via mailcow setup) <!-- Please include information on whether you built gitea yourself, used one of our downloads or are using some other package --> <!-- Please also tell us how you are running gitea, e.g. if it is being run from docker, a command-line, systemd etc. ---> <!-- If you are using a package or systemd tell us what distribution you are using --> - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No -- the gitea server did not send me the activation link. - Log gist: not relevant <!-- It really is important to provide pertinent logs --> <!-- Please read https://docs.gitea.io/en-us/logging-configuration/#debugging-problems --> <!-- In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini --> ## Description <!-- If using a proxy or a CDN (e.g. CloudFlare) in front of gitea, please disable the proxy/CDN fully and connect to gitea directly to confirm the issue still persists without those services. --> I'm not sure if this issue has been reported already, but after researching the existing issues in this repo, seems like this is a new one. Anyways... here's a bug that I found: I'm using the latest release of Gitea (v1.15.0) and created a new empty repository. I opened the repository Settings and clicked on the "Add Push Mirror" button without any change to the other fields and somehow the webpage just reloads and renders two copies of the same template. Attached is the fullpage screenshot. ## Screenshots Fullpage PDF Screenshot: [screencapture-mail-aspac-io-gitea-phoenix-testing-settings-2021-08-22-23_09_30.pdf](https://github.com/go-gitea/gitea/files/7027598/screencapture-mail-aspac-io-gitea-phoenix-testing-settings-2021-08-22-23_09_30.pdf) Fullpage PNG Screenshot![image](https://user-images.githubusercontent.com/9730242/130357853-0be27fb6-1283-4315-b8a4-0e500146777c.png) [screencapture-mail-aspac-io-gitea-phoenix-testing-settings-2021-08-22-23_09_30.pdf](https://github.com/go-gitea/gitea/files/7027604/screencapture-mail-aspac-io-gitea-phoenix-testing-settings-2021-08-22-23_09_30.pdf) <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the type/bug label 2025-11-02 07:34:44 -06:00
GiteaMirror commented 2025-11-02 07:34:45 -06:00
Author
Owner
Copy Link

@delvh commented on GitHub (Aug 22, 2021):

I would like to mention that these are not two exactly equal copies:
Copy one has as error message
You are not allowed to import local repositories, and copy two has
the provided url is invalid. You must escape all components of the URL correctly.
So, could it be that the copy behavior is triggered by two different error messages being present at once, and for each error message the site is created again?

@delvh commented on GitHub (Aug 22, 2021): I would like to mention that these are not two exactly equal copies: Copy one has as error message `You are not allowed to import local repositories`, and copy two has `the provided url is invalid. You must escape all components of the URL correctly. ` So, could it be that the copy behavior is triggered by two different error messages being present at once, and for each error message the site is created again?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#7728
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?