Changeset 176

Timestamp:

01/19/07 11:51:41 (2 years ago)

Author:

jallen

Message:

Comment Challenge Version 1.02
* Fixed 'Can't locate object method "translate"' error under MT 3.2
* Implemented backwards-compatible L10N for MT 3.2
* Augmented the en_us L10N phrase file to aid in localization
* Some "best practices" code rearrangement

Files:

• trunk/comment_challenge/plugins/commchallenge/commchallenge.pl (modified) (4 diffs)
• trunk/comment_challenge/plugins/commchallenge/lib/commchallenge.pm (modified) (1 diff)
• trunk/comment_challenge/plugins/commchallenge/lib/commchallenge/L10N.pm (modified) (1 diff)
• trunk/comment_challenge/plugins/commchallenge/lib/commchallenge/L10N/en_us.pm (modified) (1 diff)
• trunk/comment_challenge/plugins/commchallenge/tmpl/blog_config.tmpl (modified) (5 diffs)

trunk/comment_challenge/plugins/commchallenge/commchallenge.pl

@@ -8 +8 @@
-
-use strict;
+use 5.006;    # requires Perl 5.6.x
+use MT 3.2;   # requires MT 3.2 or later
+use warnings;
+
-use constant DEBUG_MODE => 0;
-
+
-use base 'MT::Plugin';
-use MT::JunkFilter qw(ABSTAIN);
-use vars qw($VERSION $plugin $_cache);
-
-
-
+
+
+
+
+
-    name => 'Comment Challenge',
-    version => $VERSION,
@@ -33 +38 @@
-        ['commchallenge_throttle_nobeacon', { Default => 0 }]
-    ]),
-
-
+
+
+
+
+
+
+
+
-
-require MT::Template::Context;
@@ -57 +68 @@
-}
-
-# sub apply_default_settings {
-#     my $plugin = shift;
-#     my ($data, $scope) = @_;
-#     if ($scope ne 'system') {
-#         my $sys = $plugin->get_config_obj('system');
-#         my $sysdata = $sys->data();
-#         if ($plugin->{settings} && $sysdata) {
-#             foreach (keys %$sysdata) {
-#                 $data->{$_} = $sysdata->{$_}
-#                     if (!exists $data->{$_}) || (!defined $data->{$_});
-#             }
-#         }
-#     } else {
-#         $plugin->SUPER::apply_default_settings(@_);
-#     }
-# }
-
-sub load_tmpl {
@@ -99 +94 @@
-}
-
+# We use an MT::App::CMS::pre_run callback to
+# bootstrap the plugin's localization module
+# and then handle the translate calls if needed.
+sub add_l10n {
+    my ($cb,$app) = @_;
+    (my $lang = $app->current_language) =~ s/-/_/g;
+    eval "require commchallenge::L10N::$lang";
+}
+sub translate {
+    my $plugin = shift;
+    return $MT::VERSION < 3.3   ?   MT->instance->translate(@_)
+                                :   $plugin->SUPER::translate(@_);
+}
+
-# Utility debug method for writing to error log
-sub debug {

trunk/comment_challenge/plugins/commchallenge/lib/commchallenge.pm

@@ -6 +6 @@
-
-package commchallenge;
+
+use MT::JunkFilter qw(ABSTAIN);
-
-use constant DEBUG_MODE => 0;

trunk/comment_challenge/plugins/commchallenge/lib/commchallenge/L10N.pm

@@ -2 +2 @@
-use strict;
-
-
+
+
+
+
+
-
-1;

trunk/comment_challenge/plugins/commchallenge/lib/commchallenge/L10N/en_us.pm

@@ -5 +5 @@
-# $Id$
-
+# Comment challenge localization file
+#
+# This package defines the English phrases used by the plugin
+# and can be used as a basis for localization of Comment Challenge
+#
+# To create a localization, simply do the following:
+#
+# 1) Create a copy of this file with a name beginning with your
+#    language code and ending in '.pm'.  For example, a French
+#    localization file would be named 'fr.pm'.
+# 2) Translate the strings on the right side of the => operators
+#    below or on the following line if following a => operator.
+#    You must use a backslash to escape single quotes.
+# 3) Replace all occurances of 'en_us' in this file with your
+#    own language code
+#
-package commchallenge::L10N::en_us;
-
-use strict;
-
-use base 'commchallenge::L10N';
-use vars qw( %Lexicon );
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
-1;

trunk/comment_challenge/plugins/commchallenge/tmpl/blog_config.tmpl

@@ -5 +5 @@
-                <ul>
-                <li>
-Check for MTCommentChallenge beacon in comment submissions.
-This option prevents spam bots from directly injecting comments into the system via the comment script.">  <TMPL_UNLESS NAME=COMMCHALLENGE_MODE><MT_TRANS phrase="WARNING: Make sure that the MTCommentChallenge tag is in your templates and that they are rebuilt before enabling this option
+BEACON_SETTING
+BEACON_DESCRIPTION">  <TMPL_UNLESS NAME=COMMCHALLENGE_MODE><MT_TRANS phrase="BEACON_WARNING
-                </li>
-                </ul>
@@ -16 +16 @@
-        <ul>
-            <li>
-Deny (&quot;throttle&quot;) submissions without beacon (instead of Junking)
+THROTTLE_SETTING
-            </li>
-        </ul>
-While throttling such submissions reduces the load on the system, it could also cause lost comments if the MTCommentChallenge tag is not in your comment form. <strong>See plugin documentation for discussion</strong> before enabling this option.
+THROTTLE_DESCRIPTION
-        </div>
-    </div>
@@ -30 +30 @@
-                <div class="label"><MT_TRANS phrase="Challenge/Response CAPTCHA:"></div>
-                <div class="field">
-You can optionally present your commenters with a challenge CAPTCHA.  The answer given will be compared case-insensitively to the answer you provide below.
+CAPTCHA_DESCRIPTION
-                        <ul>
-                        <li>                            
@@ -41 +41 @@
-                        </li>
-                        </ul>
-WARNING: If you change this setting and the template containing your comment form is static, you must immediately rebuild that template type after you save this configuration! For most people, this means a rebuild of your individual entries.
+REBUILD_WARNING
-                </div>
-        </div>
@@ -53 +53 @@
-            <li><input type="radio" name="commchallenge_inform_commenter" value="1" <TMPL_IF NAME=COMMCHALLENGE_INFORM_COMMENTER>checked="checked"</TMPL_IF> class="rb" /> <MT_TRANS phrase="Inform commenter of problem"></li>
-        </ul>
-Informing the commenter of a blank or incorrect response allows them to correct the error, but if your question is too difficult, their comment is never submitted.  See plugin documentation for discussion.
+RESPONSE_DESCRIPTION
-        </div>
-    </div>