Pär Thernström

Earth People

WP JS Error Logger is a small plugin that I very quickly put together after wathcing <a href="https://twitter.com/dicode" rel="nofollow ugc">Diogo Antunes’</a> presentation <a href="https://speakerdeck.com/dicode/know-your-errors" rel="nofollow ugc">“Know your errors”</a> at <a href="http://2013.front-trends.com/" rel="nofollow ugc">Front Trends 2013</a> in Warsaw, Poland.
It’s a plugin that will log the JavaScript-errors that occur on the front-end of your public website. Errors are logged to a non-public custom post type inside WordPress.
The errors that are logged are the errors that call window.onerror. Please note that not all errors end up there. But… some do, and now you can catch them! 😉

WP JavaScript Error Logger

A plugin that will log JavaScript-errors that occurs on the front-end of your website. Errors are logged to a non-public custom post type.

Samir Shah

Matt Calvert

This plugin issues an HTTP <code>410</code> response for URLs corresponding to content that has been permanently removed from your site. Originally created by Samir Shah, now maintained by Matt Calvert. When a post or page is deleted, the plugin logs the old URL and returns a <code>410</code> response when that URL is requested. You can also manually manage the list of obsolete URLs.
The <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.11" rel="nofollow ugc">HTTP Specification</a> defines the <code>410 Gone</code> response for resources that have been permanently removed. It informs search engines and crawlers that the content will not return, improving crawl efficiency and SEO clarity.
This plugin is actively maintained by Matt Calvert as a personal project, informed by previous professional experience with similar 410-handling logic. No proprietary or employer-owned code has been used.

HTTP 410 (Gone) responses

Sends HTTP 410 (Gone) responses for deleted content, telling search engines the page is permanently removed.

WP JavaScript Error Logger vs HTTP 410 (Gone) responses