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

This plugin will issue a HTTP <code>410</code> response to requests for articles that no longer exist on your blog. When you delete a post or page, it records the URL for that page and issues 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</code> response header for use when a resource has been permanently removed. It informs robots visiting your site that the requested content has gone, and that they should stop trying to access it.
If you come across any bugs or have suggestions, please use the plugin support forum. I can’t fix it if I don’t know it’s broken! Please check the <a href="https://wordpress.org/extend/plugins/wp-410/faq/" rel="ugc">FAQ</a> for common issues.

410 for WordPress

A plugin that sends HTTP 410 (Gone) responses to requests for articles that no longer exist on your blog.

WP JavaScript Error Logger vs 410 for WordPress