Customizability is the Key!
Lets face it MT Protect 1.x is hard to customize. Sure you've got 5 (!) attributes to customize the various messages to appear but they were hard to remember (
oi_barred_text - I had to look these up from the manual!) and if you used them all, you could end up with this monstrosity:
<MTEntryProtect password_text="Entry Password Protected" tk_signin_text="Sign in with TK" tk_barred_text="Sorry, not allowed" oi_signin_text="OpenID Protected" oi_barred_text="You are not allowed to read this">
And that was only customizing the message, the rest of the form was hardcoded into the plugin. So that entire mess was scrapped with v2.0 and you've now got a mini template.
The mini template is used in conjunction with the
MTProtect tags. Whenever an entry, category or blog is protected, the contents of the mini template is parsed and shown. By default it looks like this (kudos to PlasticMind Design for the fabulous buttons)
Click one of the buttons and the appropriate form appears.
The beauty of the mini template is that not only can you define it at both the system and blog levels (with the blog level template overriding the system level template) it can be completely changed and recognizes all Movable Type template tags!
How's that for customizability?