upup needs to learn about i18n.js

Bug #1721636 reported by Kathy Lussier
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Medium
Unassigned

Bug Description

Offline circ for the web client wasn't working correctly when apache was down on the Evergreen server. After some testing, Mike determined that problem was a result of upup not knowing about i18n.js

Revision history for this message
Mike Rylander (mrylander) wrote :

Here's a branch to address this, which contains a comment in base_js.tt2 to remind editors:

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/lp-1721636-i18n_js-for-upup

tags: added: pullrequest
Revision history for this message
Kathy Lussier (klussier) wrote :

I'm confirming that, after loading this patch, when I turned off apache, offline circ worked as expected.

I'm not sure if this is related to the patch or is already occurring in master. After I had loaded the patch and then stepped away from this server for a few days, I was unable to log into web client while I was online. I was able to get to the staff login page, but after logging in, I got a blank screen.

I saw the following in the Console:

Cannot connect to offline DB: Error: http://google.github.io/lovefield/error_lookup/src/error_lookup.html?c=201&p0=Object.pkObject&p1=%5B%22ccs%22%2C%2218%22%5D

http://google.github.io/lovefield/error_lookup/src/error_lookup.html?c=201&p0=Object.pkObject&p1=%5B%22ccs%22%2C%2218%22%5D

That URL leads me to a message that says:
Constraint error: (201) Duplicate keys are not allowed, index: Object.pkObject, key: ["ccs","18"]

Mike, do you think this is related to the patch or is a separate issue that needs to be added to LP. I know we encountered similar errors in the past that were subsequently fixed.

Revision history for this message
Galen Charlton (gmc) wrote :

Pushed to master and rel_3_0. Thanks, Mike!

Kathy: the issue you're seeing is unrelated to this patch and is worth opening a separate bug if you're still seeing it.

Changed in evergreen:
status: New → Confirmed
importance: Undecided → Medium
milestone: none → 3.0.2
status: Confirmed → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.