WordPress.org

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

Translation of Development Readme (trunk): Dutch

← 1 2 3 … 5 →

Prio	Original string	Translation	—
↑	Network monitor for WordPress. Connection overview for monitoring and controlling outgoing data traffic. Priority: high	You have to log in to add a translation.	Details
Original untranslated Permalink to original Translation History View original in consistency tool Discussion Network monitor for WordPress. Connection overview for monitoring and controlling outgoing data traffic. Comment Short description. You have to log in to edit this translation. Meta Discussion Others Status: untranslated Priority of the original: high Translation Memory Other locales History
↑	Snitch Priority: high	You have to log in to add a translation.	Details
Original untranslated Permalink to original Translation History View original in consistency tool Discussion Snitch Comment Plugin name. You have to log in to edit this translation. Meta Discussion Others Status: untranslated Priority of the original: high Translation Memory Other locales History
	Snitch connection list	You have to log in to add a translation.	Details
Original untranslated Permalink to original Translation History View original in consistency tool Discussion Snitch connection list Comment Screenshot description. You have to log in to edit this translation. Meta Discussion Others Status: untranslated Priority of the original: normal Translation Memory Other locales History
	A complete documentation is available on the <a href="https://snitch.pluginkollektiv.org/documentation/">Snitch website</a>.	You have to log in to add a translation.	Details
Original untranslated Permalink to original Translation History View original in consistency tool Discussion A complete documentation is available on the <a href="https://snitch.pluginkollektiv.org/documentation/">Snitch website</a>. Comment Found in faq paragraph. You have to log in to edit this translation. Meta Discussion Others Status: untranslated Priority of the original: normal Translation Memory Other locales History
	The fact that every new <em>Snitch</em> entry automatically sends a message to Facebook and/or Twitter, is clearly not due to <em>Snitch</em>. Rather, the cause is to be found in the inserted Auto-Tweet-Facebook-Plugin, which faulty triggers an automatic event at every - also non-public - <a href="https://codex.wordpress.org/Post_Types">WordPress Custom Post Type</a>. And that's wrong. The usage of such Plugins should be reconsidered.	You have to log in to add a translation.	Details
Original untranslated Permalink to original Translation History View original in consistency tool Discussion The fact that every new <em>Snitch</em> entry automatically sends a message to Facebook and/or Twitter, is clearly not due to <em>Snitch</em>. Rather, the cause is to be found in the inserted Auto-Tweet-Facebook-Plugin, which faulty triggers an automatic event at every - also non-public - <a href="https://codex.wordpress.org/Post_Types">WordPress Custom Post Type</a>. And that's wrong. The usage of such Plugins should be reconsidered. The fact that every new <em>Snitch</em> entry automatically sends a message to Facebook and/or Twitter, is clearly not due to <em>Snitch</em>. Rather, the cause is to be found in the inserted Auto-Tweet-Facebook-Plugin, which faulty triggers an automatic event at every - also non-public - <a href="https://codex.wordpress.org/Post_Types">WordPress Custom Post Type</a>. And that's wrong. The usage of such Plugins should be reconsidered. Comment Found in faq paragraph. You have to log in to edit this translation. Meta Discussion Others Status: untranslated Priority of the original: normal Translation Memory Other locales History
	And so it quickly happens that Google suddenly hits <em>Snitch</em> entries (as blog pages) which are not intended for public access. For example, because <em>Snitch</em> entries appear in the sitemap XML of the blog, as a sitemap XML plugin is of the opinion that it is also necessary to add private entries and to have them released for indexing. There is also no help to block via <code>robots.txt</code> because the <code>robots.txt</code> file does not prevent the indexing of the pages.	You have to log in to add a translation.	Details
Original untranslated Permalink to original Translation History View original in consistency tool Discussion And so it quickly happens that Google suddenly hits <em>Snitch</em> entries (as blog pages) which are not intended for public access. For example, because <em>Snitch</em> entries appear in the sitemap XML of the blog, as a sitemap XML plugin is of the opinion that it is also necessary to add private entries and to have them released for indexing. There is also no help to block via <code>robots.txt</code> because the <code>robots.txt</code> file does not prevent the indexing of the pages. And so it quickly happens that Google suddenly hits <em>Snitch</em> entries (as blog pages) which are not intended for public access. For example, because <em>Snitch</em> entries appear in the sitemap XML of the blog, as a sitemap XML plugin is of the opinion that it is also necessary to add private entries and to have them released for indexing. There is also no help to block via <code>robots.txt</code> because the <code>robots.txt</code> file does not prevent the indexing of the pages. Comment Found in faq paragraph. You have to log in to edit this translation. Meta Discussion Others Status: untranslated Priority of the original: normal Translation Memory Other locales History
	<em>Snitch</em> stores its entries as <a href="https://codex.wordpress.org/Post_Types">WordPress Custom Post Types</a>. Important step: By a WordPress attribute Snitch marks all log entries as private, therefore not public. So far, the ideology with private and inaccessible entries would work if there were not WordPress plugins that would carry all - including private - Custom Post Types into the world and communicate with search engines. With fatal consequences for the blogger.	You have to log in to add a translation.	Details
Original untranslated Permalink to original Translation History View original in consistency tool Discussion <em>Snitch</em> stores its entries as <a href="https://codex.wordpress.org/Post_Types">WordPress Custom Post Types</a>. Important step: By a WordPress attribute Snitch marks all log entries as private, therefore not public. So far, the ideology with private and inaccessible entries would work if there were not WordPress plugins that would carry all - including private - Custom Post Types into the world and communicate with search engines. With fatal consequences for the blogger. <em>Snitch</em> stores its entries as <a href="https://codex.wordpress.org/Post_Types">WordPress Custom Post Types</a>. Important step: By a WordPress attribute Snitch marks all log entries as private, therefore not public. So far, the ideology with private and inaccessible entries would work if there were not WordPress plugins that would carry all - including private - Custom Post Types into the world and communicate with search engines. With fatal consequences for the blogger. Comment Found in faq paragraph. You have to log in to edit this translation. Meta Discussion Others Status: untranslated Priority of the original: normal Translation Memory Other locales History
	The following code snippet in the WordPress configuration file <code>wp-config.php</code> switches off the logging of the internal WordPress queries:	You have to log in to add a translation.	Details
