Matt Amos [Thu, 6 Aug 2009 17:28:49 +0000 (17:28 +0000)]
Made XML parsing routines raise an exception if the document is valid XML, but not valid as an OSM document. This is now the same behaviour as when the document isn't valid XML.
Tom Hughes [Wed, 5 Aug 2009 23:39:24 +0000 (23:39 +0000)]
Render the links using partial so we can do the appropriate rendering
for HTML and Atom versions and hopefully get the escaping right in the
feed. Closes #2135.
Tom Hughes [Mon, 3 Aug 2009 23:42:29 +0000 (23:42 +0000)]
Rework password reset system to do away with the second email and instead
just allow the user (providing they possess a valid token from the first
email) to enter a new password on the site.
Change the messages on the changeset page so that @heading is succinct
and @description has more detail. This looks better than having the
two be equivalent and the <h1> would sometimes overflow the page with
long usernames.
Atom readers (Firefox/Liferea) don't like when we embed XHTML anchors
in the description. So adjust the code that creates the changeset
browser title/description to emit a XHTML and plaintext version with
the HTML and Atom output can use, respectively.
Also:
* Split up @title into @title and @heading as elsewhere
* Turn the username on the user / user+bbox browser into a link to the userpage
* Say "Changesets" instead of "Recent changes". Unlike Wikipedia the changes on OSM aren't guaranteed to be recent, they're just going to be the latest
* Turn the hardcoded #<%= changeset.id %> into t('msg', :id =>
changeset.id). Some languages may have a different numeric
indicator than the ASCII pound symbol
* Instead of including a column on :user/edits with a "more" link
make the changeset ID link to the changeset page.
Matt Amos [Tue, 28 Jul 2009 16:09:13 +0000 (16:09 +0000)]
Fixed dumb-arse bug with wrong variable name. Added tag cleanup and checking on nodes which are part of ways (i.e: not 'POIs' in potlatch terminology).
Tom Hughes [Tue, 21 Jul 2009 20:23:07 +0000 (20:23 +0000)]
Update the :en and :sl pluralizers to default to :other if a more
specific key does not exist. This then allows r16613 to be reverted
as there is no need to distinguish the cases. Fixes #2087.
Tom Hughes [Wed, 15 Jul 2009 23:42:56 +0000 (23:42 +0000)]
Fix compatible_language_from in the http_accept_language plugin to
correctly follow the RFC 2616 language selection algorithm and then
revert to the previous way of selecting languages.
Tom Hughes [Wed, 15 Jul 2009 23:29:07 +0000 (23:29 +0000)]
Try preferred_language_from as it looks for an exact match - only if that
fails do we fall back to compatible_language_from which will take any
language where the first token matches. Fixes #2069.
New Potlatch translations pulled in as a result of http://wiki.openstreetmap.org/index.php?title=Template%3APotlatch%2FTranslation&diff=302859&oldid=301148
Potlatch's i18n support predates our Rails i18n effort, so it was
still doing its own language detection.
Scrap that and use I18n.locale instead, now Potlatch is guaranteed to
use whatever translation the rest of the site uses.
I've tested this by switching the language in preferences back and
forth, and also ensured that Potlatch will fall back on English if the
specified language doesn't exist in its list of translations.
Fixed a bug in how fields in /message/new were being pre-filled out.
When someone went to /message/new/:user the "Subject" are would be
pre-filled out with t('message.new.title'). The problem was that the
@title template variable was being used for two purposes, to set the
HTML <title> AND to pre-fill out the subject.
We don't always want these two to be the same, but sometimes we
do. E.g. when someone replies to a diary entry and visits
/message/new/:user?title=Foo we want Foo in the <title> and in the
pre-filled out Subject, and the same goes for replying to a message.
So I've split up the @title variable into @title and @subject.
projects / rails.git / log