Localized values are not displayed in the "Field only appears when" field when editing custom fields

RESOLVED FIXED in Bugzilla 3.6

Status

()

P3
normal
RESOLVED FIXED
9 years ago
9 years ago

People

(Reporter: leszekz, Assigned: LpSolit)

Tracking

Bugzilla 3.6
Bug Flags:
approval +
approval3.6 +

Details

Attachments

(2 attachments, 1 obsolete attachment)

(Reporter)

Description

9 years ago
How I can localize strings which are on included images. These are displayed on the Add a new Custom Field page
(Reporter)

Comment 1

9 years ago
Created attachment 444090 [details]
Images with strings
This is more of a support or localization question than a bug. You might want to subscribe to the localizers@bugzilla.org mailing list and ask them.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INVALID
(Reporter)

Comment 3

9 years ago
(In reply to comment #2)
> This is more of a support or localization question than a bug. You might want
> to subscribe to the localizers@bugzilla.org mailing list and ask them.

OK, I changed summary. This is developer issue, not localizers. Developers should prepare all strings to localize.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Summary: How localize strings → Why strings on images aren't localized
(Assignee)

Comment 4

9 years ago
Rewording the bug summary, which was totally confusing. I confirm that localized bug statuses and resolutions are not used in editfields.cgi, which is inconsistent with values displayed in bugs or the search page.
Assignee: ui → administration
Status: REOPENED → NEW
Component: User Interface → Administration
OS: Windows XP → All
Hardware: x86 → All
Summary: Why strings on images aren't localized → Localized values are not displayed in the "Field only appears when" field when editing custom fields

Updated

9 years ago
Flags: blocking4.0?
(Assignee)

Comment 5

9 years ago
Created attachment 456031 [details] [diff] [review]
patch, v1
Assignee: administration → LpSolit
Attachment #444090 - Attachment is obsolete: true
Status: NEW → ASSIGNED
Attachment #456031 - Flags: review?(mkanat)

Updated

9 years ago
Attachment #456031 - Flags: review?(mkanat) → review+

Updated

9 years ago
Flags: blocking4.0?
Flags: approval3.6+
Flags: approval+
Target Milestone: --- → Bugzilla 3.6
(Assignee)

Comment 6

9 years ago
Created attachment 456106 [details] [diff] [review]
patch for 3.6, v1

Backport for 3.6.1. I already committed the patch for tip when I realized it didn't apply cleanly on the 3.6 branch.
Attachment #456106 - Flags: review?(mkanat)
Comment on attachment 456106 [details] [diff] [review]
patch for 3.6, v1

Oh wow, yeah. I didn't realize that it couldn't be backported straight to 3.6.
Attachment #456106 - Flags: review?(mkanat) → review+
(Assignee)

Comment 8

9 years ago
Committing to: bzr+ssh://lpsolit%40gmail.com@bzr.mozilla.org/bugzilla/trunk/
modified template/en/default/admin/custom_fields/cf-js.js.tmpl
modified template/en/default/admin/custom_fields/edit.html.tmpl
Committed revision 7266.

Committing to: bzr+ssh://lpsolit%40gmail.com@bzr.mozilla.org/bugzilla/3.6/
modified template/en/default/admin/custom_fields/cf-js.js.tmpl
modified template/en/default/admin/custom_fields/edit.html.tmpl
Committed revision 7119.
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago9 years ago
Resolution: --- → FIXED

Comment 9

9 years ago
I know 3.4 branch is pretty much closed, but how can this be done for this version? Thanks for the tips.
(Assignee)

Comment 10

9 years ago
(In reply to comment #9)
> I know 3.4 branch is pretty much closed, but how can this be done for this
> version? Thanks for the tips.

Probably something similar to what I did for 3.6, assuming the same functions exist in 3.4 (I don't remember).

Comment 11

9 years ago
I tried that already and this code don't work. Unfortunately I am not a programmer, so can't debug this.
You need to log in before you can comment on or make changes to this bug.