New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Import and export your widgets. | Importeer en exporteer je widgets. | Details |
Original current |
|||
| ↑ | Widget Importer & Exporter | Widget Importer & Exporter | Details |
Original current |
|||
| Widget Importer & Exporter is useful for moving widgets from one WordPress site to another, backing up widgets and for theme developers to give users sample widgets. See the <a href="https://churchthemes.com/plugins/widget-importer-exporter/">details</a> on ChurchThemes.com. | Widget Importer & Exporter is handig voor het verplaatsen van widgets van de ene WordPress site naar de andere, het maken van back-ups van widgets en voor thema-ontwikkelaars om gebruikers voorbeeld widgets te geven. Zie de <a href="https://churchthemes.com/plugins/widget-importer-exporter/">details</a> op ChurchThemes.com. | Details | |
Original current
Widget Importer & Exporter is useful for moving widgets from one WordPress site to another, backing up widgets and for theme developers to give users sample widgets. See the <a href="https://churchthemes.com/plugins/widget-importer-exporter/">details</a> on ChurchThemes.com.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| The export file contains JSON data that is not compatible with any other plugin. Therefore it has a proprietary file extension. This keeps people from confusing export files from other widget import/export plugins. | Het exportbestand bevat JSON gegevens die niet compatibel zijn met een andere plugin. Daarom heeft het een eigen bestandsextensie. Dit voorkomt dat mensen de export bestanden van andere widget import/export plugins door elkaar halen. | Details | |
Original current
The export file contains JSON data that is not compatible with any other plugin. Therefore it has a proprietary file extension. This keeps people from confusing export files from other widget import/export plugins.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Why does the JSON export file use a .wie extension? | Waarom heeft het JSON exportbestand een .wie extensie? | Details | |
Original current
Why does the JSON export file use a .wie extension?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| After activation, go to <em>Tools > Widget Importer & Exporter</em> | Na activering, ga naar <em>Gereedschappen > Widget Importer & Exporter</em> | Details | |
Original current
After activation, go to <em>Tools > Widget Importer & Exporter</em>
CommentFound in installation paragraph. You have to log in to edit this translation. |
|||
| Please see <a href="http://codex.wordpress.org/Managing_Plugins#Installing_Plugins">Installing Plugins</a> in the WordPress Codex. | Zie <a href="http://codex.wordpress.org/Managing_Plugins#Installing_Plugins">Installeren van plugins</a> in de WordPress Codex. | Details | |
Original current
Please see <a href="http://codex.wordpress.org/Managing_Plugins#Installing_Plugins">Installing Plugins</a> in the WordPress Codex.
CommentFound in installation paragraph. You have to log in to edit this translation. |
|||
| Please jump on <a href="https://github.com/churchthemes/widget-importer-exporter">GitHub</a> to report issues and follow development. | Ga naar <a href="https://github.com/churchthemes/widget-importer-exporter">GitHub</a> om problemen te melden en de ontwikkeling te volgen. | Details | |
Original current
Please jump on <a href="https://github.com/churchthemes/widget-importer-exporter">GitHub</a> to report issues and follow development.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| The <code>wie_before_import</code> action fires after a file is uploaded but before the data is imported. <code>wie_after_import</code> fires after the data is imported. The <code>wie_import_data</code> filter can be used to filter data before it is imported. Other filters are used throughout. Make a pull request on GitHub if you need another hook. | De <code>wie_before_import</code> actie vuurt af nadat een bestand is geüpload, maar voordat de gegevens is geïmporteerd. <code>wie_after_import</code> vuurt af nadat de gegevens zijn geïmporteerd. Het <code>wie_import_data</code> filter kan worden gebruikt om gegevens te filteren voordat ze worden geïmporteerd. Andere filters worden overal gebruikt. Doe een pull aanvraag op GitHub als je een andere hook nodig hebt. | Details | |
Original current
The <code>wie_before_import</code> action fires after a file is uploaded but before the data is imported. <code>wie_after_import</code> fires after the data is imported. The <code>wie_import_data</code> filter can be used to filter data before it is imported. Other filters are used throughout. Make a pull request on GitHub if you need another hook.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Widget Importer & Exporter can create an export file (in JSON format with .wie extension) out of currently active widgets. This file can be imported into other sites using this plugin or used to restore widgets to the same site later. | Widget Importer & Exporter kan een export bestand maken (in JSON format met .wie extensie) van de op dat moment actieve widgets. Dit bestand kan geïmporteerd worden in andere sites met deze plugin of gebruikt worden om widgets later terug te zetten op dezelfde site. | Details | |
Original current
Widget Importer & Exporter can create an export file (in JSON format with .wie extension) out of currently active widgets. This file can be imported into other sites using this plugin or used to restore widgets to the same site later.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Importation takes into consideration widget areas not existing in the current theme (widgets imported as <em>Inactive</em>), widgets that already exist in the same widget area (widgets not duplicated) and widgets that are not supported by the site (widgets not imported). | Bij het importeren wordt rekening gehouden met widget gebieden die niet bestaan in het huidige thema (widgets geïmporteerd als <em>Inactief</em>), widgets die al bestaan in hetzelfde widget gebied (widgets niet gedupliceerd) en widgets die niet worden ondersteund door de site (widgets niet geïmporteerd). | Details | |
Original current
Importation takes into consideration widget areas not existing in the current theme (widgets imported as <em>Inactive</em>), widgets that already exist in the same widget area (widgets not duplicated) and widgets that are not supported by the site (widgets not imported).
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Importing is done by uploading an export file created by the plugin. The results of an import are shown in a nicely formatted table with an explanation of what happened with each widget area and widget. | Importeren wordt gedaan door het uploaden van een export bestand gemaakt door de plugin. De resultaten van een import worden getoond in een mooi opgemaakte tabel met een uitleg van wat er is gebeurd met elk widget gebied en widget. | Details | |
Original current
Importing is done by uploading an export file created by the plugin. The results of an import are shown in a nicely formatted table with an explanation of what happened with each widget area and widget.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Developers | Ontwikkelaars | Details | |
Original current |
|||
| Exporting | Exporteren | Details | |
Original current |
|||
| Importing | Importeren | Details | |
Original current |
|||
Export as
Comment
Short description.