New to Translating WordPress? Read through our Translator Handbook to get started. Hide

Translation of Development Readme (trunk): Dutch

1 2
Prio Original string Translation
Advanced Custom Fields: Table Field
Priority: high
Advanced Custom Fields: Table Field Details
Advanced Custom Fields: Table Field
Comment

Plugin name.

You have to log in to edit this translation.

A Table Field Add-on for the Advanced Custom Fields Plugin.
Priority: high
Een tabelveld add-on voor de Advanced Custom Fields plugin. Details
A Table Field Add-on for the Advanced Custom Fields Plugin.
Comment

Short description.

You have to log in to edit this translation.

<strong>Example of changing table data using get_field() and update_field()</strong> <strong>Voorbeeld van het veranderen van tabelgegevens met get_field() en update_field()</strong> Details
<strong>Example of changing table data using get_field() and update_field()</strong>
Comment

Found in faq paragraph.

You have to log in to edit this translation.

The table data obtained by get_field() are formatted and differ by the original database data obtained by get_post_meta(). De tabelgegevens die zijn verkregen door get_field() zijn geformatteerd en verschillen van de oorspronkelijke databasegegevens verkregen door get_post_meta(). Details
The table data obtained by get_field() are formatted and differ by the original database data obtained by get_post_meta().
Comment

Found in faq list item.

You have to log in to edit this translation.

The array key 'c' stands for the content of the cells to have the option of adding other cell setting in future development. De array-sleutel "c" staat voor de inhoud van de cellen om de mogelijkheid te hebben in de toekomstige ontwikkeling andere celinstellingen toe te voegen. Details
The array key 'c' stands for the content of the cells to have the option of adding other cell setting in future development.
Comment

Found in faq list item.

You have to log in to edit this translation.

Make sure that the number of entries in the header array matches the number of cells in the body rows. Zorg ervoor dat het aantal items in de header array overeenkomt met het aantal cellen in de body rijen. Details
Make sure that the number of entries in the header array matches the number of cells in the body rows.
Comment

Found in faq list item.

You have to log in to edit this translation.

<strong>Notice</strong> <strong>Bericht</strong> Details
<strong>Notice</strong>
Comment

Found in faq paragraph.

You have to log in to edit this translation.

<strong>Example of adding a new row</strong> <strong>Voorbeeld van het toevoegen van een nieuwe rij</strong> Details
<strong>Example of adding a new row</strong>
Comment

Found 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
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>
Comment

Found in description paragraph.

You have to log in to edit this translation.

You can use the ACF PHP function <code>update_field()</code> to change a tables data. Je kunt de ACF PHP functie <code>update_field()</code> gebruiken om de gegevens van een tabel te wijzigen. Details
You can use the ACF PHP function <code>update_field()</code> to change a tables data.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Updating a table using update_field() Een tabel updaten met update_field() Details
Updating a table using update_field()
Comment

Found 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
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…
Comment

Found 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
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.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Third party plugins issues Problemen met plugins van derden Details
Third party plugins issues
Comment

Found in faq header.

You have to log in to edit this translation.

If the table has only one empty cell, then <code>get_field()</code> returns <code>FALSE</code>. <code>get_field()</code> returns NULL when a field is not stored in the database. That happens when a page is copied but not their fields content. You can check both with <code>empty()</code> Als de tabel slechts één lege cel heeft, dan geeft <code>get_field()</code> een <code>FALSE</code> terug. <code>get_field()</code> geeft NULL terug wanneer een veld niet in de database is opgeslagen. Dat gebeurt als een pagina wordt gekopieerd, maar niet de inhoud van de velden. Je kunt beide controleren met <code>empty()</code>... Details
If the table has only one empty cell, then <code>get_field()</code> returns <code>FALSE</code>. <code>get_field()</code> returns NULL when a field is not stored in the database. That happens when a page is copied but not their fields content. You can check both with <code>empty()</code>
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Legend:
Current
Waiting
Rejected
Fuzzy
Old
Changes requested
With warnings
1 2

Export as