New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Advanced Custom Fields: Table Field | Advanced Custom Fields: Table Field | Details |
Original current |
|||
| ↑ | A Table Field Add-on for the Advanced Custom Fields Plugin. | Een tabelveld add-on voor de Advanced Custom Fields plugin. | Details |
Original current
A Table Field Add-on for the Advanced Custom Fields Plugin.
CommentShort description. You have to log in to edit this translation. |
|||
| <strong>Notice</strong> | <strong>Bericht</strong> | Details | |
Original current
<strong>Notice</strong>
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| The table field works also with the repeater and flexible field types and supports the <a href="https://www.advancedcustomfields.com/blog/acf-5-8-introducing-acf-blocks-for-gutenberg/">ACF Blocks for Gutenberg</a> | Het tabelveld werkt ook met de repeater en flexibele veldtypes en ondersteunt de <a href="https://www.advancedcustomfields.com/blog/acf-5-8-introducing-acf-blocks-for-gutenberg/">ACF Blocks for Gutenberg</a> | Details | |
Original current
The table field works also with the repeater and flexible field types and supports the <a href="https://www.advancedcustomfields.com/blog/acf-5-8-introducing-acf-blocks-for-gutenberg/">ACF Blocks for Gutenberg</a>
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Updating a table using update_field() | Een tabel updaten met update_field() | Details | |
Original current
Updating a table using update_field()
CommentFound in faq header. You have to log in to edit this translation. |
|||
| The table field plugin prevents broken JSON strings to save as a table field data and throws an error message that explains the issue. But this may also breaks the functionality of the third party plugin trying to update the table data. You could disable the JSON string check in the table field plugin using the following code in the wp-config.php file. But then the table JSON data are no longer protected from destroing by <code>update_post_metadata()</code>. Use the following code in wp-config.php only, if you understand the risk… | De tabel veld plugin voorkomt dat gebroken JSON strings worden opgeslagen als een tabel veld gegevens en geeft een melding met uitleg over het probleem. Maar dit kan ook de functionaliteit van de derde partij plugin breken die probeert de tabelgegevens te updaten. Je zou de JSON string controle in de tabelveld plugin kunnen uitschakelen met de volgende code in het wp-config.php bestand. Maar dan zijn de tabel JSON gegevens niet langer beschermd tegen vernietiging door <code>update_post_metadata()</code>. Gebruik de volgende code alleen in wp-config.php, als je het risico begrijpt... | Details | |
Original current
The table field plugin prevents broken JSON strings to save as a table field data and throws an error message that explains the issue. But this may also breaks the functionality of the third party plugin trying to update the table data. You could disable the JSON string check in the table field plugin using the following code in the wp-config.php file. But then the table JSON data are no longer protected from destroing by <code>update_post_metadata()</code>. Use the following code in wp-config.php only, if you understand the risk…
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Since version 1.3.1 of the table plugin, the storing format of the table data changes from JSON string to serialized array for new or updated tables. The issue with JSON is because of third party plugins that do not properly applying <code>wp_slash()</code> to a post_meta value before updating with <code>update_post_metadata()</code>. This can break JSON strings because <code>update_post_metadata()</code> removes backslashes by default. Backslashes are part of the JSON string syntax escaping quotation marks in content. | Sinds versie 1.3.1 van de tabel plugin verandert het opslag format van de tabel gegevens van JSON string naar geserialiseerde array voor nieuwe of geüpdatet tabellen. Het probleem met JSON is te wijten aan plugins van derden die <code>wp_slash()</code> niet correct toepassen naar een post_meta waarde, alvorens bij te werken met <code>update_post_metadata()</code>. Dit kan JSON strings breken omdat <code>update_post_metadata()</code> standaard backslashes verwijdert. Backslashes maken deel uit van de JSON string syntaxis om aanhalingstekens in de inhoud te escapen. | Details | |
Original current
Since version 1.3.1 of the table plugin, the storing format of the table data changes from JSON string to serialized array for new or updated tables. The issue with JSON is because of third party plugins that do not properly applying <code>wp_slash()</code> to a post_meta value before updating with <code>update_post_metadata()</code>. This can break JSON strings because <code>update_post_metadata()</code> removes backslashes by default. Backslashes are part of the JSON string syntax escaping quotation marks in content.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Plugin name.