Update of /cvs/scoop/scoop/struct
In directory lithium.sabren.com:/tmp/cvs-serv31932/struct
Modified Files:
scoop.sql
Log Message:
Removing Sourceforge references from the default scoop.sql file, removing some junk from patch-30, and adding a patch for a perm that was missing from patch 30. Ooops. -j
Index: scoop.sql
===================================================================
RCS file: /cvs/scoop/scoop/struct/scoop.sql,v
retrieving revision 1.223
retrieving revision 1.224
diff -C2 -d -r1.223 -r1.224
*** scoop.sql 15 Jan 2006 20:40:31 -0000 1.223
--- scoop.sql 15 Jan 2006 22:31:42 -0000 1.224
***************
*** 217,221 ****
/*!40000 ALTER TABLE `blocks` DISABLE KEYS */;
LOCK TABLES `blocks` WRITE;
! INSERT INTO `blocks` VALUES ('footer','<DIV id=\"footer\">\r\n<P><A href=\"http://sourceforge.net\"><IMG src=\"http://sourceforge.net/sflogo.php?group_id=4901&type=1\" width=\"88\" height=\"31\" border=\"0\" alt=\"SourceForge Logo\"></A> \r\n<A HREF=\"http://scoop.kuro5hin.org\"><IMG SRC=\"%%imagedir%%/new_powered.gif\" ALT=\"Powered by Scoop\" BORDER=0></A></P>\r\n\r\n<FORM NAME=\"Search\" ACTION=\"%%rootdir%%\" METHOD=\"POST\">\r\n <INPUT TYPE=\"hidden\" NAME=\"op\" VALUE=\"search\">\r\n <INPUT TYPE=\"text\" SIZE=20 NAME=\"string\"><INPUT TYPE=\"submit\" VALUE=\"Search\">\r\n</FORM> \r\n\r\n<P>%%smallfont%%All trademarks and copyrights on this page are owned by their respective companies. Comments are owned by the Poster. The Rest © 2004 The Management \r\n%%smallfont_end%%</P>\r\n</DIV>','1','<P>This block is used at the bottom of each page. It should be fairly self-contained HTML, and contain any copyright notices and badges you want displayed at the bottom of all !
pages. This block has no special keys.</P>','General','default','en'),('index_template','<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\r\n<HTML>\r\n<HEAD>\r\n<TITLE>%%sitename%% %%bars%% %%subtitle%%</TITLE>\r\n%%css_includes%%\r\n</HEAD>\r\n<BODY>\r\n\r\n%%header%%\r\n\r\n<!-- Main layout table -->\r\n<TABLE id=\"main\">\r\n <TR>\r\n <!-- Left info column -->\r\n <TD VALIGN=\"top\" WIDTH=\"20%\" HEIGHT=20>\r\n <!-- About Scoop -->\r\n %%scoop_intro%%\r\n <!-- X About Scoop -->\r\n </TD>\r\n <!-- X Left info column -->\r\n\r\n <!-- Center content section -->\r\n <TD VALIGN=\"top\" width=\"55%\">\r\n %%BOX,section_title%%\r\n %%CONTENT%%\r\n </TD>\r\n <!-- X center content section -->\r\n\r\n <!-- Right boxes column -->\r\n <TD VALIGN=\"top\" width=\"25%\">\r\n \r\n %%BOX,main_menu%%\r\n %%BOX,ad_box%%\r\n %%BOX,user_box%%\r\n %%BOX,!
rdf_feeds%%\r\n %%BOX,hotlist_box%%\r\n %%BOX,admin_tools%%\
r\n %%BOX,poll_box%%\r\n %%BOX,older_list_box%%\r\n\r\n </TD>\r\n <!-- X Right boxes column -->\r\n\r\n </TR> \r\n <!-- X main page block -->\r\n</TABLE>\r\n<!-- X Main layout table -->\r\n\r\n%%footer%%\r\n\r\n<CENTER>%%BOX,menu_footer%%</CENTER>\r\n</BODY>\r\n</HTML>\r\n','1','<P>This block is used to build the front and section story index pages. It must be a full HTML page; dynamic content is added through the use of special keys. The special keys recognised are:</p>\r\n<DL>\r\n <DT>subtitle</dt>\r\n <DD>This is replaced with the display name of the section being displayed.</dd>\r\n <DT>CONTENT</dt>\r\n <DD>This is replaced with the story summaries for all of the stories that should be displayed on this page. It is built using the block <B>story_summary</b> once for each story displayed.</dd>\r\n</dl>\r\n','Page Templates','default','en'),('header','<!-- header table -->\r\n<DIV id=\"header\">\r\n%%section_links%%\r\n<A href=\"%%rootdir%%/\"><I!
MG SRC=\"%%imagedir%%/small_logo.jpg\" BORDER=0 ALT=\"Scoop -- the free news and discussion system\"></A>\r\n</DIV>\r\n<!-- X header table -->\r\n%%dynamicmode_iframe%%','1','<P>This block is used at the top of each page. It should be fairly self-contained HTML, and contain any site-wide navigation you want displayed at the top of all pages. This block has one special key; dynamicmode_iframe is replaced with an IFRAME tag on pages displaying dynamic comments, and with nothing otherwise.</P>','General','default','en'),('comment','<!-- start comment -->\r\n<DIV class=\"commenthead\">\r\n<A NAME=\"%%cid%%\">%%norm_font%%%%new%% <B>%%subject%%</B></A>\r\n%%rating_format%% (<A CLASS=\"light\" HREF=\"%%rootdir%%/comments/%%sid%%/%%cid%%#%%cid%%\">#%%cid%%</A>)%%norm_font_end%% <BR>%%norm_font%%by %%name%% %%email%% on %%date%%\r\n<BR>%%user_info%%%%edit_user%% %%url%%%%norm_font_end%%\r\n</DIV>\r\n\r\n<DIV class=\"commentbody\">\r\n%%norm_font%%%%comment%%\r\n<BR>%%sig%%\r\n<BR>%!
%actions%%%%norm_font_end%%\r\n</DIV>\r\n%%replies%%\r\n<!-- end comme
nt -->\r\n','1','<P>This block is used to format each topical comment attached to a story or poll. It is not used directly in any block, but is called repeatedly in the code, once for each topical comment displayed. (Editorial comments use the block <B>moderation_comment</B>). This should be a self-contained chunk of HTML code that can be nested arbitrarily deep. The special keys recognised are:</P>\n<DL>\n <DT>uid</DT>\n <DD>The numeric user ID of the comment poster</DD>\n <DT>edit_user</DT>\n <DD>The edit user link, only displayed if the user viewing the page has the perm <B>edit_user</B>.</DD>\n <DT>name</DT>\n <DD>The nickname of the comment poster</DD>\n <DT>date</DT>\n <DD>A formatted time/date string</DD>\n <DT>subject</DT>\n <DD>The subject of the comment</DD>\n <DT>new</DT>\n <DD>The contents of the block <B>new_comment_marker</B>, if the comment is not yet marked as read for the user viewing the comment. Use this, not new_comment_marker, in this block.</!
DD>\n <DT>member</DT>\n <DD>The contents of the block <B>mark_(groupname)</B>, if it exists for the poster\'s group</DD>\n <DT>sig</DT>\n <DD>The user\'s signature, if one is set.</DD>\n <DT>rating_format</DT>\n <DD>If ratings are turned off, or the user chooses not to see ratings, this is blanked; if ratings should be displayed, this is replaced with the contents of the block <B>rating_format</B> which may use the special keys <B>score</B> and <B>num_ratings</B> to display the current ratings.</DD>\n <DT>comment</DT>\n <DD>The body of the comment</DD>\n <DT>cid</DT>\n <DD>The comment ID. This plus the sid uniquely identifies each comment.</DD>\n <DT>actions</DT>\n <DD>The parent, reply, delete, toggle, and dynamic mode expand and collapse links; each part according to permissions.</DD>\n <DT>user_info</DT>\n <DD>A link to the comment poster\'s user info page.</DD>\n <DT>sid</DT>\n <DD>The story ID. This plus the cid uniquely identifies each comment; this alone uni!
quely identifies each story or poll.</DD>\n <DT>score</DT>\n <DD>The
comment\'s current score, an average of all the ratings.</DD>\n <DT>num_ratings</DT>\n <DD>The number of ratings given to the comment.</DD>\n <DT>email</DT>\n <DD>The user\'s \"fake email\" from their user preferences in a mailto: link, if present</DD>\n <DT>url</DT>\n <DD>The user\'s homepage from their user preferences in a link, if present</DD>\n <DT>replies</DT>\n <DD>All comment replies. If in threaded or minimal, this is formatted as just the subject; if in nested, this is formatted as the full comment.</DD>\n</DL>','Comments','default','en'),('admin_template','<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\r\n<HTML>\r\n<HEAD>\r\n<TITLE>%%sitename%% %%bars%% %%subtitle%%</TITLE>\r\n%%css_includes%%\r\n</HEAD>\r\n<BODY>\r\n\r\n%%header%%\r\n\r\n<!-- Main layout table -->\r\n<TABLE id=\"main\">\r\n <!-- Main page block -->\r\n <TR>\r\n \r\n <!-- Center content section -->\r\n <TD VALIGN=\"top\" wid!
th=\"72%\">\r\n %%CONTENT%%\r\n </TD>\r\n <!-- X center content section -->\r\n \r\n <!-- Right boxes column -->\r\n <TD VALIGN=\"top\" WIDTH=\"25%\">\r\n\r\n %%BOX,main_menu%%\r\n %%BOX,hotlist_box%%\r\n %%BOX,user_box%%\r\n %%BOX,admin_tools%%\r\n \r\n </TD>\r\n <!-- X Right boxes column -->\r\n </TR>\r\n <!-- X main page block -->\r\n</TABLE>\r\n<!-- X Main layout table -->\r\n\r\n%%footer%%\r\n\r\n<CENTER>%%BOX,menu_footer%%</CENTER>\r\n</BODY>\r\n','1','This block is used to build most pages on the site. It must be a full HTML page; dynamic content is added through the use of special keys. The special keys recognised are:</P>\n<DL>\n <DT>subtitle</DT>\n <DD>This is replaced with an appropriate subtitle indicating which page is currently being viewed.</DD>\n <DT>CONTENT</DT>\n <DD>This is replaced with any other content specific to the page being requested. It is provided by the function or box named in the Ops Admin T!
ool which handles the op (the first pseudo-directory) of the page.</P>
\n<P>This block is used to create the Admin Tools pages, including the Blocks Admin Tool, so be very careful when changing it. If you break this block, you will not be able to use any of the Admin Tools anymore and will not be able to fix it without going directly to the database.</P>','Page Templates','default','en'),('story_info','<!-- Story info -->\r\n<DIV class=\"story_info\">\r\n %%smallfont%%%%story_info%%%%smallfont_end%%\r\n</DIV>\r\n<!-- X Story info -->\r\n\r\n','1','<P>This block displays information about the story and links to some of the things you can do. It recognizes one special key, story_info, which is replaced with the story name, number and type of comments, and the \'post a comment\' and \'edit\' links as permissions allow.</P>','Stories','default','en'),('story_summary','<DIV class=\"story_summary\">\r\n<DIV class=\"story_title\"><H2>%%title%%</H2>\r\n%%norm_font%%%%hotlist%%%%norm_font_end%%\r\n<BR>%%topic_img%%</DIV>\r\n\r\n<P>%%smallfont%%By %%in!
fo%%, Section %%section_link%%\r\n<BR>Posted on %%time%%\r\n%%tags%%%%smallfont_end%%</P>\r\n\r\n<DIV class=\"introtext\">\r\n%%norm_font%%%%introtext%%%%norm_font_end%%\r\n</DIV>\r\n<P>%%norm_font%%%%stats%% %%readmore%%%%norm_font_end%%</P>\r\n</DIV>','1','<P>This block is used to format the story headlines and introtext, both on the index pages and the story pages. It should be a self-contained bit of HTML that lays out the story\'s information. The following special keys are recognized:</P>\n<DL>\n <DT>info</DT>\n <DD>The author\'s name and the story\'s \"department\" (if used)</DD>\n <DT>title</DT>\n <DD>The story\'s title</DD>\n <DT>introtext</DT>\n <DD>The formatted contents of the story\'s introtext field</DD>\n <DT>hotlist</DT>\n <DD>The link to either add or remove the story to the user\'s hotlist. Blank for anonymous users and stories that haven\'t been published yet.</DD>\n <DT>topic_img</DT>\n <DD>The topic image, linked to the search results for that topi!
c.</DD>\n <DT>topic_text</DT>\n <DD>The alt text for the topic image
as a text link, linked to the search results for that topic.</DD>\n <DT>time</DT>\n <DD>The localized time the story was posted.</DD>\n <DT>sid</DT>\n <DD>The story ID; can be used in custom links.</DD>\n <DT>section_icon</DT>\n <DD>The file name of the section icon; can be used in an IMG tag to display an icon.</DD>\n <DT>section_title</DT>\n <DD>The title of the section.</DD>\n <DT>aid</DT>\n <DD>The nickname of the story author</DD>\n <DT>section</DT>\n <DD>The title of the section.</DD>\n <DT>new</DT>\n <DD>The new story marker; displays the contents of the block <B>new_story_marker</B> if the logged-in user has not yet read the story, otherwise blank.</DD>\n <DT>readmore</DT>\n <DD>The link to the full story, drawing on either the block <B>readmore_txt</B> or <B>no_body_txt</B> as appropriate. Also the link to edit the story, if the user has the appropriate perms.</DD>\n <DT>stats</DT>\n <DD>The number of comments and unread comments, and the number of words in!
the story.</DD>\n <DT>section_link</DT>\n <DD>The section title as a link to the section index page</DD>\n</DL>','Stories','default','en'),('box','<DIV class=\"box\">\r\n%%box_title_font%%%%title%%%%box_title_font_end%%\r\n%%smallfont%%\r\n%%content%%\r\n%%smallfont_end%%\r\n</DIV>','1','<P>This block is used to provide a container for box output, and is not used directly in the page templates. It should be self-contained HTML, and provide the frame seen around the boxes in the sidebar. The special keys recognised are:</P>\n<DL>\n <DT>title</DT>\n <DD>The title of the box; if the box code returns a value for the title, that is used, otherwise the title field set in the Boxes Admin Tool is used</DD>\n <DT>content</DT>\n <DD>The main body of the box. This is the only thing the box code must return; if the box returns nothing or an empty string, the entire box (and its template) is not displayed at all</DD>\n <DT>bid</DT>\n <DD>The internal name for the box.</DD>\n</DL!
>','Box Templates','default','en'),('submission_message','<P><FONT =\"
+1\">Thank you for your submission. This is a community-edited site, so hopefully your fellow readers will see fit to post your story. Good Luck!</FONT></P>','1','<P>This block is displayed below the story body when it has been submitted to the queue. It should be self-contained HTML and should explain what will happen to the user\'s story now that it has been submitted.</P>','Stories','default','en'),('submission_guidelines','<P>Thank you for taking the time to submit a story!</P>\r\n<P>Here are some general guidelines for new stories:</P>\r\n<UL>\r\n<LI>Pick the topic carefully! Try your best to match the topic with the story you\'re submitting.</LI>\r\n<LI>Only the html tags listed are allowed in story text. No HTML is allowed in \"title\" or \"dept.\"</LI>\r\n<LI>You must preview at least once. Please read over your story carefully. <LI>Check all URLS!</LI>\r\n<LI>Check all facts! :-)</LI>\r\n<LI>This site is community-edited (mostly), so don\'t whine to the admins if yo!
ur story doesn\'t get posted. If you\'re logged in, you\'ll see a \"Moderate Submissions\" link to the right. This is how you decide what gets posted here! Use it!</LI>\r\n</UL>\r\n<P>Now post away!</P>','1','<P>This block is displayed above the story submission form. It should be self-contained HTML and should explain the site\'s submission guidelines. Keep in mind that the majority of people will at most skim this when going to post a story, so put the most important points up top.</P>','Stories','default','en'),('moderate_head','<P>%%norm_font%%Current score:<B>%%score%%</B><BR>\r\nTotal votes: <B>%%votes%%</B></FONT></P>\r\n','1','<P>This block is used at the top of the story moderation form, after the user has voted on a story in the queue. It should be self-contained HTML, and summarize the story\'s current standing in the queue. The special keys recognized are:</P>\n<DL>\n <DT>score</DT>\n <DD>The story\'s current score.</DD>\n <DT>votes</DT>\n <DD>The total number!
of votes cast.</DD>\n</DL>','Stories','default','en'),('moderation_co
mment','<!-- start comment -->\r\n<DIV class=\"editorialhead\">\r\n<A NAME=\"%%cid%%\">%%norm_font%%%%new%% <B>%%subject%%</B></A> %%rating_format%% (<A CLASS=\"light\" HREF=\"%%rootdir%%/comments/%%sid%%/%%cid%%#%%cid%%\">#%%cid%%</A>)%%norm_font_end%% \r\n<BR>%%norm_font%%by %%name%% %%email%% on %%date%%\r\n<BR>%%user_info%%%%edit_user%% %%url%%%%norm_font_end%%\r\n</DIV>\r\n\r\n<DIV class=\"commentbody\">\r\n%%norm_font%%%%comment%%\r\n<BR>%%sig%%\r\n<BR>%%actions%%%%norm_font_end%%\r\n</DIV>\r\n%%replies%%\r\n<!-- end comment -->\r\n\r\n','1','<P>This block is used to format each editorial comment attached to a story or poll. It is not used directly in any block, but is called repeatedly in the code, once for each editorial comment displayed. (Topical comments use the block <B>comment</B>). This should be a self-contained chunk of HTML code that can be nested arbitrarily deep. The special keys recognised are:</P>\n<DL>\n <DT>uid</DT>\n <DD>The numeric user ID of th!
e comment poster</DD>\n <DT>edit_user</DT>\n <DD>The edit user link, only displayed if the user viewing the page has the perm <B>edit_user</B>.</DD>\n <DT>name</DT>\n <DD>The nickname of the comment poster</DD>\n <DT>date</DT>\n <DD>A formatted time/date string</DD>\n <DT>subject</DT>\n <DD>The subject of the comment</DD>\n <DT>new</DT>\n <DD>The contents of the block <B>new_comment_marker</B>, if the comment is not yet marked as read for the user viewing the comment. Use this, not new_comment_marker, in this block.</DD>\n <DT>member</DT>\n <DD>The contents of the block <B>mark_(groupname)</B>, if it exists for the poster\'s group</DD>\n <DT>sig</DT>\n <DD>The user\'s signature, if one is set.</DD>\n <DT>rating_format</DT>\n <DD>If ratings are turned off, or the user chooses not to see ratings, this is blanked; if ratings should be displayed, this is replaced with the contents of the block <B>rating_format</B> which may use the special keys <B>score</B> and <B>num_!
ratings</B> to display the current ratings.</DD>\n <DT>comment</DT>\n
<DD>The body of the comment</DD>\n <DT>cid</DT>\n <DD>The comment ID. This plus the sid uniquely identifies each comment.</DD>\n <DT>actions</DT>\n <DD>The parent, reply, delete, toggle, and dynamic mode expand and collapse links; each part according to permissions.</DD>\n <DT>user_info</DT>\n <DD>A link to the comment poster\'s user info page.</DD>\n <DT>sid</DT>\n <DD>The story ID. This plus the cid uniquely identifies each comment; this alone uniquely identifies each story or poll.</DD>\n <DT>score</DT>\n <DD>The comment\'s current score, an average of all the ratings.</DD>\n <DT>num_ratings</DT>\n <DD>The number of ratings given to the comment.</DD>\n <DT>email</DT>\n <DD>The user\'s \"fake email\" from their user preferences in a mailto: link, if present</DD>\n <DT>url</DT>\n <DD>The user\'s homepage from their user preferences in a link, if present</DD>\n <DT>replies</DT>\n <DD>All comment replies. If in threaded or minimal, this is formatted as just the su!
bject; if in nested, this is formatted as the full comment.</DD>\n</DL>','Comments','default','en'),('error_font','<FONT COLOR=\"#FF0000\">','1','','Fonts','default','en'),('error_font_end','</FONT>','1','','Fonts','default','en'),('commentdisclaimer','Trolling is <B>not</B> tolerated here. Any comment may be \r\ndeleted by a site admin, and all trolls <B>will</B> be \r\ndeleted. This is fair warning. If you don\'t know what \r\ntrolling is, then you\'re probably not about to do it, so \r\ndon\'t worry. :-)','1','<P>This block is displayed just above the comment posting form. Put whatever message or warning you want displayed every time somebody posts a comment. This should be self-contained HTML. There are no special keys.</P>','Comments','default','en'),('login_box','<P>%%LOGIN_ERROR%%</P>\r\n<P>%%norm_font%%<B><A CLASS=\"light\" HREF=\"%%rootdir%%/newuser\">Make a new account</A></B>\r\n%%norm_font_end%%</P>\r\n\r\n<DIV class=\"loginform\"><P><FORM NAME=\"login\" ACTI!
ON=\"%%rootdir%%/\" METHOD=\"post\">\r\n%%smallfont%%Username: <INPUT
TYPE=\"text\" SIZE=12 NAME=\"uname\">\r\n<BR>Password: <INPUT TYPE=\"password\" SIZE=12 NAME=\"pass\">\r\n<BR><INPUT TYPE=\"submit\" NAME=\"login\" VALUE=\"Login\">\r\n<INPUT TYPE=\"submit\" NAME=\"mailpass\" VALUE=\"Mail Password\">%%smallfont_end%%\r\n</FORM></DIV>','1','<P>Despite its name, this is not a box template. It is an entire static box used to present the login form and new account link in place of the user box to a visitor who is not logged in. It should be self-contained HTML. It should contain the special key below:</P>\n<DL>\n <DT>LOGIN_ERROR</DT>\n <DD>The error message generated from a failed login attempt. The text and format of the error messages are set in the blocks <B>login_error_message</B>, <B>login_mailed_message</B>, or <B>login_mail_failed</B>, depending on which error was encountered.</DD>\n</DL>\n<P>The block must contain the following form elements or the login process will not work properly:</P>\n<DL>\n <DT>FORM</DT>\n <DD>The form should po!
st to the root directory of your site.</DD>\n <DT>Username field</DT>\n <DD>The text input field must be named \"uname\"</DD>\n <DT>Password field</DT>\n <DD>The password input field must be named \"pass\"</DD>\n <DT>Login button</DT>\n <DD>The button that submits both above fields for login must be named \"login\"</DD>\n <DT>Mail forgotton password button</DT>\n <DD>The button that submits the username field for creation of a new password must be named \"mailpass\"</DD>\n</DL>','Accounts','default','en'),('hotlist_link','+Hotlist','1','<P>This block is used as the text of the link used to add a story to a user\'s personal hotlist. It is only displayed to users who are logged in and who have not hotlisted that story; the block <B>hotlist_remove_link</B> is displayed to users who have already hotlisted the story. This block has no special keys.</P>','Stories','default','en'),('hotlist_remove_link','-Hotlist','1','<P>This block is used as the text of the link used to remo!
ve a story from a user\'s personal hotlist. It is only displayed to us
ers who are logged in and who have hotlisted that story; the block <B>hotlist_link</B> is displayed to users who have not hotlisted the story. This block has no special keys.</P>','Stories','default','en'),('poll_block','<!-- Poll Block -->\r\n%%title_font%%<B>%%title%%</B>%%title_font_end%%\r\n\r\n<TABLE>\r\n%%poll_image%%\r\n</TABLE>\r\n<!-- X Poll Block -->','1','<P>This block is used to format the poll results when displayed as the main content of the page. The following special keys are recognized:</P>\n<DL>\n <DT>title</DT>\n <DD>The poll question</DD>\n <DT>poll_image</DT>\n <DD>The poll results, with poll answers beside images representing the votes. The image file used is set in the block <B>poll_img</B>, and the width used to represent 100% is set in the block <B>poll_img_width</B>.</DD>\n</DL>','Polls','default','en'),('dot','+','1','<P>This block is used whenever a dot or list item indicator of some sort is needed. It is called directly by other blocks, never a!
ssembled as part of a special key, and recognizes no special keys itself.</P>','General','default','en'),('vote_console','<!-- vote_console -->\r\n<DIV id+\"vote_console\">\r\n <P>%%norm_font%%Your vote really does count! <B>You</B> decide whether this story ever sees the light of the front page. So vote!%%norm_font_end%%</P>\r\n\r\n<P>%%norm_font%%\r\n%%vote_form%%\r\n%%norm_font_end%%</P>\r\n</DIV>\r\n<!-- X vote_console -->\r\n','1','<P>This block is displayed below the story body for stories still in the voting queue. It should be self-contained HTML and explain what the voting is for. The special key vote_form is replaced with the actual form.</P>','Stories','default','en'),('blank_box','<DIV class=\"blank_box\">%%content%%</DIV>','1','<P>This block is used to provide a container for box output, and is not used directly in the page templates. It should be self-contained HTML, and provide a \"blank\" frame for the box output. The special keys recognised are:</P>\n<DL!
>\n <DT>title</DT>\n <DD>The title of the box; if the box code return
s a value for the title, that is used, otherwise the title field set in the Boxes Admin Tool is used</DD>\n <DT>content</DT>\n <DD>The main body of the box. This is the only thing the box code must return; if the box returns nothing or an empty string, the entire box (and its template) is not displayed at all</DD>\n <DT>bid</DT>\n <DD>The internal name for the box.</DD>\n</DL>','Box Templates','default','en'),('story_template','<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\r\n<HTML>\r\n<HEAD>\r\n<TITLE>%%sitename%% %%bars%% %%subtitle%%</TITLE>\r\n%%css_includes%%\r\n</HEAD>\r\n%%dynamicmode_javascript%%\r\n<BODY>\r\n\r\n%%header%%\r\n\r\n<!-- Main layout table -->\r\n<TABLE id=\"main\">\r\n <!-- Main page block -->\r\n <TR>\r\n \r\n <!-- Center content section -->\r\n <TD VALIGN=\"top\" width=\"75%\">\r\n <!-- Story stuff -->\r\n %%STORY%%\r\n <!-- X story stuff -->\r\n </TD>\r\n <!
!-- X center content section -->\r\n \r\n <!-- Right boxes column -->\r\n <TD VALIGN=\"top\" WIDTH=\"25%\">\r\n %%BOX,main_menu%%\r\n %%BOX,user_box%%\r\n %%BOX,hotlist_box%%\r\n %%BOX,admin_tools%%\r\n %%BOX,poll_box%%\r\n %%BOX,related_links%%\r\n %%BOX,mod_stats%%\r\n </TD>\r\n <!-- X Right boxes column -->\r\n </TR>\r\n <!-- X main page block -->\r\n</TABLE>\r\n<!-- X Main layout table -->\r\n\r\n<!-- comments -->\r\n%%CONTENT%%\r\n%%BOX,tag_listing%%\r\n%%BOX,comment_controls%%\r\n%%COMMENTS%%\r\n%%BOX,comment_controls%%\r\n<!-- X comments -->\r\n\r\n%%footer%%\r\n\r\n<CENTER>%%BOX,menu_footer%%</CENTER>\r\n</BODY>\r\n</HTML>\r\n','1','<P>This block is used to build the story and comment display pages. It must be a full HTML page. The special keys recognised are:</P>\r\n<DL>\r\n <DT>subtitle</DT>\r\n <DD>This is replaced with an appropriate subtitle indicating which page is currently being viewed.</DD>\r\n <DT>dynamic!
mode_javascript</DT>\r\n <DD>This is replaced with javascript for the
dynamic comment display if the page template is being used for comment display.</DD>\r\n <DT>STORY</DT>\r\n <DD>This is replaced with either the poll display or the story display, if either are being viewed.</DD>\r\n <DT>CONTENT</DT>\r\n <DD>This is replaced with any other content specific to the page being requested. It is provided by the function or box named in the Ops Admin Tool which handles the op (the first pseudo-directory) of the page.</DD>\r\n</DL>','Page Templates','default','en'),('attach_poll_message','poll:<br><br>\r\nPolls are not required, but if you want one, fill in a question and some answers.','1','<P>This block is displayed below the story submission form and above the attached poll submission form. It should be self-contained HTML and should contain an explanation of polls attached to stories. There are no special keys.</P>','Polls,Stories','default','en'),('edit_story_form','<FORM NAME=\"editstory\" ACTION=\"%%rootdir%%/\" METHOD=\"POST\" enctype!
=\"multipart/form-data\">\r\n%%hidden_form_data%%\r\n<table width=\"100%\" border=0 cellpadding=\"8\" cellspacing=0>\r\n<tr>\r\n<td valign=\"top\" colspan=\"2\">%%guidelines%%</td>\r\n</tr>\r\n<tr>\r\n<td valign=\"top\" colspan=\"2\">%%all_buttons%%</td>\r\n</tr>\r\n<tr>\r\n<td valign=\"top\">post to:</td>\r\n<td valign=\"top\">%%section_select%% %%topic_select%% %%postmode_select%%</td>\r\n</tr>\r\n%%edit_queue%%\r\n<tr>\r\n<td valign=\"top\">title:</td>\r\n<td valign=\"top\"><INPUT TYPE=\"text\" NAME=\"title\" VALUE=\"%%title%%\" SIZE=50><br>\r\n%%dept%%</td>\r\n</tr>\r\n%%notes%%\r\n<tr>\r\n<td valign=\"top\">intro:</td>\r\n<td valign=\"top\"><TEXTAREA NAME=\"introtext\" COLS=\"%%textarea_cols%%\" ROWS=\"%%textarea_rows%%\" WRAP=\"soft\">%%introtext%%</TEXTAREA></td>\r\n</tr>\r\n<tr>\r\n<td valign=\"top\">body:</td>\r\n<td valign=\"top\"><TEXTAREA NAME=\"bodytext\" COLS=\"%%textarea_cols%%\" ROWS=\"%%textarea_rows%%\" WRAP=\"soft\">%%bodytext%%</TEXTAREA></td>\r\n</!
tr>\r\n%%upload_page%%\r\n%%spellcheck%%\r\n%%tags%%\r\n<tr>\r\n<td></
td>\r\n<td valign=\"top\">%%displaystatus_select%% %%commentstatus_select%% %%edit_category_select%%\r\n</td>\r\n</tr>\r\n%%time_update%%\r\n<tr>\r\n<td>%%poll_message%%</td>\r\n<td>%%poll_form%%</td>\r\n</tr>\r\n<tr>\r\n<td valign=\"top\" colspan=\"2\">%%all_buttons%%</td>\r\n</tr>\r\n</table>\r\n</FORM>','1','The main form for submitting and editing stories. This one has a lot of permitted special keys. Here goes:\r\n\r\n<ul>\r\n<li> allowed_html_intro: the string for what html is allowed in intro. Optional.\r\n<li> allowed_html_body: likewise, for the body field\r\n<li> notes: Block \"story_edit_notes\" -- traditionally for the ED and UPDATE explanations\r\n<li> tid: Topic id of story\r\n<li> section: section id of story\r\n<li> parent: section id of parent section, if there is one\r\n<li> topic_select: The selector for topics. Generated internally based on perms and vars. REQUIRED -- it will be a hidden field if you\'re not using topics, but you must have it.\r\n<li> dis!
playstatus_select: Selector for displaystatus. Generated based on perms\r\n<li> commentstatus_select: Obvious\r\n<li> edit_category_select: If you\'re using edit categories, this\'ll be the selector\r\n<li> postmode_select: Selector for posting mode, like \"front page\", \"editing\" etc\r\n<li> all_buttons: The set of currently allowed and relevant buttons. Very required.\r\n<li> aid: uid of author\r\n<li> hidden_form_data: various bits of hdden stuff for the form that scoop needs to track. Very required.\r\n<li> title: Text of the title -- use your own html form element, just include this for \"value\"\r\n<li> dept: Dept field, formatted by block \"story_edit_dept\". Included if show_dept is turned on\r\n<li> upload_page: Story upload form, if you\'re using that.\r\n<li> spellcheck: Spellcheck element, if used. Formatted in block story_edit_spellcheck\r\n<li> edit_queue: Post to edit queue element, if you\'re using that. Formatted in block story_edit_editqueue\r\n<li> time!
_update: Update timestamp to now button, if you have permission. Forma
tted in block story_edit_timeupdate, subject to perm \"story_time_update\"\r\n<li> update_txt: block story_edit_updatetxt\r\n<li> edit_txt: block story_edit_edittxt\r\n<li> textarea_cols: textarea columns, based on perfs and stuff\r\n<li> textarea_rows: textarea rows, likewise\r\n<li> poll_message: Poll into message, from attach_poll_message, if you\'re using polls\r\n<li> poll_form: Poll form, if you\'re using polls\r\n<li> introtext: introtext of the story\r\n<li> bodytext: body text of the story\r\n<li> guidelines: The block \"submission_guidelines\", included for user-level story submit\r\n</ul>','Admin Pages','default','en'),('default_template','<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\r\n<HTML>\r\n<HEAD>\r\n<TITLE>%%sitename%% %%bars%% %%subtitle%%</TITLE>\r\n%%dynamicmode_javascript%%\r\n%%css_includes%%\r\n</HEAD>\r\n<BODY>\r\n\r\n%%header%%\r\n\r\n<!-- Main layout table -->\r\n<TABLE id=\"main\">\r\n !
<!-- Main page block -->\r\n <TR>\r\n \r\n <!-- Center content section -->\r\n <TD VALIGN=\"top\" width=\"72%\">\r\n %%STORY%%\r\n %%BOX,comment_controls%%\r\n %%CONTENT%%\r\n %%BOX,comment_controls%%\r\n </TD>\r\n <!-- X center content section -->\r\n \r\n <!-- Right boxes column -->\r\n <TD VALIGN=\"top\" WIDTH=\"25%\">\r\n\r\n %%BOX,main_menu%%\r\n %%BOX,hotlist_box%%\r\n %%BOX,user_box%%\r\n %%BOX,admin_tools%%\r\n \r\n </TD>\r\n <!-- X Right boxes column -->\r\n </TR>\r\n <!-- X main page block -->\r\n</TABLE>\r\n<!-- X Main layout table -->\r\n\r\n%%footer%%\r\n\r\n<CENTER>%%BOX,menu_footer%%</CENTER>\r\n</BODY>\r\n','1','<P>This block is used to build most pages on the site. It must be a full HTML page; dynamic content is added through the use of special keys. The special keys recognised are:</P>\n<DL>\n <DT>subtitle</DT>\n <DD>This is replaced with an appropriate subtitle indicating which page!
is currently being viewed.</DD>\n <DT>dynamicmode_javascript</DT>\n
<DD>This is replaced with javascript for the dynamic comment display if the page template is being used for comment display.</DD>\n <DT>STORY</DT>\n <DD>This is replaced with either the poll display or the story display, if either are being viewed.</DD>\n <DT>CONTENT</DT>\n <DD>This is replaced with any other content specific to the page being requested. It is provided by the function or box named in the Ops Admin Tool which handles the op (the first pseudo-directory) of the page. This can be forms, comments, special pages, or custom content from your own boxes.</DD>\n</DL>','Page Templates','default','en'),('submit_template','<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\r\n<HTML>\r\n<HEAD>\r\n<TITLE>%%sitename%% %%bars%% %%subtitle%%</TITLE>\r\n%%css_includes%%\r\n</HEAD>\r\n<BODY>\r\n\r\n%%header%%\r\n\r\n<!-- Main layout table -->\r\n<TABLE id=\"main\">\r\n <!-- Main page block -->\r\n <TR>\r\n <!-- Ce!
nter content section -->\r\n <TD VALIGN=\"top\" width=\"75%\">\r\n %%STORY%%\r\n %%CONTENT%%\r\n </TD>\r\n <!-- X center content section -->\r\n \r\n <!-- Right boxes column -->\r\n <TD VALIGN=\"top\" WIDTH=\"25%\">\r\n %%BOX,main_menu%%\r\n %%BOX,hotlist_box%%\r\n %%BOX,user_box%%\r\n %%BOX,admin_tools%%\r\n %%BOX,poll_box%%\r\n </TD>\r\n <!-- X Right boxes column -->\r\n </TR>\r\n <!-- X main page block -->\r\n</TABLE>\r\n<!-- X Main layout table -->\r\n\r\n%%footer%%\r\n\r\n<CENTER>%%BOX,menu_footer%%</CENTER>\r\n</BODY>\r\n</HTML>\r\n','1','<P>This block is the page template used to build the story and ad submission forms. It must be a full HTML page. The special keys recognised are:</P>\n<DL>\n <DT>subtitle</DT>\n <DD>This is replaced with an appropriate subtitle indicating which page is currently being viewed.</DD>\n <DT>STORY</DT>\n <DD>This is replaced with either the poll display or the story display, if !
either are being viewed.</DD>\n <DT>CONTENT</DT>\n <DD>This is replac
ed with any other content specific to the page being requested. It is provided by the function or box named in the Ops Admin Tool which handles the op (the first pseudo-directory) of the page.</DD>\n</DL>','Page Templates','default','en'),('story_body','<DIV class=\"story_body\">%%norm_font%%\r\n%%bodytext%%\r\n%%norm_font_end%%</DIV>\r\n','1','<P>This block is used to format the body (extended copy only) of a story. It should be self-contained HTML. It recognizes one special key, bodytext, which is replaced with the formatted contents of the extended copy field of the story.</P>','Stories','default','en'),('readmore_txt','Full Story','1','<P>This block is used as the text of the link leading to the full story and comments, when there is a story body. If there is no story body, the block <B>no_body_txt</B> is used instead.</P>','Stories','default','en'),('section_links','<DIV id=\"section_links\">\r\n%%norm_font%% \r\n <A HREF=\"%%rootdir%%/\">Front Page</A> \r\n %%dot%%!
\r\n <A HREF=\"%%rootdir%%/section/__all__\">Everything</A> \r\n %%dot%%\r\n <A HREF=\"%%rootdir%%/section/news\">News</A> \r\n %%dot%%\r\n <A HREF=\"%%rootdir%%/section/Diary\">Diaries</A>\r\n%%norm_font_end%%\r\n</DIV>','1','<P>This block contains the links to the different sections available on the site. It is typically displayed in the page header but can be used anywhere. Any sections that exist but aren\'t linked here are typically hard for visitors to find, so don\'t forget to update it when you change your sections.</P>','General','default','en'),('diary_post_message','<FONT SIZE=\"+1\">Your new entry has been posted. Enjoy!</FONT>','1','<P>This block is displayed just underneath a user\'s diary when they have just posted it. It should contain a message informing the user that their diary was successfully saved, and is otherwise free-form, self-contained HTML. There are no special keys.</P>','Diaries','default','en'),('box_title_bg','#006699','1','<P>This bloc!
k is used wherever a colour value is needed to set the colour of the s
idebar box title bars. It should be a hex colour value, including the #, such as #000000 for black. There are no special keys.</P>','Colours','default','en'),('comment_head_bg','#eeeeee','1','<P>This block is used wherever a colour value is needed to set the background colour of the comment header (which typically contains the subject and poster\'s information, but not the comment itself). It should be a hex colour value, including the #, such as #000000 for black. There are no special keys.</P>','Colours','default','en'),('dept_font','<FONT FACE=\"arial, helvetica, sans-serif\" SIZE=2>','1','<P>This block is used to format the \"from the x department\" string attached to stories, if the variable <B>show_dept</B> is turned on. It should be a complete opening font or text style indicator, such as a font or b tag. It must be properly closed by the contents of the block <B>dept_font_end</B>. There are no special keys.</P>','Fonts','default','en'),('no_body_txt','Comments !
>>','1','<P>This block is used as the text of the link leading to the full story and comments, when there is no story body, only an intro. If there is a story body, the block <B>readmore_txt</B> is used instead.</P>','Stories','default','en'),('sectiononlystory_bg','#eeeeee','1','<P>This block is used as a row background colour in the Story List Admin Tool, for those stories that are published to section only, including ad stories and user diaries. This should be a hex colour value including the #, such as #000000 for black.','Colours','default','en'),('smallfont','<FONT FACE=\"arial, Helvetica, Sans-Serif\" SIZE=2>','1','<P>This block should be a complete opening FONT tag. It must match the closing tag set in the block <B>smallfont_end</B>.</P>','Fonts','default','en'),('smallfont_end','</FONT>','1','<P>This block should be a closing FONT tag, or otherwise close the tag opened in the block <B>smallfont</B>.</P>','Fonts','default','en'),('story_mod_bg','#EEEEEE','1','<P>Thi!
s block is used as a row background colour in the story voting queue.
It is applied to stories in the voting queue that the user has not yet voted on. It should be a hex colour value, including the #.</P>','Colours','default','en'),('story_nav_bg','#EEEEEE','1','<P>This block is used as the background colour for the story navigation bar, which provides links to the next and previous stories at the bottom of the current story body. It should be a hex colour value, including the #.</P>','Colours','default','en'),('submittedstory_bg','#c6dae4','1','<P>This block is used as a row background colour in the Story List Admin Tool and the moderation queue, for those stories that are in the voting queue awaiting votes. This should be a hex colour value including the #, such as #000000 for black.','Colours','default','en'),('title_bgcolor','#EEEEEE','1','<P>This block is used anywhere a title bar needs a background (except in the sidebar boxes, which use <B>box_title_bg</B>). It should be a hex colour value, including the #.</P>','Colours','default','en'!
),('undisplayedstory_bg','#c0c0c0','1','<P>This block is used as the background colour for a line in the Story List Admin Tool for stories that have been voted down in the queue or hidden by an admin. It should be a hex colour value, including the #.','Colours','default','en'),('scoop_intro','<DIV class=\"box\">\r\n%%box_title_font%%Welcome to Scoop%%box_title_font_end%%\r\n\r\n<P>%%norm_font%%Holy Crap! You have your own <A HREF=\"http://scoop.kuro5hin.org\">Scoop</A> site now. Well, there\'s too many features for me to explain right here, but I can give you some places to look for help and whatnot.%%norm_font_end%%</P>\r\n\r\n<P>%%norm_font%%The main development site is at <A HREF=\"http://scoop.kuro5hin.org\">scoop.kuro5hin.org</A>. This contains links to all the other stuff, so poke around a little.%%norm_font_end%%</P>\r\n\r\n<P>%%norm_font%%For immediate help and assistance from the Scoop code monkeys, join the <A HREF=\"http://sourceforge.net/mail/?group_id=4901\">sc!
oop-help mailing list</A>. This is practically a requirement for a ple
asant Scoop administrative experience, as Scoop is rather complicated and it isn\'t always obvious where to find things.%%norm_font_end%%</P>\r\n\r\n<P>%%norm_font%%To help figure things out, there is a <A\r\nHREF=\"http://scoop.kuro5hin.org/guide/\">Scoop Admin Guide</A> which can\r\nhopefully answer most of your questions. Look in the doc/ directory of your\r\nScoop install for another copy of the admin guide.%%norm_font_end%%</P>\r\n\r\n<P>%%norm_font%%Other things of note:%%norm_font_end%%</P>\r\n\r\n<UL>\r\n<LI>%%norm_font%%Many Scoop developers can often be found on IRC, channel #scoop at irc.slashnet.org.%%norm_font_end%%</LI>\r\n<LI>%%norm_font%%The <A HREF=\"http://sourceforge.net/project/?group_id=4901\">main Sourceforge page</A> has some information on the project%%norm_font_end%%</LI>\r\n<LI>%%norm_font%%The latest code is always <A HREF=\"http://scoop.versionhost.com/viewcvs.cgi/\">in CVS</A> (username and password are both \"anonymous\")%%norm_font_end%%</LI>\r!
\n<LI>%%norm_font%%You can look at a convenient <A HREF=\"http://scoop.kuro5hin.org/special/sites\">list of other Scoop sites</A> to see what folks are doing with it%%norm_font_end%%</LI>\r\n</UL>\r\n</DIV>\r\n','1','<P>This block contains introductory information and is displayed in the left column of the front page when you first install Scoop. There is useful information on where to get help in this block, so make a note of it before deleting. This block should not be displayed on a live site, because its content is of no interest except to the administrator.</P>','General','default','en'),('blank_template','<HTML>\r\n<HEAD>\r\n<TITLE></TITLE>\r\n</HEAD>\r\n<BODY>\r\n</BODY>\r\n</HTML>','1','<P>This block is a complete, blank HTML page. No header, footer, or CONTENT. It must be a complete HTML page. This template is used for commands which do not display pages, such as the logout or redirect ops.</P>','Page Templates','default','en'),('empty_box','%%content%%','1','<P>Th!
is block is a box template that should have absolutely nothing but the
content special key in it, so that the box output has no frame and will not mess up the formatting of whatever part of the page it\'s placed on. The special key content is replaced with the output of whichever box uses it as a wrapper.</P>','Box Templates','default','en'),('new_comment_marker','<FONT COLOR=\"#FF0000\"><B>[new]</B></FONT>','1','<P>This block is inserted in the comment if the user has not yet read this comment, according to Scoop\'s read-tracking system. It replaces the special key <TT>|new|</TT> in the blocks <B>comment</B> and <B>moderation_comment</B>.</P>','Comments','default','en'),('submit_rdf_message','<P>Know of any good sites that syndicate their headlines, but aren\'t carried by this site yet? Well, most likely this is because the admins don\'t know about the site yet, or that they syndicate headlines with RDF. All it takes is for you to find a URL for the site where their RDF file is, and copy it to the form below. Once submitted, and admin will re!
view it, and will either approve it or delete it.</P>','1','<P>This block is displayed just above the form used to submit an RDF file explaining what the form is for.</P>','RDF','default','en'),('titled_box','<DIV class=\"titled_box\">\r\n%%box_title_font%%%%title%%%%box_title_font_end%%\r\n%%content%%\r\n</DIV>\r\n','1','<P>This block is used as a box template, and is not used directly from other blocks. It should be self-contained HTML and provide a box with a title bar. The following special keys are recognized:</P>\n<DL>\n <DT>title</DT>\n <DD>The title of the box; either a value explicitly returned by the box code, or the text in the box title field if nothing is explicitly returned.</DD>\n <DT>content</DT>\n <DD>The content of the box; the text that the box code returns after running.</DD>\n</DL>','Box Templates','default','en'),('cron_template','<html>\r\n<head>\r\n<title>%%slogan%% %%%% Cron</title>\r\n</head>\r\n<body bgcolor=\"#FFFFFF\"><pre>%%CONTENT%%</pre></b!
ody>\r\n</html>','1','<P>This block is used to format Scoop\'s cron sy
stem output. It parsed by run_cron.pl and should not be changed as neither users nor administrators ever use it directly.</P>','Page Templates','default','en'),('digest_storyformat','\n%%title%% \n By %%aid%%, %%time%% \n Section: %%section%%, Topic: %%tid%% \n\n%%introtext%% \n\n%%url%%\n\n----\n','1','<P>This block is used to format each story summary in the story digest email sent to users who request it. This should be plain text, with no HTML formatting. Because this is an email and is not sent through the usual processing given an HTML page, the only keys that work at all are the special keys defined for this block. The following special keys are recognised:</P>\n<DL>\n <DT>sid</DT>\n <DD>The story ID for the story being formatted. This is used in <TT>url</TT> (below) to create the full URL of the story and probably isn\'t needed on its own.</DD>\n <DT>tid</DT>\n <DD>The \"alt text\" of the topic attached to the story.</DD>\n <DT>aid</DT>\n <DD>The author\'s nick!
name.</DD>\n <DT>nick</DT>\n <DD>The author\'s nickname.</DD>\n <DT>time</DT>\n <DD>The time and date the story was posted on.</DD>\n <DT>title</DT>\n <DD>The title of the story</DD>\n <DT>dept</DT>\n <DD>The \"department\" of the story, if that feature is turned on in Site Controls (<B>show_dept</B>).</DD>\n <DT>introtext</DT>\n <DD>The story summary; that part of the story that is displayed on the index page of the scoop site. HTML line breaks are converted to newlines, links have their URL displayed beside the link text, and all other HTML tags are stripped. The intro text is then wrapped to 75 columns.</DD>\n <DT>section</DT>\n <DD>The title of the section the story is filed in.</DD>\n <DT>url</DT>\n <DD>The full URL of the story, built from the site\'s base URL and the story\'s sid.</DD>\n</DL>\n','Story Digests','default','en'),('digest_headerfooter','---------------------------------------------------------\nThis is the %%FREQUENCY%% digest for SITENAME.\nIf y!
ou have received this email in error, just reply to \nthis message and
say that you got it in error.\nPlease mention that this email was sent for user number %%USERID%%.\n---------------------------------------------------------\n','1','<P>This block is displayed at the top and bottom of the story digest email sent to users who request it. It should name the site and introduce the digest in a way suited for any frequency. This should be plain text, with no HTML formatting. If either of the blocks <B>digest_header</B> or <B>digest_footer</B> exist, they override this block for the email header and footer, respectively. Because this is an email and is not sent through the usual processing given an HTML page, the only keys that work at all are the special keys defined for this block. The following special keys are recognised:</P>\n<DL>\n <DT>FREQUENCY</DT>\n <DD>This key is replaced with the digest frequency requested by the user receiving the email, which may be daily, weekly, or monthly.</DD>\n <DT>USERID</DT>\n <DD>The numeric user ID of!
the recipient of the digest</DD>\n <DT>NICKNAME</DT>\n <DD>The nickname of the recipient of the digest</DD>\n</DL>','Story Digests','default','en'),('next_page_link','<a class=\"light\" href=\"%%LINK%%\">%%norm_font%%Next %%maxstories%% >>%%norm_font_end%%</a>','1','<P>This block is the text of the link displayed at the bottom of the front and section index pages if there are more stories published earlier than those displayed. It should be self-contained HTML. The following special key is recognized:</P>\n<DL>\n <DT>maxstories</DT>\n <DD>The value of the variable <B>maxstories</B>, or the user preference \"Number of story summaries to show\" if set.</DD>\n</DL>','General','default','en'),('prev_page_link','<a class=\"light\" href=\"%%LINK%%\">%%norm_font%%<< Previous %%maxstories%%%%norm_font_end%%</a>','1','<P>This block is the text of the link displayed at the top and bottom of the front and section index pages if there are more stories published more rece!
ntly than those displayed. It should be self-contained HTML. The follo
wing special key is recognized:</P>\n<DL>\n <DT>maxstories</DT>\n <DD>The value of the variable <B>maxstories</B>, or the user preference \"Number of story summaries to show\" if set.</DD>\n</DL>','General','default','en'),('subscribe','<p>You are not currently a paid member. Why not <a href=\"%%rootdir%%/subscribe\">become one</a>?</p>','1','<P>This block is displayed on a user\'s preferences page if they are not already subscribed, if they have the <B>allow_subscription</B> perm, and if the variable <B>use_subscriptions</B> is on. This should be a short note encouraging users to subscribe and should provide a link to the subscription purchase page. There are no special keys.</P>','Subscriptions','default','en'),('story_separator','\n','1','<P>This block is placed between the <B>story_summary</B> and <B>story_body</B> blocks when building the story page. It can contain any HTML and is usually used when visual separation between the two parts of the story is wanted.</P>','S!
tories','default','en'),('spell_err','<font color=\"red\">','1','<P>This block is used to format misspelled words if the spellchecking system is installed and active. It should be a complete opening font tag or other formatting tag. It should match its closing tag set in the block <B>spell_err_end</B>.</P>','Fonts','default','en'),('spell_err_end','</font>','1','<P>This block is used to format misspelled words if the spellchecking system is installed and active. It should be a closing tag for whatever is in the block <B>spell_err</B>.</P>','Fonts','default','en'),('new_user_html','%%title_font%%Create New User Account%%title_font_end%%\r\n<H3><CENTER>%%error_font%%%%error%%%%error_font_end%%</CENTER></H3>\r\n\r\n<P>%%norm_font%%In order to create an account (which is free), fill out this form. You will receive an email containing your an account activation link, at the address you provide here. Click the link, and your account will be activated and logged in. It\'s that eas!
y.%%norm_font_end%%</P>\r\n\r\n<P>%%norm_font%%Why do you have to resp
ond to the email? By requiring you to activate your account, we can make sure that the email address is valid. This makes it harder for malicious users to abuse the account creation system by creating an arbitrary number of accounts and spamming the site with stories or comments.%%norm_font_end%%</P>\r\n\r\n<P>%%norm_font%%The email address you enter here, so it <B>must</B> work. Do NOT enter a spam-protected or fake email address, or your account will not work.%%norm_font_end%%</P>\r\n\r\n<P>%%norm_font%%If you are concerned about privacy, this email does not have to be in any way traceable to you. We will never use the email you provide here for anything else, ever. All it needs to be is working, and accessible to you, at the time the account is created.%%norm_font_end%%</P>\r\n\r\n<P>%%norm_font%%Now get started, and we hope you enjoy %%sitename%%!%%norm_font_end%%</P>\r\n\r\n<FORM NAME=\"adduser\" METHOD=\"post\" ACTION=\"%%rootdir%%/\">\r\n <INPUT TYPE=\"hidden\" name=!
\"tool\" VALUE=\"writeuser\">\r\n <INPUT TYPE=\"hidden\" name=\"op\" VALUE=\"newuser\">\r\n <INPUT TYPE=\"hidden\" name=\"formkey\" VALUE=\"%%formkey%%\">\r\n\r\n<TABLE>\r\n <TR>\r\n <TD>%%norm_font%%Please enter your desired username:</TD>\r\n <TD>%%norm_font%%<INPUT TYPE=\"text\" NAME=\"nickname\" SIZE=30 VALUE=\"%%uname%%\">%%norm_font_end%%</TD>\r\n </TR>\r\n\r\n <TR>\r\n <TD COLSPAN=2>%%smallfont%%(Legal characters: a-z, A-Z, 0-9, space. Names may not start or end with a space, and may not contain more than one space in a row.)%%smallfont_end%%</TD>\r\n </TR>\r\n\r\n <TR>\r\n <TD>%%norm_font%%and a working email (this will never be made public!):\r\n <BR><B><FONT COLOR=\"#FF0000\">Check this for typos!</FONT></B>%%norm_font_end%%</TD>\r\n <TD>%%norm_font%%<INPUT TYPE=\"text\" NAME=\"email\" VALUE=\"%%email%%\" SIZE=30>%%norm_font_end%%</TD>\r\n </TR>\r\n\r\n%%BOX,signup_password%%\r\n\r\n <tr>\r\n <td colspan=2 align=\"right\">%%norm_font%%%%si!
gnup_prefs%%<br><input type=\"submit\" value=\"Create Account!\" size=
\"30\" />%%norm_font_end%%</td>\r\n </tr>\r\n</table>\r\n</form>\r\n','1','<P>This block contains the explanation of the account creation process as well as the form the user fills in to create an account. It should be reasonably self-contained. It must contain the following form elements:</p>\r\n<DL>\r\n <DT>FORM</dt>\r\n <DD>The form should post to your site\'s rootdir.</dd>\r\n <DT>op</dt>\r\n <DD>This should be a hidden field with a value of \"newuser\".</dd>\r\n <DT>tool</dt>\r\n <DD>This should be a hidden field with a value of \"writeuser\".</dd>\r\n <DT>formkey</dt>\r\n <DD>This should be a hidden field with a value of \"|formkey|\" (see special keys, below).</dd>\r\n <DT>nickname</dt>\r\n <DD>This should be a text field with a default value of \"|uname|\" (see special keys, below).</dd>\r\n <DT>email</dt>\r\n <DD>This should be a text field with a default value of \"|email|\" (see special keys, below).</dd>\r\n <DT>button</dt>\r\n <DD>A submit button to sen!
d the fields in.</dd>\r\n</dl>\r\n<P>The following special keys are recognized:</p>\r\n<DL>\r\n <DT>error</dt>\r\n <DD>Any error messages (such as invalid characters in the nickname field).</dd>\r\n <DT>uname</dt>\r\n <DD>Usually blank; if there is an error with the email field, this is the nickname entered by the user.</dd>\r\n <DT>email</dt>\r\n <DD>Usually blank; if there is an error with the nickname field, this is the email address entered by the user.</dd>\r\n <DT>formkey</dt>\r\n <DD>A code-generated formkey used to hinder scripts trying to make large numbers of accounts.</dd>\r\n</dl>','General','default','en'),('new_advertiser_html','%%title_font%%Upgrade to an Advertiser Account%%title_font_end%%\r\n<H3><CENTER>%%error_font%%%%error%%%%error_font_end%%</CENTER></H3>\r\n\r\n<P>%%norm_font%%Since you have expressed an interest in advertising on this site, I\'ll be needing a bit more information about you, for billing purposes.%%norm_font_end%%</P>\r\n<P>%%norm_f!
ont%% %%advertising_account_disclaimer%% %%norm_font_end%%</P>\r\n\r\n
<form name=\"adduser\" method=\"post\" action=\"%%rootdir%%\">\r\n<input type=\"hidden\" name=\"tool\" value=\"writeuser\">\r\n<input type=\"hidden\" name=\"op\" value=\"newuser\">\r\n<input type=\"hidden\" name=\"formkey\" value=\"%%formkey%%\">\r\n<input type=\"hidden\" name=\"advertiser\" value=\"1\">\r\n\r\n<TABLE>\r\n <TR>\r\n <TD align=\"right\">%%norm_font%%Your Name:%%norm_font_end%%</TD>\r\n <TD align=\"left\"><input type=\"text\" name=\"realname\" value=\"%%yourname%%\" size=\"30\"></TD>\r\n </TR>\r\n <TR>\r\n <TD align=\"right\">%%norm_font%%Business name:%%norm_font_end%%</TD>\r\n <TD align=\"left\"><input type=\"text\" name=\"bizname\" value=\"%%bizname%%\" size=\"40\"></TD>\r\n </TR>\r\n <TR>\r\n <TD align=\"right\">%%norm_font%%Contact phone number:%%norm_font_end%%</TD>\r\n <TD align=\"left\"><input type=\"text\" name=\"bizphone\" value=\"%%bizphone%%\" size=\"12\"></TD>\r\n </TR>\r\n <TR>\r\n <TD align=\"right\">%%norm_font%%Mailing Address:%%norm_fon!
t_end%%</TD>\r\n <TD align=\"left\"><textarea cols=\"30\" rows=\"5\" name=\"snailmail\" value=\"%%snailmail%%\"></textarea></TD>\r\n </TR>\r\n <tr>\r\n <td colspan=2 align=\"right\">%%norm_font%%<input type=\"submit\" value=\"Create Account!\" size=\"30\">\r\n%%norm_font_end%%</td>\r\n </tr>\r\n</table>\r\n</form>','1','<P>This block is displayed on the account signup page if the user is creating an advertising account. This is yet another unimplemented ad feature. Advertising accounts are only partly implemented; for now, there is no automated way to collect extra information from advertisers.</P>','Ads','default','en'),('advertising_account_disclaimer','<P>Please remember the following with your new advertising account.</P>\r\n\r\n<P><b>Any stories posted to this site for purely advertising purposes will void your contract with us.</b> The articles and diaries on this site are <b>not for advertising purposes</b>. This account entitles you to submit ads for posting in s!
pecified places on the page only. If you are caught abusing this acco
unt, you\'re ads will be disabled, no money will be refunded, and your account will be disabled. If you have any questions about this send mail to %%local_email%%.\r\n</P>\r\n\r\n<P>Thank you for your understanding.</P>','1','<P>This block is displayed in the form that collects extra information from advertisers when they create an \"advertiser account\". It is only relevant if the variable <B>req_extra_advertiser_info</B> is set to 1. It should contain whatever extra terms your site requires of an advertising account, if they are distinguished from regular accounts. There are no special keys.</P>','Ads','default','en'),('ad_test_template','<HTML>\r\n<HEAD>\r\n<TITLE>%%slogan%%</TITLE>\r\n</HEAD>\r\n<BODY BGCOLOR=\"#FFFFFF\">%%BOX,show_ad,fromurl%%</body>\r\n</html>','1','<P>This block is used to display a single ad for preview purposes without counting impressions. It must be a complete HTML page, and should contain a call to the <B>show_ad</B> box. There are no speci!
al keys.</P>','Ads,Page Templates','default','en'),('text_ad_template','<DIV class=\"advert\">\r\n<a href=\"%%REDIRECT_URL%%?to_url=%%LINK_URL%%\" title=\"%%LINK_URL%%\" %%TARGET%%>%%norm_font%%%%TITLE%%%%norm_font_end%%</a>\r\n<BR>%%norm_font%%%%TEXT1%%%%norm_font_end%%\r\n</DIV>','1','<P>This block is used to provide the layout for the simple text ad type. It should be self-contained HTML. The special keys recognized are:</P>\n<DL>\n <DT>FILE_PATH</DT>\n <DD>The path to the image file used in the ad. This does not include the value set in the variable ad_server_url.</DD>\n <DT>TEXT1</DT>\n <DD>The text the ad sponsor entered in the text1 field.</DD>\n <DT>TEXT2</DT>\n <DD>The text the ad sponsor entered in the text2 field.</DD>\n <DT>TITLE</DT>\n <DD>The text the ad sponsor entered in the title field.</DD>\n <DT>LINK_URL</DT>\n <DD>The URL of the page being advertised.</DD>\n <DT>SID</DT>\n <DD>The story ID associated with the ad, if ad comments are active. See the !
Scoop Admin Guide for details on setting up ad comments.</DD>\n <DT>RE
DIRECT_URL</DT>\n <DD>The URL used in the actual link of the ad, for clickthrough counting. The URL of the page advertised is not required in the actual link, but you may put it there in a dummy cgi variable (such as url=) so users know where they\'re going.</DD>\n</DL><P>The special keys used in the ad template become the required fields for the ad, as well as the only fields permitted.</P>','Ads','default','en'),('donate_email_success','Thank you for your donation of $%%AMOUNT%%.',NULL,'<P>This block is an email sent to a user who has made a donation. It should be plain text and indicate that the donation has been received. Because this is an email and is not sent through the usual processing given an HTML page, no keys except the following special keys will work.</P>\n<DL>\n <DT>AMOUNT</DT>\n <DD>The amount donated.</DD>\n</DL>','Emails','default','en'),('next_previous_links','<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\" width=\"100%\">\n<tr>\n<td>%%PREVIOUS_!
LINK%%</td>\n<td align=\"right\">%%NEXT_LINK%%</td>\n</tr>\n</table>',NULL,'<P>This block is used to create the next and previous page links at the top and bottom of the section index pages.</P>\nFIXME: not implemented correctly. Links won\'t disappear if not needed. Leave blank for now and it\'ll work.','General','default','en'),('ad_step1_rules','<!-- ad_step1_rules. Do not take out the |NEXT_LINK| text, as it will be replaced with a button to get the user to the next step in the process -->\r\n\r\n%%title_font%% Rules for Submitting Ads %%title_font_end%%\r\n\r\n%%norm_font%%\r\n<ul>\r\n<li>These are the rules for submitting ads on this Scoop site.\r\n</ul>\r\n%%norm_font_end%%\r\n<P>%%norm_font%% %%NEXT_LINK%% %%norm_font_end%%</P>','1','<P>This block is displayed as the first step when a user starts submitting ads. It should be self-contained HTML, and should explain all of the rules, terms, and conditions for ad submission before the actual submission process begins!
.</P>\n<P>There is one special key: NEXT_LINK which is the \"I agree\"
button.</P>','Ads','default','en'),('error_template','<h1>%%ERROR_TYPE%%</h1>\r\n<p>\r\n<b>Time:</b> %%thetime%%<br>\r\n<b>Package:</b> %%package%%<br>\r\n<b>File:</b> %%file%% <br>\r\n<b>Line:</b> %%line%% <br>\r\n<b>Additional Messages:</b> %%ERROR_MSG%%\r\n<b>Var Dump:</b><br>\r\n%%VARDUMP%%\r\n</p>','1','<P>The HTML output generated by Scoop if it runs into certain types of errors. Don\'t change this, except maybe to put your email address in it and ask the user to send you a copy of the text in the page. Everything on this page is a special key.</P>','Page Templates','default','en'),('ad_confirm_text','<p>Your ad is shown above for you to make sure that its how you want it. If you see any problems, hit back and fix them. Make sure that you take note of how much this will cost, as the next step is where you pay. If you are purchasing a free ad, there is no payment step.</P>\r\n\r\n<P>If you like what you see, hit \"Purchase Ad\" below, if not, hit back and make your c!
hanges.</p>','1','<P>This block is displayed on the advertisement preview screen when a user is submitting an ad. It should be a self-contained bit of text and should explain how to make changes if the previewed ad is not what the submittor wanted, and how to purchase if it is. There are no special keys.</P>','Ads','default','en'),('no_submit_ad_perm','%%title_font%%Submit Ad Error%%title_font_end%%\r\n\r\n<P>%%norm_font%%Sorry, but you do not have permission to submit advertisements. You must have a user account or login before you can submit ads on this site. You may login using the box to your right. To create an account you may go <a href=\"%%rootdir%%/newuser\">here</a>%%norm_font_end%%</P>\r\n','1','<P>This block is displayed if a user without the submit_ad perm (set in the Groups Admin Tool) tries to submit an ad. It should be customized depending on which criteria your site uses to determine who may submit advertisements.</P>','Ads','default','en'),('ad_disappro!
val_mail','The ad that you submitted to %%sitename%% was disapproved t
oday\r\nfor the following reason:\r\n\r\n%%REASON%%\r\n\r\nAdvertisement details:\r\nTitle: %%TITLE%%\r\nText1: %%TEXT1%%\r\nURL: %%URL%%\r\n\r\nIf you have received this message in error, please reply and let us know.\r\n\r\n-%%sitename%%\r\n%%local_email%%\r\n','1','<P>This block is emailed to a user when an advertisement he submitted has been disapproved by a site admin. It should be plain text and say that the ad has been disapproved. The special keys recognised are:</P>\n<DL>\n <DT>REASON</DT>\n <DD>The reason given by the administrator when disapproving the ad, if any</DD>\n <DT>TITLE</DT>\n <DD>The title of the advertisement disapproved</DD>\n <DT>TEXT1</DT>\n <DD>The \"TEXT1\" field of the advertisement disapproved</DD>\n <DT>URL</DT>\n <DD>The url the advertisement points to</DD>\n <DT>VIEWS_LEFT</DT>\n <DD>The number of impressions remaining</DD>\n <DT>IMPRESSIONS</DT>\n <DD>The number of impressions to buy (only used in ad renewals, which is yet another un!
implemented ad feature)</DD>\n <DT>AD_ID</DT>\n <DD>The internal ID number of the advertisement disapproved</DD>\n <DT>sitename</DT>\n <DD>The contents of the variable <B>sitename</B></DD>\n <DT>site_url</DT>\n <DD>The contents of the variable <B>site_url</B></DD>\n <DT>local_email</DT>\n <DD>The contents of the variable <B>local_email</B></DD>\n</DL>\n<P>The last three are not technically special keys, but since emails are not sent through the normal page processing, keys are not substituted normally. No keys other than the ones listed here will be interpolated. Not all available keys are necessarily relevant.</P>','Ads,Emails','default','en'),('ad_approval_mail','The ad that you submitted to %%sitename%% was accepted for display on our site.\r\n\r\nAdvertisement details:\r\nTitle: %%TITLE%%\r\nText1: %%TEXT1%%\r\nURL: %%URL%%\r\n\r\nIf you have received this message in error, please reply and let us know.\r\n\r\n-%%sitename%%\r\n%%local_email%%\r\n','1','<P>This blo!
ck is emailed to a user when an advertisement he submitted has been ap
proved by a site admin. It should be plain text and say that the ad has been approved. The special keys recognised are:</P>\n<DL>\n <DT>REASON</DT>\n <DD>The reason given by the administrator when approving the ad, if any</DD>\n <DT>TITLE</DT>\n <DD>The title of the advertisement approved</DD>\n <DT>TEXT1</DT>\n <DD>The \"TEXT1\" field of the advertisement approved</DD>\n <DT>URL</DT>\n <DD>The url the advertisement points to</DD>\n <DT>VIEWS_LEFT</DT>\n <DD>The number of impressions remaining</DD>\n <DT>IMPRESSIONS</DT>\n <DD>The number of impressions to buy (only used in ad renewal, which is yet another unimplemented ad features)</DD>\n <DT>AD_ID</DT>\n <DD>The internal ID number of the advertisement approved</DD>\n <DT>sitename</DT>\n <DD>The contents of the variable <B>sitename</B></DD>\n <DT>site_url</DT>\n <DD>The contents of the variable <B>site_url</B></DD>\n <DT>local_email</DT>\n <DD>The contents of the variable <B>local_email</B></DD>\n</DL>\n<P>The la!
st three are not technically special keys, but since emails are not sent through the normal page processing, keys are not substituted normally. No keys other than the ones listed here will be interpolated. Not all available keys are necessarily relevant.</P>','Ads,Emails','default','en'),('mail_ad_almost_done_msg','The ad that you submitted to %%sitename%% has is almost \r\nfinished with its campaign. You only have %%VIEWS_LEFT%% \r\nimpressions left before it\'s gone.\r\n\r\nAdvertisement details:\r\nTitle: %%TITLE%%\r\nText1: %%TEXT1%%\r\nURL: %%URL%%\r\n\r\nIf you have received this message in error, please reply \r\nand let us know.\r\n\r\n-%%sitename%%\r\n%%local_email%%\r\n','1','<P>This is the text of the email sent to the sponsor of an ad when his ad campaign is almost finished. Whether or not this email is sent at all is determined by the variable <B>mail_ad_reminders</B>. The number of impressions remaining when the email is sent is determined by the variable <B!
>mail_ad_reminder_on</B>. This block should have no HTML formatting, a
nd recognizes no keys except the special keys listed below, as it is not sent through the normal page processing. The special keys recognized are:</P>\n<DL>\n <DT>sitename</DT>\n <DD>The value of the sitename variable</DD>\n <DT>site_url</DT>\n <DD>The value of the site_url variable</DD>\n <DT>local_email</DT>\n <DD>The value of the local_email variable</DD>\n <DT>TITLE</DT>\n <DD>The title of the advertisement</DD>\n <DT>TEXT1</DT>\n <DD>The text field of the advertisement</DD>\n <DT>URL</DT>\n <DD>The URL in the ads link</DD>\n <DT>VIEWS_LEFT</DT>\n <DD>The number of impressions remaining until the ad expires</DD>\n <DT>AD_ID</DT>\n <DD>The internal ID number of the ad</DD>\n</DL>','Ads,Emails','default','en'),('mail_ad_done_msg','The ad that you submitted to %%sitename%% has finished its \r\ncampaign. Thank you for advertising on %%sitename%%; we \r\nlook forward to doing business with you again.\r\n\r\nAdvertisement details:\r\nTitle: %%TITLE%%\r\nText1: %%TEXT1!
%%\r\nURL: %%URL%%\r\n\r\nIf you have received this message in error, please reply \r\nand let us know.\r\n\r\n-%%sitename%%\r\n%%local_email%%\r\n','1','<P>This is the text of the email sent to the sponsor of an ad when his ad campaign is finished. Whether or not this ad is sent at all is determined by the variable <B>mail_ad_reminders</B> and <B>mail_ad_finished_reminder</B>. Both must be on for the email to be sent. This reminder email is sent when the last impression is used up. For an advance warning, see the block <B>mail_ad_almost_done_msg</B>. This block should have no HTML formatting, and recognizes no keys except the special keys listed below, as it is not sent through the normal page processing. The special keys recognized are:</P>\n<DL>\n <DT>sitename</DT>\n <DD>The value of the sitename variable</DD>\n <DT>site_url</DT>\n <DD>The value of the site_url variable</DD>\n <DT>local_email</DT>\n <DD>The value of the local_email variable</DD>\n <DT>TITLE</DT>\n <D!
D>The title of the advertisement</DD>\n <DT>TEXT1</DT>\n <DD>The text
field of the advertisement</DD>\n <DT>URL</DT>\n <DD>The URL in the ads link</DD>\n <DT>AD_ID</DT>\n <DD>The internal ID number of the ad</DD>\n</DL>','Ads,Emails','default','en'),('buy_ad_impression_message','<P>This is where you can buy ad impressions in a block. Once you have prepaid impressions on your account, you can distribute them to any ad you have submitted, from the <a href=\"%%rootdir%%/ads/dist\">distribution</a> page.</P>','1','not used. Yet another unimplemented ad feature.','Ads','default','en'),('confirm_purchase_impressions','<P>If you\'re sure that you want to buy this many impressions, click \"Purchase\" below, and proceed to the payment page. If you need to make a change, change the number and hit confirm again.</P>','1','yet another unimplemented ad feature','Ads','default','en'),('editqueuestory_bg','#99ccdd','1','<P>This block is used as a background colour in the story list for stories in the edit queue, to distinguish them from stories that ma!
y be voted on. It should contain a hex colour value or a recognized colour name.It only applies if the edit queue is turned on. This block has no special keys.</P>','Colours','default','en'),('author_edit_console','<!-- author_edit_console -->\r\n<DIV id=\"author_console\">\r\n<P>%%norm_font%%As the author of this story, you may cancel the submission at any time during voting. Simply check the confirm box below, and click \"Cancel Submission\". If the story is still in editing, you may also edit it using the \"Edit\" button. To finish the editing period and move the story to voting, click \"Edit\", uncheck \"Request editorial feedback\" and save.%%norm_font_end%%</P>\r\n\r\n<P>%%norm_font%%\r\n%%author_edit_form%%\r\n%%norm_font_end%%</P>\r\n</DIV>\r\n<!-- X author_edit_console -->\r\n','1','<P>This block is displayed below a story in the queue for the author only. It should be self-contained HTML, and should explain the process for cancelling stories. The special keys r!
ecognised are:</P>\n<DL>\n <DT>author_edit_form</DT>\n <DD>The form i
ncluding the delete checkbox and the edit button if the story is in the edit queue</DD>\n <DT>author_edit_instructions</DT>\n <DD>Instructions to the author for the editing process, displayed only if the story is in the edit queue. The contents are taken from the block <B>author_edit_instructions</B></DD>\n</DL>','Stories','default','en'),('edit_instructions','<!-- vote_console -->\r\n<DIV class=\"vote_console\">\r\n<P>%%norm_font%%<b>Please Help.</b> The author of this story has requested editorial help from you, and the rest of the community. Please read, and post your editorial suggestions below. The author can edit at any time, so some suggestions may already have been fixed when you read them. After editing, the story will continue on to voting as usual.%%norm_font_end%%</P>\r\n%%spam_form%%\r\n</DIV>\r\n<!-- X vote_console -->','1','<P>This block is displayed underneath the text of a story in the edit queue, informing readers of its status. This should be a reasonabl!
y self-contained bit of HTML and text which explains the process of story editing from the point of view of a reader who is not the author. This block recognizes the following special key:</P>\n<DL>\n <DT>spam_form</DT>\n <DD>This is replaced with the contents of <B>edit_instructions_abuse</B> if the edit queue anti-spam feature is turned on.</DD>\n</DL>','Stories','default','en'),('renew_ad_message','Renew an ad. Right here! Today!','1','<P>This block is displayed on the ad renewal page. It should contain a message encouraging people to renew their ads. There are no special keys. Ad renewals are yet another unimplemented ad feature.</P>','Ads','default','en'),('renew_choose_ad','<P>%%norm_font%%You need to choose an ad to renew. Check <a href=\"%%rootdir%%/my/ads\">your ad listing page</a> to \r\nchoose an ad to renew and click on the renewal link there.%%norm_font_end%%</P>','1','<P>This block is displayed if a user tries to visit the ad renewal page without specifyin!
g which ad to renew. It should contain instructions for finding the ad
renewal link. There are no special keys. Ad renewals are yet another unimplemented ad feature.</P>','Ads','default','en'),('renew_ad_no_permission','<P>%%norm_font%%Sorry, but you cannot renew this advertisement. Please choose an ad from <a href=\"%%rootdir%%/my/ads\">your ad list</a> to renew.%%norm_font_end%%</P>','1','<P>This block is displayed if a user tries to renew somebody else\'s ad. It should contain a message indicating that a given account can only renew ads submitted by that same account. There are no special keys. Ad renewals are yet another unimplemented ad feature.</P>','Ads','default','en'),('rating_format','(<A HREF=\"%%rootdir%%/comments/%%sid%%/%%cid%%?mode=alone;showrate=1#%%cid%%\">%%score%% / %%num_ratings%%</A>)',NULL,'<P>This block is used in the <B>comment</B> and <B>moderation_comment</B> blocks for the rating value display. This allows the entire rating value to disappear if the user has turned off ratings in their user preferences. The followin!
g special keys are recognized:</P>\n<DL>\n <DT>sid</DT>\n <DD>The story ID of the comment.</DD>\n <DT>cid</DT>\n <DD>The comment ID</DD>\n <DT>score</DT>\n <DD>The averaged score earned by the comment, or \"none\"</DD>\n <DT>num_ratings</DT>\n <DD>The number of people who have rated this comment.</DD>\n</DL>','Comments','default','en'),('donate_email_pledge','Thank you for your donation. Please remember to send $%%AMOUNT%% to our mailing address.',NULL,'<P>This block is an email sent to a user who has pledged to send a donation. It should be plain text and contain the amount the user has pledged and a reminder to send the amount. Putting the mailing address in this block is probably a good idea too. Because this is an email and is not sent through the usual processing given an HTML page, no keys except the following special keys will work.</P>\n<DL>\n <DT>AMOUNT</DT>\n <DD>The amount pledged.</DD>\n</DL>','Emails','default','en'),('confirm_ad_renew','<P>%%norm_font%% B!
e sure this is the number of impressions you want to purchase, and hit
\"Purchase\" below when you are ready to renew your ad %%norm_font_end%%</P>','1','<P>This block is used during the final confirmation step of ad renewal. It should be reasonably self-contained HTML and contain a message explaining that this is the final confirmation step before the ad renewal is actually processed. There are no special keys. Ad renewal is yet another unimplemented ad feature.</P>','Ads','default','en'),('dynamic_template','<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\r\n<HTML>\r\n<HEAD>\r\n<TITLE>%%sitename%% %%bars%% %%subtitle%%</TITLE>\r\n%%dynamicmode_javascript%%\r\n%%css_includes%%\r\n</HEAD>\r\n<BODY onload=\"copyContent(%%mainpid%%,%%dynamicmode%%)\">\r\n%%CONTENT%%\r\n</BODY>\r\n</HTML>\r\n','1','<P>This block is a nearly empty page template used for loading individual comments in dynamic mode. It must contain the correct <B>BODY onload</B> event. You probably shouldn\'t change this, !
since it will never be seen directly anyway. There are two special keys: mainpid and dynamicmode; both are set by the code to indicate whether or not dynamic comments are in use.</P>','Comments,Page Templates','default','en'),('dynamic_collapse_thread_link','<img src=\"%%imagedir%%/dyn_cola.gif\" alt=\"--\" title=\"Collapse Subthread\" width=\"12\" height=\"12\" border=\"0\">',NULL,'<P>This block should contain either the text or an image used as the link to collapse an entire subthread of comments when expanded comments are viewed in either of the dynamic modes. If it is an image, it should have an alt element to stand in if the image is missing. It is placed with the actions at the bottom of the comment. This block has no special keys.</P>','Comments','default','en'),('ad_renewal_mail','Your ad on %%sitename%% has been renewed.\r\n\r\nAdvertisement details:\r\nTitle: %%TITLE%%\r\nText1: %%TEXT1%%\r\nURL: %%URL%%\r\nAdditional Impressions: %%IMPRESSIONS%%\r\n\r\nIf you hav!
e received this message in error, please reply and let us know.\r\n\r\
n-%%sitename%%\r\n%%local_email%%\r\n','1','not used. Yet another unimplemented ad feature.','Ads,Emails','default','en'),('paypal_finished','<P>Thank you for your order! An administrator will soon review your ad to ensure that it meets our guidelines. You will receive a notice by email when your ad is reviewed. If your ad is not approved, the charge to your account will be reversed. If it is approved, it will begin running immediately.</P>','1','<P>This block is displayed when an ad purchase paid via paypal is completed. It should be self-contained HTML and should indicate that payment has been received and the advertisement is pending approval by an administrator.</P>','Payments','default','en'),('paypal_canceled','<P>We\'re sorry you decided to cancel your order.</P>','1','<P>This block is displayed when an ad purchase paid via paypal is canceled. It should be self-contained HTML and should indicate that the order has been canceled.</P>','Payments','default','en'),('dyna!
mic_loading_link','<img src=%%imagedir%%/dyn_wait.gif width=12 height=16 ALT=x border=0>','1','<P>This block contains the image tag that will replace the expand/collapse link when a comment is in the process of being loaded/unloaded. This shouldn\'t actually be a link, just a marker of the same size and format as <B>dynamic_expand_link</B> and <B>dynamic_collapse_link</B>. This block has no special keys.</P>','Comments','default','en'),('dynamic_collapse_bottom_link','<img src=%%imagedir%%/dyn_colb.gif width=12 height=12 ALT=- border=0>','1','<P>This block should contain either the text or an image used as the link to collapse a comment when expanded comments are viewed in either of the dynamic modes. If it is an image, it should have an alt element to stand in if the image is missing. It is placed with the actions at the bottom of the comment; the block <B>dynamic_collapse_link</B> is the one placed at the top. This block has no special keys.</P>','Comments','default','en'!
),('block_category_list','<tr>\r\n<td>%%norm_font%%<a href=\"%%rootdir
%%/admin/blocks/%%item_url%%\">%%item%%</a>%%norm_font_end%%</td>\r\n<td>%%norm_font%%<a href=\"%%rootdir%%/admin/blocks/%%item_url%%\">%%item%%</a>%%norm_font_end%%</td>\r\n<td>%%norm_font%%<a href=\"%%rootdir%%/admin/blocks/%%item_url%%\">%%item%%</a>%%norm_font_end%%</td>\r\n</tr>\r\n',NULL,'<P>This block is used to build the list of category links in the Blocks Admin Tool. It is repeated as many times as necessary to display all the categories. It should contain a complete single line (by default a table row) that can be inserted into the containing block (by default a table with no rows) present in the block <B>edit_block</B> (This block is placed as many times as necessary in the spot designated by the special key <B>catlist</B>). Multiple instances of the special keys listed below are permitted in this block. The special keys recognised are:</P>\n<DL>\n <DT>item_url</DT>\n <DD>The url-safe name of the category; you must insert it into the URL of the hyperlink you!
rself.</DD>\n <DT>item</DT>\n <DD>The display name of the category, typically used as the text of the hyperlink</DD>\n</DL>','Admin Pages','default','en'),('edit_block','<form name=\"editblocks\" action=\"%%rootdir%%/admin/blocks/\" method=\"post\">\r\n<input type=\"hidden\" name=\"cat\" value=\"%%category%%\" />\r\n\r\n<table border=\"0\" cellpadding=\"2\" cellspacing=\"0\" width=\"100%\">\r\n<tr><td bgcolor=\"%%title_bgcolor%%\">%%title_font%%Blocks: %%category%%%%title_font_end%%</td></tr>\r\n<tr><td>%%norm_font%%%%update_msg%%%%norm_font_end%%</td></tr>\r\n<tr><td>%%norm_font%%%%theme_sel%%%%norm_font_end%%</td></tr>\r\n<tr><td>%%norm_font%%Choose a category to edit:%%norm_font_end%%</td></tr>\r\n<tr><td>\r\n <table border=\"0\" cellpadding=\"0\" cellspacing=\"2\" width=\"100%\">%%catlist%%</table>\r\n</td></tr>\r\n<tr><td>%%norm_font%%<input type=\"submit\" name=\"save\" value=\"Save\"> <input type=\"submit\" name=\"edit\" value=\"Get\" />%%norm_font_end%%</td></tr>\r!
\n<tr><td>%%norm_font%%%%html_check%%%%norm_font_end%%</td></tr>\r\n<t
r><td>\r\n <table border=0 cellpadding=1 cellspacing=0 width=\"100%\">%%form_body%%</table>\r\n</td></tr>\r\n<tr><td>%%norm_font%%<input type=\"submit\" name=\"save\" value=\"Save\"> <input type=\"submit\" name=\"edit\" value=\"Get\" />%%norm_font_end%%</td></tr>\r\n</table>\r\n</form>\r\n',NULL,'<P>This block is used to build the block editing form. It should contain the admin page structure, set up the form, and contain all of the special keys listed below to ensure that block editing is not broken. This block recognizes the following special keys:</P>\n<DL>\n <DT>catlist</DT>\n <DD>The list of all block categories in the current theme, linkified to bring you to the form with all blocks in that category within the current theme. The list itself is built using the block <B>block_category_list</B> as many times as necessary to display all of the categories.</DD>\n <DT>category</DT>\n <DD>Either the block name or the category name (depending on whether you\'re in single blo!
ck or category edit mode) and the name of the theme you\'re currently working in, just so it\'s easier to remember where you are.</DD>\n <DT>update_msg</DT>\n <DD>Any save, status, or error messages generated due to one of your actions in this admin tool.</DD>\n <DT>theme_sel</DT>\n <DD>The list of themes across the top of the page that allows you to switch between which theme you\'re working in. The current theme is not linkified, all others are.</DD>\n <DT>html_check</DT>\n <DD>The checkbox that determines if Scoop should check the HTML of the block when saving. Valid HTML is determined by the block <B>all_html</B>.</DD>\n <DT>form_body</DT>\n <DD>The body of the block editing form. This will either be the single block form from <B>edit_one_block</B> or the category edit form from <B>edit_cat_blocks</B>, depending on whether you are editing one block or an entire category.</DD>\n</DL>\n<P>Be very careful when changing this block, as it is used to build the interface r!
equired to change it back if it is broken. Changing the form elements
is strongly not recommended.</P>','Admin Pages','default','en'),('edit_cat_blocks','<!-- category line begin -->\r\n<tr>\r\n <td>\r\n %%norm_font%%%%name%%<br />\r\n %%description%%%%norm_font_end%%\r\n </td>\r\n <td>%%norm_font%%%%value%%%%norm_font_end%%</td>\r\n</tr>\r\n<!--category line end -->\r\n',NULL,'<P>This block is used to build the block editing form when in category view. It should contain one line of the category view (that is, the code for one block only). This block recognizes the following special keys:</P>\n<DL>\n <DT>name</DT>\n <DD>The name of the block, formatted as a link to the single block edit form for that block.</DD>\n <DT>value</DT>\n <DD>A textarea field containing the value of the block.</DD>\n <DT>description</DT>\n <DD>The block description.</DD>\n</DL>','Admin Pages','default','en'),('edit_cat_vars','<tr>\r\n <td>%%norm_font%%%%name%%%%norm_font_end%%</td>\r\n <td>%%norm_font%%%%value%%%%norm_font_end%%</td>\r\n <td>%%norm_font%%%%descri!
ption%%%%norm_font_end%%</td>\r\n</tr>\r\n',NULL,'<P>This block is used to build the Site Control editing form when in category view. It should contain one line of the category view (that is, the code for one variable only). This block recognizes the following special keys:</P>\n<DL>\n <DT>name</DT>\n <DD>The name of the variable, formatted as a link to the single variable edit form for that variable.</DD>\n <DT>value</DT>\n <DD>A field containing the value of the variable. Depending on the variable type, this may be a checkbox (boolean), a short text field (number), a longer text field (text), or a textarea field (textarea).</DD>\n <DT>description</DT>\n <DD>The variable description.</DD>\n</DL>','Admin Pages','default','en'),('edit_one_block','<tr><td>%%norm_font%%Or edit a block directly:%%norm_font_end%%</td></tr>\n<tr><td><table cellspacing=\"2\" cellpadding=\"0\" width=\"100%\">\n<tr>\n <td colspan=\"2\">%%norm_font%%<b>Delete:</b><input type=\"checkbox\" name=\"de!
lete\" value=\"1\">%%norm_font_end%%</td>\n</tr>\n<tr>\n <td>%%norm_fo
nt%%<b>Select Block:</b>%%norm_font_end%%</td>\n <td>%%blockselect%%</td>\n</tr>\n<tr>\n <td>%%norm_font%%<b>Select Categories:</b>%%norm_font_end%%</td>\n <td>%%catselect%%</td>\n</tr>\n<tr>\n <td>%%norm_font%%<b>Name:</b>%%norm_font_end%%</td>\n <td><input type=\"text\" size=\"60\" name=\"name\" value=\"%%bid%%\"></td>\n</tr>\n<tr>\n <td>%%norm_font%%<b>Theme:</b>%%norm_font_end%%</td>\n <td><input type=\"text\" size=\"60\" name=\"block_theme\" value=\"%%theme%%\"><input type=\"hidden\" name=\"theme\" value=\"%%curr_theme%%\"></td>\n</tr>\n<tr>\n <td>%%norm_font%%<b>New Category:</b>%%norm_font_end%%</td>\n <td><input type=\"text\" size=\"60\" name=\"category\" value=\"\"><br>\n %%norm_font%%<i>(seperate multiple categories with commas)</i>%%norm_font_end%%\n </td>\n</tr>\n<tr>\n <td colspan=\"2\">\n %%norm_font%%<b>Value:</b>%%norm_font_end%%<br>\n <textarea cols=\"60\" rows=\"20\" name=\"value\" wrap=\"soft\">%%value%%</textarea>\n </td>\n</tr>\n<tr>\n <td colspan=\"2\">!
%%norm_font%%%%description%%%%norm_font_end%%</td>\n</tr>\n<tr>\n <td colspan=\"2\">\n %%norm_font%%<b>Description:</b>%%norm_font_end%%<br>\n <textarea cols=\"60\" rows=\"5\" name=\"description\"\n wrap=\"soft\">%%description%%</textarea>\n </td>\n</tr>\n</table></td></tr>\n',NULL,'<P>This block is used to build the single block edit form for the Blocks Admin Tool. It contains the form elements and special keys required for block editing to work. This block recognizes the following special keys:</P>\n<DL>\n <DT>blockselect</DT>\n <DD>The select form element listing all the blocks available to edit.</DD>\n <DT>catselect</DT>\n <DD>The select form element listing all the categories available to file a block in.</DD>\n <DT>bid</DT>\n <DD>The name of the block (block ID).</DD>\n <DT>value</DT>\n <DD>The value of the block.</DD>\n <DT>theme</DT>\n <DD>The name of the theme the block should be saved in.</DD>\n <DT>curr_theme</DT>\n <DD>The name of the theme you are current!
ly working in. If a new block is created and the theme (above) is left
empty, this value is used in its place, so blocks are created where you\'d expect them.</DD>\n <DT>description</DT>\n <DD>The description of the block.</DD>\n</DL>','Admin Pages','default','en'),('edit_one_var','<tr><td>%%norm_font%%Or edit a variable directly:%%norm_font_end%%</td></tr>\r\n<tr><td><table cellspacing=\"2\" cellpadding=\"0\" width=\"100%\">\r\n <tr>\r\n <td colspan=\"2\">%%norm_font%%<b>Delete:</b><input type=\"checkbox\" name=\"delete\" value=\"1\" />%%norm_font_end%%</td>\r\n </tr>\r\n <tr>\r\n <td>%%norm_font%%<b>Type:</b>%%norm_font_end%%</td>\r\n <td>%%typeselect%%</td>\r\n </tr>\r\n <tr>\r\n <td>%%norm_font%%<b>Select Variable:</b>%%norm_font_end%%</td>\r\n <td>%%varselect%%</td>\r\n <tr>\r\n <td>%%norm_font%%<b>Select Categories:</b>%%norm_font_end%%</td>\r\n <td>%%catselect%%</td>\r\n </tr>\r\n <tr>\r\n <td>%%norm_font%%<b>Name:</b>%%norm_font_end%%</td>\r\n <td><input type=\"text\" size=\"60\" name=\"name\" value=\"%%name%%\" /></td>\r\n <!
/tr>\r\n <tr>\r\n <td>%%norm_font%%<b>New Category:</b>%%norm_font_end%%</td>\r\n <td><input type=\"text\" size=\"60\" name=\"category\" value=\"\"><br />\r\n %%norm_font%%<i>(seperate multiple categories with commas)</i>%%norm_font_end%%\r\n </td>\r\n </tr>\r\n <tr>\r\n <td colspan=\"2\">\r\n %%norm_font%%<b>Value:</b>%%norm_font_end%%<br />\r\n <textarea cols=\"60\" rows=\"12\" name=\"value\" wrap=\"soft\">%%value%%</textarea>\r\n </td>\r\n </tr>\n <tr>\n <td colspan=\"2\">%%norm_font%%%%description%%%%norm_font_end%%</td>\n </tr>\r\n <tr>\r\n <td colspan=\"2\">\r\n %%norm_font%%<b>Description:</b>%%norm_font_end%%<br />\r\n <textarea cols=\"60\" rows=\"3\" name=\"description\" wrap=\"soft\">%%description%%</textarea>\r\n </td>\r\n </tr>\r\n</table></td></tr>\r\n',NULL,'<P>This block is used to build the single variable edit form for the Site Controls Admin Tool. It contains the form elements and special keys required for variable editing to work. This b!
lock recognizes the following special keys:</P>\n<DL>\n <DT>varselect<
/DT>\n <DD>The select form element listing all the variables available to edit.</DD>\n <DT>catselect</DT>\n <DD>The select form element listing all the categories available to file a variable in.</DD>\n <DT>name</DT>\n <DD>The name of the variable.</DD>\n <DT>value</DT>\n <DD>The value of the variable.</DD>\n <DT>typeselect</DT>\n <DD>The select form element listing the possible variable types.</DD>\n <DT>description</DT>\n <DD>The description of the variable.</DD>\n</DL>','Admin Pages','default','en'),('edit_var','<form name=\"editvars\" action=\"%%rootdir%%/admin/vars/\" method=\"post\">\r\n<input type=\"hidden\" name=\"cat\" value=\"%%category%%\" />\r\n\r\n<table border=\"0\" cellpadding=\"0\" cellspacing=\"0\" width=\"100%\">\r\n<tr><td bgcolor=\"%%title_bgcolor%%\">%%title_font%%Site Controls: %%category%%%%title_font_end%%</td></tr>\r\n<tr><td>%%norm_font%%%%update_msg%%%%norm_font_end%%</td></tr>\r\n<tr><td> </td></tr>\r\n<tr><td>%%norm_font%%Choose a category !
to edit:%%norm_font_end%%</td></tr>\r\n<tr><td>\r\n <table border=\"0\" cellpadding=\"0\" cellspacing=\"2\" width=\"100%\">%%catlist%%</table>\r\n</td></tr>\r\n<tr><td>%%norm_font%%<input type=\"submit\" name=\"save\" value=\"Save\" /> <input type=\"submit\" name=\"edit\" value=\"Get\" />%%norm_font_end%%</td></tr>\r\n<tr><td><table border=\"0\" cellpadding=\"2\" cellspacing=\"0\" width=\"100%\">%%form_body%%</table></td></tr>\r\n<tr><td>%%norm_font%%<input type=\"submit\" name=\"save\" value=\"Save\" /> <input type=\"submit\" name=\"edit\" value=\"Get\" />%%norm_font_end%%</td></tr>\r\n</table>\r\n</form>\r\n',NULL,'<P>This block is used to build the Site Controls editing form. It should contain the admin page structure, set up the form, and contain all of the special keys listed below to ensure that variable editing is not broken. This block recognizes the following special keys:</P>\n<DL>\n <DT>catlist</DT>\n <DD>The list of all variable categories, linkified to bring y!
ou to the form with all variables in that category. The list itself is
built using the block <B>var_category_list</B> as many times as necessary to display all of the categories.</DD>\n <DT>category</DT>\n <DD>The name of the category you\'re currently editing.</DD>\n <DT>update_msg</DT>\n <DD>Any save, status, or error messages generated due to one of your actions in this admin tool.</DD>\n <DT>form_body</DT>\n <DD>The body of the variable editing form. This will either be the single variable form from <B>edit_one_var</B> or the category edit form from <B>edit_cat_vars</B>, depending on whether you are editing one variable or an entire category.</DD>\n</DL>','Admin Pages','default','en'),('var_category_list','<tr>\r\n <td>%%norm_font%%<a href=\"%%rootdir%%/admin/vars/%%item_url%%\">%%item%%</a>%%norm_font_end%%</td>\r\n <td>%%norm_font%%<a href=\"%%rootdir%%/admin/vars/%%item_url%%\">%%item%%</a>%%norm_font_end%%</td>\r\n <td>%%norm_font%%<a href=\"%%rootdir%%/admin/vars/%%item_url%%\">%%item%%</a>%%norm_font_end%%</td>\r\n</tr>\r\n',NULL,!
'<P>This block is used on the Site Controls Admin Tool, to build the list of categories above the form. This should be one row of a table as many cells wide as desired. The special keys may be repeated; each time they are repeated they will be replaced with the values for a different category. The special keys recognized are:</P>\n<DL>\n <DT>item_url</DT>\n <DD>The part of the URL after /admin/vars/ that will lead to the category overview form.</DD>\n <DT>item</DT>\n <DD>The name of the category.</DD>\n</DL>\n<P>The special keys, if repeated, should all be repeated the same number of times, and each set should be associated, so as not to mix up the title and destination of the links.</P>','Admin Pages','default','en'),('edit_macro','<form name=\"editmacros\" action=\"%%rootdir%%/admin/macros/\" method=\"post\">\r\n<input type=\"hidden\" name=\"cat\" value=\"%%category%%\" />\r\n\r\n<table border=\"0\" cellpadding=\"0\" cellspacing=\"0\" width=\"100%\">\r\n<tr><td bgcolor=!
\"%%title_bgcolor%%\">%%title_font%%Macros: %%category%%%%title_font_e
nd%%</td></tr>\r\n<tr><td>%%norm_font%%%%update_msg%%%%norm_font_end%%</td></tr>\r\n<tr><td> </td></tr>\r\n<tr><td>%%norm_font%%Choose a category to edit:%%norm_font_end%%</td></tr>\r\n<tr><td>\r\n <table border=\"0\" cellpadding=\"0\" cellspacing=\"2\" width=\"100%\">%%catlist%%</table>\r\n</td></tr>\r\n<tr><td>%%norm_font%%<input type=\"submit\" name=\"save\" value=\"Save\" /> <input type=\"submit\" name=\"edit\" value=\"Get\" />%%norm_font_end%%</td></tr>\r\n<tr><td><table border=\"0\" cellpadding=\"2\" cellspacing=\"0\" width=\"100%\">%%form_body%%</table></td></tr>\r\n<tr><td>%%norm_font%%<input type=\"submit\" name=\"save\" value=\"Save\" /> <input type=\"submit\" name=\"edit\" value=\"Get\" />%%norm_font_end%%</td></tr>\r\n</table>\r\n</form>\r\n',NULL,'The main edit macro page. The special var \"form_body\" is either the single-var edit form, or the category table, depending on which view you\'re using.','Admin Pages','default','en'),('edit_one_macro','<tr><td>%%nor!
m_font%%Or edit a macro directly:%%norm_font_end%%</td></tr>\r\n<tr><td><table cellspacing=\"2\" cellpadding=\"0\" width=\"100%\">\r\n <tr>\r\n <td colspan=\"2\">%%norm_font%%<b>Delete:</b><input type=\"checkbox\" name=\"delete\" value=\"1\">%%norm_font_end%%</td>\r\n </tr>\r\n <tr>\r\n <td>%%norm_font%%<b>Select Macro:</b>%%norm_font_end%%</td>\r\n <td>%%macroselect%%</td>\r\n <tr>\r\n <td>%%norm_font%%<b>Select Categories:</b>%%norm_font_end%%</td>\r\n <td>%%catselect%%</td>\r\n </tr>\r\n <tr>\r\n <td>%%norm_font%%<b>Name:</b>%%norm_font_end%%</td>\r\n <td><input type=\"text\" size=\"60\" name=\"name\" value=\"%%name%%\"></td>\r\n </tr>\r\n <tr>\r\n <td>%%norm_font%%<b>New Category:</b>%%norm_font_end%%</td>\r\n <td><input type=\"text\" size=\"60\" name=\"category\" value=\"\"><br>\r\n %%norm_font%%<i>(seperate multiple categories with commas)</i>%%norm_font_end%%\r\n </td>\r\n </tr>\r\n <tr>\r\n <td>%%norm_font%%<b>Parameters:</b>%%norm_font_end%%</td>\r\n !
<td><input type=\"text\" size=\"60\" name=\"parameter\" value=\"%%para
meter%%\"></td>\r\n </tr>\r\n <tr>\r\n <td colspan=\"2\">\r\n %%norm_font%%<b>Value:</b>%%norm_font_end%%<br>\r\n <textarea cols=\"60\" rows=\"6\" name=\"value\" wrap=\"soft\">%%value%%</textarea>\r\n </td>\r\n </tr>\r\n <tr>\r\n <td colspan=\"2\">\r\n %%norm_font%%<b>Description:</b>%%norm_font_end%%<br>\r\n <textarea cols=\"60\" rows=\"3\" name=\"description\" wrap=\"soft\">%%description%%</textarea>\r\n </td>\r\n </tr>\r\n</table></td></tr>\r\n',NULL,'','Admin Pages','default','en'),('macro_category_list','<tr>\r\n <td>%%norm_font%%<a href=\"%%rootdir%%/admin/macros/%%item_url%%\">%%item%%</a>%%norm_font_end%%</td>\r\n <td>%%norm_font%%<a href=\"%%rootdir%%/admin/macros/%%item_url%%\">%%item%%</a>%%norm_font_end%%</td>\r\n <td>%%norm_font%%<a href=\"%%rootdir%%/admin/macros/%%item_url%%\">%%item%%</a>%%norm_font_end%%</td>\r\n</tr>\r\n',NULL,'One line of the macro category list. Usually one table row.','Admin Pages','default','en'),('edit_instructions_abuse',!
'<P>If this article is abusing the edit queue please indicate this by pressing the button below.</P>\n<FORM NAME=\"storymoderate\" ACTION=\"%%rootdir%%/\" METHOD=\"POST\">\n<P align=\"center\">\n <INPUT type=\"hidden\" NAME=\"op\" VALUE=\"displaystory\">\n <INPUT type=\"hidden\" NAME=\"sid\" VALUE=\"%%sid%%\">\n <INPUT type=\"hidden\" NAME=\"mode\" VALUE=\"spam\">\n %%formkey%%\n <INPUT type=\"hidden\" NAME=\"vote\" VALUE=\"-1\">\n <INPUT type=\"submit\" name=\"save\" value=\"Spam\">\n</P>\n</FORM>',NULL,'<P>This block is displayed underneath the text of a story in the edit queue, if the edit queue anti-spam feature is activated. This should be a reasonably self-contained bit of HTML which explains what the spam button is to be used for and sets up the form for the spam button. All of the hidden form elements are required. This block recognizes the following special keys:</P>\n<DL>\n <DT>sid</DT>\n <DD>The story ID of the current story.</DD>\n <DT>formkey</DT>\n <DD>A for!
mkey element used to help prevent duplicate votes, scripted votes, and
other form spoofing strategies.</DD>\n</DL>','Stories','default','en'),('admin_boxes_form','<form name=\"boxes\" action=\"%%rootdir%%/admin/boxes\" method=\"post\">\r\n <table width=\"100%\" border=\"0\" cellpadding=\"0\" cellspacing=\"0\">\r\n <tr>\r\n <td bgcolor=\"%%title_bgcolor%%\">%%title_font%%Edit Boxes</font></td>\r\n </tr>\r\n <tr><td>%%title_font%%<font color=\"#FF0000\">%%admin_boxes_errormsg%%</font></font></td></tr>\r\n <tr> \r\n <td>%%norm_font%%<b>Box:</b> %%admin_boxes_box_menu%%\r\n <input type=\"submit\" name=\"get\" value=\"Get Box\" /></font></td>\r\n </tr><tr><td>\r\n%%norm_font%%<b>%%admin_boxes_delete_check%%</b></font>\r\n</td></tr>\r\n <tr>\r\n <td>%%norm_font%%<b>Box ID:</b>\r\n <input type=\"text\" name=\"boxid\" value=\"%%admin_boxes_boxid%%\" size=\"40\" />\r\n </font></td>\r\n </tr>\r\n <tr>\r\n <td>%%norm_font%%<b>Title:</b>\r\n <input type=\"text\" name=\"title\" value=!
\"%%admin_boxes_title%%\" size=\"40\" />\r\n </font></td>\r\n </tr>\r\n <tr>\r\n <td>%%norm_font%%<b>Template:</b>%%admin_boxes_template_menu%% %%admin_boxes_template_link%%</font></td>\r\n </tr>\r\n <tr>\r\n <td><input type=\"checkbox\" name=\"choose\" value=\"1\" %%admin_boxes_choose_checked%% />\r\n %%norm_font%%Allow users to toggle box off%%norm_font_end%%\r\n </td>\r\n </tr>\r\n <tr><td>%%norm_font%%<b>Description:</b></td></tr>\r\n <tr>\r\n <td>%%norm_font%%\r\n <textarea cols=\"50\" rows=\"3\" name=\"description\" wrap=\"soft\">%%admin_boxes_description%%</textarea>\r\n </font></td>\r\n </tr>\r\n <tr><td>%%norm_font%%<b>Content:</b></td></tr>\r\n <tr><td>%%norm_font%%\r\n <textarea cols=\"50\" rows=\"25\" name=\"content\">%%admin_boxes_content%%</textarea>\r\n </font></td></tr>\r\n <tr><td>%%norm_font%%\r\n <input type=\"submit\" name=\"write\" value=\"Save Box\" /> <input type!
=\"reset\" />\r\n </font></td></tr>\r\n </table>\r\n</form> \r\n'
,NULL,'<P>This block is used to create the Box Admin Tool page. It must contain all of the form elements used in the Box Admin page, and should be self-contained HTML. The special keys recognised are:</P>\n<DL>\n <DT>admin_boxes_errormsg</DT>\n <DD>A message indicating whether a save was successful or not, and if not, the text of the error message</DD>\n <DT>admin_boxes_box_menu</DT>\n <DD>The select box used to choose a box to edit</DD>\n <DT>admin_boxes_delete_check</DT>\n <DD>The delete checkbox displayed when a box is being edited</DD>\n <DT>admin_boxes_template_menu</DT>\n <DD>The select box used to choose the box template to use for a particular box</DD>\n <DT>admin_boxes_template_link</DT>\n <DD>A link to the block admin tool to edit the box template selected for the box currently being edited</DD>\n <DT>admin_boxes_choose_checked</DT>\n <DD>The \"checked\" status of the checkbox which determines whether or not the users can choose to show or hide that particu!
lar box in their display preferences</DD>\n <DT>admin_boxes_boxid</DT>\n <DD>The name of the box currently being edited</DD>\n <DT>admin_boxes_title</DT>\n <DD>The title of the box currently being edited</DD>\n <DT>admin_boxes_description</DT>\n <DD>The description of the box currently being edited</DD>\n <DT>admin_boxes_content</DT>\n <DD>The perl code of the box currently being edited</DD>\n </DL>\n<P>Do not change the names of the form elements, or remove any form elements, or box editing may fail in unexpected ways.</P>','Admin Pages','default','en'),('login_error_message','%%norm_font%%<FONT COLOR=\"#FF0000\"><B>Login Incorrect</B></FONT>%%norm_font_end%%','2','<P>This is the error message displayed in the <B>login_box</B> if either the username or password (or both) are incorrect. This block contains the special key \"uname\" which is replaced with the username entered in the login form.</P>','Accounts','default','en'),('login_mailed_message','%%norm_font%%<FONT C!
OLOR=\"#FF0000\"><B>New password for %%uname%% mailed.</B></FONT>%%nor
m_font_end%%','2','<P>This is the status message displayed in the <B>login_box</B> when a new password has successfully been mailed to the user. This block contains the special key \"uname\" which is replaced with the username entered in the login form.</P>','Accounts','default','en'),('login_mail_failed','%%norm_font%%<FONT COLOR=\"#FF0000\"><B>Could not mail password for %%uname%%.</B></FONT>%%norm_font_end%%','2','<P>This is the error message displayed in the <B>login_box</B> when Scoop could not send the email containing the user\'s new password as requested. This block contains the special key \"uname\" which is replaced with the username entered in the login form.</P>','Accounts','default','en'),('user_prefs_message','%%title_font%%Sorry!%%title_font_end%%\r\n<P>%%norm_font%%Sorry, you can only edit user preferences if you have a user account. Why not <A HREF=\"%%rootdir%%/newuser\">make one</A>?%%norm_font_end%%</P>','2','<P>This block is displayed instead of the form!
when a user who is not logged in tries to change his display or comment preferences. It should be self-contained HTML and explain that accounts are required to set preferences. There are no special keys.</P>','General','default','en'),('interface_prefs_main_form',' <DIV>\r\n %%title_font%%Edit Interface Preferences for %%nickname%%%%title_font_end%%\r\n <P><FONT COLOR=\"#FF0000\">%%title_msg%%</FONT></P>\r\n\r\n %%interface_form%%\r\n </DIV>','2','<P>This block is used to build the page for the interface preferences form, one of the userprefs pages. It should be self-contained HTML and contain the page title and the special keys listed below:</P>\n<DL>\n <DT>nickname</DT>\n <DD>The nickname of the user changing his preferences</DD>\n <DT>title_msg</DT>\n <DD>Any error or status messages regarding the save</DD>\n <DT>interface_form</DT>\n <DD>The entire form containing all preferences suppor!
ted by Scoop</DD>\n</DL>','Preferences','default','en'),('comment_post
ed_message','<A NAME=\"here\">Comment posted!</A> Thank you for contributing.','2','<P>This block is displayed after a user has successfully posted a message. It should contain a message telling the user so. There are no special keys.</P>','Comments','default','en'),('box_title_bg','#999999','1','<P>This block is used wherever a colour value is needed to set the colour of the sidebar box title bars. It should be a hex colour value, including the #, such as #000000 for black. There are no special keys.</P>','Colours','greyscale','en'),('comment_head_bg','#eeeeee','1','<P>This block is used wherever a colour value is needed to set the background colour of the comment header (which typically contains the subject and poster\'s information, but not the comment itself). It should be a hex colour value, including the #, such as #000000 for black. There are no special keys.</P>','Colours','greyscale','en'),('title_bgcolor','#aaaaaa','1','<P>This block is used anywhere a title ba!
r needs a background (except in the sidebar boxes, which use <B>box_title_bg</B>). It should be a hex colour value, including the #.</P>','Colours','greyscale','en'),('theme_list','<form name=\"themes\" action=\"%%rootdir%%/admin/blocks/overview\" method=\"post\">\n<table border=\"0\" cellpadding=\"2\" cellspacing=\"0\" width=\"100%\">\n<tr><td bgcolor=\"%%title_bgcolor%%\">%%title_font%%Blocks: Themes Overview%%title_font_end%%</td></tr>\n<tr><td>%%norm_font%%<a href=\"%%rootdir%%/admin/blocks\">Back to blocks admin</a>%%norm_font_end%%</td></tr>\n<tr><td>%%norm_font%%%%themesel%%%%norm_font_end%%</td></tr>\n<tr><td>%%norm_font%%<input type=\"submit\" name=\"show\" value=\"Show Selected Themes\">%%norm_font_end%%</td></tr>\n</table>\n</form>\n<table border=1 cellpadding=1 cellspacing=0 width=\"100%\">\n %%list%%\n</table>\n','1','<P>This block creates the admin tool structure for the block theme overview. It contains a form and two special keys. The form elements are:</P>!
\n<DL>\n <DT>FORM</DT>\n <DD>The form should post to |rootdir|/admin/
blocks/overview</DD>\n <DT>show</DT>\n <DD>The submit button should have the name \"show\"</DD>\n</DL>\n<P>The following special keys are recognized:</P>\n<DL>\n <DT>themesel</DT>\n <DD>A set of checkboxes, one for each theme, to allow the admin to select which themes to display in the overview.</DD>\n <DT>list</DT>\n <DD>The list of all blocks in the selected theme. Matching blocks in two different themes are displayed in the same row, so you can see at a glance which blocks will be replaced when applying themes.</DD>\n</DL>','Admin Pages','default','en'),('dynamic_loading_message','%%norm_font%%<i>Loading...</i>%%norm_font_end%%',NULL,'<P>This block contains the message that will replace the comment title or comment when that comment is in the process of being loaded or unloaded. This should be small and indicate that Scoop is working on it and the comment or comment title will appear shortly.</P>','Comments','default','en'),('dynamic_expand_thread_link','<img src=\"%%i!
magedir%%/dyn_expa.gif\" alt=\"++\" title=\"Expand Subthread\" width=\"12\" height=\"12\" border=\"0\">',NULL,'<P>This block should contain either the text or an image used as the link to expand an entire subthread of comments when comments are viewed in either of the dynamic modes. If it is an image, it s