Original untranslated Permalink to original Translation History View original in consistency tool Discussion The following code snippet in the WordPress configuration file <code>wp-config.php</code> switches off the logging of the internal WordPress queries: Comment Found in faq paragraph. You have to log in to edit this translation. Meta Discussion Others Status: untranslated Priority of the original: normal Translation Memory Other locales History
	If cronjobs are listed too often, something possibly isn't correct. Therefore, it is recommend to check the list of scheduled cronjob jobs.	You have to log in to add a translation.	Details
Original untranslated Permalink to original Translation History View original in consistency tool Discussion If cronjobs are listed too often, something possibly isn't correct. Therefore, it is recommend to check the list of scheduled cronjob jobs. Comment Found in faq paragraph. You have to log in to edit this translation. Meta Discussion Others Status: untranslated Priority of the original: normal Translation Memory Other locales History
	WordPress calls internal Cronjobs via <a href="http://codex.wordpress.org/HTTP_API">WordPress HTTP API</a> - exactly this interface is monitored by <em>Snitch</em> and also records Cronjob accesses accordingly.	You have to log in to add a translation.	Details
Original untranslated Permalink to original Translation History View original in consistency tool Discussion WordPress calls internal Cronjobs via <a href="http://codex.wordpress.org/HTTP_API">WordPress HTTP API</a> - exactly this interface is monitored by <em>Snitch</em> and also records Cronjob accesses accordingly. Comment Found in faq paragraph. You have to log in to edit this translation. Meta Discussion Others Status: untranslated Priority of the original: normal Translation Memory Other locales History
	<em>Snitch</em> catches any connection that leaves the blog via <a href="http://codex.wordpress.org/HTTP_API">WordPress HTTP API</a> (internal WordPress interface for data communication). This affects both the back-end and the front-end of a WordPress installation.	You have to log in to add a translation.	Details
Original untranslated Permalink to original Translation History View original in consistency tool Discussion <em>Snitch</em> catches any connection that leaves the blog via <a href="http://codex.wordpress.org/HTTP_API">WordPress HTTP API</a> (internal WordPress interface for data communication). This affects both the back-end and the front-end of a WordPress installation. Comment Found in faq paragraph. You have to log in to edit this translation. Meta Discussion Others Status: untranslated Priority of the original: normal Translation Memory Other locales History
	DELETE FROM <code>wp_posts</code> WHERE <code>post_type</code> = 'snitch'↵ `	You have to log in to add a translation.	Details
Original untranslated Permalink to original Translation History View original in consistency tool Discussion DELETE FROM <code>wp_posts</code> WHERE <code>post_type</code> = 'snitch'↵ ` Comment Found in faq paragraph. You have to log in to edit this translation. Meta Discussion Others Status: untranslated Priority of the original: normal Translation Memory Other locales History
	<em>Snitch</em> automatically ensures that there are not more than 200 entries are kept in the database. If it is nevertheless necessary to remove <em>Snitch</em> entries from the database manually, two smart database commands could help:	You have to log in to add a translation.	Details
Original untranslated Permalink to original Translation History View original in consistency tool Discussion <em>Snitch</em> automatically ensures that there are not more than 200 entries are kept in the database. If it is nevertheless necessary to remove <em>Snitch</em> entries from the database manually, two smart database commands could help: Comment Found in faq paragraph. You have to log in to edit this translation. Meta Discussion Others Status: untranslated Priority of the original: normal Translation Memory Other locales History
	As a reminder: <em>Snitch</em> is designed to help you improve your WordPress performance by detecting and displaying connections as bottleneck. The task for the blog administrator is to eliminate the source of the cause (plugin, theme, etc.).	You have to log in to add a translation.	Details
Original untranslated Permalink to original Translation History View original in consistency tool Discussion As a reminder: <em>Snitch</em> is designed to help you improve your WordPress performance by detecting and displaying connections as bottleneck. The task for the blog administrator is to eliminate the source of the cause (plugin, theme, etc.). Comment Found in faq paragraph. You have to log in to edit this translation. Meta Discussion Others Status: untranslated Priority of the original: normal Translation Memory Other locales History
	<em>Snitch</em> is designed to log any outgoing connection in WordPress. If the database fills fast, you should look up the cause. Why does your WordPress and plugins communicate so often to the outside that the database table fills? Is this communication really necessary?	You have to log in to add a translation.	Details
Original untranslated Permalink to original Translation History View original in consistency tool Discussion <em>Snitch</em> is designed to log any outgoing connection in WordPress. If the database fills fast, you should look up the cause. Why does your WordPress and plugins communicate so often to the outside that the database table fills? Is this communication really necessary? Comment Found in faq paragraph. You have to log in to edit this translation. Meta Discussion Others Status: untranslated Priority of the original: normal Translation Memory Other locales History

Legend:

Current

Waiting

Rejected

Fuzzy

Old

Changes requested

With warnings

← 1 2 3 … 5 →

Export as

Translation of Development Readme (trunk): Dutch

Original untranslated

Original untranslated

Original untranslated

Original untranslated

Original untranslated

Original untranslated

Original untranslated

Original untranslated

Original untranslated

Original untranslated

Original untranslated

Original untranslated

Original untranslated

Original untranslated

Original untranslated