If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[traceback] AttributeError: 'NoneType' object has no attribute 'localized_string'

RESOLVED FIXED in 2013-03-21

Status

Marketplace
Payments/Refunds
P2
normal
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: andym, Assigned: basta)

Tracking

2013-03-21
x86
Mac OS X
Points:
---

Details

(Whiteboard: p=1)

(Reporter)

Description

5 years ago
No addon.name when connecting to bango in payments setup.
 
sentry.dmz.phx1.mozilla.com/addons/marketplace-dev/group/12331/
Why is this using addon.name.localized_string? It should use unicode(addon.name) because that falls back to the default, unlocalized string IIRC.
Blocks: 775802
Priority: -- → P2
Summary: [traceback] AAttributeError: 'NoneType' object has no attribute 'localized_string' → [traceback] AttributeError: 'NoneType' object has no attribute 'localized_string'
-> basta wrote this and comment 1 sounds like an easy 1 line fix.
Assignee: nobody → mattbasta
Target Milestone: --- → 2013-03-21
Whiteboard: p=1
Version: 1.0 → 1.2
(Assignee)

Comment 3

5 years ago
https://github.com/mozilla/zamboni/commit/07dae64d3aa7a7ecf092371f1107329c89c465f5
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Does this work? I don't actually remember if addon.name falls back to the default, unlocalized string.
(Assignee)

Comment 5

5 years ago
Does it matter what name Solitude is storing? I mean if we wanted to do it right, we'd have to send a dict of all of the translations to Solitude and let it decide which locale to use when it wants to list the app name, no?
mmm, yes, right you are! I created bug 854039

For now we can just send the default locale. Does unicode(addon.name) do that? I am asking because comment #1 was just a guess.
You need to log in before you can comment on or make changes to this bug.