updated webform, webform_localization, profile2, term_merge, search_api_saved_pages, rules, redirect, overide_node_options
This commit is contained in:
@@ -2,11 +2,11 @@
|
||||
Localization Update
|
||||
-------------------
|
||||
Automatically download and update your translations by fetching them from
|
||||
http://localize.drupal.org or any other Localization server.
|
||||
https://localize.drupal.org or any other Localization server.
|
||||
|
||||
The l10n update module helps to keep the translation of your drupal core and
|
||||
contributed modules up to date with the central Drupal translation repository
|
||||
at http://localize.drupal.org. Alternatively locally stored translation files
|
||||
at https://localize.drupal.org. Alternatively locally stored translation files
|
||||
can be used as translation source too.
|
||||
|
||||
By choice updates are performed automatically or manually. Locally altered
|
||||
@@ -14,12 +14,13 @@ Localization Update
|
||||
|
||||
The l10n update module is developed for:
|
||||
* Distributions which include their own translations in .po files.
|
||||
* Site admins who want to update the translation with each new module revision.
|
||||
* Site admins who want to update the translation with each new module
|
||||
revision.
|
||||
* Site builders who want an easy tool to download translations for a site.
|
||||
* Multi-sites that share one translation source.
|
||||
|
||||
Project page: http://drupal.org/project/l10n_update
|
||||
Support queue: http://drupal.org/project/issues/l10n_update
|
||||
Project page: https://www.drupal.org/project/l10n_update
|
||||
Support queue: https://www.drupal.org/project/issues/l10n_update
|
||||
|
||||
Installation
|
||||
------------
|
||||
@@ -44,9 +45,11 @@ Update interface translations
|
||||
-----------------------------
|
||||
You want to import translations regularly using cron. You can enable this
|
||||
on Administration > Configuration > Regional and language > Languages:
|
||||
Choose the "Translation updates" tab.
|
||||
Change "Check for updates" to "Daily" or "Weekly" instead of the default "Never".
|
||||
From now on cron will check for updated translations, and import them is required.
|
||||
* Choose the "Translation updates" tab.
|
||||
* Change "Check for updates" to "Daily" or "Weekly" instead of the default
|
||||
"Never".
|
||||
From now on cron will check for updated translations, and import them is
|
||||
required.
|
||||
|
||||
The status of the translations is reported on the "Status report" page at
|
||||
Administration > Reports.
|
||||
@@ -55,7 +58,8 @@ Update interface translations
|
||||
Administration > Configuration > Regional and language > Translate inteface
|
||||
Choose the "Update" tab.
|
||||
You see a list of all modules and their translation status.
|
||||
On the bottom of the page, you can manually update using "Update translations".
|
||||
On the bottom of the page, you can manually update using "Update
|
||||
translations".
|
||||
|
||||
Use Drush
|
||||
---------
|
||||
@@ -68,10 +72,12 @@ Use Drush
|
||||
Summary of administrative pages
|
||||
-------------------------------
|
||||
Translations status overview can be found at
|
||||
Administration > Configuration > Regional and language > Languages > Translation updates
|
||||
Administration > Configuration > Regional and language > Languages
|
||||
> Translation updates
|
||||
|
||||
Update configuration settings can be found at
|
||||
Administration > Configuration > Regional and language > Translate interface > Update
|
||||
Administration > Configuration > Regional and language > Translate interface
|
||||
> Update
|
||||
|
||||
Translating Drupal core, modules and themes
|
||||
-------------------------------------------
|
||||
@@ -90,7 +96,8 @@ Translating Drupal core, modules and themes
|
||||
strings will not be overwritten by translation updates.
|
||||
NOTE: Only manual changes made AFTER installing Localization Update module
|
||||
are preserved. To preserve manual changes made prior to installation of
|
||||
Localization Update module, use the option 'All existing translations are kept...'.
|
||||
Localization Update module, use the option 'All existing translations are
|
||||
kept...'.
|
||||
|
||||
po files, multi site and distributions
|
||||
--------------------------------------
|
||||
@@ -100,7 +107,8 @@ po files, multi site and distributions
|
||||
as their translation source.
|
||||
|
||||
All installations that share the same translation files must be configured
|
||||
with the same 'Store downloaded files' file path e.g. 'sites/all/translations'.
|
||||
with the same 'Store downloaded files' file path e.g.
|
||||
'sites/all/translations'.
|
||||
Set the 'Update source' of one installation to 'Local files and remote server'
|
||||
or 'Remote server only', all other installations are set to
|
||||
'Local files only' or 'Local files and remote server'.
|
||||
@@ -115,6 +123,30 @@ po files, multi site and distributions
|
||||
|
||||
Po files included in distributions should match this syntax too.
|
||||
|
||||
Missing translations
|
||||
--------------------
|
||||
|
||||
If you see "Missing translations for ..." on the Translate interface update
|
||||
page this means that Localization Update module was not able to find a
|
||||
translation file for one or more of your modules or themes. This is usually
|
||||
the case with features, but can also occur with custom modules.
|
||||
|
||||
In case of custom modules, remove the line "project = ..." from the .info
|
||||
file. Only use "project = ..." for modules that are available at drupal.org or
|
||||
custom modules for which an alternative source of translation is provided (see
|
||||
below). In case of a feature add the feature machine name to 'Project' at
|
||||
admin/config/regional/language/update > Disable update. This will prevent
|
||||
Localization Update module from checking for updates for this feature.
|
||||
|
||||
If "missing translations" lists all your enabled modules the webserver has no
|
||||
access to ftp.drupal.org. Contact your hosting to allow access.
|
||||
|
||||
If only a few of your contributed modules are in the list, first verify that
|
||||
the translation is actually missing by visiting the listed URL of the .po file
|
||||
(for example "https://ftp.drupal.org/files/translations/7.x/views/views.hu.po")
|
||||
When the file is not found, you either try again later or contact a
|
||||
translation administrator of your language at https://localize.drupal.org/.
|
||||
|
||||
Alternative source of translation
|
||||
---------------------------------
|
||||
|
||||
@@ -126,7 +158,7 @@ Alternative source of translation
|
||||
|
||||
Modules can force Locale to load the translation of an other project by
|
||||
defining 'interface translation project' in their .info file. This can be
|
||||
usefull for custom modules to use for example a common translation file
|
||||
useful for custom modules to use for example a common translation file
|
||||
|
||||
interface translation project = my_project
|
||||
|
||||
@@ -151,6 +183,16 @@ API
|
||||
|
||||
See l10n_update.api.php for more information.
|
||||
|
||||
Using a Proxy
|
||||
-------------
|
||||
|
||||
Use the cURL HTTP Request module (https://www.drupal.org/project/chr) if your
|
||||
website is behind a proxy. If you want to use an alternative http request
|
||||
function, set the 'drupal_http_request_function', the same way as you would
|
||||
set it to override Drupal core's http_request function:
|
||||
|
||||
$conf['drupal_http_request_function'] = 'my_custom_http_request';
|
||||
|
||||
Maintainers
|
||||
-----------
|
||||
Erik Stielstra
|
||||
|
||||
Reference in New Issue
Block a user