locale
The locale
keyword returns the locale
. It is determined like this in descending priority:
- URL parameter “locale”
- User locale
- Browser locale
- Default locale (
java.util.Locale.getDefault();
)
You have been redirected from an outdated version of the article. Below is the content available on this topic. To view the old article click here.
The locale
keyword returns the locale
. It is determined like this in descending priority:
java.util.Locale.getDefault();
)The locale
keyword returns the current locale. It is determined like this in descending priority:
locale
locale
java.util.Locale.getDefault();
)Returns a boolean value that indicates whether the locale of the current context is one of the given locale values.
is_locale(locales, ...)
Sets the locale for the current scripting context. This setting directly influences the result of date parsing and formatting functions.
set_locale(locale)
application.localization.logmissing | If enabled, missing requested localizations are logged. |
application.localization.usefallbacklocale | Turns on usage of fallback locale if for the current locale no localization is found |
application.localization.fallbacklocale | The default locale used, if no localization is found and using a fallback is active. |
The Localizations flyout allows you to load all localizations for the given locale on the current page (including the UUID of the details object which is also used for the preview).
A localization is an expression that is included in the content of a page or any other textual element in the following form:
Here, key
is a term describing the concept that should be rendered depending on the locale which is currently active for the accessing user, and domain
describes the context for this term. The combination of key
and domain
has to be unique.
The retrieval process works just as rendering the page. If you request the locale en_US
you might get localizations for en
as a fallback if no exact match is found. If no localization could be found, an empty input field is rendered where you can quickly create the missing localization.
geocoding.provider | Fully qualified class name of the geocoding provider. |
geocoding.language | Locale for the geocoding functionality. |
geocoding.apikey | API key for the geocoding provider. |
folder / file | description |
---|---|
components | Contains the shared components of the pages editor of Structr. |
files | Contains all files out of Sturctr’s virtual filesystem. Folders and files in the virtual filesystem are not being exported by default. If you want to include a folder or file into the export you have to set the flag includeInFrontendExport on each file or folder. Each file or folder will inherit this flag from its parent folder. |
mail-templates | Contains the mail-templates. |
modules | Contains the application configuration and definition of additional modules of Structr e.g. the flow engine. |
pages | Contains the created pages in the pages editor of Structr. |
schema | Contains the schema definition and code entered in the schema and code section of the Structr UI. |
security | Contains the resource access grants defined in the security section of the Structr UI. |
templates | Contains all template elements of the pages editor of Structr. |
application-configuration-data.json | Contains the configured schema layouts of Structr’s schema editor. |
components.json | Contains the settings e.g. visiblity flags, contentType or uuid for each file in the components folder of the export. |
deploy.conf | Contains information about the Structr system that created the export of the application. |
files.json | Contains the settings e.g. visiblity flags, contentType or uuid for each file in the files folder of the export. |
localizations.json | Contains the localizations that where created in the localizations section of the Structr UI and that can be used in server side scripting with the localize() function of Structr. |
mail-templates.json | Contains the settings e.g. visiblity flags, locale or uuid for each file in the mail-templates folder of the export. |
pages.json | Contains the settings e.g. visiblity flags, contentType or uuid for each file in the pages folder of the export. |
pre-deploy.conf | Script that is run before deployment import. Use this to create users who are granted access to nodes in the export files. |
post-deploy.conf | Script that is run after deployment import. Can be used to start any tasks which are necessary after import. |
sites.json | Contains sites that are configured in the pages section of the Structr UI. |
templates.json | Contains the settings e.g. visiblity flags, contentType or uuid for each file in the templates folder of the export. |
widget.json | Contains the widgets that were created in the pages section of the Structr UI. |
page
, pageSize
, sort
, order
, loose
, locale
, latlon
, location
, state
, house
, country
, postalCode
, city
, street
, distance
, outputNestingDepth
, debugLoggingEnabled
, forceResultCount
, disableSoftLimit
, parallelizeJsonOutput
, batchSize
_page
, _pageSize
, _sort
, _order
, _loose
, _locale
, _latlon
, _location
, _state
, _house
, _country
, _postalCode
, _city
, _street
, _distance
, _outputNestingDepth
, _debugLoggingEnabled
,_forceResultCount
, _disableSoftLimit
, _parallelizeJsonOutput
, _batchSize