Age | Commit message (Collapse) | Author |
|
|
|
|
|
failure, further lookups in the same process will be skipped for the next 60 seconds (also configurable).
Makes a Geonames outage much less disruptive to site operations.
|
|
|
|
As there's no admin control panel yet, this is mainly meant for batch administration and using setconfig.php
|
|
regular theme, which works better on its larger screen (was tripped on 'mobile' in the UA though we had no explicit check for 'ipad' previously)
|
|
variables in MobileProfile.
This needs some cleanup...
|
|
* added locale/en/LC_MESSAGES/statusnet.po to make it easier to start customizing English texts
* added notes to locale/README about customizing and how to disable languages you haven't customized
* renamed PO templates from *.po to *.pot to match general conventions and reduce confusion for people trying to find which file they're supposed to edit
|
|
Signed-off-by: Siebrand Mazeland <s.mazeland@xs4all.nl>
|
|
right before the line with the message, otherwise gettext does not pick it up.
* add another TRANS comment
|
|
for the list of groups a user is a member of. I've changed the
wording and added a // TRANS: comment to hopefully make it more
clear.
|
|
|
|
|
|
|
|
Signed-off-by: Siebrand Mazeland <s.mazeland@xs4all.nl>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Setting focus into the form to make it easier to submit by keyboard. Enter or space will now trigger the button right off without having to mouse around to find the button after we've clicked into the conf form, and keyboarders can also get to the 'no' button more easily.
|
|
Setting focus into the form to make it easier to submit by keyboard. Enter or space will now trigger the button right off without having to mouse around to find the button after we've clicked into the conf form, and keyboarders can also get to the 'no' button more easily.
|
|
|
|
The tartget page's URL was not being URL-escaped when passed as a parameter into the query string. Result was that any URL-encoded bytes in the link would be unescaped and interpreted as raw UTF-8 when our bookmarklet post target page reads its parameters; this would break 8-bit high characters (eg a Latin-1 %FC turning into a corrupt UTF-8 byte) or reserved chars that needed to be kept escaped (eg a %3F turning into literal ?)
Unfortunately as this was a bug in the original bookmarklet's JS code, this'll only fix it for people who grab a fresh copy of the bookmarklet.
|
|
The tartget page's URL was not being URL-escaped when passed as a parameter into the query string. Result was that any URL-encoded bytes in the link would be unescaped and interpreted as raw UTF-8 when our bookmarklet post target page reads its parameters; this would break 8-bit high characters (eg a Latin-1 %FC turning into a corrupt UTF-8 byte) or reserved chars that needed to be kept escaped (eg a %3F turning into literal ?)
Unfortunately as this was a bug in the original bookmarklet's JS code, this'll only fix it for people who grab a fresh copy of the bookmarklet.
|
|
Signed-off-by: Siebrand Mazeland <s.mazeland@xs4all.nl>
|
|
|
|
|
|
the packed box loaded at insert time, so we can simply unpack it and check before doing the update query.
Should help with dupes that come in when inbox distrib jobs die and get restarted, etc.
Conflicts:
classes/Inbox.php
Looks like this was implemented on master recently and not copied up to testing. Merging to my version on testing as I've added some doc comments and extracted a couple functions for future ease of use.
|
|
the packed box loaded at insert time, so we can simply unpack it and check before doing the update query.
Should help with dupes that come in when inbox distrib jobs die and get restarted, etc.
|
|
Switching to a raw() output for the <span> of the nickname removes the extra whitespace and fixes display.
|
|
Switching to a raw() output for the <span> of the nickname removes the extra whitespace and fixes display.
|
|
|
|
|
|
to (profile_id, id) instead of (profile_id, created, id).
It's been falling back to PRIMARY instead, which is really
very inefficient for a profile that hasn't posted in a few
months. Even though forcing the index will cause a filesort,
it's usually going to be better. Even for large profiles it
seems much faster than the badly-indexed query.
|
|
to (profile_id, id) instead of (profile_id, created, id).
It's been falling back to PRIMARY instead, which is really
very inefficient for a profile that hasn't posted in a few
months. Even though forcing the index will cause a filesort,
it's usually going to be better. Even for large profiles it
seems much faster than the badly-indexed query.
|
|
location use profile location""
This reverts commit 8b24ad8a9c681585e95612084eb629df8b364b74.
|
|
This reverts commit a09b27ff41df41a86fdb0abae14239907d5ee6ec.
|
|
This reverts commit 650074c648d98f81674c6e2b0ebf052c473ada6e.
|
|
profile location"
This reverts commit 4b80ce0be89fe50eabec1a19dbf4a0c26a413423.
|