Closed
Bug 557763
Opened 14 years ago
Closed 14 years ago
The default assignee and QA contact are not displayed correctly if the component name starts with a dot or an underscore
Categories
(Bugzilla :: Administration, task)
Tracking
()
VERIFIED
DUPLICATE
of bug 284650
People
(Reporter: timeless, Unassigned)
References
()
Details
Attachments
(1 file)
13.03 KB,
text/html
|
Details |
i'm setting up a proposal for a product, and i started adding components. but after adding my second component, i got a strange grid. things look fine in 'describecomponents.cgi', but they look bad in 'editcompoents.cgi'
Comment 1•14 years ago
|
||
The problem happens if the component name starts with a dot or an underscore. Not sure why.
Comment 2•14 years ago
|
||
Targetting 3.6 for now. But I may take the fix for 3.4 if we aren't locked to security fixes yet.
Summary: default assignee and default qa contact show as '1' and '1' for plugins:.NET (Microsoft) → The default assignee and QA contact are not displayed correctly if the component name starts with a dot or an underscore
Target Milestone: --- → Bugzilla 3.6
Comment 3•14 years ago
|
||
Ah yes, I remember! The problem is that keys starting with . or _ are seen as private by TT, and so are not passed further. This is exactly the same root cause as in bug 160595, bug 284650 and bug 346280. I still think my proposed fix from bug 160595 is the right way to go for us, per myk's URL in bug 160595 comment 6.
Comment 4•14 years ago
|
||
Oh, even simpler: http://template-toolkit.org/docs/manual/Variables.html#section_Hash_Array_References "Any key in a hash which starts with a '_' or '.' character will be considered private and cannot be evaluated or updated from within a template. The undefined value will be returned for any such variable accessed which the Template Toolkit will silently ignore. You can disable this feature by setting the $Template::Stash::PRIVATE package variable to a false value."
Comment 5•14 years ago
|
||
I fixed this problem in bug 284650, which was here first. :) As it's the same root cause, it's a dupe.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Target Milestone: Bugzilla 3.6 → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•