[prod] http://m.input.mozilla.com/ja/feedback#happy always returns internal error

VERIFIED FIXED

Status

Input Graveyard
Submission
--
critical
VERIFIED FIXED
7 years ago
a year ago

People

(Reporter: m_kato, Assigned: nigelb)

Tracking

Details

(Whiteboard: [prod], [stage], URL)

(Reporter)

Description

7 years ago
When using Fennec with Japanese locale, feedback into preferences accesses http://m.input.mozilla.com/ja/feedback#happy or http://m.input.mozilla.com/ja/feedback#sad to input a feedback.

But http://m.input.mozilla.com/ja/feedback always returns internal error.

Of course, English page (http://m.input.mozilla.com/en-US/feedback#happy) works fine.
(Reporter)

Updated

7 years ago
Severity: normal → critical
Matt, can you take a look at this?
Component: Sites → Submission
QA Contact: sites → submission
Makoto thank you for catching this. Aakash, yes indeed this is occurring on both prod and stage.

Steps to reproduce (from comment 0):
1. goto http://m.input.mozilla.com/ja/feedback, #sad, or #happy

Expected:
User is able to leave feedback

Actual:
A 500 response code is returned by the server.
Summary: http://m.input.mozilla.com/ja/feedback#happy always returns internal error → [prod] http://m.input.mozilla.com/ja/feedback#happy always returns internal error
Whiteboard: [prod], [stage]
(Assignee)

Comment 3

7 years ago
Triaged this to us wrongly linking to support.mozilla.org on mobile pages.  We try to assign the locale as well to the link and fail.  Fixed in https://github.com/mozilla/input.mozilla.org/pull/22
Assignee: nobody → nigelbabu
Status: NEW → ASSIGNED
(Assignee)

Comment 4

7 years ago
Fixed in https://github.com/mozilla/input.mozilla.org/commit/a62d74deeb0afd5e7714305d7b7305be9e276638

Verified on m.input.allizom.org/ja/feedback
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
QA verified on stage ... http://m.input.allizom.org/ja/feedback#happy
Status: RESOLVED → VERIFIED
Resolution: WORKSFORME → FIXED
Product: Input → Input Graveyard
You need to log in before you can comment on or make changes to this bug.