Automatic localization of numbers (L10N) in templates can cause invalid sitemap priorities

[Mathijs de Bruin]

When specifying priorities for a sitemap as a float (as is suggested by the official documentation) and USE_L10N = True, it can happen that requested sitemaps contain comma's in the priority values for items when the server detects certain locales. As the sitemaps specification requires a dot as a separator for float values this yields an invalid sitemap and has been confirmed to prohibit the indexing of certain sites.

The problem can be reproduced as follows:

1. Make sure USE_L10N = True in settings.py.
2. Create a Sitemap object with a priority and expose it somewhere in the URL space. (For example: priority = 0.5)
3. Request the sitemap with a browser for which the decimal separator is something other than a dot. (This holds for many European locales.)
4. Priority value should now be rendered wrongly. (For example: <priority>0,5</priority>)

As this problem is likely to occur for other situations where templates are used to render machine-parseable content, a structural solution should be in order.

[Mathijs de Bruin]

One workaround that seems to do the job (for now) is to use a string value as the priority.

[vung]

Convert priority to str

[Russell Keith-Magee]

(In [13644]) Fixed #14164 -- Ensure that sitemap priorities aren't rendered with localized numerical formats. Thanks to dokterbob for the report, and vung for the draft patch.

[Russell Keith-Magee]

(In [13646]) [1.2.X] Fixed #14164 -- Ensure that sitemap priorities aren't rendered with localized numerical formats. Thanks to dokterbob for the report, and vung for the draft patch.

Backport of r13644 from trunk.

[Russell Keith-Magee]

Getting sitemaps working is a priority, so I've committed the str() based patch. However, I've also opened #14181 to track the larger issue of 'delocalized' template rendering.

[palkeo]

I have applied this patch on my django installation because i had the same problem.

But there is another problem, only with the GenericSitemap : when the priority is not specified, i have « None » in the priority field of the sitemap.

I think you have to modify the lines 84 and 87 of the same file, and change the default value of priority, from None to .

[Russell Keith-Magee]

@palkeo - I can't reproduce the behavior you describe. Defining a sitemap with no priority, or a priority that returns None (either as a class attribute or method) results in the priority field being omitted.

If you still think this is a bug, please open a *new* ticket with a specific test case -- preferably one using the newly provided test suite for the sitemaps app.