Add missing CSS properties for simple markup, refs #6644

It seems that we missed this back when we wrote Dominion. The markup
was being generated (see render_value() in QubitHelper), but it wasn't
styled in the theme.
Handle case where uploads/ not created, refs #7173
Remove admin/bio from DACS tmpl, fixes #6286
Don't use mixed case, refs #6308
Add raw version of refCode in the index, refs #6308

Store a not analyzed version of the inherit_reference_code field for
better sorting. Also, the sorting option was pointing to reference_code
instead of inherit_reference_code causing an error.
s/inheritReferenceCode/referenceCode
Use empty instead of empty + isset
Update © to 2014
Transifex: update slug for 2.1
Support Elasticsearch 1.0+, refs #6334

Squashed commit of the following:

commit 988bff63258260afb6add71f085d325fea05cc25
Author: Jesús García Crespo <jesus@sevein.com>
Date:   Fri Sep 5 17:27:50 2014 +0000

    Check that we are running a recent ES release

    Added a constant MIN_VERSION = "1.3.0". Used version_compare() in order to
    validate the release and cached the result with a short ttl to avoid hitting
    the server every single request.

commit 0634b0db9238d804c292d140aa3c282dc1f907d5
Author: Jesús García Crespo <jesus@sevein.com>
Date:   Fri Sep 5 00:32:39 2014 +0000

    Fix indexing of lat/lon (geo_point type)

    Nulls are not accepted, which is good. But this never came up in ES 0.90,
    I'm guessing they've change they have improved the validation.

commit 199785caa7c11a23d2dac329cead32dbd8c277de
Author: Jesús García Crespo <jesus@sevein.com>
Date:   Tue Sep 2 21:33:40 2014 +0000

    Add custom analyzers with stopwords lists

    Before Elasticsearch 1.0, the standard analyzer used the list of English
    stopwords by default. But now is set to use the empty stopwords.

    This commit defines a set of new analyzers based on the standard analyzer
    for each language where Elasticsearch provides a predefined stopwords list.

commit f2d4b06eca92ff5a40966b364f55e440cafbd7b5
Author: Jesús García Crespo <jesus@sevein.com>
Date:   Sun Aug 31 21:40:52 2014 +0000

    Stop using multi_field type

    Use the new syntax instead, introduced in ES 1.x.

commit 522a01fe86f3ecfde52ec08af983485e162248b5
Author: Jesús García Crespo <jesus@sevein.com>
Date:   Sun Aug 31 21:20:25 2014 +0000

    Update code to expect arrays where "fields" is used

    Field values, in response to the fields parameter, are now always returned
    as arrays by Elasticsearch. We don't really use "fields" much, but I have
    to update the search/autocomplete template to extract the fields attending
    to its new structure.

    More info in "breaking changes in 1.0 » return values":
    http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/_return_values.html

commit 80fae21dfe228b2cab43bbf431de6c46f9b0ed33
Author: Jesús García Crespo <jesus@sevein.com>
Date:   Sun Aug 31 18:34:00 2014 +0000

    Replace deprecated Query\Text with Query\Match

    ES 1.0.0.RC1 removed the text query in support of the match query.
    The behaviour of the match query is pretty similar to its predecessor.

commit 9561e79d0d693579de22ff3927902397d58b8d17
Author: Jesús García Crespo <jesus@sevein.com>
Date:   Sun Aug 31 18:27:24 2014 +0000

    Upgrade Elastica to v1.3.0.0
Add missing gettext call for term label, fixes #4113
Add places and subjects to typeahead, refs #5570
Delete .input-append
Layout fix, grouped input
Escape HTML entities in _inlineSearch
Use .inline-search in move page, fixes #5884
Update  of EAC plugin, fixes #6683
Prevent param override, fixes #7136
Use autocomplete=off in passwd, fixes #7192
Add url to clean search in move page, refs #5884