Darin Kotter

@aosmichenko Thanks for the PR! This looks like a good start to me but I think there's some changes we need here. Let me know if you're still interested in...

Reading through the ideas that have been floated in this thread, here are my thoughts: The overall structure of the plugin has changed a lot since [this comment](https://github.com/10up/safe-redirect-manager/issues/24#issuecomment-55110810) was added...

**tldr;** I propose we add proper support for 403, 404 and 410 error codes, since we already allow those to be selected when creating redirects. Full thoughts below: Not to...

I looked through the file history to better understand the reasoning behind the current code. Looks like in #11 (Mar 2017) a proposal was put forth to change how we...

> what else is needed to get this PR open for review (and then merged and ready for release)? I've left some comments on things I think should be changed,...

Thanks for all the work here @Sidsector9 (as well as continuing to remind me this needed my attention). I've made a few minor changes, mostly around maintaining backwards compatibility with...

~~Note (mostly for myself so I don't forget) I see two unit tests are failing here. At first glance I think this isn't a regression in the code changes here...

Note that I've updated the readmes with information on how to utilize these new filters

Looked into this today and the short version here is it's not set up to handle blocks properly. Longer version: - When using the `markov` option, we get all `post_content`...

@jeffpaul Excuse my ignorance here but not entirely sure what the difference is between the check added here and the one in #122? On the surface, I like the approach...