The default XHR error handler produce an alert which is appropriate to the response status code. It can be overridden per-request (by specifying the `errorHandler` option) so that the alert can be suppressed or displayed in a different position (e.g. inside a modal).
ref #118
- Adds new sub-keys to replace key prefixes, and adjusts key names accordingly.
- Moves several button strings from `admin.permissions_` to `admin.permissions_controls`
- Merges `forum.settings_notify_` strings into `forum.settings`
- Rolls `forum.user_avatar_` strings into `forum.user`
- Moves the `user_deleted_text` to the `lib` namespace.
- Adds four other leftover strings to the `lib` namespace.
- Includes minor changes to formatting and comments.
If the version in the settings table mismatches the code version, then we return a 503 error for all requests coming through index.php and api.php, while admin.php serves up a form prompting for the database password which will run outstanding migrations.
These are the translations for Laravel's Validation component. They are in their own top-level namespace. Unlike the rest of Flarum's translations, the variables are marked by a :colon prefix rather than {curlies}.
Flarum is now powered by Symfony's Translation component, which has a more powerful pluralization system. The rules for all locales are included in core so they no longer need to be included per-language pack. See http://symfony.com/doc/current/components/translation/usage.html#pluralization to learn about the format.
closes#550
We now use Symfony's Translation component. Yay! We get more powerful pluralisation and better a fallback mechanism. Will want to implement the caching mechanism at some point too. The API is replicated in JavaScript, which could definitely use some testing.
Validators have been refactored so that they are decoupled from models completely (i.e. they simply validate arrays of user input). Language packs should include Laravel's validation messages.
ref #267
