Protecting Articles With Textpattern

As stated previously, I like to post to my blog while maintaining a certain level of privacy. This post serves as nothing more than a little teaser. I’ve spent a few late nights brainstorming, designing and finally implementing a few changes under the hood.

I’ve taken my simple hacks and turned them in to something much friendlier. Storing rules in the plugin code is all fine and dandy, but what happens to the rules if the plugin is ever updated? They are lost. Plain and simple. I wanted a way to persist the rules and I figured a slick admin interface would compliment it nicely.

This image shows the list of currently configured exclusion rules. All rules are tested when an article would be displayed to a user via a page or a feed. I did my best to keep the listing as readable and informative as possible.

Creating or editing a rule had to be very simple. I broke away from the traditional Textpattern edit forms and coalesced the edit form to follow the same concept presented on the list display. I opted for check boxes to idiot proof the interface, otherwise I would risk mistyping a category or not remembering a keyword.

I still have some more improvements that I would like to make to this. I’ve already made quite a few patches to 4.0.5 and I for see a few more in the immediate future. If I continue at the same pace I’m hacking the code, I may bundle all of my patches with the plugin and distribute it as an unofficial Textpattern version. I’m not sure what I would call it, or if I will go through the motions of creating a derivative OSS project. I wonder if the name Manfrepattern is taken. ;)