New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Network monitor for WordPress. Connection overview for monitoring and controlling outgoing data traffic. | Netzwerkmonitor für WordPress. Verbindungsübersicht zur Überwachung und Kontrolle des ausgehenden Datenverkehrs. | Details |
Original current
Network monitor for WordPress. Connection overview for monitoring and controlling outgoing data traffic.
You have to log in to edit this translation. |
|||
| ↑ | Snitch | Snitch | Details |
Original current |
|||
| Please report security bugs found in the source code of the Snitch plugin through the <a href="https://patchstack.com/database/vdp/a690b1e7-428e-4bc5-a01d-2353ebf45f7b">Patchstack Vulnerability Disclosure Program</a>. The Patchstack team will assist you with verification, CVE assignment, and notify the developers of this plugin. | Bitte melde Sicherheitslücken, die im Quellcode des Snitch Plugins gefunden wurden, über das <a href="https://patchstack.com/database/vdp/a690b1e7-428e-4bc5-a01d-2353ebf45f7b">Patchstack Vulnerability Disclosure Program</a>. Das Patchstack-Team wird dich bei der Überprüfung und CVE-Zuordnung unterstützen und die Entwickler dieses Plugins benachrichtigen. | Details | |
Original current
Please report security bugs found in the source code of the Snitch plugin through the <a href="https://patchstack.com/database/vdp/a690b1e7-428e-4bc5-a01d-2353ebf45f7b">Patchstack Vulnerability Disclosure Program</a>. The Patchstack team will assist you with verification, CVE assignment, and notify the developers of this plugin.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Where do I report security bugs found in this plugin? | Wo melde ich Sicherheitslücken, die ich in diesem Plugin finde? | Details | |
Original current
Where do I report security bugs found in this plugin?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| Snitch connection list | Snitch Verbindungsliste | Details | |
Original current |
|||
| A complete documentation is available on the <a href="https://snitch.pluginkollektiv.org/documentation/">Snitch website</a>. | Die vollständige Dokumentation ist auf der <a href="https://snitch.pluginkollektiv.org/de/dokumentation/">Snitch-Website</a> verfügbar. | Details | |
Original current
A complete documentation is available on the <a href="https://snitch.pluginkollektiv.org/documentation/">Snitch website</a>.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| 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. | Die Tatsache, dass jeder neue <em>Snitch</em>-Eintrag automatisch eine Nachricht an Facebook und/oder Twitter sendet, liegt eindeutig nicht an <em>Snitch</em>. Vielmehr ist die Ursache im eingebauten Auto-Tweet-Facebook-Plugin zu suchen, das fälschlicherweise bei jedem - auch nicht-öffentlichen - <a href="https://wordpress.org/support/article/post-types/">WordPress Individuellen Inhaltstyp</a> ein automatisches Ereignis auslöst. Und das ist falsch. Die Verwendung solcher Plugins sollte überdacht werden. | Details | |
Original current
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.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| 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. | Und so passiert es schnell, dass Google plötzlich auf <em>Snitch</em>-Einträge (als Blog-Seiten) stößt, die nicht für die Öffentlichkeit bestimmt sind. Zum Beispiel, weil <em>Snitch</em>-Einträge in der Sitemap-XML des Blogs auftauchen, da ein Sitemap-XML-Plugin der Meinung ist, dass man auch private Einträge hinzufügen und für die Indexierung freigeben muss. Da hilft auch keine Sperrung per <code>robots.txt</code>, denn die <code>robots.txt</code>-Datei verhindert nicht die Indexierung der Seiten. | Details | |
Original current
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.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| <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> speichert seine Einträge als <a href="https://wordpress.org/support/article/post-types/">WordPress Individuelle Inhaltstypen</a>. Wichtiger Schritt: Über ein WordPress-Attribut markiert Snitch alle Protokolleinträge als privat, also nicht öffentlich. So weit würde die Ideologie mit den privaten und unzugänglichen Einträgen funktionieren, wenn es nicht WordPress-Plugins gäbe, die alle - auch die privaten - Individuellen Inhaltstypen in die Welt tragen und mit Suchmaschinen kommunizieren. Mit fatalen Folgen für den Blogger. | Details | |
Original current
<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.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| The following code snippet in the WordPress configuration file <code>wp-config.php</code> switches off the logging of the internal WordPress queries: | Der folgende Codeschnipsel in der WordPress-Konfigurationsdatei <code>wp-config.php</code> schaltet die Protokollierung der internen WordPress-Abfragen aus: | Details | |
Original current
The following code snippet in the WordPress configuration file <code>wp-config.php</code> switches off the logging of the internal WordPress queries:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| If cronjobs are listed too often, something possibly isn't correct. Therefore, it is recommend to check the list of scheduled cronjob jobs. | Wenn Cronjobs zu oft angezeigt werden, stimmt vermutlich irgendwas nicht. Daher empfiehlt es sich, die Liste der geplanten Cronjobs zu überprüfen. | Details | |
Original current
If cronjobs are listed too often, something possibly isn't correct. Therefore, it is recommend to check the list of scheduled cronjob jobs.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| 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. | WordPress ruft interne Cronjobs über die <a href="https://developer.wordpress.org/plugins/http-api/">WordPress HTTP API</a> auf - genau diese Schnittstelle wird von <em>Snitch</em> überwacht und zeichnet auch die Cronjob-Zugriffe entsprechend auf. | Details | |
Original current
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.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| <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. | <em>Snitch</em> erfasst jede Verbindung, die den Blog über die <a href="https://developer.wordpress.org/plugins/http-api/">WordPress HTTP API</a> (interne WordPress-Schnittstelle zur Datenkommunikation) verlässt. Dies betrifft sowohl das Backend als auch das Frontend einer WordPress-Installation. | Details | |
Original current
<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.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| DELETE FROM <code>wp_posts</code> WHERE <code>post_type</code> = 'snitch'↵ ` | DELETE FROM <code>wp_posts</code> WHERE <code>post_type</code> = 'snitch' ` | Details | |
Original current
DELETE FROM <code>wp_posts</code> WHERE <code>post_type</code> = 'snitch'↵
`
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| <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: | <em>Snitch</em> stellt automatisch sicher, dass nicht mehr als 200 Einträge in der Datenbank behalten werden. Wenn es trotzdem erforderlich ist, <em>Snitch</em>-Einträge manuell aus der Datenbank zu entfernen, helfen zwei Datenbankabfragen: | Details | |
Original current
<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:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.