github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-22 14:34:54 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

TypeError: undefined is not an object (evaluating '_i18n.textEdited') #10863

New Issue
Closed
opened 2025-11-02 09:20:21 -06:00 by GiteaMirror · 11 comments
GiteaMirror commented 2025-11-02 09:20:21 -06:00
Owner
Copy Link

Originally created by @HernanLencinas on GitHub (May 17, 2023).

Originally assigned to: @wxiaoguang on GitHub.

Description

Some users are reporting that in the Gitea console, they are being shown the following error message:

JavaScript error: TypeError: undefined is not an object (evaluating '_i18n.textEdited') (https://git.cloudvalley.telecom.com.ar/assets/js/index.js?v=1.19.3 @ 54:663).
Open browser console to see more details.

Screenshot attached.

This happens randomly and from what we've observed, it mainly occurs with users using the Safari browser. We have checked the server and Gitea logs but haven't found any relevant error messages.

Users experiencing this issue also report that their user session is being closed, preventing them from working normally.

Gitea Version

1.19.3

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

image
image

Git Version

2.31.1

Operating System

Linux

How are you running Gitea?

We are running Gitea from the binary available at https://dl.gitea.com/gitea/1.19.3/gitea-1.19.3-linux-amd64 on a virtual server.

Database

MySQL

Originally created by @HernanLencinas on GitHub (May 17, 2023). Originally assigned to: @wxiaoguang on GitHub. ### Description Some users are reporting that in the Gitea console, they are being shown the following error message: JavaScript error: TypeError: undefined is not an object (evaluating '_i18n.textEdited') (https://git.cloudvalley.telecom.com.ar/assets/js/index.js?v=1.19.3 @ 54:663). Open browser console to see more details. Screenshot attached. This happens randomly and from what we've observed, it mainly occurs with users using the Safari browser. We have checked the server and Gitea logs but haven't found any relevant error messages. Users experiencing this issue also report that their user session is being closed, preventing them from working normally. ### Gitea Version 1.19.3 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots ![image](https://github.com/go-gitea/gitea/assets/12104700/be49ab1c-df34-4eea-b6d3-8c7c52d4df7d) ![image](https://github.com/go-gitea/gitea/assets/12104700/d6c97214-2266-45e0-a785-d8e58897f5a8) ### Git Version 2.31.1 ### Operating System Linux ### How are you running Gitea? We are running Gitea from the binary available at https://dl.gitea.com/gitea/1.19.3/gitea-1.19.3-linux-amd64 on a virtual server. ### Database MySQL
GiteaMirror added the issue/confirmedissue/needs-feedbacktype/bug labels 2025-11-02 09:20:21 -06:00
GiteaMirror commented 2025-11-02 09:20:22 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (May 17, 2023):

Do you mean that, if a user sees the error, then they refresh page, then the refreshed page doesn't have the error?

@wxiaoguang commented on GitHub (May 17, 2023): Do you mean that, if a user sees the error, then they refresh page, then the refreshed page doesn't have the error?
GiteaMirror commented 2025-11-02 09:20:22 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (May 17, 2023):

I think I know the problem now.

Will propose a fix later (at most 1 day).

@wxiaoguang commented on GitHub (May 17, 2023): I think I know the problem now. Will propose a fix later (at most 1 day).
GiteaMirror commented 2025-11-02 09:20:22 -06:00
Author
Owner
Copy Link

@HernanLencinas commented on GitHub (May 17, 2023):

When users encounter that error message, it closes their session, and they have to log in again. Then, while browsing the repositories, it may or may not appear. It seems to be quite random.

When the same user tries it with Chrome, it works without any issues.

@HernanLencinas commented on GitHub (May 17, 2023): When users encounter that error message, it closes their session, and they have to log in again. Then, while browsing the repositories, it may or may not appear. It seems to be quite random. When the same user tries it with Chrome, it works without any issues.
GiteaMirror commented 2025-11-02 09:20:22 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (May 17, 2023):

Oh .... if the user gets kicked-out, then that's another problem.

I think it has been fixed by https://github.com/go-gitea/gitea/pull/24330

The related issue is https://github.com/go-gitea/gitea/issues/24176 , there are more details.

The fix is only in 1.20 (you can try nightly), but it's not easy to backport hmm, not difficult.

According to my test, disabling Safari's "prevent cross-site tracking" could help.

I can try to send a partial backport to 1.19

@wxiaoguang commented on GitHub (May 17, 2023): Oh .... if the user gets kicked-out, then that's another problem. I think it has been fixed by https://github.com/go-gitea/gitea/pull/24330 The related issue is https://github.com/go-gitea/gitea/issues/24176 , there are more details. The fix is only in 1.20 (you can try nightly), ~~but it's not easy to backport~~ hmm, not difficult. According to my test, disabling Safari's "prevent cross-site tracking" could help. ---- I can try to send a partial backport to 1.19
GiteaMirror commented 2025-11-02 09:20:22 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (May 17, 2023):

-> Fix safari cookie session bug #24772

I am not 100% sure but it looks like that's the problem (the user's session is closed after some time)

