I don't remember why the login_form hook had to be moved up into the table (it was in fact always in the form), but placing it seemingly haphazard into just one of the two table cells is not useful for any of the plugins I can think of. Moving to a table row of its own.

ChangeLog

@@ -134,6 +134,7 @@ Version 1.5.2 - CVS
   - Provide View Unsafe Images link on viewing a text/html attachment.
   - Added APOP, TLS and STLS support to mail_fetch plugin (#575299).
   - Added Courier IMAP OUTBOX check to configtest utility.
+  - Moved login_form hook to its own table row on login page.
 
 Version 1.5.1 (branched on 2006-02-12)
 --------------------------------------

templates/default/login.tpl

@@ -53,6 +53,10 @@ extract($t);
   </td>
   <td class="sqm_loginFieldInput">
    <input type="password" name="secretkey" value="" id="secretkey" />
+  </td>
+ </tr>
+ <tr>
+  <td colspan="2">
    <?php echo $login_extra; ?>
   </td>
  </tr>
@@ -62,4 +66,4 @@ extract($t);
   </td>
  </tr>
 </table>
-</div>
+</div>

templates/default_advanced/login.tpl

@@ -66,6 +66,10 @@ extract($t);
      </td>
      <td class="fieldInput">
       <input type="password" name="secretkey" value="" id="secretkey" class="input" />
+     </td>
+    </tr>
+    <tr>
+     <td colspan="2">
       <?php echo $login_extra; ?>
      </td>
     </tr>
@@ -78,4 +82,4 @@ extract($t);
   </td>
  </tr>
 </table>
-</div>
+</div>