Opened 13 years ago

Closed 13 years ago

Last modified 12 years ago

#1823 closed defect (invalid)

404 errors via Date/Time i18n

Reported by: sjmiles Owned by: Adam Peller
Priority: high Milestone:
Component: Internationalization Version: 0.4
Keywords: nls, i18n, 404 Cc: Adam Peller
Blocked By: Blocking:

Description (last modified by sjmiles)

These errors are showing up in users' logs:

"GET /dojo/src/i18n/calendar/nls/en-us/gregorian.js HTTP/1.1" 404 343
"GET /dojo/src/i18n/calendar/nls/en/gregorianExtras.js HTTP/1.1" 404 346
"GET /dojo/src/i18n/calendar/nls/en-us/gregorianExtras.js HTTP/1.1" 404 34

"GET /dojo/src/widget/nls/en/TimePicker.js HTTP/1.1" 404 334
"GET /dojo/src/widget/nls/en-us/TimePicker.js HTTP/1.1" 404 337

I'm not sure if this is a problem with the client packages or the i18n system in general.

Change History (5)

comment:1 Changed 13 years ago by sjmiles

Component: WidgetsInternationalization
Description: modified (diff)

comment:2 Changed 13 years ago by jkuhnert

sjmiles: See http://opencomponentry.com:8080/timetracker/app . It took me a while to get correctly but eventually I succumbed to reading "some" of the docs...

The default locale object loaded nls.dojo_ROOT doesn't contain some of the special locale specific things that time / date items might want.

The url I referenced shows the only thing I've had to do to get it working, which is set a djConfig.locale = "en-us".. (Assuming you are in an en-us locale)

After setting this djConfig.locale property properly all of my 404 requests went away.

comment:3 Changed 13 years ago by Adam Peller

It's unclear from the report if "builds" are involved at all, or if this is "loose" dojo. If the latter, it is working as designed. The first time a particular resource is accessed via requireLocalization, a search path must be followed to search for all relevant locales, the number of these hits varies with the number of variants specified on the locale. The variants are not required to be present, so 404's may occur. This is somewhat like the original package search (not sure if that has changed?)

If a build is involved, this search should go away entirely. However, you must include the nls/ directory with the relevant locale builds. You do not have to specify djConfig.locale unless you wish to have your server override the user agent's normal settings.

nls.dojo_ROOT contains the fallbacks for all locales and therefore will not have *ANY* locale-specific settings. It should be included in the nls/ directory along with the other locales you build.

Marking invalid. If I am missing something, please re-open.

comment:4 Changed 13 years ago by Adam Peller

Resolution: invalid
Status: newclosed

comment:5 Changed 12 years ago by (none)

Milestone: 0.4.1

Milestone 0.4.1 deleted

Note: See TracTickets for help on using tickets.