@wxiaoguang commented on GitHub (May 17, 2023): -> Fix safari cookie session bug #24772 I am not 100% sure but it looks like that's the problem (the user's session is closed after some time)
GiteaMirror commented 2025-11-02 09:20:22 -06:00
Author
Owner
Copy Link

@HernanLencinas commented on GitHub (May 17, 2023):

Oh .... if the user gets kicked-out, then that's another problem.

I think it has been fixed by #24330

The related issue is #24176 , there are more details.

The fix is only in 1.20 (you can try nightly), but it's not easy to backport hmm, not difficult.

According to my test, disabling Safari's "prevent cross-site tracking" could help.

I can try to send a partial backport to 1.19

On our side, we can try upgrading to version 1.20 over the weekend, and once it's done, test again to see if the issue is solved.

@HernanLencinas commented on GitHub (May 17, 2023): > Oh .... if the user gets kicked-out, then that's another problem. > > I think it has been fixed by #24330 > > The related issue is #24176 , there are more details. > > The fix is only in 1.20 (you can try nightly), ~but it's not easy to backport~ hmm, not difficult. > > According to my test, disabling Safari's "prevent cross-site tracking" could help. > > I can try to send a partial backport to 1.19 On our side, we can try upgrading to version 1.20 over the weekend, and once it's done, test again to see if the issue is solved.
GiteaMirror commented 2025-11-02 09:20:23 -06:00
Author
Owner
Copy Link

@liyimeng commented on GitHub (May 18, 2023):

Same problem here.

@liyimeng commented on GitHub (May 18, 2023): Same problem here.
GiteaMirror commented 2025-11-02 09:20:23 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (May 18, 2023):

Same problem here.

It could be another problem IMO. This issue about "user randomly gets logged out".

@wxiaoguang commented on GitHub (May 18, 2023): > Same problem here. It could be another problem IMO. This issue about "user randomly gets logged out".
GiteaMirror commented 2025-11-02 09:20:23 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jun 6, 2023):

I think this issue could be closed since #24772 has been backported to 1.19 nightly.

Feel free to reopen if there is any other problem.

@wxiaoguang commented on GitHub (Jun 6, 2023): I think this issue could be closed since #24772 has been backported to 1.19 nightly. Feel free to reopen if there is any other problem.
GiteaMirror commented 2025-11-02 09:20:23 -06:00
Author
Owner
Copy Link

@liyimeng commented on GitHub (Jul 20, 2023):

Is this fixed in 1.20.0. I upgrade this version, but still get the same errors

JavaScript error: TypeError: undefined is not an object (evaluating 'p.i18n.textEdited') (https://git.tdology.com/assets/js/index.js?v=1.20.0 @ 50:663). Open browser console to see more details.

I have safari Version 16.4 (18615.1.26.110.1)

The same problem on my iPhone.

@liyimeng commented on GitHub (Jul 20, 2023): Is this fixed in 1.20.0. I upgrade this version, but still get the same errors `JavaScript error: TypeError: undefined is not an object (evaluating 'p.i18n.textEdited') (https://git.tdology.com/assets/js/index.js?v=1.20.0 @ 50:663). Open browser console to see more details.` I have safari `Version 16.4 (18615.1.26.110.1)` The same problem on my iPhone.
GiteaMirror commented 2025-11-02 09:20:23 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jul 20, 2023):

Is this fixed in 1.20.0. I upgrade this version, but still get the same errors

JavaScript error: TypeError: undefined is not an object (evaluating 'p.i18n.textEdited') (https://git.tdology.com/assets/js/index.js?v=1.20.0 @ 50:663). Open browser console to see more details.

I have safari Version 16.4 (18615.1.26.110.1)

The same problem on my iPhone.

Could you try to clear your web browser cache?

@lunny commented on GitHub (Jul 20, 2023): > Is this fixed in 1.20.0. I upgrade this version, but still get the same errors > > `JavaScript error: TypeError: undefined is not an object (evaluating 'p.i18n.textEdited') (https://git.tdology.com/assets/js/index.js?v=1.20.0 @ 50:663). Open browser console to see more details.` > > I have safari `Version 16.4 (18615.1.26.110.1)` > > The same problem on my iPhone. Could you try to clear your web browser cache?
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 issue/confirmed issue/needs-feedback 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#10863
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?