\r\n![\"Powered](\"%%imagedir%%/new_powered.gif\")
%%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%%
\r\n\r\n
%%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%%
\r\nThis 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.
','General','default','en'); INSERT INTO `blocks` VALUES ('scoop_intro','%%norm_font%%Holy Crap! You have your own Scoop 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%%
\r\n\r\n%%norm_font%%The main development site is at scoop.kuro5hin.org. This contains links to all the other stuff, so poke around a little.%%norm_font_end%%
\r\n\r\n%%norm_font%%For immediate help and assistance from the Scoop code monkeys, join the scoop-help mailing list. This is practically a requirement for a pleasant Scoop administrative experience, as Scoop is rather complicated and it isn\'t always obvious where to find things.%%norm_font_end%%
\r\n\r\n%%norm_font%%To help figure things out, there is a
%%norm_font%%Other things of note:%%norm_font_end%%
\r\n\r\nThis 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.
','General','default','en'); INSERT INTO `blocks` VALUES ('index_template','\r\n\r\n\r\n| \r\n \r\n %%scoop_intro%%\r\n \r\n | \r\n \r\n\r\n \r\n\r\n %%BOX,section_title%%\r\n %%CONTENT%%\r\n | \r\n \r\n\r\n \r\n\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 | \r\n \r\n\r\n
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:
\r\n![\"Scoop](\"%%imagedir%%/small_logo.jpg\"){kind=logo}
\r\nThis 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.
','General','default','en'); INSERT INTO `blocks` VALUES ('comment','\r\nThis 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 moderation_comment). This should be a self-contained chunk of HTML code that can be nested arbitrarily deep. The special keys recognised are:
\n| \r\n %%CONTENT%%\r\n | \r\n \r\n \r\n \r\n\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 | \r\n \r\n
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.
','Page Templates','default','en'); INSERT INTO `blocks` VALUES ('story_info','\r\nThis 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.
','Stories','default','en'); INSERT INTO `blocks` VALUES ('story_summary','%%smallfont%%By %%info%%, Section %%section_link%%\r\n
Posted on %%time%%\r\n%%tags%%%%smallfont_end%%
%%norm_font%%%%stats%% %%readmore%%%%norm_font_end%%
\r\nThis 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:
\nThis 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:
\nThank you for your submission. This is a community-edited site, so hopefully your fellow readers will see fit to post your story. Good Luck!
','1','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.
','Stories','default','en'); INSERT INTO `blocks` VALUES ('submission_guidelines','Thank you for taking the time to submit a story!
\r\nHere are some general guidelines for new stories:
\r\nNow post away!
','1','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.
','Stories','default','en'); INSERT INTO `blocks` VALUES ('moderate_head','%%norm_font%%Current score:%%score%%
\r\nTotal votes: %%votes%%
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:
\nThis 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 comment). This should be a self-contained chunk of HTML code that can be nested arbitrarily deep. The special keys recognised are:
\nThis 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.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('login_box','%%LOGIN_ERROR%%
\r\n%%norm_font%%Make a new account\r\n%%norm_font_end%%
\r\n\r\nDespite 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:
\nThe block must contain the following form elements or the login process will not work properly:
\nThis 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 hotlist_remove_link is displayed to users who have already hotlisted the story. This block has no special keys.
','Stories','default','en'); INSERT INTO `blocks` VALUES ('hotlist_remove_link','-Hotlist','1','This block is used as the text of the link used to remove a story from a user\'s personal hotlist. It is only displayed to users who are logged in and who have hotlisted that story; the block hotlist_link is displayed to users who have not hotlisted the story. This block has no special keys.
','Stories','default','en'); INSERT INTO `blocks` VALUES ('poll_block','\r\n%%title_font%%%%title%%%%title_font_end%%\r\n\r\nThis block is used to format the poll results when displayed as the main content of the page. The following special keys are recognized:
\nThis block is used whenever a dot or list item indicator of some sort is needed. It is called directly by other blocks, never assembled as part of a special key, and recognizes no special keys itself.
','General','default','en'); INSERT INTO `blocks` VALUES ('vote_console','\r\n%%norm_font%%Your vote really does count! You decide whether this story ever sees the light of the front page. So vote!%%norm_font_end%%
\r\n\r\n%%norm_font%%\r\n%%vote_form%%\r\n%%norm_font_end%%
\r\nThis 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.
','Stories','default','en'); INSERT INTO `blocks` VALUES ('blank_box','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:
\n| \r\n \r\n %%STORY%%\r\n \r\n | \r\n \r\n \r\n \r\n\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 | \r\n \r\n
This block is used to build the story and comment display pages. It must be a full HTML page. The special keys recognised are:
\r\nThis 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.
','Polls,Stories','default','en'); INSERT INTO `blocks` VALUES ('edit_story_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| \r\n %%STORY%%\r\n %%BOX,comment_controls%%\r\n %%CONTENT%%\r\n %%BOX,comment_controls%%\r\n | \r\n \r\n \r\n \r\n\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 | \r\n \r\n
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:
\n| \r\n %%STORY%%\r\n %%CONTENT%%\r\n | \r\n \r\n \r\n \r\n\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 | \r\n \r\n
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:
\nThis 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.
','Stories','default','en'); INSERT INTO `blocks` VALUES ('readmore_txt','Full Story','1','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 no_body_txt is used instead.
','Stories','default','en'); INSERT INTO `blocks` VALUES ('section_links','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.
','General','default','en'); INSERT INTO `blocks` VALUES ('diary_post_message','Your new entry has been posted. Enjoy!','1','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.
','Diaries','default','en'); INSERT INTO `blocks` VALUES ('box_title_bg','#006699','1','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.
','Colours','default','en'); INSERT INTO `blocks` VALUES ('comment_head_bg','#eeeeee','1','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.
','Colours','default','en'); INSERT INTO `blocks` VALUES ('dept_font','','1','This block is used to format the \"from the x department\" string attached to stories, if the variable show_dept 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 dept_font_end. There are no special keys.
','Fonts','default','en'); INSERT INTO `blocks` VALUES ('no_body_txt','Comments >>','1','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 readmore_txt is used instead.
','Stories','default','en'); INSERT INTO `blocks` VALUES ('sectiononlystory_bg','#eeeeee','1','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');
INSERT INTO `blocks` VALUES ('smallfont','','1',' This block should be a complete opening FONT tag. It must match the closing tag set in the block smallfont_end.
This block should be a closing FONT tag, or otherwise close the tag opened in the block smallfont.
','Fonts','default','en'); INSERT INTO `blocks` VALUES ('story_mod_bg','#EEEEEE','1','This 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 #.
','Colours','default','en'); INSERT INTO `blocks` VALUES ('story_nav_bg','#EEEEEE','1','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 #.
','Colours','default','en'); INSERT INTO `blocks` VALUES ('submittedstory_bg','#c6dae4','1','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'); INSERT INTO `blocks` VALUES ('title_bgcolor','#EEEEEE','1','
This block is used anywhere a title bar needs a background (except in the sidebar boxes, which use box_title_bg). It should be a hex colour value, including the #.
','Colours','default','en'); INSERT INTO `blocks` VALUES ('undisplayedstory_bg','#c0c0c0','1','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'); INSERT INTO `blocks` VALUES ('diary_guidelines','
Thank you for taking the time to submit a diary!
\r\nThere are no rules, you can post basically anything you want here. This is your spot to tell the rest of the community what\'s on your mind, or what\'s going on in your life, or just anything really.
\r\nNow post away!
','2','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.
','Stories','default','en'); INSERT INTO `blocks` VALUES ('blank_template','\r\n\r\nThis 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.
','Page Templates','default','en'); INSERT INTO `blocks` VALUES ('empty_box','%%content%%','1','This 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.
','Box Templates','default','en'); INSERT INTO `blocks` VALUES ('new_comment_marker','[new]','1','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 |new| in the blocks comment and moderation_comment.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('submit_rdf_message','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 review it, and will either approve it or delete it.
','1','This block is displayed just above the form used to submit an RDF file explaining what the form is for.
','RDF','default','en'); INSERT INTO `blocks` VALUES ('titled_box','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:
\n%%CONTENT%%\r\n','1','
This block is used to format Scoop\'s cron system output. It parsed by run_cron.pl and should not be changed as neither users nor administrators ever use it directly.
','Page Templates','default','en'); INSERT INTO `blocks` VALUES ('digest_storyformat','\n%%title%% \n By %%aid%%, %%time%% \n Section: %%section%%, Topic: %%tid%% \n\n%%introtext%% \n\n%%url%%\n\n----\n','1','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:
\nThis 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 digest_header or digest_footer 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:
\nThis 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:
\nThis 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 recently than those displayed. It should be self-contained HTML. The following special key is recognized:
\nYou are not currently a paid member. Why not become one?
','1','This block is displayed on a user\'s preferences page if they are not already subscribed, if they have the allow_subscription perm, and if the variable use_subscriptions 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.
','Subscriptions','default','en'); INSERT INTO `blocks` VALUES ('story_separator','\n','1','This block is placed between the story_summary and story_body 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.
','Stories','default','en'); INSERT INTO `blocks` VALUES ('spell_err','','1','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 spell_err_end.
','Fonts','default','en'); INSERT INTO `blocks` VALUES ('spell_err_end','','1','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 spell_err.
','Fonts','default','en'); INSERT INTO `blocks` VALUES ('new_user_html','%%title_font%%Create New User Account%%title_font_end%%\r\n%%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 easy.%%norm_font_end%%
\r\n\r\n%%norm_font%%Why do you have to respond 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%%
\r\n\r\n%%norm_font%%The email address you enter here, so it must work. Do NOT enter a spam-protected or fake email address, or your account will not work.%%norm_font_end%%
\r\n\r\n%%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%%
\r\n\r\n%%norm_font%%Now get started, and we hope you enjoy %%sitename%%!%%norm_font_end%%
\r\n\r\n\r\n','1','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:
\r\nThe following special keys are recognized:
\r\n%%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%%
\r\n%%norm_font%% %%advertising_account_disclaimer%% %%norm_font_end%%
\r\n\r\n','1','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.
','Ads','default','en'); INSERT INTO `blocks` VALUES ('advertising_account_disclaimer','Please remember the following with your new advertising account.
\r\n\r\nAny stories posted to this site for purely advertising purposes will void your contract with us. The articles and diaries on this site are not for advertising purposes. This account entitles you to submit ads for posting in specified places on the page only. If you are caught abusing this account, 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
\r\n\r\nThank you for your understanding.
','1','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 req_extra_advertiser_info 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.
','Ads','default','en'); INSERT INTO `blocks` VALUES ('ad_test_template','\r\n\r\nThis 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 show_ad box. There are no special keys.
','Ads,Page Templates','default','en'); INSERT INTO `blocks` VALUES ('text_ad_template','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:
\nThe special keys used in the ad template become the required fields for the ad, as well as the only fields permitted.
','Ads','default','en'); INSERT INTO `blocks` VALUES ('donate_email_success','Thank you for your donation of $%%AMOUNT%%.',NULL,'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.
\n| %%PREVIOUS_LINK%% | \n%%NEXT_LINK%% | \n
This block is used to create the next and previous page links at the top and bottom of the section index pages.
\nFIXME: not implemented correctly. Links won\'t disappear if not needed. Leave blank for now and it\'ll work.','General','default','en'); INSERT INTO `blocks` VALUES ('ad_step1_rules','\r\n\r\n%%title_font%% Rules for Submitting Ads %%title_font_end%%\r\n\r\n%%norm_font%%\r\n%%norm_font%% %%NEXT_LINK%% %%norm_font_end%%
','1','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.
\nThere is one special key: NEXT_LINK which is the \"I agree\" button.
','Ads','default','en'); INSERT INTO `blocks` VALUES ('error_template','\r\nTime: %%thetime%%
\r\nPackage: %%package%%
\r\nFile: %%file%%
\r\nLine: %%line%%
\r\nAdditional Messages: %%ERROR_MSG%%\r\nVar Dump:
\r\n%%VARDUMP%%\r\n
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.
','Page Templates','default','en'); INSERT INTO `blocks` VALUES ('ad_confirm_text','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.
\r\n\r\nIf you like what you see, hit \"Purchase Ad\" below, if not, hit back and make your changes.
','1','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.
','Ads','default','en'); INSERT INTO `blocks` VALUES ('no_submit_ad_perm','%%title_font%%Submit Ad Error%%title_font_end%%\r\n\r\n%%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 here%%norm_font_end%%
\r\n','1','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.
','Ads','default','en'); INSERT INTO `blocks` VALUES ('ad_disapproval_mail','The ad that you submitted to %%sitename%% was disapproved today\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','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:
\nThe 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.
','Ads,Emails','default','en'); INSERT INTO `blocks` VALUES ('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','This block is emailed to a user when an advertisement he submitted has been approved by a site admin. It should be plain text and say that the ad has been approved. The special keys recognised are:
\nThe 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.
','Ads,Emails','default','en'); INSERT INTO `blocks` VALUES ('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','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 mail_ad_reminders. The number of impressions remaining when the email is sent is determined by the variable mail_ad_reminder_on. 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:
\nThis 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 mail_ad_reminders and mail_ad_finished_reminder. 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 mail_ad_almost_done_msg. 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:
\nThis 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 distribution page.
','1','not used. Yet another unimplemented ad feature.','Ads','default','en'); INSERT INTO `blocks` VALUES ('confirm_purchase_impressions','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.
','1','yet another unimplemented ad feature','Ads','default','en'); INSERT INTO `blocks` VALUES ('editqueuestory_bg','#99ccdd','1','This block is used as a background colour in the story list for stories in the edit queue, to distinguish them from stories that may 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.
','Colours','default','en'); INSERT INTO `blocks` VALUES ('author_edit_console','\r\n\r\n\r\n','1','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 recognised are:
\n%%norm_font%%Please Help. 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%%
\r\n%%spam_form%%\r\nThis block is displayed underneath the text of a story in the edit queue, informing readers of its status. This should be a reasonably 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:
\nThis 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.
','Ads','default','en'); INSERT INTO `blocks` VALUES ('renew_choose_ad','%%norm_font%%You need to choose an ad to renew. Check your ad listing page to \r\nchoose an ad to renew and click on the renewal link there.%%norm_font_end%%
','1','This block is displayed if a user tries to visit the ad renewal page without specifying 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.
','Ads','default','en'); INSERT INTO `blocks` VALUES ('renew_ad_no_permission','%%norm_font%%Sorry, but you cannot renew this advertisement. Please choose an ad from your ad list to renew.%%norm_font_end%%
','1','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.
','Ads','default','en'); INSERT INTO `blocks` VALUES ('rating_format','(%%score%% / %%num_ratings%%)',NULL,'This block is used in the comment and moderation_comment 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 following special keys are recognized:
\nThis 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.
\n%%norm_font%% Be 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%%
','1','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.
','Ads','default','en'); INSERT INTO `blocks` VALUES ('dynamic_template','\r\n\r\n\r\nThis block is a nearly empty page template used for loading individual comments in dynamic mode. It must contain the correct BODY onload 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.
','Comments,Page Templates','default','en'); INSERT INTO `blocks` VALUES ('dynamic_collapse_thread_link','![\"--\"](\"%%imagedir%%/dyn_cola.gif\" "\\"Collapse")
',NULL,'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.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('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 have 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'); INSERT INTO `blocks` VALUES ('paypal_finished','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.
','1','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.
','Payments','default','en'); INSERT INTO `blocks` VALUES ('paypal_canceled','We\'re sorry you decided to cancel your order.
','1','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.
','Payments','default','en'); INSERT INTO `blocks` VALUES ('dynamic_loading_link','
','1','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 dynamic_expand_link and dynamic_collapse_link. This block has no special keys.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('dynamic_collapse_bottom_link','
','1','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 dynamic_collapse_link is the one placed at the top. This block has no special keys.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('block_category_list','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 edit_block (This block is placed as many times as necessary in the spot designated by the special key catlist). Multiple instances of the special keys listed below are permitted in this block. The special keys recognised are:
\nThis 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:
\nBe very careful when changing this block, as it is used to build the interface required to change it back if it is broken. Changing the form elements is strongly not recommended.
','Admin Pages','default','en'); INSERT INTO `blocks` VALUES ('edit_cat_blocks','\r\nThis 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:
\nThis 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:
\n| %%norm_font%%Delete:%%norm_font_end%% | \n|
| %%norm_font%%Select Block:%%norm_font_end%% | \n%%blockselect%% | \n
| %%norm_font%%Select Categories:%%norm_font_end%% | \n%%catselect%% | \n
| %%norm_font%%Name:%%norm_font_end%% | \n\n |
| %%norm_font%%Theme:%%norm_font_end%% | \n\n |
| %%norm_font%%New Category:%%norm_font_end%% | \n\n %%norm_font%%(seperate multiple categories with commas)%%norm_font_end%%\n | \n
| \n %%norm_font%%Value:%%norm_font_end%% \n \n | \n|
| %%norm_font%%%%description%%%%norm_font_end%% | \n|
| \n %%norm_font%%Description:%%norm_font_end%% \n \n | \n
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:
\n| %%norm_font%%Delete:%%norm_font_end%% | \r\n|
| %%norm_font%%Type:%%norm_font_end%% | \r\n%%typeselect%% | \r\n
| %%norm_font%%Select Variable:%%norm_font_end%% | \r\n%%varselect%% | \r\n
| %%norm_font%%Select Categories:%%norm_font_end%% | \r\n%%catselect%% | \r\n
| %%norm_font%%Name:%%norm_font_end%% | \r\n\r\n |
| %%norm_font%%New Category:%%norm_font_end%% | \r\n\r\n %%norm_font%%(seperate multiple categories with commas)%%norm_font_end%%\r\n | \r\n
| \r\n %%norm_font%%Value:%%norm_font_end%% \r\n \r\n | \r\n |
| %%norm_font%%%%description%%%%norm_font_end%% | \n|
| \r\n %%norm_font%%Description:%%norm_font_end%% \r\n \r\n | \r\n
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 block recognizes the following special keys:
\nThis 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:
\nThis 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:
\nThe 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.
','Admin Pages','default','en'); INSERT INTO `blocks` VALUES ('edit_macro','\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'); INSERT INTO `blocks` VALUES ('edit_one_macro','| %%norm_font%%Delete:%%norm_font_end%% | \r\n|
| %%norm_font%%Select Macro:%%norm_font_end%% | \r\n%%macroselect%% | \r\n
| %%norm_font%%Select Categories:%%norm_font_end%% | \r\n%%catselect%% | \r\n
| %%norm_font%%Name:%%norm_font_end%% | \r\n\r\n |
| %%norm_font%%New Category:%%norm_font_end%% | \r\n\r\n %%norm_font%%(seperate multiple categories with commas)%%norm_font_end%%\r\n | \r\n
| %%norm_font%%Parameters:%%norm_font_end%% | \r\n\r\n |
| \r\n %%norm_font%%Value:%%norm_font_end%% \r\n \r\n | \r\n |
| \r\n %%norm_font%%Description:%%norm_font_end%% \r\n \r\n | \r\n
If this article is abusing the edit queue please indicate this by pressing the button below.
\n',NULL,'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:
\nThis 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:
\nDo not change the names of the form elements, or remove any form elements, or box editing may fail in unexpected ways.
','Admin Pages','default','en'); INSERT INTO `blocks` VALUES ('login_error_message','%%norm_font%%Login Incorrect%%norm_font_end%%','2','This is the error message displayed in the login_box 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.
','Accounts','default','en'); INSERT INTO `blocks` VALUES ('login_mailed_message','%%norm_font%%New password for %%uname%% mailed.%%norm_font_end%%','2','This is the status message displayed in the login_box 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.
','Accounts','default','en'); INSERT INTO `blocks` VALUES ('login_mail_failed','%%norm_font%%Could not mail password for %%uname%%.%%norm_font_end%%','2','This is the error message displayed in the login_box 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.
','Accounts','default','en'); INSERT INTO `blocks` VALUES ('user_prefs_message','%%title_font%%Sorry!%%title_font_end%%\r\n%%norm_font%%Sorry, you can only edit user preferences if you have a user account. Why not make one?%%norm_font_end%%
','2','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.
','General','default','en'); INSERT INTO `blocks` VALUES ('interface_prefs_main_form','%%title_msg%%
\r\n\r\n %%interface_form%%\r\nThis 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:
\nThis 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.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('box_title_bg','#999999','1','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.
','Colours','greyscale','en'); INSERT INTO `blocks` VALUES ('comment_head_bg','#eeeeee','1','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.
','Colours','greyscale','en'); INSERT INTO `blocks` VALUES ('title_bgcolor','#aaaaaa','1','This block is used anywhere a title bar needs a background (except in the sidebar boxes, which use box_title_bg). It should be a hex colour value, including the #.
','Colours','greyscale','en'); INSERT INTO `blocks` VALUES ('theme_list','\nThis block creates the admin tool structure for the block theme overview. It contains a form and two special keys. The form elements are:
\nThe following special keys are recognized:
\nThis 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.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('dynamic_expand_thread_link','![\"++\"](\"%%imagedir%%/dyn_expa.gif\" "\\"Expand")
',NULL,'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 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.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('dynamic_js_tag','',NULL,'This block is what allows dynamic comments to work. On pages where comments are viewed and dynamic comment mode is active, the key |dynamicmode_javascript| is replaced with the contents of this block. (That key is best placed in the header block, so it is always available.) This block should only be modified to reflect the location of the dynamic-comments.js file, which it loads. This block has no special keys.','Comments','default','en');
INSERT INTO `blocks` VALUES ('dynamic_expand_link','
',NULL,'
This block should contain either the text or an image used as the link to expand a single comment when viewing comments 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 near the subject at the top of the comment. This block has no special keys.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('dynamic_collapse_link','
',NULL,'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 near the subject at the top of the comment; the block dynamic_collapse_bottom_link is the one used at the bottom. This block has no special keys.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('subscribe_template','\r\n\r\n\r\n| \r\n %%CONTENT%%\r\n | \r\n \r\n \r\n \r\n\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 | \r\n \r\n
This block is the page template used for subscription signup and payment. It must be a full HTML page. The special keys recognized are:
\nThis block is the body of an email sent to the site administrator (at the addresses in the variable admin_alert) notifying them of a user who has bought a subscription but cannot be placed in the subscriber group automatically. This is determined by the perm sub_allow_group_change. It should not contain any HTML formatting, and recognizes no keys except the special keys listed below, because it does not go through the normal page processing. The special keys recognized are:
\nThis block is the body of an email sent to a user when Scoop has successfully added to their subscription. It should not contain any HTML formatting, and recognizes no keys except the special keys listed below, because it does not go through the normal page processing before being emailed. The special keys recognized are:
\nThis block can be used where you want Scoop to output only the content, with no HTML page wrapper at all. It should contain only the special key CONTENT and nothing else. The special key CONTENT is replaced with the output of whichever function or box is run using this block as its page template (see the Ops Admin Tool).
','Page Templates','default','en'); INSERT INTO `blocks` VALUES ('sub_paypal_canceled','Sorry you cenceled.','1','This block is displayed when a user cancels a subscription purchase while using paypal. It should be self-contained HTML and should let the user know that the transaction has been canceled.
','Payments,Subscriptions','default','en'); INSERT INTO `blocks` VALUES ('editqueuespam_bg','#f9e5de','1','This block is used as a background colour in the story list for stories in the edit queue that the user has voted \"Spam\" on, to make it easy to remember which ones they can safely ignore while they remain in the edit queue. It should contain a hex colour value or a recognized colour name. It only applies if both the edit queue and the edit queue anti-spam button are turned on. This block has no special keys.
','Colours','default','en'); INSERT INTO `blocks` VALUES ('story_vote_form','',NULL,'This is the form used to vote on stories in the voting queue. The following form elements must be present:
\nThe following special keys are recognized:
\nYou are a trusted user. For more information on the extra rights and responsibilities of trusted users, please see \"Trusted User Guidelines\".
','1','This block is displayed on a user\'s own user info page when they are a trusted user. (See the Scoop Admin Guide for more information on trusted and untrusted users and mojo, which determines trust level.) It should notify the user of their trusted status, and either explain what it means or link to a page that explains what it means.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('untrusted_post_message','You are an untrusted user. Your comment has been posted, but it must be reviewed by a trusted user before it will become visible. For more information, please see \"Why am I untrusted?\"
','1','This block is displayed above the comment posted message when an untrusted user posts a comment. (See the Scoop Admin Guide for more information on trusted and untrusted users and mojo, which determines trust level.) It should notify the user of their untrusted status, and either explain what it means or link to a page that explains what it means.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('subscribe_denied_message','Sorry, but you can\'t subscribe to %%sitename%% at this time.
','1','This block is displayed if a user attempts to subscribe while not having the appropriate permissions. It should be self-contained HTML and should explain why the user cannot subscribe.
','Subscriptions','default','en'); INSERT INTO `blocks` VALUES ('subscribe_intro_text','This is where you should put some introductory information about your subscription offerings. Edit the block \"subscribe_intro_text\" with the text you want here.
','1','This block is displayed on the subscription page. It should be self-contained HTML and should describe the subscription options and what extra features are available to subscribers.
','Subscriptions','default','en'); INSERT INTO `blocks` VALUES ('ad_submit_help','Any general ad help you would like to display should go here. This message can be customized in the block ad_submit_help.
','1','This block is displayed at the bottom of ad submission step 3. It should be self-contained HTML, and should contain general instructions for ad submission. There are no special keys.
','Ads','default','en'); INSERT INTO `blocks` VALUES ('mark_Subscribers','(!)','1','This block is inserted in the comment headers for users in the Subscribers group. It should be a small bit of self-contained HTML. It is placed with a special key in the blocks comment and moderation_comment. This block has no special keys.','Subscriptions','default','en'); INSERT INTO `blocks` VALUES ('new_story_marker','=>','1','
This block is inserted in the story summary if the user has not yet read this story, according to Scoop\'s read-tracking system. It replaces the special key |new| in the block story_summary.
','Stories','default','en'); INSERT INTO `blocks` VALUES ('comment_word','comment','1','This block contains the word used for comments in the comment count on the front page. This should be the singular form; the plural suffix is set in the block comment_plural. There are no special keys.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('comment_plural','s','1','This block is used to provide a plural suffix if there is more than one comment attached to a story. It is simply appended to the value in comment_word where appropriate. There are no special keys.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('comment_num_format_start','','1','This block is used just before the number of total comments attached to a story. 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 comment_num_format_end. There are no special keys.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('comment_num_format_end','','1','This block is used just after the number of total comments attached to a story. It should be a complete closing font or text style indicator, such as a font or b tag. It must properly close the tags opened by the contents of the block comment_num_format_start. There are no special keys.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('new_comment_format_start','','1','This block is used to format the number of new comments in a story on the index page. It should be an opening HTML tag that matches the closing tag used in the block new_comment_format_end.
','Fonts','default','en'); INSERT INTO `blocks` VALUES ('new_comment_format_end','','1','This block is used to format the number of new comments in a story on the index page. It should be a closing HTML tag that matches the formatting tag used in the block new_comment_format_start.
','Fonts','default','en'); INSERT INTO `blocks` VALUES ('poll_img_width','300','','This block determines the maximum width in pixels of the poll bar, and the width of the bar used for the poll option with 100% of the votes. All poll bar widths are percentages of this value corresponding to the percentage of votes the option received. It should be a number only.
','Polls','default','en'); INSERT INTO `blocks` VALUES ('norm_font_end','',NULL,'This block is used extensively in the default install. It should be a closing FONT tag, or otherwise close the tag opened in the block norm_font.
','Fonts','default','en'); INSERT INTO `blocks` VALUES ('box_title_font','This block is used in box templates before the box title. 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 box_title_font_end. There are no special keys.
','Fonts','default','en'); INSERT INTO `blocks` VALUES ('title_font_end','',NULL,'This block is used to format titles. It should be a closing font or other formatting tag. It must match the opening tags in the block title_font.
','Fonts','default','en'); INSERT INTO `blocks` VALUES ('title_font','This block is used to format titles. It should be a complete opening font or other formatting tag. It must match the closing tags in the block title_font_end.
','Fonts','default','en'); INSERT INTO `blocks` VALUES ('box_title_font_end','',NULL,'This block is used in box templates after the box title. It should be a complete closing font or text style indicator, such as a closing font or b tag. It must properly close the tags opened in the block box_title_font. There are no special keys.
','Fonts','default','en'); INSERT INTO `blocks` VALUES ('norm_font','',NULL,'This block is used extensively in the default install. It should be a complete opening tag, or blank. It must match the closing tag set in the block norm_font_end. The following special keys are recognised:
\nThis is the name of the file to use when building the poll image. The file should be in the images directory. The value of this block should not have any path information. The image is stretched horizontally to the desired width, so it should not have any horizontal detail that may be deformed.
','Polls','default','en'); INSERT INTO `blocks` VALUES ('slogan','Collaborative Media for the Masses',NULL,'This block is used in the browser\'s title bar. It should contain a witty saying that describes your site and should not contain the name of the site or any HTML formatting commands. It is only used on the site\'s index pages.
','General','default','en'); INSERT INTO `blocks` VALUES ('digest_subject','My Site Digest',NULL,'This block is used as the subject line of 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, none of the usual keys will work. This block has no special keys.
','Story Digests','default','en'); INSERT INTO `blocks` VALUES ('bars','||',NULL,'This block is used as a separator in the page title. It should be short and have no HTML tags in it. There are no special keys.
','General','default','en'); INSERT INTO `blocks` VALUES ('edit_ops','','1','This block is used to build the ops 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 op editing is not broken. This block recognizes the following special keys:
\nHey! You already have an account! I wouldn\'t worry about creating another. You must have arrived here in error. Please email %%local_email%% if you\'re having troubles with this site.
','1','This block is displayed if a logged-in user visits the user creation page. It should be a self-contained bit of HTML letting the user know that they can\'t create an account while logged in. There are no special keys.
','Accounts','default','en'); INSERT INTO `blocks` VALUES ('new_user_is_advertiser','You already have an account that is enabled for advertising. You must have arrived here in error. Please email %%local_email%% if you\'re having troubles with this site.
','1','This block is displayed if a logged-in advertiser visits the advertiser account creation page. It should be a self-contained bit of HTML letting the user know that they already have an advertiser account. This only applies if the site control req_extra_advertiser_info is set to 1. There are no special keys.
','Accounts','default','en'); INSERT INTO `blocks` VALUES ('newuser_confirm_page','You should soon receive an email at %%EMAIL%%. This email will contain instructions and a link to activate your account.
\r\nThanks for creating an account at %%SITENAME%%!
','1','This page is displayed when the user has successfully created an account and the email containing their password has been sent. It should be a self-contained bit of HTML telling the user to look for the email, and may contain any welcome message you like. The special keys recognised are:
\r\nNow that you\'ve submitted your ad, it has to be approved. Our crack team of site maintainers who pore over all of the ad submissions daily will notice yours has arrived, and approve it so that it can be displayed on the site. If for some reason they don\'t see fit to approve it, you will get an email sent to your real_email address explaining why.
\r\n%%AD_CC_PAY%%\r\n%%AD_PAYPAL_PAY%%\r\n%%AD_FREE_MESSAGE%%','1','This message is displayed when an advert has gone through all the stages of submission, apart from payment, and is waiting to be approved. If the advert needs paying for, then some more message will be displayed at the same time.\r\nIf the total cost of the advert is nothing, then |AD_FREE_MESSAGE| will be replaced by the contents of the block, ad_free_msg. AD_CC_PAY and AD_PAYPAL_PAY will be ignored.\r\nIf the site control ads_use_cc is enabled, then |AD_CC_PAY| will be replaced with the contents of the block ad_pay_cc_msg.\r\nIf the site control ads_use_paypal is enable, then |AD_PAYPAL_PAY| will be replaced with the contents of the block ad_pay_paypal_msg.\r\n','Ads','default','en'); INSERT INTO `blocks` VALUES ('ad_renewed_message','Thank you for renewing your advertisement. As it\'s already been approved, you don\'t have to wait. As soon as it\'s paid for, it will appear.
\r\n%%AD_CC_PAY%%\r\n%%AD_PAYPAL_PAY%%\r\n%%AD_FREE_MESSAGE%%','1','This message is displayed when an advert has gone through all the stages of renewal, apart from payment. As renewals don\'t need approving, the advert will appear as soon as it is paid for. If the advert needs paying for, then some more messages will be displayed at the same time.\r\nIf the total cost of the advert is nothing, then |AD_FREE_MESSAGE| will be replaced by the contents of the block, ad_free_msg. AD_CC_PAY and AD_PAYPAL_PAY will be ignored.\r\nIf the site control ads_use_cc is enabled, then |AD_CC_PAY| will be replaced with the contents of the block ad_pay_cc_msg.\r\nIf the site control ads_use_paypal is enable, then |AD_PAYPAL_PAY| will be replaced with the contents of the block ad_pay_paypal_msg.\r\n','Ads','default','en'); INSERT INTO `blocks` VALUES ('ad_pay_cc_msg','%%norm_font%%
Pay with Visa or Mastercard%%norm_font_end%%
%%norm_font%%
Pay with Paypal%%norm_font_end%%
This ad is free, you don\'t have to pay for it.','1','This message is displayed as part of the advert submission process. See the block ad_submitted_message for more information on where it will appear.\r\nThere are two special variables concerned with this. |num_impressions| will be replaced by the number of impressions ordered.\r\n|price| will be replace by the total cost of the order.','Ads','default','en'); INSERT INTO `blocks` VALUES ('main_css','/* this makes IE6 not act retarded */\r\nh1, h2, h3, h4, h5, h6, p, div {\r\n position: relative;\r\n}\r\n/* main page stuff */\r\nBODY { background-color: #ffffff;\r\n color: #000000; }\r\n\r\n:link { color: #006699; }\r\n:visited { color: #003366; }\r\n\r\n#main { width: 100%;\r\n border-spacing: 7px; }\r\n\r\n#main TD { vertical-align: top; }\r\n\r\nH1 { background-color: %%title_bgcolor%%;\r\n font-size: 1.6em;\r\n padding: 3px;\r\n margin: 0px; }\r\n\r\n.advert { border: 1px solid #ff0000; }\r\n\r\n.loginform { text-align: right; }\r\n\r\n/* header and footer */\r\n\r\n#section_links { float: right;\r\n padding: 0.5em; }\r\n\r\n#footer { text-align: center; }\r\n\r\n#footer FORM { display: inline; \r\n vertical-align: top; }\r\n\r\n/* sidebar boxes */\r\n\r\n.box { border: 1px solid black;\r\n padding: 3px;\r\n margin-bottom: 8px; }\r\n\r\n.box H2 { background-color: %%box_title_bg%%;\r\n color: #ffffff;\r\n font-size: 1.2em;\r\n padding: 5px;\r\n margin: -3px;\r\n margin-bottom: 3px; }\r\n\r\n/* sections admin tool */\r\n/* this is because box_title_font is used in the code */\r\n/* and not in a DIV.box - this will be fixed in later */\r\n/* releases of Scoop as HTML is moved out of the code */\r\n\r\nTH H2 { color: #ffffff;\r\n font-size: 1em; }\r\n\r\nTD H2 { color: #ffffff;\r\n font-size: 1em; }\r\n\r\n/* story stuff */\r\n\r\n.story_title H2 { font-size: 1.2em;\r\n color: #000000;\r\n display: inline; }\r\n\r\n.story_summary { border-bottom: 1px dashed black;\r\n padding-top: 0.5em; }\r\n\r\n.story_body { padding-top: 0.5em; }\r\n\r\n.story_info { background-color: %%story_mod_bg%%;\r\n text-align: center; }\r\n\r\n#author_console { border: 1px solid #006699;\r\n background-color: %%story_mod_bg%% }\r\n\r\n#vote_console { border: 1px solid #006699;\r\n background-color: %%story_mod_bg%% }\r\n\r\n/* comment stuff */\r\n\r\n.commenthead { border: 1px solid #006699;\r\n background-color: %%comment_head_bg%%; }\r\n\r\n.editorialhead { border: 1px solid #FF0000;\r\n background-color: %%comment_head_bg%%; }\r\n\r\n\r\n/* misc css */\r\n\r\n.title { font-size: 1.2em;\r\n fint-weight: bold;\r\n }\r\n\r\n/* tag-cloud styles */\r\n\r\n.cloud li { list-style-type: none; display: inline; margin-right: 8px; }\r\n\r\n.cloud .tag-popularity-1 { font-size: 80%; }\r\n\r\n.cloud .tag-popularity-5 { font-size: 90%; }\r\n\r\n.cloud .tag-popularity-10 { font-size: 100%; }\r\n\r\n.cloud .tag-popularity-15 { font-size: 110%; }','1','
This block contains the CSS stylesheet for the site. It should be what you\'d expect to find in a .css file on the filesystem, except it recognizes the standard keys for interpolation. There are no special keys. This is sent to the client via the URL |rootdir|/css/main - any other stylesheets you create must also have _css at the end of their name if you want them accessible via the css op.
','CSS','default','en'); INSERT INTO `blocks` VALUES ('sub_paypal_finished','Thank you, your PayPal payment has been recieved.',NULL,'Message displayed in the body of the page after a user returns from making a paypal payment.','Ads,Subscriptions','default','en'); INSERT INTO `blocks` VALUES ('new_user_email_subject','Welcome to %%sitename%%','1','This block defines the subject line for the email sent to new accounts. It should be short and not have any HTML. Because this is an email it is not processed the way web pages are and the only key recognized is the special key sitename, which is replaced with the contents of the site control sitename
','Accounts,Emails','default','en'); INSERT INTO `blocks` VALUES ('new_user_email','Someone requested a new user account on %%url%%/\r\nand gave this email address as their contact.\r\n\r\nIf this was you, please use the following link to activate your account:\r\n\r\n %%url%%/activate/%%pass%%\r\n\r\n%%showprefs%%\r\nIf it wasn\'t you, please ignore this email. Our system will delete the\r\naccount automatically if it remains unused. You will not get any\r\nfurther e-mail from us. The account is free.\r\n\r\nWe hope you enjoy %%sitename%%!\r\n\r\n-- %%from%%','1','This block contains the body of the email send when new accounts are created. It should not have any HTML. Because this is an email it is not processed the way web pages are and the only keys recognized are:
\r\nThis block contains text that will be included in the block new_user_email if the site control show_prefs_on_first_login is set to 1. It should not have any HTML. Since emails are not sent through the usual page processing, this block cannot use any of the normal keys available to most blocks.
','Accounts,Emails','default','en'); INSERT INTO `blocks` VALUES ('email_error','Failed to send mail. It could be a problem with the address you entered, or with the server. Please double-check the email address you entered, make sure that it is receiving email, and if still fails, copy and paste the error message and send it to %%local_email%% for help. The error message is: \"%%error%%\".','1','This block is displayed when somebody attempts to create an account but the email sending process fails. The one special key recognised is error, which is whatever Mail::Sendmail returns as its error string.
','Emails,Accounts','default','en'); INSERT INTO `blocks` VALUES ('error_box','%%title%%
\n%%bid%%: %%content%%
\nThis 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. It provides the frame for the error message generated by any box that fails with a fatal error. The special keys recognised are:
\nThe message displayed inside the template error_box when a box fails with a fatal error. The actual error message generated will be printed to the site\'s error log. There are no special keys.
','Error Messages','default','en'); INSERT INTO `blocks` VALUES ('commentreply_display','This block lays out the comment post form. It recognises the following special keys:
\n%%norm_font%%You are not logged in. If you don\'t have a user account yet, by all means go make one! If you do have one, you can post as \"yourself\" by filling in your nickname and password below. Otherwise, your comment will be posted as %%anon_user_nick%%.%%norm_font_end%%
\r\n\r\n%%norm_font%%Create Account\r\n
Nickname: \r\n
Password: %%norm_font_end%%
This block contains the message and login form shown when an anonymous user tries to post a comment (if anonymous users can post comments). There are no special keys. The login form must have fields named \"uname\" and \"pass\".
','Comments','default','en'); INSERT INTO `blocks` VALUES ('comment_posted_display','%%comment_controls%%\r\nThis block lays out the comment display after the comment has been posted. The special keys are:
\nThis block lays out the comment post form. The following form elements are used:
\nThe following special keys are used:
\nThis is the \"Preview Comment\" title bar. Make sure it has an anchor named \"here\" in it. There are no special keys.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('spellcheck_form_item','%%norm_font%%Spellcheck text (will force \"Preview\"): %%norm_font_end%%','1','This is the form element displayed when spellcheck is available. There is one special key, checked, which makes the checkbox pre-checked or not, depending on user action or preferences.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('invalid_user_msg','Sorry, I can\'t seem to find that user','1','The error message displayed when somebody requests a page for a user that doesn\'t exist
','Accounts','default','en'); INSERT INTO `blocks` VALUES ('selectbox_pref','%%required%%%%title%%: %%control%%\r\n
%%description%%
The preference item template generally used for selectboxes. This should be a self-contained bit of HTML as it is used to display a single user preference, both on the user info page and the preferences edit forms. The following special keys are recognised:
\n%%required%%%%title%%: %%description%%\r\n
%%allowed_html%%\r\n
%%control%%
The preference item template generally used for text boxes. This should be a self-contained bit of HTML as it is used to display a single user preference, both on the user info page and the preferences edit forms. The following special keys are recognised:
\nNickname: \r\n
\r\nUser ID: %%uid%%
\r\nUser group: %%BOX,user_group_box,%%perm_group%%%%
\r\nOriginal Email: %%origemail%%
\r\nCreated At: %%creation_time%%
\r\nOriginal IP: %%creation_ip%%
\r\nUser\'s current mojo: %%mojo%%
\r\nThis block displays admin-only user info on the Protected user preference page. This should be a self-contained block of HTML. It is displayed just above the real email and password fields on the Protected user preference page for users with the edit_user perm only. The following special keys are recognised:
\nProtected settings\r\n%%passwd%%\r\n
Real Email: \r\n
This is the address that will be used to email forgotten passwords. It will not be shown anywhere. Please do not insert any kind of spam protection here, or you will not be able to get a new password!
New Password: Leave both fields blank for no change. This is asked twice to detect typos.\r\n
New Password: \r\n
Confirm: \r\n
This block displays the user portion of the Protected user preferences page. The following special keys are recognised:
\nThis block contains the content column template for the displayed user info page. It should be self-contained HTML and contain the page title (the title bar most pages have, just under the header). The following special keys are recognised:
\nThis block contains the content column template for the user preference edit pages. It should be self-contained HTML and contain the page title (the title bar most pages have, just under the header). The following special keys are recognised:
\nWelcome to %%sitename%%! As this is your first login, you probably want to change some of the settings on this and the other preference pages. None of these changes are required. Enjoy your stay.
\r\nIf you don\'t want to make any changes, you can go to the front page.
','1','This block is displayed at the top of the Protected settings page the first time a user logs in, if the variable show_prefs_on_first_login is on. It should be self-contained HTML that encourages the new user to change his password and explore the other preference pages. There are no special keys.
','Accounts','default','en'); INSERT INTO `blocks` VALUES ('formkey_err','Invalid form key. You probably tried to save your settings more than once. Do not hit \"BACK\"! If you are certain that your settings have not been saved, try to save them from this screen.','1','The error message displayed if there is a formkey error, such as a user double-clicking a button or going too long between loading the form and submitting it.
','Accounts','default','en'); INSERT INTO `blocks` VALUES ('edit_prefs','%%title_font%%Edit User Preferences%%title_font_end%%\r\n\r\n%%err_font%%%%update_msg%%%%err_font_end%%
\r\n\r\n\r\n','1','','Admin Pages','default','en'); INSERT INTO `blocks` VALUES ('userpref_reset','','1','This block contains the reset button for the userpref pages. The button must be named \"reset\" but you can otherwise change how it looks.
','Accounts','default','en'); INSERT INTO `blocks` VALUES ('userpref_oldpass_field','You must enter your account password to change protected settings.\r\nThis block is the description and form element in which the user enters his old password to change protected settings. On the user\'s first login, the block userpref_oldpass_hidden is used instead.
','Accounts','default','en'); INSERT INTO `blocks` VALUES ('userpref_oldpass_hidden','','1','This block is the hidden form element containing the user\'s old password. It is only used on the user\'s first login; the block userpref_oldpass_field is used the rest of the time.
','Accounts','default','en'); INSERT INTO `blocks` VALUES ('required_pref_marker','*','1','','Accounts','default','en'); INSERT INTO `blocks` VALUES ('special_page_layout','| %%norm_font%%%%content%%%%norm_font_end%% | \r\n
This is the structure all pages created in the Special Pages admin tool are formatted with. The special keys are:
\n%%msg%%
\n\n| Calendar | \nOwner | \nActions | \n
|---|
This block creates the calendar list admin tool. This is inserted into the block admin_calendar_main when you are working specifically with the calendar list. The names of the form elements should not be changed. The following special keys are recognized:
\nThis block formats a single item of the calendar list admin tool. The following special keys are recognized:
\n| %%title_font%%Events and Calendars%%title_font_end%% | \n
Calendar List\n Event List\n Event Properties
\n\n%%calendar_form%%\n','1','This block is used to create the Calendars Admin Tool page. It should be self-contained HTML. The special keys recognised are:
\n%%error_font%%%%admin_events_errormsg%%%%error_font_end%%
\n%%prevlink%%
\n| Event | \nOrganizer | \nCalendar(s) | \n
|---|
%%nextlink%%
\n','1','This block is used to create the Event List for the Calendar Admin Tool.
\nThis block is used to format each row in the event list in the calendars admin tool. The following special keys are recognized:
\nAlso recognized are all valid event fields, including all built-in fields and all fields defined in Event Properties.
','Admin Pages','default','en'); INSERT INTO `blocks` VALUES ('admin_event_list_item_cals','%%primary_marker%% %%title%% [edit] %%owner_nick%%This block is used to format each calendar an event is included in, for the event list in the calendars admin tool. The special keys recognized are:
\nAlso recognized are all calendar properties and all event properties and event fields which do not share a name with a calendar property.
','Admin Pages','default','en'); INSERT INTO `blocks` VALUES ('admin_event_properties','\n','1','This block is used to create the Event Properties Admin Tool page. It must contain all of the form elements used in the Event Properties Admin page, and should be self-contained HTML. The special keys recognised are:
\nDo not change the names of the form elements, or remove any form elements, or event property editing may fail in unexpected ways.
','Admin Pages','default','en'); INSERT INTO `blocks` VALUES ('calendar_body_daily','| \r\n \r\n \r\n%%calendar_title%% - %%dow%% %%month%% %%day_num%%, %%year%% \r\n%%BOX,calendar_actions%%\r\n
|
\r\n
This block formats the body of the calendar in \"daily\" view. This should be a self-contained block of HTML that can be inserted anywhere. The following special keys are recognized:
\n| \r\n \r\n \r\n%%calendar_title%% - %%longdate%% \r\n%%BOX,calendar_actions%%\r\n
|
\r\n
| Monday | \r\nTuesday | \r\nWednesday | \r\nThursday | \r\nFriday | \r\nSaturday | \r\nSunday | \r\n\r\n |
|---|
This block formats the body of the calendar in \"monthly\" view. This should be a self-contained block of HTML that can be inserted anywhere. The following special keys are recognized:
\n| M | \r\nT | \r\nW | \r\nT | \r\nF | \r\nS | \r\nS | \r\n
|---|---|---|---|---|---|---|
This block formats the body of the mini monthly calendar on the front page. This should be a self-contained block of HTML that can be inserted anywhere. The following special keys are recognized:
\nThis block formats the inside of a single day from either calendar_body_monthly, calendar_body_weekly, or calendar_body_daily. By default it is a single table cell, so all three of the calendar templates must treat it as such and encapsulate it in the appropriate table structure. The following special keys are recognized:
\n| \r\n \r\n \r\n%%calendar_title%% - Week starting %%dow%% %%month%% %%day_num%%, %%year%% \r\n%%BOX,calendar_actions%%\r\n
|
\r\n\r\n\r\n
| Monday | \r\nTuesday | \r\nWednesday | \r\nThursday | \r\nFriday | \r\nSaturday | \r\nSunday | \r\n
|---|---|---|---|---|---|---|
This block formats the body of the calendar in \"weekly\" view. This should be a self-contained block of HTML that can be inserted anywhere. The following special keys are recognized:
\nSorry, the calendar you requested either doesn\'t exist or is private. Your personal calendar view.
','1','This is the error message displayed when a user requests a calendar that either doesn\'t exist or which they don\'t have permission to see.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('calendar_invitations','%%title_font%%Invite users%%title_font_end%%\r\n\r\n%%edit_calendar_links%%\r\n\r\n%%msg%%
\r\n\r\nUsers invited to view this calendar
\r\n\r\nUsers invited to submit events to this calendar
\r\n\r\nThis block formats the page where a calendar owner manages the invitation lists for their calendar. The following special keys are recognized:
\nThis block contains the form used in the block calendar_invitations and event_invitations to add to either list available in those two pages. The special keys recognized are:
\nThis block formats a single item in either list in either calendar or event invitation management. The special keys recognized are:
\nThe text placed in calendar_navigation_item to indicate the currently selected calendar date. By default this is an HTML id property for use with CSS, but it can be anything.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('calendar_navigation_item','This block formats a single item in the calendar navigation bar. By default it is a single list item, so the block calendar_header must contain the appropriate list start and end HTML. The following special keys are recognized:
\nThe text placed in calendar_body_one_day to indicate days which are outside the range being displayed. This is only used in the monthly view, to fill in the grid. By default this is an HTML id property for use with CSS, but it can be anything.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('calendar_settings','%%title_font%%%%pagetitle%%%%title_font_end%%\r\n\r\n%%edit_calendar_links%%\r\n\r\nThis block is the form used to edit a particular calendar. The special keys recognized are:
\nThis is one item in the list of calendars we can subscribe to. It is shown in the personal calendar view. If this is a list item, the block calendar_subscribe_multi_form must contain the list start and end tags. The following special keys are recognized:
\nThis block is the subscribe link shown underneath a calendar to which the user is not currently subscribed, if the site control allow_personal_calendar_view is on. The special keys recognized are:
\nCalendars in your personal calendar view:
\r\n
This is the framework for the calendar subscription form shown underneath the personal calendar view, if the site control allow_personal_calendar_view is on. The special keys recognized are:
\nThe text placed in calendar_body_one_day to indicate today. By default this is an HTML id property for use with CSS, but it can be anything.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('calendar_unsubscribe_link','Unsubscribe from this calendar
','1','This block is the unsubscribe link shown underneath a calendar to which the user is currently subscribed, if the site control allow_personal_calendar_view is on. The special keys recognized are:
\nThis is the menu at the top of the calendar edit page which links to the other pages available through the calendar edit form. The only special key recognized is cal_id, the ID number of the calendar being edited.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event','%%title_font%%%%title%%%%title_font_end%%\r\n\r\n%%description%%
\r\nOrganizer: %%owner_nick%%
\r\nDate: %%date_start%%
Calendar: %%calendar_title%%
\r\n%%deadline%%\r\n%%address%%\r\n%%City%%\r\n%%state%%\r\n%%country%%\r\n%%rsvp%%\r\n%%edit_link%% %%add_cal_link%% %%add_child_link%% %%event_sub_link%% %%add_story_link%%
\r\nThis block formats the page when viewing a single event in full detail. This should be a fully self-contained block of HTML. The special keys recognized are any defined event property name. Each one is replaced with the value of that property, formatted according to the template defined for that event property. If no template is defined, the value alone is used.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_add_child_link','[Add a sub-event]','1','This is the link shown on the event page when the event displayed is a parent event and may have sub-events added, and the user viewing the event has permission to submit an event. The only special key recognized is eid, the current event\'s ID number.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_add_story_link','[Write a story]','1','This is the link displayed when the current user has permission to submit a story to the event being displayed. The only special key recognized is eid, the current event\'s event ID number.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_also_submit',' %%cal_title%%This is a single item in the list of alternate calendars to submit an event to, on the event edit form. The following special keys are recognized:
\nLocal events:
\r\nThis sets up the list of child events (or sub-events) on the display of a parent event. The only special key is child_list, which is built from one copy of event_child_list_item per child event.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_child_list_item','This is one item in the list of child events (or sub-events) for a parent event. The special keys recognized are any defined event property.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_edit_displaystatus','','1','This is the displaystatus selectbox shown on the event edit form to those users who have admin permissions for an event. The special keys recognized are the three *_selected keys, which show which option is currently set for the event being displayed.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_edit_form','%%title_font%%Edit Event%%title_font_end%%\r\n%%msg%%
\r\n','1','This block builds the single event edit and submit form. The special keys recognized are:
\nSorry, the event you requested either doesn\'t exist or is private. Your personal calendar view.
','1','This is the error message displayed in place of the event body if the event requested is not viewable either because it doesn\'t exist or because the user doesn\'t have permission to see it.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_error_title','No Such Event','1','This is the title used for the page if the event requested is not viewable either because it doesn\'t exist or because the user doesn\'t have permission to see it.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_format_daily','%%title%%\r\n%%description%%\r\n%%deadline%%','1','This block formats a single event for use in calendar_body_one_day for the daily view. Zero, one, or more copies of this block may be displayed in a single day. The special keys recognized are any defined event property name. Each one is replaced with the value of that property, formatted according to the calendar_template defined for that event property. If no calendar_template is defined, the value alone is used.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_format_monthly','%%title%%','1','This block formats a single event for use in calendar_body_one_day for the monthly view. Zero, one, or more copies of this block may be displayed in a single day. The special keys recognized are any defined event property name. Each one is replaced with the value of that property, formatted according to the calendar_template defined for that event property. If no calendar_template is defined, the value alone is used.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_format_weekly','%%title%%\r\n%%description%%','1','This block formats a single event for use in calendar_body_one_day for the weekly view. Zero, one, or more copies of this block may be displayed in a single day. The special keys recognized are any defined event property name. Each one is replaced with the value of that property, formatted according to the calendar_template defined for that event property. If no calendar_template is defined, the value alone is used.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_invitation_link',' Invite users to view this event','1','This is the link to the event invitation management page. It is placed in event_edit_form for existing events.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_invitations','%%title_font%%Invite users%%title_font_end%%\r\n\r\n%%msg%%
\r\n\r\nUsers invited to view this event
\r\n\r\nUsers invited to attach stories to this event
\r\nThis block formats the event invitation management page. The following special keys are used:
\nThis is the email sent to users invited to view a particular event. It is sent to the real email address of the invitee. Because this is an email and not a regular Scoop page, only the special keys listed below will work.
\nAny defined event property may also be used.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_invite_mail_subject','You\'re invited!','1','The subject line for the email sent when a user is invited to attend (view) an event. Because this is used in an email and does not go through Scoop\'s usual page out process, no regular keys may be used. There are no special keys for this block.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_list','%%title_font%%Events in %%title%%%%title_font_end%%\r\n\r\n%%edit_calendar_links%%\r\n\r\n%%msg%%
\r\n\r\n%%prevlink%%
\r\n| Event | \r\nSubmitted By | \r\nStart Date | \r\nActions | \r\n
|---|
%%nextlink%%
','1','This is the structure of the event list page. By default, it creates a table, and event_list_item contains each row of the table\'s data. The number of columns and associated headings should match the structure and data in event_list_item. The following special keys are recognized:
\nThis is the link used in the event list to a calendar\'s event moderation page, where events can be approved or disapproved for inclusion in a calendar. The only special key is cal_id, the ID number of the calendar currently being edited.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_list_action_edit',' (edit)','1','This is the link used in the event list to the event\'s edit form. The only special key is eid, the event\'s ID number.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_list_action_remove','(remove)','1','This is the link used to remove an event from the calendar being edited, if this is a \"secondary\" calendar for the event (the \"also show this event in...\" item on the event edit form)
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_list_item','This is one line (one event) in the event list page. It should have the same number of columns as the table in the block event_list, and its data should match the table headers. The following special keys are recognized:
\n%%msg%%
\r\n\r\n','1','This provides the page structure for the event moderation. The following special keys are recognized:
\nThis formats each item in the event moderation list. The structure must match the structure set out in the block event_moderate. The following special keys are recognized:
\nThis is the portion of the event edit form that displays checkboxes for each calendar the user can submit the event to, excluding the one the event is primarily submitted to. The only special key is also_submit, which is replaced with the actual checkboxes
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_parent_item','','1','This is the link back to the parent event, shown if the event currently displayed is actually a child event (sub-event). The only special key is eid, the parent event\'s ID
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_parent_line','This is the part of the event edit form that sets whether or not an event is a \"parent\" event or not. The only special key recognized is is_parent, a checkbox checked indicator used for the current status of the event.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_property_date','This block formats any date event properties on the submit/edit event form. It should be one item in the structure defined in event_edit_form. The following special keys are recognized:
\nThis block formats any plain text format event properties on the submit/edit event form. It should be one item in the structure defined in event_edit_form. The following special keys are recognized:
\nThis block formats any textarea format event properties on the submit/edit event form. It should be one item in the structure defined in event_edit_form. The following special keys are recognized:
\nThis is the message displayed when a new event has been submitted. It should provide useful links to things the user might want to do after submitting an event. The following special keys are recognized:
\nAny fields left blank will not be used in the search.
\r\n\r\n\r\n','1','This is the page for event searching. The following special keys are recognized:
\nThis formats one event property form element in the event search form. The special keys are:
\n%%title%% (%%date_start%%)
\r\n%%description%%
This formats one event search result. It should be HTML suitable for repeating an arbitrary number of times.
\nThe special keys are any defined event property.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_submit','%%title_font%%Submit an Event%%title_font_end%%\r\n\r\n','1','The page title for event submission
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_subscribe_link','[Notify me of changes to this event]\r\n','1','This is the link displayed on the event display page when the current user is not subscribed to the event being viewed. The only special key is eid, the event ID number.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('event_unsubscribe_link','[Stop notifying me of changes to this event]\r\n','1','This is the link displayed on the event display page when the current user is already subscribed to the event being viewed. The only special key is eid, the event ID number.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('month_link_up','This block is the link used in weekly and daily calendar views to allow the user to move back up to monthly view. The following special keys are recognized:
\nThe title used when in a user\'s personal calendar view. The special key nick is replaced with the user\'s nickname.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('primary_calendar_marker','*','1','The text used to indicate that a calendar is the event\'s primary calendar in the admin event list.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('rsvp_form','','1','The form shown on the event display page for users who have not yet replied via this form for RSVP. The special keys are:
\n%%number%% people signed up.
\r\nThis is displayed in place of the RSVP form for the event owner, so the number and names of people signed up (and volunteering) can be easily seen. The special keys are:
\nThis is one item in the list of people who have indicated that they are coming via the RSVP form. It is used in the block rsvp_list. The special keys are:
\nYou have indicated that you\'re coming to this event
','1','This is shown in place of the RSVP form when a user has submitted that form.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('rsvp_volunteer_email','%%owner_nick%%:\r\n\r\n%%volunteer_nick%% has just volunteered to help out at the \r\nevent %%title%%.\r\n<%%url%%>\r\n\r\n%%volunteer_nick%% can be reached at %%volunteer_email%%\r\n\r\n-- %%sitename%%','1','This is the text of the email sent to an event owner when somebody uses the RSVP form and indicates that they wish to volunteer. Because this is an email and does not go through the same processing as a normal Scoop page, only the keys listed below may be used. The following special keys are used:
\nAny defined event property may also be used.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('rsvp_volunteer_form','This is the portion of the RSVP form displayed when the event owner has indicated that volunteers would be appreciated. Since the system emails the volunteer\'s realemail to the event owner, and the realemail is generally considered secret information, a notice informing the user of this is strongly recommended.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('story_event_link','Attached to event %%title%%\r\n','1','This is the text placed in the story_summary block if the story is attached to an event. Any defined event property may be used.
','Calendars and Events','default','en'); INSERT INTO `blocks` VALUES ('week_link_up','This block is the link used in the daily calendar view to allow the user to move back up to weekly view. The following special keys are recognized:
\nThe link to remove a comment (replace with a placeholder indicating that the comment has been deleted), if the user has the comment_remove perm. Special keys sid and cid identify the comment.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('comment_delete_link',' (delete)','1','The link to delete a comment (remove entirely and make replies to this comment become replies to this comment\'s parent), if the user has the comment_delete perm. Special keys sid and cid identify the comment.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('comment_toggle_link',' (toggle)','1','The link to toggle a comment between topical and editorial, if the user has the comment_toggle perm. Special keys sid and cid identify the comment, and toggle sets the type (topical or editorial).
','Comments','default','en'); INSERT INTO `blocks` VALUES ('removed_comment_body','This comment has been deleted by %%nick%%
','1','The body of a removed comment. One special key, nick, contains the nickname of the admin who removed the comment. If you have jokers on your site who may claim that their comments have been wiped, I recommend putting something in this block that users can normally not put in their comments, as an \"authenticity\" marker.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('removed_comment_subject','(Comment Deleted)','1','The subject of a removed comment. One special key, nick, contains the nickname of the admin who removed the comment.
','Comments','default','en'); INSERT INTO `blocks` VALUES ('submit_page_title','Submit Story','1','','','default','en'); INSERT INTO `blocks` VALUES ('story_list_title','Story List','1','','','default','en'); INSERT INTO `blocks` VALUES ('archive_list_title','Archived Stories','1','','','default','en'); INSERT INTO `blocks` VALUES ('pending_list_title','Pending Stories','1','','','default','en'); INSERT INTO `blocks` VALUES ('poll_form_multi',' Allow multiple selections in poll','1','Allow multiple choice portion of the poll edit form. Included if var \"allow_multiple_choice\" is on.','Polls','default','en'); INSERT INTO `blocks` VALUES ('poll_form_question','%%last_update%%\r\n%%attached_to%%\r\n%%current%%\r\n%%hidden_form_input%%\r\n%%multiple_choice%%\r\n\r\nPoll Question:
\r\n
\r\nPoll Answers:
\r\n\r\n','1','','Polls','default','en');
INSERT INTO `blocks` VALUES ('edit_story_archive_success','
| %%norm_font%%Story archived.%%norm_font_end%% |
| %%norm_font%%Could not archive story.%%norm_font_end%% |
| %%norm_font%%Story deleted.%%norm_font_end%% |
\r\n%%edit_form%%','1','','Admin Pages','default','en'); INSERT INTO `blocks` VALUES ('story_edit_spellcheck','
| \n %%smallfont%%%%last%%%%sep%%%%next%%%%smallfont_end%%\n | \n
This provides the overall layout for the story navigation bar which links to the previous and next stories at the bottom of the story text and should be a self-contained block of HTML. This navigation bar can be turned off entirely using the Site Control disable_story_navbar. The special keys are:
\nThis displays the number of comments attached to a story listed in the story navigation bar, if the current user can read comments in the story\'s section. The special key num is replaced with the number of comments in the relevant story.','Stories','default','en'); INSERT INTO `blocks` VALUES ('navbar_last','< %%title%% %%comments%%','1','
This formats the \"last story\" entry in the story navigation bar. The special keys are:
\nThis formats the \"next story\" entry in the story navigation bar. The special keys are:
\nThis is the divider used to separate the \"next\" and \"last\" stories in the story navigation bar, if both have an entry. (The most recent story, for example, will only have a \"last\" entry, as there is no \"next\" story yet.) There are no special keys.
','Stories','default','en'); INSERT INTO `blocks` VALUES ('story_already_post_msg','This story has already been posted. It must have gone up while you were voting. Thanks for your vote anyway!
','1','This message is displayed when a user has just voted on a story that was posted after they started reading it but before they voted. There are no special keys.
','Stories','default','en'); INSERT INTO `blocks` VALUES ('story_post_message','You\'re the straw that broke the camel\'s back!
Your vote put this story over the threshold, and it should now appear on the %%where%% page. Enjoy!
This message is displayed when a user has just voted on a story and that vote caused the story to reach the post threshold. The special key where is replaced by either \"front\" or \"section\", depending on how the votes were cast.
','Stories','default','en'); INSERT INTO `blocks` VALUES ('story_dumped_message','You were the last vote, and the voters have decided that this story will be hidden. Thank you for voting.
','1','This message is displayed when a user has just voted and that vote caused the story to reach the hide threshold. There are no special keys.
','Stories','default','en'); INSERT INTO `blocks` VALUES ('story_autopost_message','You were the last vote. We\'ve considered the votes and comments, and decided the story should be %%status%%. Thank you!
','1','This message is displayed when a user has just voted and the auto-post calculations have been triggered. The special key status will contain either \"posted\" or \"hidden\", depending on the auto-post calculation results.','Stories','default','en'); INSERT INTO `blocks` VALUES ('story_spam_vote_msg','
Your vote was recorded for consideration.
','1','This message is displayed when a user has pressed the \"Spam\" button on a story in the edit queue. There are no special keys.
','Stories','default','en'); INSERT INTO `blocks` VALUES ('story_vote_msg','Your vote (%%vote%%) was recorded.
This story currently has a total score of %%curr_score%%.
This message is displayed when a user votes on a story. There are two special keys:
\nYour entry has been automatically posted
','1','This block is displayed below the story body when it has been auto-posted. It should be self-contained HTML.
','Stories','default','en'); INSERT INTO `blocks` VALUES ('story_edit_tags','\r\nSpecial keys:\r\n
\r\nSpecial keys:\r\n
\r\nSpecial keys:\r\n
Hey, you didn\'t read the rules! You have too much text in the introtext box. Please edit your submission accordingly and use the bodytext box for the bulk of your diary.
','1','A warning message for users who have too much stuff in their intro.','Stories','default','en'); INSERT INTO `blocks` VALUES ('min_intro_warning','Sorry, your story/diary is not long enough. Please edit it so it has more content.
\r\n\r\nThe minumum is __MININTRO__ __UNIT__.','1','','Stories','default','en'); INSERT INTO `blocks` VALUES ('comment_ip_display','From: %%ip%%','19','Format for the IP display/link attached to comments. \r\n\r\nSpecial keys:\r\n
| %%norm_font%%%%text%% %%norm_font_end%% | \r\n','1','','Comments','default','en');
INSERT INTO `blocks` VALUES ('delimiter_dyn_end',' ','1','','Comments','default','en');
INSERT INTO `blocks` VALUES ('delimiter_dyn_itemend',' |
','19','Formatting for an item in a comment search result list.\r\n
\r\nSpecial keys:\r\n
| \r\n \r\n %%scoop_intro%%\r\n \r\n | \r\n \r\n\r\n \r\n\r\n %%BOX,section_title%%\r\n %%BOX,tag_sort_change%%\r\n %%CONTENT%%\r\n | \r\n \r\n\r\n \r\n\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 | \r\n \r\n\r\n
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:
\r\n\r\nKeys:\r\n
\r\nKeys:\r\n
\r\nKeys:\r\n
\r\nKeys: \r\n
\r\n $story->{ftime}|;\r\n }\r\n $box_content .= qq|\r\n
%%dot%% {sid}\">$story->{title} ($story->{commentcount} comments)|;\r\n \r\n if ($S->have_perm(\'story_list\')) {\r\n $box_content .= qq| [{sid}\">edit]|;\r\n }\r\n}\r\n\r\nmy $offset = $S->{UI}->{VARS}->{maxstories} + $#{$stories};\r\nmy $search_url = qq{%%rootdir%%/?op=search;offset=$offset};\r\n$search_url .= \';section=\'.$section if ($section ne \'front\');\r\n\r\n$box_content .= qq|\r\n
\r\n Older Stories...\r\n
|;\r\nmy $return = {content => \"%%smallfont%%$box_content%%smallfont_end%%\"};\r\nif ($section ne \'front\' && $section ne \'__all__\') {\r\n $return->{title} = $S->{SECTION_DATA}->{$section}->{title};\r\n} elsif ($section eq \'__all__\') {\r\n $return->{title} = \'All Stories\';\r\n}\r\n\r\nreturn $return;','\"Older stories\" list','box',0); INSERT INTO `box` VALUES ('fortune_box','Inspiration','my $content = `/usr/games/fortune -s`;\r\n$content =~ s/\\n\\s+-/%%norm_font_end%%<\\/I><\\/TD><\\/TR>\r\n %%norm_font%%\r\n
| %%norm_font%%Results%%norm_font_end%% | \r\n%%norm_font%%|%%norm_font_end%% | \r\n%%norm_font%% Other Polls%%norm_font_end%% | %%norm_font%%{\'qid\'}\">Results%%norm_font_end%% | \r\n%%norm_font%%|%%norm_font_end%% | \r\n%%norm_font%% Other Polls%%norm_font_end%% | \r\n };\r\n}\r\n\r\n$poll_form .= qq{\r\n
| %%norm_font%%{uid}\">$user->{nickname}%%norm_font_end%% | \r\n%%norm_font%%$rating->{rating}%%norm_font_end%% | \r\n
| %%norm_font%%Zero $word: $zeros%%norm_font_end%% | \r\n|
\r\n\r\n
\r\n\r\n|;\r\n\r\nreturn $form;\r\n\r\n}\r\n\r\n','Box to do submitrdf op and such.','titled_box',0); INSERT INTO `box` VALUES ('whos_online','Who\'s online','## New Who\'s Online Box\n## Quite a bit of stuff borrowed from the old one.\n\n# return if anonymous for now\nreturn if $S->{UID} == -1;\n\n# The time stuff can be changed to taste\n\n# The query\n\nmy ($rv,$sth) = $S->db_select({\n FROM => \'whos_online\',\n WHAT => \'ip, uid\',\n WHERE => \'last_visit > DATE_SUB(NOW(), INTERVAL 30 MINUTE)\',\n ORDER_BY => \'uid\'\n});\n\nmy %uids;\nmy $total;\nmy $anontotal;\n\nwhile (my $s = $sth->fetchrow_hashref()) {\n if ($s->{\'uid\'} == -1) {\n $anontotal++;\n next;\n }\n $total++;\n $uids{ $s->{\'uid\'} }++;\n}\n\n$sth->finish;\n\nmy @sorted = sort keys %uids;\n\nmy $out;\nmy $hidden;\nforeach (@sorted) {\n if ($S->user_data($_)->{prefs}->{online_cloak} eq \'on\') {\n $hidden++;\n next;\n }\n my $nick = $S->user_data($_)->{nickname};\n $out .= qq~%%dot%% $nick~;\n $out .= \" ($uids{$_})\" if $uids{$_} > 1;\n $out .= \"~;\n} else {\n $out .= \'
\';\n}\n$total = $total + $anontotal;\n$out .= qq~Note: You may cloak yourself from appearing here in your Display Preferences.~;\nreturn {content => $out, title => \"Who\'s Online? ($total)\"};\n','','box',1);
INSERT INTO `box` VALUES ('show_ad','Show Advertisement','my $arg0 = $ARGS[0];\r\nmy $arg1 = $ARGS[1];\r\nmy $ad_id;\r\nmy $adhash = {};\r\nmy $content = \'\';\r\n\r\n# if the ad_id is in the url, use the url\r\nif( $arg0 eq \'fromurl\' || $arg0 eq \'allcgi\' ) {\r\n $ad_id = $S->{CGI}->param(\'ad_id\');\r\n\r\n# if they want to see what the fields are...\r\n} elsif( $arg0 eq \'showfields\' ){\r\n\r\n my $ex_ad = $S->get_example_ad($arg1);\r\n return \'\' unless( defined($ex_ad) && (ref($ex_ad) eq \'HASH\') );\r\n\r\n if( exists $S->{UI}->{BLOCKS}->{\"preview_\" . $ex_ad->{ad_tmpl}} ) {\r\n $content = $S->{UI}->{BLOCKS}->{ \"preview_\". $ex_ad->{ad_tmpl} };\r\n } else {\r\n $content = $S->{UI}->{BLOCKS}->{ $ex_ad->{ad_tmpl} };\r\n }\r\n\r\n $content =~ s/%%FILE_PATH%%//g;\r\n $content =~ s/%%TEXT1%%/This is text1/g;\r\n $content =~ s/%%TEXT2%%/This is text2/g;\r\n $content =~ s/%%TITLE%%/This is the title/g;\r\n $content =~ s/%%LINK_URL%%/This is the link url/g;\r\n $content =~ s[%%REDIRECT_URL%%][%%rootdir%%]g;\r\n\r\n return { content => $content };\r\n\r\n# else if ad_id is specified in template, use that\r\n} elsif( $arg0 =~ /\\d/ ) {\r\n $ad_id = $arg0;\r\n}\r\n\r\nunless( defined( $ad_id ) || $arg0 eq \'allcgi\' ) {\r\n return \'\';\r\n}\r\n\r\n# if we need everything from cgi, let get_ad_hash know\r\nmy $source = \'db\';\r\n$source = \'cgi\' if( $arg0 eq \'allcgi\' );\r\n\r\n$adhash = $S->get_ad_hash($ad_id, $source);\r\n\r\nmy $image = $adhash->{ad_file};\r\nmy $subdir = $adhash->{sponsor};\r\n$subdir = \'example\' if( $adhash->{example} == 1 );\r\n\r\nmy $image_path = $subdir . \'/\' . $image;\r\n\r\nif( exists $S->{UI}->{BLOCKS}->{\"preview_\" . $adhash->{ad_tmpl}} ) {\r\n $content = $S->{UI}->{BLOCKS}->{ \"preview_\". $adhash->{ad_tmpl} };\r\n} else {\r\n $content = $S->{UI}->{BLOCKS}->{ $adhash->{ad_tmpl} };\r\n}\r\n\r\n$content =~ s/%%FILE_PATH%%/$image_path/g;\r\n$content =~ s/%%TEXT1%%/$adhash->{ad_text1}/g;\r\n$content =~ s/%%TEXT2%%/$adhash->{ad_text2}/g;\r\n$content =~ s/%%TITLE%%/$adhash->{ad_title}/g;\r\n$content =~ s/%%LINK_URL%%/$adhash->{ad_url}/g;\r\n$content =~ s/%%SID%%/$adhash->{ad_sid}/g;\r\n$content =~ s[%%REDIRECT_URL%%][%%rootdir%%/redirect/$ad_id]g;\r\n\r\nreturn { content => $content };\r\n','Just a simple box that will show the ad specified','box',0);
INSERT INTO `box` VALUES ('ad_box','Advertisement','return \'\' if( $S->pref(\'showad\') eq \'off\' );\nreturn \'\' unless( $S->{UI}->{VARS}->{use_ads} );\r\n\r\nmy $adhash = $S->get_next_ad();\r\nreturn \'\' unless( $adhash->{ERROR} != 1 );\r\n\r\nmy $content = $S->{UI}->{BLOCKS}->{$adhash->{ad_tmpl}};\r\n\r\nmy $subdir = ($adhash->{example} == 1) ? \'example\' : $adhash->{sponsor};\nmy $file_path = $subdir . \'/\' . $adhash->{ad_file};\n\n$content =~ s/%%LINK_URL%%/$adhash->{ad_url}/g;\r\n$content =~ s/%%TITLE%%/$adhash->{ad_title}/g;\r\n$content =~ s/%%TEXT1%%/$adhash->{ad_text1}/g;\r\n$content =~ s/%%TEXT2%%/$adhash->{ad_text2}/g;\r\n$content =~ s/%%FILE_PATH%%/$file_path/g;\r\n$content =~ s/%%SID%%/$adhash->{ad_sid}/g;\r\n$content =~ s[%%REDIRECT_URL%%][%%rootdir%%/redirect/$adhash->{ad_id}];\r\n\r\nif( $S->pref(\'ad_open_new_win\') eq \'on\' ) {\r\n $content =~ s/%%TARGET%%/target=\"_blank\"/g;\r\n}\r\n\r\nreturn { content => $content };\r\n','Simple ad box for the side of the page','box',0);
INSERT INTO `box` VALUES ('ad_types','Advertisement Type Listing','my $content = $S->make_ad_type_list(\'no_choice\');\r\n\r\nreturn { content => $content };\r\n','Shows a list of all of the advertisement types','blank_box',0);
INSERT INTO `box` VALUES ('buyimpressions_box','Purchase Ad Impressions','# This box controls /ads\r\n# -> If no argument is given, assumes the user wants to purchase\r\n# more impressions.\r\n# -> If distribute=1 will bring up ad impression distribution\r\n# page.\r\n\r\nmy $content = \'\';\r\n\r\nmy $distribute = $S->cgi->param(\'distribute\');\r\n\r\nif( $distribute eq \'dist\' ) {\r\n $content = $S->ad_impression_distribute();\r\n}\r\nelse {\r\n $content = $S->purchase_impressions();\r\n}\r\n\r\nreturn { content => $content };\r\n','controls /ads. Displays either a form to distribute impressions between multiple ads, or to just buy impressions directly.','blank_box',0);
INSERT INTO `box` VALUES ('ad_story_format','Ad Story formatter','my $ad_id = $ARGS[0];\r\n\r\nmy $content = qq{\r\n%%BOX,show_ad,$ad_id%%\r\n};\r\n\r\nreturn { content => $content };','Use this to format the advertisments in the introtext of their stories.','blank_box',0);
INSERT INTO `box` VALUES ('section_title_subsections','null','my $content;\r\nmy $op = $S->{CGI}->param(\'op\');\r\nmy $section = $S->cgi->param(\'section\');\r\n\r\nif( $op eq \'section\' ) {\r\n return unless $S->have_section_perm(\'norm_read_stories\', $section);\n if( $S->{UI}->{VARS}->{enable_subsections} ) {\r\n\r\n my @paths = $S->section_paths($section);\r\n while( my $path = shift(@paths) ){\r\n\r\n $path =~ s/\\/?$section$//; # Remove if Current Section\r\n $path =~ s/([^\\/]+)/<\\/b>%%norm_font_end%%%%norm_font%%$S->{SECTION_DATA}->{$1}->{title}<\\/b>%%norm_font_end%%<\\/a>%%norm_font%%/g;\r\n $path =~ s/^<\\/b>%%norm_font_end%%//; # Clean Up After Ourselves\r\n $path = ($path) ? \"%%norm_font%%/%%norm_font_end%%$path\" : \'\';\r\n $content .= qq{%%norm_font%%Home%%norm_font_end%%$path%%norm_font%%/$S->{SECTION_DATA}->{$section}->{title}%%norm_font_end%% };\r\n if ($S->cgi->param(\'pay\')) {\r\n $content .= $S->cc_preview_order($price,$num);\r\n }\r\n\r\n my $p_form = $S->cc_make_person_form();\r\n my $c_form = $S->cc_make_card_form();\r\n\r\n $content .= qq{\r\n \r\n Please fill in the payment form below. Required fields are in red. When you are done, click \"Preview Order\". You will not be billed yet, and you will be able to change what you\'ve entered before confirming the order.\r\n \r\nYour purchase details are below. Click the Paypal button, and you will go to a page on Paypal where you will finish the payment process.\r\n
\\n};\r\n }\r\n $content=~s/<\\/br>$//;\r\n } else {\r\n $content = $S->{SECTION_DATA}->{$section}->{title} || \'All Stories\';\r\n $content = \"%%title_font%%$content%%title_font_end%%\";\r\n }\r\n}\r\nelse {\r\n $content = \'%%title_font%%Latest News%%title_font_end%%\';\r\n}\r\n\r\nreturn { content=>$content }\r\n','Display title of current section','blank_box',0);
INSERT INTO `box` VALUES ('renewad_box','Renew Advertisement','my $content = \'\';\r\nmy $err = \'\';\r\nmy $ad_id = $S->cgi->param(\'ad_id\') || 0;\r\nmy $confirm = $S->cgi->param(\'confirm\') || \'nope\';\r\nmy $purchase = $S->cgi->param(\'purchase\') || \'nope\';\r\nmy $cgi_amount = $S->cgi->param(\'amount\');\r\nmy $confirm_amt = $S->cgi->param(\'confirm_amt\') || \'1.11\'; # 1.11 so that it != $cgi_amount\r\n\r\n# first get the page set up\r\n$content = qq{\r\n};\r\n return { content => $content };\r\n}\r\n\r\nunless( $ad_hash->{sponsor} eq $S->{UID} ) {\r\n $content .= qq{ %%norm_font%% %%renew_ad_no_permission%% %%norm_font_end%% %%BOX,show_ad,$ad_id%% %%norm_font%% $err %%norm_font_end%% %%norm_font%% %%renew_ad_message%% %%norm_font_end%% %%norm_font%% Order Size: %%norm_font_end%% \r\n %%norm_font%% %%norm_font_end%% \r\n %%norm_font%% Minimum order size is $min_impressions impressions %%norm_font_end%% %%norm_font%% $confirm_msg %%norm_font_end%% %%norm_font%% $purchase_button
\r\n
\" if $DEBUG;\r\n push @{$orders}, {\'ad_id\' => $ad_id,\r\n \'orderID\' => $order_id,\r\n \'amount\' => $cost};\r\n}\r\n$sth->finish();\r\n\r\nif ($#{$orders} >= 0) { \r\n $err = $S->cc_bill_approved_ads($orders);\r\n}\r\n\r\n\r\nreturn $err;\r\n ','Post-auth CC orders','blank_box',0);
INSERT INTO `box` VALUES ('ad_pay_paypal','Pay using paypal','my $ad_id = $ARGS[0];\r\nmy $count = $ARGS[1];\r\nmy $content;\r\nmy $site = $S->{UI}->{VARS}->{site_url}.$S->{UI}->{VARS}->{rootdir};\r\nmy $secure_site = $S->{UI}->{VARS}->{secure_site_url}.$S->{UI}->{VARS}->{rootdir};\r\nmy $business_id = $S->{UI}->{VARS}->{paypal_business_id};\r\n\r\nunless ($ad_id) {\r\n return \"No ad id passed.\";\r\n}\r\n\r\nmy ($num, $price, $item);\r\nif ($count) {\r\n # Get total price\r\n my ($rv, $sth) = $S->db_select({\r\n WHAT => \'ad_types.cpm\',\r\n FROM => \'ad_info, ad_types\',\r\n WHERE => \"ad_info.ad_id = $ad_id AND ad_info.ad_tmpl = ad_types.type_template\"\r\n });\r\n my ($cpm) = $sth->fetchrow();\r\n $price = ($count/1000) * $cpm;\r\n $price = sprintf(\"%1.2f\", $price);\r\n $num = $count;\r\n $item = \"Ad Renewal\";\r\n} else {\r\n my ($rv, $sth) = $S->db_select({\r\n WHAT => \'purchase_size,purchase_price\',\r\n FROM => \'ad_info\',\r\n WHERE => \"ad_id=$ad_id\"});\r\n ($num, $price) = $sth->fetchrow();\r\n $sth->finish();\r\n $item = \"Advertisement\";\r\n}\r\n\r\nmy $finished = $S->cgi->param(\'finished\');\r\nmy $canceled = $S->cgi->param(\'canceled\');\r\n\r\nif ($finished) {\r\n my $content = $S->{UI}->{BLOCKS}->{paypal_finished}; \r\n return $content;\r\n} elsif ($canceled) {\r\n my $content = $S->{UI}->{BLOCKS}->{paypal_canceled};\r\n return $content;\r\n}\r\n\r\nmy $paypal_form = qq{\r\n};\r\n\r\n$content = qq{\r\nYour ad:
\r\n
\r\n
| \r\n ||||||
| %%norm_font%%\r\n$purchase_display%%norm_font_end%%};\r\n\r\nif ($price eq \'ERROR\') {\r\n $content .= qq{ |
Ok, now it\'s time for payment. Please select a payment type below.
\r\n%%norm_font_end%%\r\n};\n$content .= qq{![\"Pay](\"%%imagedir%%/paypal.gif\")
![\"We](\"%%imagedir%%/cclogos.gif\")
\r\nPlease fill in the payment form below. Required fields are in \r\nred. When you are done, click \"Preview Order\". \r\nYou will not be billed yet, and you will be able to change what you\'ve \r\nentered before confirming the order.\r\n
%%norm_font_end%%};\r\n\r\n#\'\r\n\r\nreturn $content;\r\n','Purchase a subscription with a credit card','blank_box',0); INSERT INTO `box` VALUES ('subpay_paypal','','my $content;\r\nmy $type = $ARGS[0];\r\nmy $months = $ARGS[1];\r\nmy $site = $S->{UI}->{VARS}->{site_url}.$S->{UI}->{VARS}->{rootdir};\r\nmy $secure_site = $S->{UI}->{VARS}->{secure_site_url}.$S->{UI}->{VARS}->{rootdir};\r\nmy $business_id = $S->{UI}->{VARS}->{paypal_business_id};\r\nmy $item = \'Subscription\';\r\n\r\nmy $type_data = $S->sub_get_type($type);\r\n\r\n# Bounds check the period\r\n$months = $type_data->{max_time} \r\n if (($type_data->{max_time}) && $months > $type_data->{max_time});\r\n\r\nmy ($price, $remaining) = $S->sub_calculate_purchase_cost($type, $months);\r\n\r\nmy $finished = $S->cgi->param(\'finished\');\r\nmy $canceled = $S->cgi->param(\'canceled\');\r\n\r\nif ($finished) {\r\n $content = $S->{UI}->{BLOCKS}->{sub_paypal_finished}; \r\n return $content;\r\n} elsif ($canceled) {\r\n $content = $S->{UI}->{BLOCKS}->{sub_paypal_canceled};\r\n return $content;\r\n}\r\n\r\nmy $paypal_form = qq{\r\n};\r\n\r\n$content = qq{\r\n%%norm_font%%\r\n$remaining\r\n\r\nClick the Paypal button, and you will go to a page on Paypal where you will finish the payment process.\r\n%%norm_font_end%%\r\n
\r\n
\r\n
| \r\n ||
| %%title_font%%Search Admin Tools%%title_font_end%% |
| $content |
You are not currently a subscriber. Why not become one?};\r\n}','','empty_box',0);
INSERT INTO `box` VALUES ('commentmode_overflow_pref','','my $choice = $ARGS[0];\r\n\r\nmy %choices = ( \"minimal\", \"Minimal\", \"threaded\", \"Threaded\", \"nested\", \"Nested\", \"flat\", \"Flat\", \"flat_unthread\", \"Flat (unthread)\" );\r\n\r\nif ( $S->var(\'allow_dynamic_comment_mode\') && $S->pref(\'dynamic_interface\') eq \'on\' ) {\r\n $choices{\'dminimal\'} = \"Dynamic Minimal\";\r\n $choices{\'dthreaded\'} = \"Dynamic Threaded\";\r\n} else {\r\n $choice =~ s/^d//;\r\n}\r\n\r\nmy $select = qq{\r\n };\r\n\r\nreturn $select;','','empty_box',0);
INSERT INTO `box` VALUES ('commentmode_pref','','my $choice = $ARGS[0];\r\n\r\nmy %choices = ( \"use_overflow\", \"Always use overflow mode\", \"minimal\", \"Minimal\", \"threaded\", \"Threaded\", \"nested\", \"Nested\", \"flat\", \"Flat\", \"flat_unthread\", \"Flat (unthreaded)\" );\r\n\r\nif ( $S->var(\'allow_dynamic_comment_mode\') && $S->pref(\'dynamic_interface\') eq \'on\' ) {\r\n $choices{\'dminimal\'} = \"Dynamic Minimal\";\r\n $choices{\'dthreaded\'} = \"Dynamic Threaded\";\r\n} else {\r\n $choice =~ s/^d//;\r\n}\r\n\r\nmy $select = qq{\r\n };\r\n\r\nreturn $select;','','empty_box',0);
INSERT INTO `box` VALUES ('cookie_expire_pref','','my $choice = $ARGS[0];\r\n\r\nmy %choices = ( \"3600\", \"1 hour\", \"86400\", \"1 day\", \"604800\", \"1 week\", \"1209600\", \"2 weeks\", \"2592000\", \"1 month (30 days)\", \"5184000\", \"2 months\" );\r\n\r\nmy $select = qq{\r\n };\r\n\r\nreturn $select;','','empty_box',0);
INSERT INTO `box` VALUES ('startpage_validation','','if ( $S->{SECTION_DATA}->{$ARGS[1]} || $ARGS[1] eq \'__main__\' || $ARGS[1] eq \'__all__\' ) {\r\n return \'\';\r\n} else {\r\n return \"Start Page not valid
\";\r\n}','validates the start page pref','empty_box',0);
INSERT INTO `box` VALUES ('cal_day_select','','my $day = $ARGS[0];\nmy $select;\n\n$select = qq{\n};\nforeach (1..31) {\n my $selected = ( $day == $_ ) ? \' SELECTED\' : \'\';\n $select .= qq{\n};\n}\n\nreturn $select;','The options in a selectbox for a day field. Does not include the
Tags $newtags added.
\";\r\n $newtags = \'\';\r\n # and if we\'ve added tags, we\'re heading\r\n # back to whence we came.\r\n my $url = $S->{UI}->{VARS}->{site_url} \r\n . $S->{UI}->{VARS}->{rootdir} . \"/\"\r\n . \"story/$sid\";\r\n $S->{APACHE}->headers_out->{\'Location\'} = $url;\r\n $S->{HEADERS_ONLY}=1;\r\n }\r\nmy $curtags = $S->tag_display($sid);\r\n$content = \"Current $curtags\" . $content;\r\n\r\nmy $tagform = qq~\r\n\r\n\'/\' characters are not allowed in tags, and will be converted to \'-\'.
\r\n~;\r\nreturn $content . $tagform;','','empty_box',0); INSERT INTO `box` VALUES ('tag_listing','','my $sid = $S->cgi->param(\'sid\');\r\nmy $tags = $S->tag_display($sid);\r\nmy $content = \"$tags\";\r\n# if we can post comments, we can tag.\r\nif($S->have_perm(\'comment_post\')){\r\n my $addlink = ($S->have_perm(\'edit_story_tags\')) ? qq~ :: Add/Edit Tags to this Story~ : qq~ :: Add Tags to this Story~;\r\n $content .= $addlink;\r\n }\r\nreturn $content;','','empty_box',0); INSERT INTO `box` VALUES ('tag_page_order','','my $switch = $S->cgi->param(\'switch\');\r\n\r\nif($S->{UID} > 0){\r\n $S->pref(\'tag_sort\', $switch); # nice and easy\r\n }\r\nelse { # not so easy\r\n $S->session(\'tag_sort\', $switch);\r\n }\r\nmy $url = $S->{UI}->{VARS}->{site_url} . \r\n $S->{UI}->{VARS}->{rootdir} . \"/\" \r\n . \"tag\";\r\n\r\n $S->{APACHE}->headers_out->{\'Location\'} = $url;\r\n$S->{HEADERS_ONLY}=1;\r\n\r\nreturn;','','empty_box',0); INSERT INTO `box` VALUES ('tag_sort_change','','# change the default ordering for the \"All Tags\"\r\n# page\r\n# don\'t display if we\'re not looking at the \"All\r\n# Tags\" page, though.\r\nreturn if $S->cgi->param(\'tag\');\r\n\r\nmy $switchto = ($S->pref(\'tag_sort\') eq \'alpha\') ? \"count\" : \"alpha\";\r\n# and if we\'re not logged in, it\'s slightly\r\n# different\r\nif($S->{UID} < 0){\r\n $switchto = ($S->session(\'tag_sort\') eq \'alpha\') ? \"count\" : \"alpha\";\r\n }\r\nmy $ordering = ($switchto eq \'alpha\') ? \'Alphabetical\' : \'Popularity\';\r\nmy $link = qq~$ordering.~;\r\n\r\n# a little complicated, but whatever\r\nmy $linktext = ($switchto eq \'alpha\') ? \"$admin_edit ${nick}\'s \";\r\n\r\n# user info pages\r\nif ( $tool eq \'info\' ) {\r\n $links .= qq{\r\n Info};\r\n $links .= qq{\r\n Comments};\r\n $links .= qq{\r\n Stories};\r\n\r\n if ( $S->{UI}->{VARS}->{use_diaries} ) {\r\n $links .= qq{\r\n Diary};\r\n }\r\n\r\n if ( $S->{UI}->{VARS}->{use_ratings} ) {\r\n $links .= qq{\r\n Ratings};\r\n }\r\nmy $udata = $S->user_data($S->param->{\'uid\'});\r\n# if ( $S->{UI}->{VARS}->{allow_uploads} ) {\r\nif($S->{UI}->{VARS}->{allow_uploads} && (($S->have_perm(\'view_user_files\') && $S->have_perm(\'upload_user\', $udata->{\'perm_group\'})) || $S->have_perm(\'upload_admin\')) ) {\r\n $links .= qq{\r\n Files};\r\n }\r\n\r\n if ( $S->{UI}->{VARS}->{use_ads} ) {\r\n $links .= qq{\r\n Ads};\r\n }\r\n\r\n $return = $links . \"
\";\r\n} elsif ( $edit && $tool eq \'prefs\' ) {\r\n my %editlinks;\r\n my ($rv, $sth) = $S->db_select({\r\n WHAT => \'page, perm_edit\',\r\n FROM => \'pref_items\',\r\n GROUP_BY => \'page\'\r\n });\r\n while (my $item = $sth->fetchrow_hashref()) {\r\n $editlinks{\"$item->{page}\"} = \"%%rootdir%%/user/$nick/prefs/$item->{page} $item->{perm_edit}\";\r\n }\r\n $sth->finish;\r\n $links .= qq{\r\n Email and Password};\r\n\r\n foreach my $item (sort {$b cmp $a} keys %editlinks) {\r\n my $c = 0;\r\n my ($rv2, $sth2) = $S->db_select({\r\n WHAT => \'perm_edit\',\r\n FROM => \'pref_items\',\r\n WHERE => \"page = \'$item\'\"\r\n });\r\n while(my $i = $sth2->fetchrow_hashref()) {\r\n $c++ if ($S->have_perm($i->{perm_edit}) || !$i->{perm_edit});\r\n }\r\n $sth2->finish;\r\n $links .= ($c) ? qq{\r\n $item} : \'\';\r\n }\r\n $return = $links . \"\";\r\n}\r\n\r\nreturn $return;\r\n','navigation for user pref pages','empty_box',0); INSERT INTO `box` VALUES ('rating_type_selectbox','','my $choice = $ARGS[0];\r\n\r\nmy %choices = ( \"dropdown\", \"Drop Down box\", \"radio\", \"Radio Buttons\" );\r\n\r\nmy $select = qq{\r\n };\r\n\r\nreturn $select;','Rating type select box for user preferences','empty_box',0); UNLOCK TABLES; /*!40000 ALTER TABLE `box` ENABLE KEYS */; -- -- Table structure for table `cache_time` -- DROP TABLE IF EXISTS `cache_time`; CREATE TABLE `cache_time` ( `resource` varchar(50) NOT NULL default '', `last_update` int(11) NOT NULL default '0', PRIMARY KEY (`resource`) ) TYPE=MyISAM; -- -- Dumping data for table `cache_time` -- /*!40000 ALTER TABLE `cache_time` DISABLE KEYS */; LOCK TABLES `cache_time` WRITE; INSERT INTO `cache_time` VALUES ('refresh_all',1106672422); INSERT INTO `cache_time` VALUES ('vars',1106672422); INSERT INTO `cache_time` VALUES ('boxes',1106671895); INSERT INTO `cache_time` VALUES ('ops',1106671862); INSERT INTO `cache_time` VALUES ('blocks_default',1106671754); INSERT INTO `cache_time` VALUES ('macros',1087408229); INSERT INTO `cache_time` VALUES ('topics',1078970419); INSERT INTO `cache_time` VALUES ('sections',1078970419); INSERT INTO `cache_time` VALUES ('admin_tools',1078970419); INSERT INTO `cache_time` VALUES ('hooks',1078970419); INSERT INTO `cache_time` VALUES ('2000/8/27/224648/707_comments',1079152774); INSERT INTO `cache_time` VALUES ('2000/8/27/224648/707_mod',1079153501); INSERT INTO `cache_time` VALUES ('967438565_opsmxIVg_comments',1079131129); INSERT INTO `cache_time` VALUES ('preview_comments',1079158582); INSERT INTO `cache_time` VALUES ('2004/3/12/222115/671_mod',1079158875); INSERT INTO `cache_time` VALUES ('2004/3/12/222115/671_comments',1079158880); INSERT INTO `cache_time` VALUES ('2004/1/30/11733/7275_comments',1087408195); INSERT INTO `cache_time` VALUES ('2004/1/30/11244/4143_comments',1087408195); INSERT INTO `cache_time` VALUES ('2004/1/16/1046/59617_comments',1087408195); INSERT INTO `cache_time` VALUES ('2004/1/15/152751/014_comments',1087408195); INSERT INTO `cache_time` VALUES ('2004/1/15/152446/828_comments',1087408195); INSERT INTO `cache_time` VALUES ('2004/1/15/152416/551_comments',1087408195); INSERT INTO `cache_time` VALUES ('pref_items',1106316582); INSERT INTO `cache_time` VALUES ('events',1106316583); INSERT INTO `cache_time` VALUES ('calendars',1106316583); UNLOCK TABLES; /*!40000 ALTER TABLE `cache_time` ENABLE KEYS */; -- -- Table structure for table `calendar_link` -- DROP TABLE IF EXISTS `calendar_link`; CREATE TABLE `calendar_link` ( `eid` int(11) NOT NULL default '0', `cal_id` int(11) NOT NULL default '0', `is_primary_calendar` tinyint(1) NOT NULL default '0', `displaystatus` tinyint(1) default '0', PRIMARY KEY (`eid`,`cal_id`) ) TYPE=MyISAM; -- -- Dumping data for table `calendar_link` -- /*!40000 ALTER TABLE `calendar_link` DISABLE KEYS */; LOCK TABLES `calendar_link` WRITE; UNLOCK TABLES; /*!40000 ALTER TABLE `calendar_link` ENABLE KEYS */; -- -- Table structure for table `calendars` -- DROP TABLE IF EXISTS `calendars`; CREATE TABLE `calendars` ( `cal_id` int(11) NOT NULL auto_increment, `title` varchar(100) default NULL, `owner` int(11) default '0', `description` text, `public_view` varchar(10) default 'public', `public_submit` varchar(10) default 'private', PRIMARY KEY (`cal_id`), KEY `owner_idx` (`owner`) ) TYPE=MyISAM; -- -- Dumping data for table `calendars` -- /*!40000 ALTER TABLE `calendars` DISABLE KEYS */; LOCK TABLES `calendars` WRITE; INSERT INTO `calendars` VALUES (1,'Global Calendar',0,'Site-wide calendar','public','private'); UNLOCK TABLES; /*!40000 ALTER TABLE `calendars` ENABLE KEYS */; -- -- Table structure for table `commentcodes` -- DROP TABLE IF EXISTS `commentcodes`; CREATE TABLE `commentcodes` ( `code` int(1) NOT NULL default '0', `name` varchar(32) default NULL, PRIMARY KEY (`code`) ) TYPE=MyISAM; -- -- Dumping data for table `commentcodes` -- /*!40000 ALTER TABLE `commentcodes` DISABLE KEYS */; LOCK TABLES `commentcodes` WRITE; INSERT INTO `commentcodes` VALUES (0,'Comments Enabled'); INSERT INTO `commentcodes` VALUES (1,'Read-Only'); INSERT INTO `commentcodes` VALUES (-1,'Comments Disabled'); UNLOCK TABLES; /*!40000 ALTER TABLE `commentcodes` ENABLE KEYS */; -- -- Table structure for table `commentratings` -- DROP TABLE IF EXISTS `commentratings`; CREATE TABLE `commentratings` ( `uid` int(1) NOT NULL default '0', `rating` int(11) NOT NULL default '0', `cid` int(15) NOT NULL default '0', `sid` varchar(30) NOT NULL default '', `rating_time` datetime default '0000-00-00 00:00:00', `rater_ip` varchar(16) NOT NULL default '', PRIMARY KEY (`sid`,`cid`,`uid`) ) TYPE=MyISAM; -- -- Dumping data for table `commentratings` -- /*!40000 ALTER TABLE `commentratings` DISABLE KEYS */; LOCK TABLES `commentratings` WRITE; UNLOCK TABLES; /*!40000 ALTER TABLE `commentratings` ENABLE KEYS */; -- -- Table structure for table `comments` -- DROP TABLE IF EXISTS `comments`; CREATE TABLE `comments` ( `sid` varchar(30) NOT NULL default '', `cid` int(15) NOT NULL default '0', `pid` int(15) NOT NULL default '0', `date` datetime default NULL, `rank` int(1) default NULL, `subject` varchar(50) NOT NULL default '', `comment` text NOT NULL, `pending` int(1) default '0', `uid` int(1) NOT NULL default '-1', `points` decimal(4,2) default NULL, `lastmod` int(1) default '-1', `sig_status` int(1) default '1', `sig` varchar(160) default NULL, `commentip` varchar(16) default NULL, `pre_rating` decimal(4,2) default NULL, PRIMARY KEY (`sid`,`cid`), KEY `stuff` (`uid`,`pid`), FULLTEXT KEY `commentsearch_idx` (`subject`,`comment`) ) TYPE=MyISAM; -- -- Dumping data for table `comments` -- /*!40000 ALTER TABLE `comments` DISABLE KEYS */; LOCK TABLES `comments` WRITE; UNLOCK TABLES; /*!40000 ALTER TABLE `comments` ENABLE KEYS */; -- -- Table structure for table `cron` -- DROP TABLE IF EXISTS `cron`; CREATE TABLE `cron` ( `name` varchar(20) NOT NULL default '', `func` varchar(20) default NULL, `run_every` int(11) default NULL, `last_run` datetime default '0000-00-00 00:00:00', `enabled` int(1) default '1', `is_box` int(1) default '0', PRIMARY KEY (`name`) ) TYPE=MyISAM; -- -- Dumping data for table `cron` -- /*!40000 ALTER TABLE `cron` DISABLE KEYS */; LOCK TABLES `cron` WRITE; INSERT INTO `cron` VALUES ('rdf','cron_rdf',21600,'2004-03-13 16:00:02',1,0); INSERT INTO `cron` VALUES ('rdf_fetch','cron_rdf_fetch',3600,'2004-03-13 18:00:02',1,0); INSERT INTO `cron` VALUES ('sessionreap','cron_sessionreap',86400,'2004-03-12 20:00:01',1,0); INSERT INTO `cron` VALUES ('digest','cron_digest',86400,'2004-03-12 20:00:01',1,0); INSERT INTO `cron` VALUES ('edit_queue','cron_edit_queue',3600,'0000-00-00 00:00:00',0,1); INSERT INTO `cron` VALUES ('cc_bill_orders','cc_bill_orders',300,'2002-04-20 17:21:35',0,1); INSERT INTO `cron` VALUES ('paypal_bill_orders','paypal_bill_orders',300,'0000-00-00 00:00:00',0,1); INSERT INTO `cron` VALUES ('unpaid_ad_reap','unpaid_ad_reap',86400,'0000-00-00 00:00:00',0,1); INSERT INTO `cron` VALUES ('poll_archive','poll_archive',2592000,'2002-09-27 13:20:59',0,0); INSERT INTO `cron` VALUES ('archive_stories','archive_stories',86400,'2002-10-18 21:00:01',0,0); INSERT INTO `cron` VALUES ('mark_ads_inactive','mark_ads_inactive',86400,'0000-00-00 00:00:00',0,1); UNLOCK TABLES; /*!40000 ALTER TABLE `cron` ENABLE KEYS */; -- -- Table structure for table `displaycodes` -- DROP TABLE IF EXISTS `displaycodes`; CREATE TABLE `displaycodes` ( `code` int(1) NOT NULL default '0', `name` varchar(32) default NULL, PRIMARY KEY (`code`) ) TYPE=MyISAM; -- -- Dumping data for table `displaycodes` -- /*!40000 ALTER TABLE `displaycodes` DISABLE KEYS */; LOCK TABLES `displaycodes` WRITE; INSERT INTO `displaycodes` VALUES (0,'Always Display'); INSERT INTO `displaycodes` VALUES (1,'Only Display Within Section'); INSERT INTO `displaycodes` VALUES (-1,'Never Display'); INSERT INTO `displaycodes` VALUES (-2,'Submitted'); INSERT INTO `displaycodes` VALUES (-3,'Editing'); UNLOCK TABLES; /*!40000 ALTER TABLE `displaycodes` ENABLE KEYS */; -- -- Table structure for table `editcategorycodes` -- DROP TABLE IF EXISTS `editcategorycodes`; CREATE TABLE `editcategorycodes` ( `code` int(1) NOT NULL default '0', `name` varchar(32) default NULL, `orderby` int(1) NOT NULL default '0', PRIMARY KEY (`code`) ) TYPE=MyISAM; -- -- Dumping data for table `editcategorycodes` -- /*!40000 ALTER TABLE `editcategorycodes` DISABLE KEYS */; LOCK TABLES `editcategorycodes` WRITE; INSERT INTO `editcategorycodes` VALUES (1,'Submitted',0); INSERT INTO `editcategorycodes` VALUES (2,'Pending',0); UNLOCK TABLES; /*!40000 ALTER TABLE `editcategorycodes` ENABLE KEYS */; -- -- Table structure for table `event_properties` -- DROP TABLE IF EXISTS `event_properties`; CREATE TABLE `event_properties` ( `eid` int(11) NOT NULL default '0', `property` varchar(32) NOT NULL default '', `value` text, PRIMARY KEY (`eid`,`property`) ) TYPE=MyISAM; -- -- Dumping data for table `event_properties` -- /*!40000 ALTER TABLE `event_properties` DISABLE KEYS */; LOCK TABLES `event_properties` WRITE; UNLOCK TABLES; /*!40000 ALTER TABLE `event_properties` ENABLE KEYS */; -- -- Table structure for table `event_property_items` -- DROP TABLE IF EXISTS `event_property_items`; CREATE TABLE `event_property_items` ( `property` varchar(32) NOT NULL default '', `title` varchar(50) default NULL, `description` text, `field` text, `template` text, `calendar_template` text, `display_order` int(5) default NULL, `requires` varchar(32) default NULL, `is_date` tinyint(1) default NULL, `is_time` tinyint(1) default NULL, `html` tinyint(1) default NULL, `regex` text, `enabled` tinyint(1) default NULL, `required` tinyint(1) default NULL, PRIMARY KEY (`property`) ) TYPE=MyISAM; -- -- Dumping data for table `event_property_items` -- /*!40000 ALTER TABLE `event_property_items` DISABLE KEYS */; LOCK TABLES `event_property_items` WRITE; INSERT INTO `event_property_items` VALUES ('title','Event Name','','event_property_text','','%%value%%%%value%%
','%%value%%Apply/Register by: %%value%%
','Deadline: %%value%%%%value%%',1,'normal'); INSERT INTO `pref_items` VALUES ('upload_user_quota','Disk Quota','The maximum amount of space this user can take up with his uploaded files (in kb)',0,0,'','edit_user','allow_uploads',0,'0',0,'\\d+','Interface','',0,'selectbox_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('upload_max_file_size','Max File Size','The maximum size a single file can be (in kb)',0,0,'','edit_user','allow_uploads',0,'0',0,'\\d+','Interface','',0,'selectbox_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('digest','Story Digest','Story headlines and intros can be emailed to you at your real email address on the schedule you choose.',0,0,'','','enable_story_digests',0,'Never',10,'(Never|Daily|Weekly|Monthly)','Interface','%%BOX,pref_selectbox,digest,%%value%%,Never,Daily,Weekly,Monthly%%',1,'selectbox_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('time_zone','Your Time Zone','Setting your (non-daylight savings) time zone here will make the site display all times and dates in your local time',0,0,'','','',0,'EST',4,'[a-zA-z]+','Interface','%%BOX,time_zone_pref,%%value%%%%',2,'selectbox_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('maxstories','Number of story summaries to show','(on front page)',0,0,'','','',0,'8',3,'\\d+','Interface','',3,'text_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('maxtitles','Number of story titles to show','(in \"older stories\" box)',0,0,'','','',0,'10',3,'\\d+','Interface','',4,'text_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('textarea_cols','Text box width','This allows you to set how big of a text box you have to type stories and comments into.',0,0,'','','',0,'50',4,'\\d+','Interface','',5,'text_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('textarea_rows','Text box height','This allows you to set how big of a text box you have to type stories and comments into.',0,0,'','','',0,'15',4,'\\d+','Interface','',6,'text_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('norm_font_face','Font Face','',0,0,'','','',0,'verdana, arial, helvetica, sans-serif',0,'[a-zA-z,\\s]','Interface','',7,'text_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('norm_font_size','Font Size','',0,0,'','','',0,'2',5,'\\w+','Interface','',8,'text_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('showad','Show ads','',0,0,'','ad_opt_out','use_ads',0,'All',16,'^(on|off)$','Interface','%%BOX,pref_checkbox,showad,%%value%%%%',9,'selectbox_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('ad_open_new_win','Open advertisement clicks in new window','',0,0,'','','use_ads',0,'off',3,'^(on|off)$','Interface','%%BOX,pref_checkbox,ad_open_new_win,%%value%%%%',10,'selectbox_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('show_topic','Show topic images with stories','',0,0,'','','use_topics',0,'on',3,'^(on|off)$','Interface','%%BOX,pref_checkbox,show_topic,%%value%%%%',11,'selectbox_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('start_page','Start page','',0,0,'','','',0,'__main__',0,'BOX,startpage_validation','Interface','%%BOX,startpage_pref,%%value%%%%',12,'selectbox_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('online_cloak','Hide yourself in the Who\'s Online box','',0,0,'','','use_whosonline',0,'off',3,'^(on|off)$','Interface','%%BOX,pref_checkbox,online_cloak,%%value%%%%',13,'selectbox_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('dynamic_interface','Use dynamic interface elements','This turns on javascript-driven items such as dynamic comment mode',0,0,'','','allow_dynamic_comment_mode',0,'off',3,'^(on|off)$','Interface','%%BOX,pref_checkbox,dynamic_interface,%%value%%%%',14,'selectbox_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('spellcheck_default','Spellcheck posts by default','',0,0,'','use_spellcheck','spellcheck_enabled',0,'off',3,'^(on|off)$','Interface','%%BOX,pref_checkbox,spellcheck_default,%%value%%%%',15,'selectbox_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('speling','Spelling variant','',0,0,'','use_spellcheck','spellcheck_enabled',0,'american',8,'(American|Canadian|British)','Interface','%%BOX,pref_selectbox,speling,%%value%%,American,Canadian,British%%',16,'selectbox_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('imagedir','Preferred image server','Choose an image server closest to you for the quickest page load times',0,0,'','','use_alt_image_servers',0,'/images',0,'','Interface','%%BOX,img_server_pref,%%value%%%%',17,'selectbox_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('theme','Use which theme','',0,0,'','','allow_user_themes',0,'',0,'\\w+','Interface','%%BOX,user_theme_pref,%%value%%%%',18,'selectbox_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('cookie_expire','Cookie Expiry','How long does your login cookie last?',0,0,'','','',0,'2592000',0,'','Interface','%%BOX,cookie_expire_pref,%%value%%%%',19,'selectbox_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('displayed_boxes','Boxes','',0,0,'','','',0,'hotlist_box,poll_box,rdf_feeds,whos_online',0,'','Interface','%%BOX,box_pref,%%value%%%%',20,'text_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('max_rdf_titles','Maximum headlines per feed','',0,0,'','','use_rdf_feeds',0,'15',2,'\\d+','Interface','',21,'text_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('rdf_feeds','External Feeds','[Submit New Feed]',0,0,'','','use_rdf_feeds',0,'',0,'','Interface','%%BOX,rdf_pref,%%value%%%%',22,'text_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('commentmode','Comment display mode','',0,0,'','','',0,'threaded',0,'(use_overflow|minimal|dminimal|threaded|dthreaded|nested|flat|flat_unthread)','Comments','%%BOX,commentmode_pref,%%value%%%%',1,'selectbox_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('commentmode_overflow_at','Change to overflow mode at','',0,0,'','','',0,'200',0,'\\d+','Comments','',2,'selectbox_pref','',1,'normal'); INSERT INTO `pref_items` VALUES ('commentmode_overflow','Comment display mode (overflow)','Comment display modes:\n
\r\n
| \r\n%%BOX,rdf_feeds%%\r\n |
If you don\'t know HTML, that won\'t stop you from making your stories and posts as nicely formatted and fancy as posts by those who do. If you set your \"Post Mode\" in Comment Preferences to \"Auto Format\", Scoop will do its best to format your comment based on its contents, instead of forcing you to litter it with tags. The following page will describe the mechanics used by Scoop to format comments and stories posted in \"Auto Format\" mode.
\r\n\r\nIn order to start a new paragraph, simply press \r\nEnter twice. To insert a line break, press Enter once. Note that text will automatically wrap to fit the size of the screen, so line breaks like that are generally unnecessary. In most cases, you shouldn\'t need to hit Enter at all except for paragraph breaks.
\r\n\r\nIf you want to emphasize a word or phrase, you can type it into the text box surrounded in asterisks (*), *like this*. This will cause the text between the asterisks to be rendered in bold type. Similarly, you can also enter text between underscores (_) or slashes (/), _like this_ /or this/, in order to render the given text in italics.
Of course, you can\'t post on the Web without needing to insert a link every now and then. Creating a link is as simple as typing in the URL (the address shown in your browser\'s toolbar at the top of the window). Auto Format mode will automatically turn all URLs into links. For example, if you were to type the following text:
\r\nThis website runs weblog software from http://scoop.kuro5hin.org.the resulting comment will look like this:
\r\nThis website runs weblog software from http://scoop.kuro5hin.org.\r\n
Of course, it\'s not always desirable to have the text of the link be the same as the target of the link. You can use brackets (\'[\' and \']\') in order to specify both the link text and link target. For example, if you wanted the text \"This search engine\" to point to http://www.google.com/, you would type the following:
[This search engine http://www.google.com/]Which will render like so:
\r\nThis search engine\r\n\r\n
You can create bulleted lists by entering a series of lines starting with an asterisk followed by a space (\'* \'). Numbered lists can be created similarly, by typing a series of lines beginning with a number follwed by a period (\'1. \'). For example, typing in the following text:
\r\n\r\nI had these items for breakfast this morning:\r\n* Eggs\r\n* Bacon\r\n* Toast\r\n* Hot grits\r\n
will give the following result:
\r\nI had these items for breakfast this morning:\r\n\r\n'); INSERT INTO `special` VALUES ('trusted','Trusted User Guidelines','An explanation of what privileges trusted users get, and what responsibilities they have','\r\n
- Eggs
\r\n- Bacon
\r\n- Toast
\r\n- Hot grits
\r\n
This site uses a system called \"Mojo\" to try to keep the comments as high-signal as possible. All users can rate all comments, except their own, between 1 and 5. When your comments are rated by others, those ratings are combined into a weighted average (newer comments count more than older ones) called your \"Mojo\". This, roughly, represents the rating we could expect your next comment to receive based on your past comments.
\n\nUsers who have a mojo greater than a certain minimum, and who have posted a sufficient number of comments, such as yourself, for example, are considered \"trusted\" users, and have the added capability to rate comments below the normal minimum rating, and also to see comments rated below the minimum (they are hidden from normal users).
\n\nThis is a great responsibility for you. It means you\'ve earned the right to peer-review content from untrusted users, and determine if it is spam. We rely on you to rate as much as you can, and to keep the comments as high-signal as we\'ve all come to expect.
\n\nPlease use your \"zero\" rating with care! It is *only* for use on comments that are wholly content-free. If you think the poster is clueless, or an idiot, or you just don\'t agree with them, that is *not* grounds for a zero rating. Zero is for comments that are offensive, script-generated, or otherwise content-free and intended solely to annoy and/or abuse other readers.
\n\nPlease do not rate duplicate comments 0! As virtually all duplicate comments are accidental, this unfairly impacts the poster\'s mojo. A \"1\" rating and an email to %%local_email%% notifying us of the duplicate (please include direct link to the comment) is the appropriate response.
\n\nYou also have a duty to read comments posted by untrusted users (you are the only ones who can!) and rate them up if they deserve to be viewable. We hate to see users become untrusted, and want them to rejoin the community, and rating them up when they post good comments is the only way for that to happen.
\n\nIt is a cruel irony that those who are trusted, in any context, usually have more work with no particular reward for that work, and that is the case here as well. You still post with no initial rating, like a normal user, and your ratings do not carry any extra weight or power. The big reward for being trusted is that you get to see the bottom-of-the-barrel dreck. But basically, someone has to do this, and you have shown the rest of the %%sitename%% readers that you have the responsibility and perception to be trusted with this task. Hopefully there are enough of you that no one person will have to expend any unreasonable efforts.
\n\nThank you for contributing to %%sitename%%, and for taking on the mantle of responsibility for keeping the site as high-quality as you\'ve helped make it. I, and all the other readers, salute you.'); INSERT INTO `special` VALUES ('untrusted','Why am I untrusted?','An explanation of why somebody is untrusted, and what they can do about it','
This site uses a system called \"Mojo\" to try to keep the comments as high-signal as possible. All users can rate all comments, except their own, between %%rating_min%% and %%rating_max%%. When your comments are rated by others, those ratings are combined into a weighted average -- newer comments count more than older ones -- called your \"Mojo\". This, roughly, represents the rating we could expect your next comment to receive based on your past comments.
\r\n\r\nUsers who have a mojo greater than a certain minimum and who have posted a sufficient number of comments are considered \"trusted\" users, and have the added capability to rate comments below the normal minimum rating. If enough of a user\'s comments are rated below %%rating_min%%, that user becomes \"untrusted\", which means that respected members of the community have repeatedly indicated that your input is offensive, content-free, or merely intended to annoy others.
\r\n\r\nIf you are untrusted, then your comments are posted with an initial rating equal to your mojo. Since this is below the normal rating minimum, these comments are not visible to any but trusted users. They may, if they choose, rate your comments above the minimum, and make them visible to others. You may earn back the trust of the community simply by posting worthwhile comments, and not spamming.
\r\n\r\nPlease do not see this as a condemnation of you as a person. We\'re sure you\'re very nice once we get to know you. This merely means that perhaps you\'ve posted some rather ill-considered comments, and the community as a whole has decided that we\'d rather have your input peer-reviewed before it goes out to the general public. Next time you post, think carefully about what you\'re saying and whether it adds to the topic at hand. If not, there are plenty of places on the web that don\'t filter input at all, and would be glad to hear whatever\'s on your mind.
\r\n\r\nIf you believe your posting history does not warrant an untrusted rating and you have been the victim of malicious rating, then please contact us at %%local_email%%. Think carefully, and review your previous comments before you do this. If you complain and have in fact been spamming, then I will not be pleased with you. If your untrusted rating is unjustified though, then we will deal with the situation.
\r\n\r\nThank you for reading %%sitename%%.
'); UNLOCK TABLES; /*!40000 ALTER TABLE `special` ENABLE KEYS */; -- -- Table structure for table `statuscodes` -- DROP TABLE IF EXISTS `statuscodes`; CREATE TABLE `statuscodes` ( `code` int(1) NOT NULL default '0', `name` varchar(32) default NULL, PRIMARY KEY (`code`) ) TYPE=MyISAM; -- -- Dumping data for table `statuscodes` -- /*!40000 ALTER TABLE `statuscodes` DISABLE KEYS */; LOCK TABLES `statuscodes` WRITE; INSERT INTO `statuscodes` VALUES (-1,'Pending'); INSERT INTO `statuscodes` VALUES (0,'Normal'); INSERT INTO `statuscodes` VALUES (-2,'Submitted'); UNLOCK TABLES; /*!40000 ALTER TABLE `statuscodes` ENABLE KEYS */; -- -- Table structure for table `stories` -- DROP TABLE IF EXISTS `stories`; CREATE TABLE `stories` ( `sid` varchar(20) NOT NULL default '', `tid` varchar(20) NOT NULL default '', `aid` int(11) NOT NULL default '0', `title` varchar(100) default NULL, `dept` varchar(100) default NULL, `time` datetime NOT NULL default '0000-00-00 00:00:00', `introtext` text, `bodytext` text, `writestatus` int(1) NOT NULL default '0', `hits` int(1) NOT NULL default '0', `section` varchar(30) NOT NULL default '', `displaystatus` int(1) NOT NULL default '0', `commentstatus` int(1) default NULL, `totalvotes` int(11) NOT NULL default '0', `score` int(11) NOT NULL default '0', `rating` int(11) NOT NULL default '0', `attached_poll` varchar(20) default NULL, `sent_email` int(1) NOT NULL default '0', `edit_category` tinyint(1) NOT NULL default '0', PRIMARY KEY (`sid`), KEY `section_idx` (`section`,`displaystatus`), KEY `displaystatus_idx` (`displaystatus`), FULLTEXT KEY `storysearch_idx` (`title`,`introtext`,`bodytext`) ) TYPE=MyISAM; -- -- Dumping data for table `stories` -- /*!40000 ALTER TABLE `stories` DISABLE KEYS */; LOCK TABLES `stories` WRITE; INSERT INTO `stories` VALUES ('2004/3/12/222115/671','scoop',1,'Congratulations! You\'ve installed Scoop!',NULL,'2004-03-12 22:21:15','Well, if you\'re seeing this, then hot damn, it worked! I hope the install wasn\'t too hairy. Read below for a little more info about how to get started with this thing, and I wish you the best of luck!
\r\n\r\nOh yeah, and once you\'ve got it all ready for launch, why don\'t you drop by the main Scoop site and announce it? There\'s a whole section dedicated to new Scoop site announcements.
','What you\'ll want to do now is login as \'scoop\', password \'scoop\', or whatever admin username and password you gave the install script, and edit some stuff.
\r\n\r\nIf you\'re using the default login and password, the first thing you\'ll want to do is change the admin account\'s password, and possibly username as well. Don\'t leave it as scoop/scoop! You can do this by clicking on the \"User Info\" link in scoop\'s user menu, then clicking on the \"Edit User\" link on that page.
\r\n\r\nOnce you\'ve done that, the first place you\'ll want to visit is the Site Controls Admin Tool, in the General category. The site controls that must be changed for your site to work properly are there - like your email, your site\'s URL, and so on. If you used the install script, some of these will be set already.
\r\n\r\nI strongly recommend that you check out the admin guide - there is a lot of useful information in there. It can be found online or in the doc/ directory of your Scoop install.
',0,0,'news',0,0,0,0,0,'1079158272_OOvrSGzI',0,0); UNLOCK TABLES; /*!40000 ALTER TABLE `stories` ENABLE KEYS */; -- -- Table structure for table `story_tags` -- DROP TABLE IF EXISTS `story_tags`; CREATE TABLE `story_tags` ( `sid` varchar(20) NOT NULL default '', `tag` varchar(255) NOT NULL default '', `tag_order` int(11) NOT NULL default '0', PRIMARY KEY (`sid`,`tag`), KEY `sid_idx` (`sid`), KEY `tag_idx` (`tag`) ) TYPE=MyISAM; -- -- Dumping data for table `story_tags` -- /*!40000 ALTER TABLE `story_tags` DISABLE KEYS */; LOCK TABLES `story_tags` WRITE; UNLOCK TABLES; /*!40000 ALTER TABLE `story_tags` ENABLE KEYS */; -- -- Table structure for table `storymoderate` -- DROP TABLE IF EXISTS `storymoderate`; CREATE TABLE `storymoderate` ( `sid` varchar(20) NOT NULL default '', `uid` int(11) NOT NULL default '0', `time` datetime default NULL, `vote` int(11) NOT NULL default '0', `section_only` enum('N','Y','X') NOT NULL default 'X', PRIMARY KEY (`sid`,`uid`) ) TYPE=MyISAM; -- -- Dumping data for table `storymoderate` -- /*!40000 ALTER TABLE `storymoderate` DISABLE KEYS */; LOCK TABLES `storymoderate` WRITE; UNLOCK TABLES; /*!40000 ALTER TABLE `storymoderate` ENABLE KEYS */; -- -- Table structure for table `subscription_info` -- DROP TABLE IF EXISTS `subscription_info`; CREATE TABLE `subscription_info` ( `uid` int(11) NOT NULL default '0', `expires` int(11) NOT NULL default '0', `created` datetime NOT NULL default '0000-00-00 00:00:00', `last_updated` datetime NOT NULL default '0000-00-00 00:00:00', `updated_by` varchar(50) default '', `active` int(1) NOT NULL default '0', `type` varchar(50) NOT NULL default '', PRIMARY KEY (`uid`) ) TYPE=MyISAM; -- -- Dumping data for table `subscription_info` -- /*!40000 ALTER TABLE `subscription_info` DISABLE KEYS */; LOCK TABLES `subscription_info` WRITE; UNLOCK TABLES; /*!40000 ALTER TABLE `subscription_info` ENABLE KEYS */; -- -- Table structure for table `subscription_payments` -- DROP TABLE IF EXISTS `subscription_payments`; CREATE TABLE `subscription_payments` ( `uid` int(11) NOT NULL default '0', `order_id` varchar(50) NOT NULL default '', `cost` decimal(7,2) NOT NULL default '0.00', `pay_type` varchar(10) NOT NULL default '', `auth_date` date NOT NULL default '0000-00-00', `final_date` date default NULL, `paid` int(1) default NULL, `type` varchar(50) NOT NULL default '', PRIMARY KEY (`uid`,`order_id`) ) TYPE=MyISAM; -- -- Dumping data for table `subscription_payments` -- /*!40000 ALTER TABLE `subscription_payments` DISABLE KEYS */; LOCK TABLES `subscription_payments` WRITE; UNLOCK TABLES; /*!40000 ALTER TABLE `subscription_payments` ENABLE KEYS */; -- -- Table structure for table `subscription_types` -- DROP TABLE IF EXISTS `subscription_types`; CREATE TABLE `subscription_types` ( `type` varchar(50) NOT NULL default '', `perm_group_id` varchar(50) NOT NULL default '', `cost` decimal(7,2) NOT NULL default '0.00', `max_time` int(11) NOT NULL default '0', `renewable` int(1) NOT NULL default '1', `description` text ) TYPE=MyISAM; -- -- Dumping data for table `subscription_types` -- /*!40000 ALTER TABLE `subscription_types` DISABLE KEYS */; LOCK TABLES `subscription_types` WRITE; UNLOCK TABLES; /*!40000 ALTER TABLE `subscription_types` ENABLE KEYS */; -- -- Table structure for table `subsections` -- DROP TABLE IF EXISTS `subsections`; CREATE TABLE `subsections` ( `section` varchar(32) NOT NULL default '', `child` varchar(32) NOT NULL default '', `inheritable` tinyint(1) NOT NULL default '0', `invisible` tinyint(1) NOT NULL default '0', `time` timestamp NOT NULL, PRIMARY KEY (`section`,`child`) ) TYPE=MyISAM; -- -- Dumping data for table `subsections` -- /*!40000 ALTER TABLE `subsections` DISABLE KEYS */; LOCK TABLES `subsections` WRITE; UNLOCK TABLES; /*!40000 ALTER TABLE `subsections` ENABLE KEYS */; -- -- Table structure for table `topics` -- DROP TABLE IF EXISTS `topics`; CREATE TABLE `topics` ( `tid` varchar(20) NOT NULL default '', `image` varchar(30) default NULL, `alttext` varchar(40) default NULL, `width` int(11) default NULL, `height` int(11) default NULL, PRIMARY KEY (`tid`) ) TYPE=MyISAM; -- -- Dumping data for table `topics` -- /*!40000 ALTER TABLE `topics` DISABLE KEYS */; LOCK TABLES `topics` WRITE; INSERT INTO `topics` VALUES ('all','scoop.jpg','All Topics',80,50); INSERT INTO `topics` VALUES ('scoop','scoop.jpg','Scoop',80,50); INSERT INTO `topics` VALUES ('diary','scoop.jpg','Diary',80,50); UNLOCK TABLES; /*!40000 ALTER TABLE `topics` ENABLE KEYS */; -- -- Table structure for table `userprefs` -- DROP TABLE IF EXISTS `userprefs`; CREATE TABLE `userprefs` ( `uid` int(11) NOT NULL default '0', `prefname` varchar(200) NOT NULL default '', `prefvalue` text, PRIMARY KEY (`uid`,`prefname`) ) TYPE=MyISAM; -- -- Dumping data for table `userprefs` -- /*!40000 ALTER TABLE `userprefs` DISABLE KEYS */; LOCK TABLES `userprefs` WRITE; INSERT INTO `userprefs` VALUES (1,'homepage','http://www.kuro5hin.org/'); INSERT INTO `userprefs` VALUES (1,'fakeemail','scoop@example.com'); INSERT INTO `userprefs` VALUES (1,'uid','1'); UNLOCK TABLES; /*!40000 ALTER TABLE `userprefs` ENABLE KEYS */; -- -- Table structure for table `users` -- DROP TABLE IF EXISTS `users`; CREATE TABLE `users` ( `uid` int(11) NOT NULL auto_increment, `nickname` varchar(50) default NULL, `realemail` varchar(50) default NULL, `origemail` varchar(50) default NULL, `passwd` varchar(12) default NULL, `trustlev` int(1) default NULL, `perm_group` varchar(50) default NULL, `mojo` varchar(5) default NULL, `creation_ip` varchar(16) NOT NULL default '', `creation_time` datetime NOT NULL default '0000-00-00 00:00:00', `newpasswd` varchar(12) default NULL, `pass_sent_at` datetime default NULL, `is_new_account` tinyint(1) default NULL, `creation_passwd` varchar(50) default NULL, PRIMARY KEY (`uid`) ) TYPE=MyISAM; -- -- Dumping data for table `users` -- /*!40000 ALTER TABLE `users` DISABLE KEYS */; LOCK TABLES `users` WRITE; INSERT INTO `users` VALUES (1,'scoop','scoop@example.com','scoop@example.com','MioQ79w6.4o',1,'Superuser',NULL,'','0000-00-00 00:00:00',NULL,NULL,1,NULL); UNLOCK TABLES; /*!40000 ALTER TABLE `users` ENABLE KEYS */; -- -- Table structure for table `vars` -- DROP TABLE IF EXISTS `vars`; CREATE TABLE `vars` ( `name` varchar(32) NOT NULL default '', `value` text, `description` text, `type` varchar(5) NOT NULL default 'text', `category` varchar(128) NOT NULL default '', PRIMARY KEY (`name`) ) TYPE=MyISAM; -- -- Dumping data for table `vars` -- /*!40000 ALTER TABLE `vars` DISABLE KEYS */; LOCK TABLES `vars` WRITE; INSERT INTO `vars` VALUES ('max_edit_stories','1','This variable determines how many stories one user can have in the edit queue at one time. The possible values are any positive integer. The default value is 1.
\nThis variable has no effect unless the edit queue is turned on for the user submitting the stories, using the perm edit_own_story.
This variable determines how long a story may remain in the edit queue before being forced to voting. The possible values are a number followed by a letter indicating the time unit. The default value is 2h (2 hours).
\nRecognised time units are s (seconds), m (minutes), h (hours) and d (days). The author of a story in the edit queue may move the story to voting at any time; if this hasn\'t happened by the time this time limit has been reached, Scoop will force the story to voting. This variable has no effect unless the edit queue is active.
This variable is the path that must precede all Scoop-generated pseudo-directories. The possible values are any absolute path prefix, with no trailing slash. The default is blank.
\nThis will only be used if you are installing Scoop into a subdirectory. If you are installing Scoop on its own virtualhost, this should be blank. See the Scoop Admin Guide for details on how this variable should be set.
This variable contains the name of the site. The possible value is any short string. The default is Scoop.
\nThis value is used in the emails sent by the site, the browser title bar, and the RDF feeds.
This variable is used as the from address whenever Scoop has to send an email. The possible values are any valid email address. The default is an invalid email address and must be changed.
\nThis email address should probably be one you check regularly. Since members are send email from this address, they are likely to think that they can send to it as well, if they have any questions. If this email address is not valid, nobody will be able to create accounts.
This variable determines where Scoop will look for topic images. The possible values are a valid directory name under the Scoop image directory, beginning with /. The default value is /topics.
\nThe contents of this variable are appended to the variable imagedir to provide the path to the topic images. The topic image directory must be under the regular image directory.
This variable determines whether or not the initial rating on a comment counts as a \"real\" rating or if it disappears on the first rating done by a user. The possible values are: 0) initial rating is overridden by first user rating; or 1) initial rating counts as the first real rating.
This variable has no effect unless the variable use_initial_rating is set to 1. The actual rating value given to a new comment is set in the variables anonymous_default_points and user_default_points.
This variable determines how many items will be displayed in lists. The possible values are any positive integer. The default value is 30.
\nThis value applies to the story list, poll list, and ad list admin tools, as well as the voting and edit queue.
This variable determines the score a story must reach in the voting queue to be posted. The possible values are: a positive integer) the absolute score of the story; and a positive percentage) a score represented as a percentage of registered users. The default value is 4.
\nIf the variable use_alternate_scoring is set to 1, this is the number of positive votes required; if it is set to 0, this is the score of the story found by adding all positive, negative, and neutral votes together. If this number is a percentage, a score is calculated on the fly based on the number of registered users in the database. So if you have a value of 5% here and there are currently 1,000 registered users, the post threshold will be 50.
This variable determines the score at which a story in the voting queue is hidden from sight. The possible values are any negative integer, or any positive percentage. The default value is -2.
\nIf the value is a percentage, it is interpreted as the negative of the percentage of total user accounts. If the value is a number, it is interpreted as an absolute score. As soon as a vote makes the story\'s score at or below the value in this variable, the story is removed from the voting queue and hidden. Do not put a positive number (except a percentage) in this variable, as stories begin voting with a score of 0. After a single positive vote, the score will then be 1, below or equal to all positive numbers, and resulting in every single story being hidden.','num','Stories');
INSERT INTO `vars` VALUES ('show_dept','0','
This variable determines whether or not a story can be assigned a \"department\" (i.e., from the i-love-scoop department) to be displayed under the title. The possible values are: 0) do not use departments; and 1) use departments. The default value is 0.
\nThis toggles both the display of the department when viewing the story, and the presence of an input box when submitting a story.
This variable determines the minimum rating a normal user can give a comment. The possible values are any integer. The default value is 1.
\nIf the variable use_mojo is set to 1, Trusted users (see the Scoop Admin Guide) can rate comments one point below this value, and any comment with an average score below this value are hidden from everybody except trusted users.
This variable determines the maximum rating a comment can receive. The possible values are any integer. The default value is 5.
','num','Comments'); INSERT INTO `vars` VALUES ('time_zone','EST','This variable tells Scoop which time zone the server\'s clock is set to. The possible values are any valid time zone string. The default value is EST.
\nIf this variable is set incorrectly, all display times will be wrong, leading to much confusion.
This variable identifies which poll is currently displayed on the front and section pages. This variable should not be changed here; to change the front page poll, use the Poll List Admin Tool.
','text','Polls'); INSERT INTO `vars` VALUES ('story_count_words','1','This variable determines whether Scoop counts words or bytes when displaying the size of a story. The possible values are: 0) count bytes (letters) in the story; and 1) count words in the story. The default value is 1.
\nWords are defined as anything separated by spaces or tabs. The number of bytes is displayed as the number of bytes, kilobytes, or megabytes, whichever is most appropriate.
This variable determines the number of answer fields for all new polls. The possible values are any positive integer. The default value is 10.
\nIf this number is reduced after some polls are created, the existing polls are not affected and all their answers will still be available for viewing and voting. This number only affects the number of poll form fields shown and processed when creating new polls and editing existing polls.
This variable determines how many comments a user can post before triggering the rate throttling mechanism used to limit crapflooding. The possible values are any positive integer. The default value is 4.
\nThe variable rate_limit_minutes is used in combination with this variable to calculate a posting rate; if the rate of max_comments_submit/rate_limit_minutes is exceeded, the user is blocked from posting for a short time, set by the variable timeout_minutes. These three values should be set so that most normal users will never encounter them, very active users will only rarely encounter them, and people or scripts attempting to flood the site with comments will be locked out. The default values should probably only be changed if they aren\'t working.
This variable determines how many stories a user can post before triggering the rate throttlineg mechanism used to limit crapflooding. The possible values are any positive integer. The default value is 2.
\nThe variable rate_limit_minutes is used in combination with this variable to calculate a posting rate; if the rate of max_stories_submit/rate_limit_minutes is exceeded, the user is blocked from posting for a short time, set by the variable timeout_minutes. These three values should be set so that most normal users will never encounter them, very active users will only rarely encounter them, and people or scripts attempting to flood the site with comments will be locked out. The default values should probably only be changed if they aren\'t working.','num','Stories,Post Throttle');
INSERT INTO `vars` VALUES ('rate_limit_minutes','10','
This variable contains the time span to calculate the posting rate for post throttling. The possible values are any positive number of minutes. The default value is 10.
\nThis is used with the variables max_comments_submit and max_stories_submit to calculate the maximum allowed posting rate. It should be set so that normal users will rarely or never encounter the limit, but abusive users or scripts attempting to flood the site with garbage comments or stories are blocked. If the posting rate is exceeded, the user is blocked from posting for a time set in timeout_minutes.
This variable determines how long a user exceeding the post throttle rate will be blocked from posting. The possible values are any positive number of minutes. The default value is 2.
\nThe post throttle rate is set using the variables max_post_comments, max_post_stories, and rate_limit_minutes. If a blocked user attempts to post while locked out, the timeout period doubles and restarts. If the timeout period exceeds the value given in the variable max_timeout, the user is moved to the group specified in the variable untrusted_group, or failing that, the Anonymous group.
This variable determines the maximum amount of accumulated rate-throttle timout time a user can have before being blocked from posting permanently. The possible values are any positive number of minutes. The default value is 300.
\nSee the Scoop Admin Guide for a description of rate throttling and the timeout.
This variable determines how many passes Scoop will make looking for keys before calling it a day and clearing any remaining. The possible values are any positive integer. The default value is 5.
\nFIXME: There\'s a bug in this somewhere; all keys that need to be interpolated are, no matter what you set this value to. Just leave it be for now.
This variable determines whether or not the mojo system should be used to determine user trust levels. The possible values are: 0) do not use mojo; and 1) use mojo. The default value is 1.
\nFor a description of mojo calculations and limits, and trusted and untrusted users, see the Scoop Admin Guide.
This variable determines whether or not topics are used. FIXME: this setting has weird behaviour that I\'ve made suggestions for fixing and making more consistent.
','bool','Stories'); INSERT INTO `vars` VALUES ('use_macros','0','Set to 1 to enable the use of macros in stories and comments.','bool','Macros'); INSERT INTO `vars` VALUES ('macro_render_on_save','0','Set to 1 to cause macros to render when saved; if 0, macros remain as raw macro text in stories and comments until archived','bool','Macros'); INSERT INTO `vars` VALUES ('macro_render_verbose','0','Set to 1 to render macros verbosely, with HTML comments as delimiters and original macro text preserved in comment (for post-processing)','bool','Macros'); INSERT INTO `vars` VALUES ('use_ref_check','0','This variable determines whether or not Scoop will check your referer before allowing access to any administrator functions. The possible values are: 0) do not check referer; and 1) check referer and deny administrator access if it does not match the server\'s hostname. The default value is 0.
\nThis is not real security; the referer field is very easy to change. If your browser blocks the referer by default, you will not be able to perform any site administration.
This variable determines whether or not users will have the option of requesting a story digest sent to their email address periodically. The possible values are: 0) users cannot request a digest and digests will not be sent; and 1) users may request a digest and digests will be sent according to the schedule requested.
\nBefore enabling this variable, make sure that the variables digest_subject and local_email, the blocks digest_header and digest_footer (or digest_headerfooter if you want the header and footer of the email to be the same) are properly set, and that the digest cron is enabled.','bool','Stories');
INSERT INTO `vars` VALUES ('auto_post_alert','1','
This variable determines whether or not the site administrator is notified when a story is posted or dropped using the auto-post algorithm (described in the Scoop Admin Guide). The possible values are: 0) do not email the admin; and 1) email the admin. The default value is 1.
\nThis variable has no effect unless the variable use_auto_post is set to 1. This variable uses the email addresses present in the variable admin_alert as the recipient.
This variable determines whether or not Scoop will make a posting decision after certain criteria have been met, if the story is not posted or hidden using the normal voting mechanism. The possible values are: 0) use only the normal voting mechanism; and 1) use the normal voting mechanism plus the auto-post algorithm where needed. The default value is 0.
\nThe criteria are based on the time the story has spent in the voting queue if the variable auto_post_use_time is set to 1, and based on the total number of votes received if that variable is set to 0. See the Scoop Admin Guide for more details on the autopost algorithm.
This variable determines the minimum score a story can have for the auto-post algorithm to post it to the site\'s front page. The possible values are any number between the variables rating_max and rating_min, including fractional values. The default value is 4.
\nThis variable has no effect unless the variable use_auto_post is set to 1. If the comment rating scale is set to anything other than 1-5, care must be taken when choosing the auto-post thresholds. See the Scoop Admin Guide for a full description of the auto-posting algorithm.
This variable determines the minimum score a story can have for the auto-post algorithm to post it to the site\'s section page. The possible values are any number between the variables rating_max and rating_min, including fractional values. The default value is 3.25.
\nThis variable has no effect unless the variable use_auto_post is set to 1. This value should not be higher than the value in the variable auto_post_frontpage, as stories with scores higher than that value are posted to the front page without considering this value. Stories with a score lower than this value are auto-hidden. See the Scoop Admin Guide for a full description of the auto-posting algorithm.
This variable determines whether or not a new poll can have a pre-set number of votes, before anybody has voted in the poll (also known as ballot stuffing). The possible values are: 0) do not allow ballot stuffing; and 1) allow ballot stuffing. The default value is 0.
\n This variable only applies to users with the perm edit_polls. \"Stuffed\" ballots do not have any checks made for sanity. Non-numeric values are changed to 0, but negative values are not filtered and result in some very strange poll results. If you change the number of votes in the poll, any users who have voted already will not be able to vote again, even if you set the number of votes to zero.
This variable determines the maximum number of words Scoop will allow in the introtext part of a story. The possible values are: 0) no limit; and any positive integer) the number of words (excluding HTML). The default value is 0.
\nThe variable max_intro_chars does the same thing but counts characters instead of words. Onely one of the two should be used.
This variable determines the maximum number of characters Scoop will allow in the introtext part of a story. The possible values are: 0) no limit; and any positive integer) the number of characters (including spaces but excluding HTML) permitted. The default value is 0.
\nThe variable max_intro_words does the same thing but counts words instead of characters. Only one of the two should be used.
This variable determines the maximum amount of memory Scoop\'s cache is allowed to use per site and per process. The possible values are any positive number followed by one of b) bytes; k) kilobytes; m) megabytes; g) gigabytes. The default value is 5M. If no unit is specified, `bytes\' is assumed.
This is a per-site and per-process value so if you have two sites running and apache has 5 processes handling them, you will have a maximum of 5*5*2 = 50 megabytes of memory taken up by Scoop\'s cache. If this number is set too large, your server may run out of available memory, degrading performance. If this number is set too small, Scoop will be forced to hit the database a lot more frequently, degrading performance.
This variable contains the URL for the server the site is hosted on. The possible value is a fully qualified domain name with no path information and no trailing slash. The default value is an invalid URL.
\r\nThe rootdir is appended to this variable to create the full URL to the site\'s front page. If this variable or rootdir ends in a slash, many URLs including the ones sent in emails will not work properly.
This variable determines how long the introtext in your site\'s RDF feed may be, in number of words, and replaces anything more with the string \"...\". The possible values are: 0) no limit; and any positive integer) the number of words in the RDF feed. The default value is 15.
\nThis variable has no effect unless the RDF generator is active. See the Scoop Admin Guide for details.
This variable determines whether or not images included in an external RDF feed are displayed. The possible values are: 0) do not display images; and 1) display images. The default value is 1.
\nThis variable has no effect unless the site is fetching RDF feeds for display; see the Scoop Admin Guide for details.
This variable determines whether or not form elements (such as the search box Scoop includes in its RDF feeds) included in an external RDF feed are displayed. The possible values are: 0) do not display form elements; and 1) display form elements. The default value is 1.
\nThis variable has no effect unless the site is fetching RDF feeds for display; see the Scoop Admin Guide for details.
This variable determines whether or not external RDF feeds should be fetched, stored, and displayed. The possible values are: 0) do not use external RDF feeds; and 1) use external RDF feeds. The default value is 1.
\nFor Scoop to fetch RDF feeds, the cron rdf_fetch must also be turned on. See the Scoop Admin Guide for details.
This variable determines whether or not a user may choose between \"sticky\" and \"retroactive\" signatures on their comments. The possible values are: 0) users may choose only between having a retroactive sig or not having a sig at all; and 1) users may choose between sticky, retroactive, or no sigs.
\nThe default value is 1.
\nDepending on the placement of the comment vs. the signature in the comment and moderation_comment blocks, sticky or no sig may not render correctly.
This variable determines when new/read comments are tracked. The possible values are: all) track and display new comments for all stories for all registered users; hotlist) track and display new comments only for stories a user has in his hotlist; and never) do not track or display new comments for any story or any user. The default value is all.
\nNew comments are marked with the contents of the block new_comment_marker when appropriate.
This variable turns the \"admin notes\" field on or off. The possible values are: 0) disable admin notes; and 1) enable admin notes. The default value is 1.
\nAdmin notes are displayed on the edit user form, and are only visible to users with the perm edit_user. They are useful for a site with multiple admins, so the admins can leave messages for each other regarding a particular account\'s past abuses, or making a record of changes made to an account. They can also be useful even when a site has only one admin, so the admin can leave a record of past changes or abuses and not rely on memory.
This variable determines whether or not Scoop will allow an admin to fetch external RDF feeds through the RDF Admin Tool. The possible values are: 0) do not allow RDF fetching through the admin tool; and 1) allow RDF fetching through the admin tool. The default value is 1.
\nThis variable should be left at 1 unless there is a problem with fetching external RDF feeds through the RDF Admin Tool. It is intended as a workaround for those situations where Apache cannot be recompiled to correct the issue with RDF fetches. Please see the Scoop Admin Guide for details.
This variable determines which http proxy (if any) Scoop uses when fetching external RDF feeds. The possible values are a fully qualified domain name and port of the proxy. The default value is blank.
\nThis variable has no effect unless the site is fetching RDF feeds for display; see the Scoop Admin Guide for details. If blank, Scoop connects directly when fetching; if filled, Scoop uses the server named as its proxy server. The name must be in the form http://host.name:port/
This variable determines the maximum number of headlines to display in an external RDF feed. The possible values are any positive integer. The default value is 15.
\nThis variable has no effect unless the site is fetching RDF feeds for display; see the Scoop Admin Guide for details. This variable can be overruled by a user preference.
This variable determines the maximum number of stories to include in the site\'s generated RDF feed. The possible values are any positive integer. The default value is 7.
\nThis variable has no effect unless the site is generating RDF feeds for syndication; see the Scoop Admin Guide for details. This variable is used with the variable rdf_days_to_show to determine how many stories to include in the RDF file.
This variable names the file Scoop saves its generated RDF feed to. The possible values are an absolute filesystem path. The default is the probably incorrect /www/scoop/html/backend.rdf
\nThis variable has no effect unless the site is generating RDF feeds for syndication; see the Scoop Admin Guide for details. The file named must be writeable by the Apache server and in a web-accessible location.
This variable gives the full external URL of an image file you want included with your site\'s RDF feed, or blank. The possible value is the fully qualified URL of your image file. The default value is wrong.
\nThis variable has no effect unless the site is generating RDF feeds for syndication; see the Scoop Admin Guide for details. If you are including an image in your RDF feed, it should generally be fairly small; large images can ruin another site\'s layout, and they may refuse to display your feed for that reason.
This variable determines how many days worth of stories to include in the RDF file your site generates. The possible values are any positive integer. The default value is 30.
\nThis is used in combination with rdf_max_stories to limit the number of headlines your site syndicates. This variable has no effect unless the site is generating RDF feeds for syndication; see the Scoop Admin Guide for details.
This variable contains the text of the copyright notice to include in the site\'s RDF feed. The possible values are any string. The default value will need to be changed, at least for the name of your site.
\nThis variable has no effect unless the site is generating RDF feeds for syndication; see the Scoop Admin Guide for details. Do not include special characters such as the copyright symbol in this field, as it causes some RDF parsers to choke.
This variable determines how long login sessions are saved for. The possible values are in the format time unit (eg, 5 day) and can be any valid time. The number may be any positive integer, and the unit may be any of second, minute, hour, day, month, or year.
\nThis variable has no effect unless the sessionreap cron is enabled. Login sessions are updated on every visit, so frequent visitors will not have their sessions expire. Expired sessions result in logging out the user; they will have to log in again on their next visit.
This variable determines the maximum number of comments that count towards a user\'s mojo score. The possible values are any positive integer. The default value is 30.
\nThis value is the number of rated comments, not the number of total comments, counted toward mojo. Unrated comments are excluded from the calculation entirely and have no effect on mojo at all. Newer comments are weighted higher than older comments, using this value is a weight factor. See the Scoop Admin Guide for details on mojo calculation. See also mojo_max_days. This variable has no effect unless the variable use_mojo is set to 1.
This variable determines whether or not the author of a story is notified when the story is either posted or dropped through the voting queue. The possible values are: 0) do not send an email notification; and 1) send and email notification. The default value is 1.
\nEmail notification is only sent if Scoop does the posting or hiding through either the normal voting mechanism or the auto-post mechanism. The email is sent from the email address specified in the variable local_email. Manually posted or hidden stories do not cause an email to be sent. This can cause performance issues on very large sites, so if you\'re having problems try disabling this feature.
This variable determines the maximum age of comments that count towards a user\'s mojo score. The possible values are any positive number of days. The default value is 60.
\nThis value is used when selecting the comments to be used in mojo calculations; only comments newer than this will be considered. Mojo must be maintained and cannot be accumulated. See the Scoop Admin Guide for details on mojo calculation. See also mojo_max_comments. This variable has no effect unless the variable use_mojo is set to 1.
This variable determines how many rated comments a user must have before being considered for \"Trusted User\" status. The possible values are any positive integer. The default value is 10.
\nThis value should be less than the value in mojo_max_comments because a user will never have more than that number of comments considered for mojo calculations. This variable has no effect unless the variable use_mojo is set to 1.
This variable determines the minimum mojo score a user must have before being considered a \"Trusted User\". The possible values are any number between rating_min and rating_max. The default value is 3.5.
\nTrusted users have some extra abilities; see the Scoop Admin Guide for details on trusted users. This variable has no effect unless the variable use_mojo is set to 1.
This variable determines how many rated comments a user must have before being considered for \"Untrusted\" status. The possible values are any positive integer. The default value is 10.
\nThis value should be less then the value in mojo_max_comments because a user will never have more than that number of comments considered for mojo calculations. This variable has no effect unless the variable use_mojo is set to 1.
This variable determines whether or not the subscription system is used. The possible values are: 0) do not use subscriptions; and 1) use subscriptions. The default value is 0.
\nSee the Scoop Admin Guide for details on setting up the subscription system.
This variable determines how many accounts can be created per day from a given IP address. The possible values are any positive integer. The default value is 2.
\nThis number should always be 1 or higher, or nobody will be allowed to create an account. Users behind proxies (such as at work, or at school, and some ISPs) will all appear to come from the same IP address, so we can\'t limit the number of accounts total per IP.
This variable determines the number of minutes required between password requests. The possible values are any positive number of minutes. The default value is 120.
\nWhen a password is requested, a new password is created and emailed to the account holder at their \"real email\" account. This variable is designed to prevent a user from being flooded with new password emails sent by an abusive user.
This variable determines whether or not Scoop will cache story pages as plain text files for faster display to anonymous users. The possible values are: 0) do not use static pages; and 1) use static pages. The default value is 1.
\nStatic pages are only shown to anonymous users, who do not get any customization beyond the comment view chosen. The static pages are stored in the filesystem at the location defined in the variable page_path. See the Scoop Admin Guide for details.
This variable sets the filesystem location of cached pages. The possible values are an absolute filesystem path which is owned by the apache user, or at least for which the apache user has write permission. The default value is the probably invalid /www/scoop/cache.
\nThis variable has no effect unless the variable use_static_pages is set to 1. Pages are only cached for anonymous users.
This variable determines whether or not Scoop will force a newline for a very long word in a comment which won\'t wrap on its own. The possible values are: 0) do not force line wrapping; and 1) force line wrapping. The default value is 1.
\nThis feature has no effect on normal English writing, and only modifies a long series of non-space characters, such as those used to force a page ridiculously wide so readers have to scroll sideways. The maximum length of a word without a space is set in the variable wrap_long_lines_at.
This variable determines how long a word (non-space characters in a row) can be before Scoop forces a newline to allow browsers to wrap the lines properly. The possible values are any positive integer. The default value is 100.
\nThis variable has no effect unless the variable wrap_long_lines is set to 1. This variable should be set longer than any legitimate word, and short enough that displaying it will not widen the page for people with small browser windows.
This variable determines whether or not Scoop will force a newline on long lines in the <PRE> environment. The possible values are: 0) allow PRE lines to be as long as the user specifies; and 1) force a wrap after a certain length for PRE lines. The default value is 1.
\nThis variable is only useful if you have allowed the PRE tag in the variable allowed_html.
This variable determines the maximum length of a line inside the PRE tag. The possible values are any positive integer. The default value is 100.
\nThis variable has no effect unless the variable wrap_pre is set to 1. This variable should be set long enough that it doesn\'t interfere with desirable displays (such as code snippets, if your site has programmer members) but short enough that lines near the maximum length do not widen the page excessively.
This variable determines whether or not Scoop uses the optional spell-checking functionality. The possible values are: 0) do not use spellcheck; and 1) use spellcheck. The default value is 0.
\nSpell-checking requires the aspell program and the Text::Aspell perl module. See the Scoop Admin Guide for details.
This variable determines whether or not Scoop\'s advertisement system is active. The possible values are: 0) no ads; and 1) use ads. The default value is 0.
\nBefore turning on the ad system, please read the Scoop Admin Guide for detailed instructions on its configuration and use.
This variable determines where advertisement files will be served from. This does not apply to text ads, only to ads including a separate file, such as an image file. The value must be an absolute public URL ending in a slash, including any path elements required to bring it to the same level as the local pathname set in ad_files_base. In both cases, the user id is appended as a subdirectory, and the file is placed in the user\'s subdirectory. If this public URL does not correspond to the local path set in ad_files_base, the saved ad files will not be displayed.
\nThis variable has no effect unless the variable use_ads is set to 1.
This variable determines where advertisement file uploads will be stored, if an ad type requiring file uploads is available. The value must be an absolute local pathname, not ending in a slash.
\nThe default value is a (probably) invalid local path. The value set here should be that of a path for which apache has full write access, and which is available from the internet at the URL specified in the variable ad_server_url. In both cases, the user id is appended as a subdirectory, and the file is placed in the user\'s subdirectory. If the path set in this variable does not exist, or does not allow apache write access, any ads that require file uploads will not work.
\nThis variable has no effect unless the variable use_ads is set to 1.
This variable names the group a user is moved to if an admin wipes their ratings. The possible value is any existing user group which does not have the perm comment_rate set. The default value is blank.
\nIf the variable is blank, the user\'s group is not changed and only past ratings are undone. If an existing user group which still has permission to rate comments is set here, it\'s rather pointless.
This variable contains the full path to the sendmail program Scoop uses to send email. The possible value is an absolute local filesystem path to the sendmail executable. The default value is /usr/sbin/sendmail
\nThis variable has no effect unless the SMTP host variable in httpd.conf is set to \"-\".
This variable determines whether or not identifying info is logged in Apache\'s error log with every request. The possible values are: 0) do not log extra information; and 1) record the extra information. The default value is 0.
\nThe information logged is the IP address, apache process ID, user ID, nickname, session, and any arguments, including the op and the full contents of any form. There\'s a reason it\'s called \"paranoid\"...
This variable determines whether or not advertisers must provide extra information before they can submit advertisements to the site. FIXME: Yet another unimplemented ad feature.','bool','Advertising'); INSERT INTO `vars` VALUES ('time_24h_format','0','
This variable determines whether Scoop displays times using the 24 hour format, or with AM/PM. The possible values are: 0) use AM/PM times; and 1) use the 24-hour clock. The default value is 0.
','bool','General'); INSERT INTO `vars` VALUES ('use_fulltext_indexes',NULL,'This variable determines whether or not Scoop should use the \"fulltext\" indexes when searching comments and stories. The possible values are: 0) do not use fulltext indexes; and 1) use fulltext indexes. The default value is 0.
\nThis variable should only be set to 1 if your database is capable of fulltext indexes and you have created the required indexes beforehand. Fulltext indexes allows you to sort search results by relevance or date, and weights search terms based on how frequently they appear. See the Scoop Admin Guide for details.
This variable determines how long a form key (used in comment and story posting) is valid for. The possible values are any positive number of seconds. The default value is 21600 (6 hours).
\nThe formkey is required to validate comments and stories, and helps prevent accidental duplicate posting due to double-clicking the Post button and similar situations.
This variable determines whether or not ad impressions and clickthroughs are logged. The possible values are: 0) do not log individual impressions; and 1) log individual impressions. The default value is 0.
\nAd logging includes the UID and IP of the person viewing or clicking the ad, as well as the ad\'s ID and a timestamp. This variable has no effect unless the advertising system is active; see the Scoop Admin Guide for more details on advertising.
This variable determines whether or not a notice will be sent to the advertiser when a particular ad has almost run out of impressions. The possible values are: 0) do not email the notice; and 1) email the notice. The default value is 1.
\nThe number of impressions remaining which triggers the notice is set in the variable mail_ad_reminder_on. This variable has no effect unless the advertising system is active; see the Scoop Admin Guide for more details on advertising.
This variable determines how many impressions must be left for Scoop to send the advertiser a notice informing him his impressions are running low. The possible values are any positive integer. The default value is 100.
\nThis variable has no effect unless the variable mail_ad_reminders is set to 1, and the advertising system is active; see the Scoop Admin Guide for more details on advertising. The value should be high enough that the advertiser has time to return to the site and create a new ad, but low enough that the campaign really is \"almost finished\", relative to the minimum number of impressions that may be purchased.
This variable determines whether or not a notice will be sent to the advertiser when a particular ad has run out of impressions. The possible values are: 0) do not email the advertiser when the last impression is viewed; and 1) email the advertiser when the last impression is viewed. The default value is 1.
\nThis variable has no effect unless the advertising system is active; see the Scoop Admin Guide for more details on advertising.
This variable affects the activation of new advertisements. The possible values are: 1) activate an advertisement automatically when the ad is approved by an admin; and 0) the advertisement is activated by the payment processing system.
\nThe default value is 1. If you are not getting payments for the ads via Scoop\'s payment processing system, 1 is an appropriate value. If you are getting payments for the ads via Scoop\'s payment processing system, the ads will be activated by the payment processing system once they have been approved and paid for and this variable can be set to 0.
\nThis variable has no effect unless the variable use_ads is set to 1.
\nSetting this variable to 1 when you are using Scoop\'s payment processing system results in ads paid for via credit card to not actually get paid for, as credit card payments are approved through the credit card company, then sent for admin approval, and only after approval are they actually paid for and activated by the cc_bill_orders box.
This variable names the default box template, for use when a box is not assigned a template on creation. The possible values are the names of any of the box templates (in the Blocks Admin Tool, in the boxes category). The default value is box.
\nChanging this value may have unintended effects on the site\'s display; some boxes may not have had a box template assigned when they were created.
This variable determines the minimum amount of money Scoop will allow people to pay when ordering ads or subscriptions. FIXME: Yet another unimplemented ad feature.
','text','Advertising'); INSERT INTO `vars` VALUES ('auto_post_floor','0','This variable affects the story auto-posting system. It determines the lowest score at which a story will still be considered for auto-posting. Any stories with scores below this value will simply be dumped when the auto-post limit is reached. The possible value is any number between the variables hide_story_threshold and post_story_threshold, inclusive. The default value is 0.
\nThis variable has no effect unless the variable use_auto_post is set to 1. If this value is set too high, good stories may not be auto-posted when they otherwise should be.
\nPlease read the Scoop Admin Guide for a description of how the auto-post system works.
This variable affects the calculations in the auto-post algorithm (described in the Scoop Admin Guide). The possible value is any positive integer. The default value is 0.
\nThis variable has no effect unless the variable use_auto_post is set to 1.
\nThis variable is also known as the \"boring story penalty\", since if the number of rated comments in a story is below this number, the number of rated comments used in the auto-post calculations is set equal to this number, while the value of those rated comments is left alone. This results in a lower score for the story when it is considered for auto-posting. If the value is too high, it will reduce the number of stories that are auto-posted.
This variable determines whether or not the auto-post algorithm is triggered by a time limit or by a total number of votes. The possible values are: 0) auto-post stories when a certain number of votes have been cast; and 1) auto-post stories when the story has been in the voting queue for more than a certain period of time. The default value is 0.
\nThis variable has no effect unless the variable use_auto_post is set to 1.
\nThe maximum time a story may spend in the queue is set in the variable auto_post_max_minutes. The maximum number of votes a story may receive before being subject to the auto-post algorithm is set in the variable end_voting_threshold.
This variable determines how long a story must remain in the voting queue before Scoop runs the auto-post algorithm (described in the Scoop Admin Guide) on it. The possible value is any positive integer number of minutes. The default value is 2160 (36 hours).
\nThis variable has no effect unless both the variables use_auto_post and auto_post_use_time are set to 1. If this value is set too low, stories that would otherwise be voted up normally will be subject to auto-posting; if set too high, stories that need auto-posting will languish in the voting queue for far too long. A suitable value for your site will depend entirely on the amount of traffic you get and how active members are in voting on articles.
This variable determines which section advertisements will be filed in if they allow comments. The value must be the internal name (not the display name) of an existing section with the section permission \"Post Stories\" set to \"Hide\" for all groups.
\nThe default value is advertisements. This value is invalid because Scoop does not include an advertisements section by default. The section name may be any string of letters or numbers, but no spaces. It should be something that indicates the presence of ads. Once some ads with discussions available have been posted, this variable should not be changed.
\nThis variable has no effect unless both the variable use_ads and at least one active ad type has the ad property \"Allow Ad Discussions\" turned on.
This variable affects the judging process for new advertisements. The possible values are: 0) Only paid ads will be presented for judging and approval, or 1) All ads not yet approved will be presented for judging and approval, regardless of paid status.
\nThe default value is 1. Free ads are automatically marked as paid when submitted. Setting this variable to 0 is recommended, so you don\'t have to sort through a mixture of paid and unpaid ads awaiting approval.
\nThis variable has no effect unless the variable use_ads is set to 1.
This variable determines what the default display status should be when the story edit form is opened. The possible values are: -3) Editing; -2) Voting; -1) Never Display (deleted); 0) Always Display (front page); 1) Only Display in Section. The default value is 0.
This variable is used if the story edit form is loaded without a story, as in the New Story Admin Tool or the regular submit story form for users with the perm story_displaystatus_select.
This variable determines which topic advertisements will be filed in if they allow comments. The value must be the internal name (not the display name) of an existing topic.
\nThe default value is ads. This value is invalid because Scoop does not include an ads topic by default. The topic name may be any string of letters or numbers, but no spaces. It may be something that indicates the presence of ads, but a generic topic may also be used, as this topic will also be available to anybody posting a story. Once some ads with discussions available have been posted, this variable should not be changed.
\nThis variable has no effect unless both the variable use_ads and at least one active ad type has the ad property \"Allow Ad Discussions\" turned on.
This variable determines whether or not Scoop records the IP address of a poster with each comment. The possible values are: 0) do not log poster IP address; and 1) log poster IP address. The default value is 0.
\nHopefully this can help identify problem duplicate accounts. To view the IP addresses saved, see the variable view_ip_log.
This variable determines whether or not comment poster IP addresses are displayed in the comment header. The possible values are: 0) do not display IP addresses; and 1) display IP addresses. The default value is 0.
\nThis variable has no effect unless the variable comment_ip_log is set to 1 and the user has the perm view_comment_ip.
This variable determines which character set Scoop sends to a browser. The possible values are theoretically any valid character set, but there appear to be issues with some non-western character sets (such as big5). The default value is ISO-8859-1.
\nIf you must use a different character set, be aware that it may cause things to break in unusual ways. Scoop internationalization is still in the planning stages; check http://scoop.kuro5hin.org/ for any updates.
This variable determines whether or not Scoop will include the header information required to prevent proxies from caching your pages. The possible values are: 0) do not include the cache prevention headers; and 1) include the cache prevention headers. The default value is 0.
\nSince Scoop\'s pages are generally entirely dynamic, having them cached will litter out-of-date scoop pages around in caches all over the internet.
This variable determines whether or not your site will handle subsections. The possible values are: 0) subsections are not used; and 1) subsections are used. The default value is 0.
\nPlease see the Scoop Admin Guide for more information on Scoop\'s subsections.
This variable determines whether or not comments posted to diaries are counted toward a user\'s mojo. The possible values are: 0) comments in diaries are treated the same as other comments; and 1) comments in diaries do not have their ratings counted in mojo calculations. The default value is 0.
\nThis variable has no effect unless the variable use_mojo is set to 1.
This variable determines whether or not a user is allowed to renew an existing advertisement. The possible values are: 0) renewals are not allowed; and 1) renewals are allowed. The default value is 1.
\nThis variable has no effect unless the advertising system is active. If ad renewals are permitted, the renewal link is shown on the ad statistics page which only the ad owner can see. Ad renewal is yet another unimplemented ad feature. Leave this off.
This variable determines whether or not a user may use one of the dynamic comment modes to view comments. The possible values are: 0) do not allow users to choose either of the dynamic comment modes; and 1) allow users to choose either of the dynamic comment modes. The default value is 0.
\nBefore dynamic comments can be used, several blocks must be modified to include the necessary javascript and setup information. See the Scoop Admin Guide for details on how to set up dynamic comments.
\nDynamic comment mode requires javascript to work, and will only work with \"5th generation\" browsers, that is, Netscape 6 or higher, IE 5 or higher, Mozilla, and other browsers with equivalent javascript support.
This variable contains the secure version of site_url. The possible values are a fully qualified domain name. The default value is an invalid URL.
\r\nThis should most likely be the same as site_url except with https:// instead of http://. This variable has no effect unless you have the payment processing system turned on. See the Scoop Admin Guide for more details. If you have a secure site running, the entire Scoop site is browsable using it. Some pages (such as those collecting payment details) must be; you may be able to configure Apache to disallow secure browsing of other pages.
This variable determines which theme will be used as a base for all other themes to build on. The possible values are any theme name which is a complete set of Scoop blocks when taken alone. The default value is default.
\nThis variable is used whether or not the variable use_themes is set to 1 or 0; it provides a full set of blocks to use alone or as a base for other themes either way. It must always be set to a fully populated theme or your site may become completely unusable, depending on which blocks are missing.
This variable determines whether or not themes are used at all. The possible values are: 0) do not use any themes; and 1) use themes. The default value is 0.
\nSee the Scoop Admin Guide for details on configuring themes.
This variable determines what percentage of spam votes must be cast for an article in the editing queue to be forced to voting without the author\'s consent. The possible values are any number between 0 and 1. The default value is 0.25.
\nThis variable has no effect unless the variable use_anti_spam is set to 1. For a description of the edit queue anti-spam algorithm, see the Scoop Admin Guide.
This variable determines how many spam votes must be registered before the anti-spam algorithm determines whether or not force a story into the voting queue without the author\'s consent. The possible values are any positive integer. The default value is 100.
\nThis variable has no effect unless the variable use_anti_spam is set to 1. For a description of the edit queue anti-spam algorithm, see the Scoop Admin Guide.
This variable is used when a user logs off. The possible values are an absolute path (beginning with a /), a fully qualified URL, or blank, which will go to the site\'s front page. The default value is blank.
\nIf you like, you can create a page saying goodbye or any other message appropriate for logging out using the Special Pages Admin Tool, and put its path here.
This variable determines whether or not a spam button is displayed in the editing queue. The possible values are: 0) no spam button; and 1) show the spam button. The default value is 1.
\nThe variables spam_votes_threshold and spam_votes_percentage are used to calculated whether or not a story should be forcibly removed from the edit queue. Without the spam button, a \"crapflood\" or garbage story placed in the edit queue will remain there until the edit queue time limit.
This variable determines whether or not \"edit categories\" should be used. The possible values are: 0) do not use edit categories; and 1) use edit categories. The default value is 0.
\nEdit categories are really only useful with a closed moderation queue, and provide a way for the admins to distinguish between stories still being written and stories being considered for publication. See the Scoop Admin Guide for details.
This variable determines whether or not a story in the voting queue receives an automatic zero (Abstain) vote when the story is viewed. The possible values are: 0) do not auto-vote; and 1) auto-vote. The default value is 0.
\nThis variable is only useful if your site is using a closed voting queue and stories are published by an editor marking it as published instead of the normal voting mechanism. The purpose of this variable is to allow editors to see which stories they\'ve read already. If this variable is set, editing a story clears all votes, indicating to the editor that there has been an unread change to the story.
\nThis variable should never be set to 1 if you are using an open voting queue.
This variable determines whether or not the mode of a comment posted to a story in one of the queues is automatically set to \"editorial\" or if it is not pre-set. The possible values are: 0)do not pre-set the comment type; and 1) pre-set the comment type to editorial. The default value is 0.
\nOnce a story is out of the queue and is published, editorial comments are hidden by default. Users must have the permission editorial_comments in order to post comments in editorial mode.
This variable determines whether comments are permitted or not when a new story is created. The possible values are: 0) comments are permitted; -1) comments are not permitted; and 1) comments are \"read only\". The default value is 0.
\nThe distinction between \"not permitted\" and \"read only\" is explained in the Scoop Admin Guide.
\nIf you were creating a discussion site, you would want to leave this set to 0; if, however, you were using Scoop to manage articles but did not want comments by regular users, you would then change this value.
This variable determines whether or not any file uploads are permitted. The possible values are: 0) no file uploads are permitted; and 1) file uploads are permitted. The default value is 0.
\nPlease see the Scoop Admin Guide for a description of what file upload functions are available, and for an explanation of how to configure them. The variables which must be configured before this variable is set to 1 are described in the Scoop Admin Guide, and are located in the Uploads category of the Site Controls.
This variable determines whether or not a user can delete the files he uploaded to Scoop. The possible values are: 0) do not allow file deletion; and 1) allow file deletion. The default value is 0.
\nThis variable has no effect unless the variable allow_uploads is set to 1. If users are permitted to embed items (such as images) in their file upload space in their stories, allowing file deletion will break the display.
This variable determines whether or not uploaded files can be renamed by their owner. The possible values are: 0) do not allow file deletion; and 1) allow file deletion. The default value is 0.
\nThis variable has no effect unless the variable allow_uploads is set to 1. If users are permitted to embed items (such as images) in their file upload space in their stories, allowing file renaming will break the display of those images.
This variable determines where admin uploaded files will be accessible through the web. The possible values are an absolute path, ending in a /. The default value is blank.
\nThis variable has no effect unless the variable allow_uploads is set to 1. The admin upload path is shared by all users with the perm upload_admin.
This variable determines where user uploaded files will be accessible through the web. The possible values are an absolute path, ending in a /. The default value is blank.
\nThis variable has no effect unless the variable allow_uploads is set to 1. The user upload path is a subdirectory named for the user\'s UID under the path defined here.
This variable determines where admin uploaded files are saved on the filesystem. The possible values are any absolute local filesystem path, ending with a /. The default value is blank.
\nThis variable has no effect unless the variable allow_uploads is set to 1. The directory named in this variable must be either owned by the web server user, or writeable by it.','text','Uploads');
INSERT INTO `vars` VALUES ('upload_path_user','','
This variable determines where user uploaded files are saved on the filesystem. The possible values are any absolute local filesystem path, ending with a /. The default value is blank.
\nThis variable has no effect unless the variable allow_uploads is set to 1. The directory named in this variable must be either owned by the web server user, or writeable by it, and the web server must be able to create subdirectories in this directory.','text','Uploads');
INSERT INTO `vars` VALUES ('show_prefs_on_first_login','1','
This variable determines whether or not a new user is sent to the user preferences page the first time he logs on. The possible values are: 0) the first login is normal, and sends the user to the front page; and 1) the first login is special, and sends the user to his preferences page. The default value is 1.
','bool','General'); INSERT INTO `vars` VALUES ('require_story_preview','1','This variable determines whether or not a user must preview story and diary submissions at least once before submitting. The possible values are: 0) user can submit without previewing; and 1) user must preview at least once before submitting. The default values is 1.
','bool','Stories'); INSERT INTO `vars` VALUES ('use_logging','0','This variable determines how much administrator activity is logged. The possible values are: 0) log nothing; 1) log basic information; and 2) log extended information. The default value is 0.
\nLogging requires that the logging hooks as well as this variable are activated. See the Scoop Admin Guide for more details.
This variable determines which themes to apply in what order. The possible values are a comma-separated list of criteria. The default value is section.
\nThis variable has no effect unless the variable use_themes is set to 1. The themes associated with the criteria are applied in the order listed here, with later themes overwriting earlier ones, if they overlap. The possible criteria are: section, siteid, agent, pref, and group. See the Scoop Admin Guide for more information on themes.
This variable determines whether or not the user may choose a theme to apply to the site. The possible values are: 0) users may not choose a theme; and 1) users may choose a theme from a specified list. The default value is 0.
\nIf this variable is set to 1, users may only choose a theme from the list in the variable user_themes, or choose to apply none. This variable has no effect unless the variable use_themes is set to 1.
\nFor more details on themes, see the Scoop Admin Guide.
This variable determines which themes a user may choose from in his display preferences. The possible values are a comma-separated list of themes present in the Blocks Admin Tool. The default value is blank.
\nThis variable has no effect unless the variables use_themes and allow_user_themes are set to 1. The user may choose between the themes listed here.
This variable sets which theme is applied to the news section. The possible value is any existing theme name. The default value is greyscale.
\nThis variable has no effect unless the variable use_themes is turned on. This is a demonstration variable; to set themes for other sections, create new variables with the internal name of the section in place of \"news\", the same way this variable is set up. For more information on setting up themes, see the Scoop Admin Guide.
This variable extends the \"related links\" box associated with a story by allowing you to define some links Scoop should automatically add every time a particular keyword appears in a story.
\r\nThis variable affects display only. The \"related links\" box lists every link in the story in one convenient spot.
\r\nThe format is a keyword or keyphrase, a comma, and a URL. One entry per line, no comma at the end of the line.
This variable is used throughout Scoop, whenever something requires the attention of an administrator. The only possible values for this variable are a single valid email address or a list of valid email addresses separated by commas.
\nThe default value is an invalid email address, and must be changed. The email address entered should be the email address of the site administrator or administrators, and should be one that is checked regularly.
\nMany error and security functions depend on this variable holding a valid, actively read email address. If this variable contains an invalid or unread email address, notices of site errors, posting violations, and situations which require admin intervention will not be dealt with as an email to the addresses in this variable are usually the only notification provided.
This variable determines which HTML tags are available to users posting comments or stories, and which elements of those tags are allowed. The value must follow the format described below. You should have a reasonable knowledge of HTML before editing this variable.
\nThe default allows a fairly flexible, if limited, subset of HTML in all comments and stories to all user groups. Tags may be added or removed depending on the culture of the site, and you may specify some tags as allowed only to certain users or only in certain locations.
\nOne HTML tag is listed per line, beginning with the tag itself, followed by a comma-separated list of allowed tag elements and parser commands. For example:\n
A, HREF, NAME, -close\nallows the A tag to be used with only the elements \"href\" and \"name\", and requires that the tag be closed with a </A>. To further specify what is permitted, a perl regular expression may be used alongside a tag element. For example:\n
A, HREF=\"^http://\", NAME, -close\nallows the A tag to be used with the same two elements as above, but the \"href\" element must contain a value which begins with (the ^ indicates the string following must be at the beginning of the string we\'re testing against) http://.
IMG, src, alt, height, width, -groups=\"Superuser Admins Editors\"\nwould allow the use of the IMG tag and the listed tag elements for the three groups listed only. Any group name may be used here. The entire list of groups may be inverted, giving all groups except those listed access to the tag with\n
-group=\"!Anonymous Restricted\"\nwhich denies the use of a tag to the Anonymous and Restricted groups but allows it to all others).
IMG, src, alt, height, width, -context=\"body\"\nwould allow the use of the IMG tag to any user group but only in the body (extended copy) of a story. The list may be inverted in the same way as -group. Valid contexts are intro (story\'s intro copy), body (story\'s extended copy), comment (comment body), and pref (signature and bio fields).
This variable contains a list of all HTML tags and their possible tag elements, using the same format as the variable allowed_html. This is used for Scoop\'s HTML validator and parser for the blocks and special pages.
\nThis variable should generally never be changed.
This variable contains a list of all permissions used by Scoop, in a comma-separated list, one permission per line.
\nIf any perm is added or removed from this list, the change will be reflected in the list of perms in the Groups Admin Tool. Added perms default to off for all groups. Removed perms are only removed from the admin tool; any removed perms that had been granted to groups before removal are still granted to those groups afterward.
This variable contains a list of hooks recognised by Scoop for use in the Hooks Admin Tool. The format of this variable is: one hook definition per line; each definition consists of the hook name and a comma-separated list of arguments it accepts in parentheses.
\nEach hook is named based on an activity that can be taken on a Scoop site. In the Hooks Admin Tool, each of these hooks can have code attached which will run when those activities are performed. See the Scoop Admin Guide for more details.
This variable determines how old a poll must be before it is archived. The possible values are: 0) do not archive polls; and any positive integer) the age of a poll in days before it will be considered for archiving. The default value is 0.
\nThis variable has no effect unless the archiving system is active.
This variable determines whether or not the individual ratings of a comment are archived when the comment is archived. The possible values are: 0) do not archive the individual ratings; and 1) archive the individual ratings. The default value is 1.
\nThis variable has no effect unless the comment archiving system is configured and enabled. For more details on archiving, see the Scoop Admin Guide. Since a comment\'s score and number of ratings are archived with the comment and archived comments cannot be rated, the individual ratings are not required to determine the comment\'s score, it is only available for extra information.
This variable determines whether or not the voting history of a story is archived when the story is archived. The possible values are: 0) do not archive the voting history; and 1) archive the voting history. The default value is 1.
\nThis variable has no effect unless the story archiving system is configured and enabled. For more details on archiving, see the Scoop Admin Guide. Since a story\'s display status (ie, front page or section) is archived with the story, the voting history is not required to determine where it should be displayed but is only available for extra information.
This variable prevents old stories with still-active discussions from being archived. The possible values are any positive integer or zero and represent a number of days. The default is 31.
\nThis variable should be set to a smaller value than story_archive_age. If zero, stories are archived according to story_archive_age alone; if any positive number, stories that would otherwise be archived are not if they have a comment posted fewer days ago than the value of this variable.
This variable determines the age in days of stories to be archived. The possible values are any positive number of days. The default value is 0 (disabled).
\nThis variable has no effect unless the archive database has been created and configured properly. See the Scoop Admin Guide for details. The effect of this variable is modified by the variable comment_archive_age; stories older than the value in this variable but with comments newer than the age specified in comment_archive_age will not be archived.
This variable determines whether or not the navigation bar at the bottom of stories is displayed. The possible values are: 0) show the navigation bar; and 1) hide the navigation bar. The default value is 0.
\nThe navigation bar is displayed directly underneath the story text and provides links to the previous and next stories. Which stories those are can be the subject of confusion among users of the site.
This variable determines the number of votes a story in the voting queue must receive before the auto-post algorithm activates and determines if and where to post the story. The possible values are any positive integer number, or any positive percentage. The default value is -1.
\nThis variable has no effect unless the variable use_auto_post is set to 1. If the variable auto_post_use_time is set to 1, this variable is ignored and a time-based limit is used to activate the auto-post algorithm instead.
This variable determines which scoring calculations are used in the story voting queue. The possible values are: 0) compare the story\'s total score to the thresholds; and 1) compare the number of positive and negative votes to the thresholds separately. The default value is 0.
','bool','Stories'); INSERT INTO `vars` VALUES ('front_page_ratio','0.50','This variable determines whether a posted story should be placed on the front page or in the section page only. The possible values are any decimal number between 0 and 1. The default value is 0.50.
\nThe number of front page votes is divided by the total number of positive votes to provide the ratio of front page votes. If the calculated ratio is less than the value of this variable, the article is posted to the section. This variable only takes effect if a story is voted up through the normal voting queue, and not if the story is posted using the auto-post algorithm.
This variable contains the name of the creator of your site\'s RDF feed. The possible values are any string. The default value is blank.
\nThis variable has no effect unless the site is generating RDF feeds for syndication; see the Scoop Admin Guide for details. If this variable is blank, the text in the variable sitename is used instead.
This variable sets the identity of the publisher of the RDF file. The possible values are any short string. The default value is blank.
\nThis variable has no effect unless the site is generating RDF feeds for syndication; see the Scoop Admin Guide for details. If this is blank, the value of the variable sitename is used in its place.
This variable determines how long your site will wait before giving up when fetching another site\'s RDF feed. The possible values are any positive number of seconds. The default value is 60.
\nThis variable has no effect unless the site is fetching RDF feeds for display; see the Scoop Admin Guide for details.
This variable determines whether or not diaries can be searched using Scoop\'s search form. The possible values are: 0) allow diary searching; and 1) do not allow diary searching. The default value is 0.
\nThis variable has no effect unless the variable use_diaries is set to 1.
This variable determines whether or not comments to stories with comments disabled can be found in a comment search. The possible values are: 0) allow disabled comments in search results; and 1) hide disabled comments in search results. The default value is 0.
\nStories with comments disabled don\'t display any comments or the comment controls when the story is viewed.
This variable determines whether or not comments from stories not published to either the front of any section are displayed in search results. The possible values are: 0) comments attached to stories in the queue or hidden are shown in search results; and 1) comments attached to stories in the queue or hidden are not shown in search results. The default value is 0.
\nThis variable only applies to search results; comments on hidden stories can still be viewed when this variable is set to 1.
This variable determines whether or not comments require new subjects or use the parent comment as a source. The possible values are: 0) the comment\'s subject line is empty when a user clicks on the reply link; and 1) the comment\'s subject line contains \"Re: (previous subject line)\" when a user clicks on the reply link. The default value is 0.
\nIf the parent comment already has a subject beginning with \"Re:\", Scoop does not add another one. If the user has changed the subject line, Scoop does not override it with the parent\'s subject.
This variable determines whether or not newly posted comments are given an initial rating. The possible values are: 0) do not give an initial rating; and 1) give an initial rating. The default value is 0.
\nThe initial rating is completely overridden by the first real rating given by another user, unless the variable real_initial_rating is set to 1. The actual value of the initial rating given is set in the variables anonymous_default_points and user_default_points.
This variable sets an anonymously posted comment\'s initial value. The possible values are any number between the values set in rating_min and rating_max, inclusive. The default value is 2.
\nThis variable has no effect unless the variable use_initial_rating is set to 1.
\nThe value is used as an initial comment rating on all comments posted anonymously; a single rating by a user will cause the initial rating to vanish because it is not an actual comment rating. It is merely used to give unrated comments a rank when comments are sorted by rating.
This variable determines the initial rating all registered users will receive on their comments. The possible values are any number between rating_min and rating_max. The default value is 3.
\nThis variable has no effect unless the variable use_initial_rating is set to 1.
This variable determines how many topic images are shown in the (slashdot-style) list of most recent story topics. The possible values are any positive integer. The default value is 0.
\nFIXME: The box displaying the recent topic images is not included in Scoop by default. It seems to have been lost.
This variable determines whether or not the post and hide thresholds are displayed in the story moderation queue. The possible values are: 0) do not show the thresholds; and 1) show the post and hide thresholds. The default is 0.
\nThe thresholds are taken from the variables post_story_threshold and hide_story_threshold. If one or both of those thresholds are percentages, the numeric value at the time of the page request is calculated and displayed instead of the percentage.
This variable determines which sections will not be shown in the \"Everything\" pseudo-section or the RDF feed. The possible values are a comma-separated list of section names. The default list contains the Diary and adverts sections.
','text','Stories'); INSERT INTO `vars` VALUES ('story_nav_bar_sections','Diary, advertisements','This variable lists the sections whose story navigation bar should only contain other stories from that section. The possible value is a comma-separated list of section names. The default value is the diary and ad sections.
This only has an effect if the variable disable_story_navbar is set to 0. If the current story is not from one of the sections listed, then only stories also not in this list are considered when building the story navbar. If the current story is from one of the sections listed, then only stories also in that one section are considered when building the story navbar.
This variable determines whether or not users can select topics other than `diary\' for their diaries. The possible values are: 0) users may not select a topic; and 1) users may select any topic available to regular stories. The default value is 0.
','bool','Stories'); INSERT INTO `vars` VALUES ('anon_user_nick','Anonymous Hero','The nickname which will be used for the default anonymous user.','text','General'); INSERT INTO `vars` VALUES ('anon_user_group','Anonymous','The group which the standard anonymous user is a part of (most likely, this will be \"Anonymous\").','text','General'); INSERT INTO `vars` VALUES ('blocked_domains','example.com,\r\nexample.net','This variable contains a comma-separated list of domains that may not be used to create a new account with. The default value lists the ever-popular `nospam.com\' and the by-definition-invalid `example.com\'.
If a user tries to create an account with an email address in one of the blocked domains, he is told so and cannot create an account with that address.
This variable replaces the numeric values for ratings with text labels. The numbers are still there behind the scenes, but this allows you to specify right in the rating form what the different numbers mean. The possible values are a comma-separated string of values, from lowest to highest (including the \'hide\' value for trusted users as the first entry). The default value is blank, meaning numbers only are used in the rating form.
\nSo users know what the averaged score means in relation to the text labels, it\'s a good idea to include the numeric value in the text label.
This variable determines the number of ratings that must be done before the comment\'s rating is calculated and its value applied to a users mojo score. The possible values are any positive number. The default value is 1.
\nThis can prevent a single malicious vote from hiding a comment if set above 1.
This variable determines whether or not multiple ratings from the same client IP address are counted when determining a comment\'s score and a user\'s mojo. The possible values are: 0) allow any number of ratings from one IP; and 1) only count the first rating from any given IP address. The default value is 0.
\nBefore turning this variable on, consider that there are several situations in which multiple ratings may appear to come from the same IP. One is the case of a lot of computers behind a firewall; all of the computers will appear to come from one IP even though there are many people and many computers. Another is the case of a computer lab, where many users may log on or off of any number of computers at different times, and two different users may rate the same comment from the same computer. This variable does not affect the normal behaviour of only allowing one rating per account.
This variable sets the numeric value of the hide rating. The possible values are any number below rating_min. The default value is blank.
\nIf this variable is blank or zero, a value one below rating_min is used.
This variable determines whether or not non-Superusers will have access to the site. The possible values are 0) everybody has access, as normal; and 1) only accounts in the Superuser group will be allowed normal access. The default value is 0.
\nThis variable should only be set to 1 when you are making changes to the site or upgrading the code, and want to deny general access while still having access yourself. When this variable is set to 1, all non-Superuser accounts will be sent 503 Service Unavailable, which you can then configure however you like via Apache\'s ErrorDocument directive. If set to 1, make sure not to log out, or you will have to change it back to 0 via the mysql shell. The group which can access the site when this variable is active is not configurable.
This variable determines whether or not the \'main\' op (front page request, no path) will allow an EVAL block in its URL Templates field. The possible values are: 0) do not allow EVALs; and 1) allow EVALs. The default value is 0.
\nThis is useful if you have subdomains that you want to have different front pages, such as using news.mysite.org instead of www.mysite.org/section/news, or nickname.mysite.org instead of www.mysite.org/user/nickname/diary. To use the domain name as part of the path, the variable use_host_parse must be turned on. See the Scoop Admin Guide for details on Ops and how they use EVAL blocks.
This variable determines whether or not visitors should be tracked for the \"who\'s online?\" box. The possible values are: 0) do not track visitors; and 1) track visitors. The default value is 0.
\nThis only keeps user ID, IP address, and a timestamp, it does no other hit tracking. It is really only useful for seeing when a user last requested a page from your site.
This variable determines whether or not Scoop will provide a link to pay for ads or subscriptions via credit card. The possible values are: 0) do not offer credit card payments as an option; or 1) offer credit card payments as an option. The default value is 0.
\nTo use credit card payments, you must have an SSL-enabled webserver, a certificate, and a credit card merchant account. Scoop currently only supports the Linkpoint credit card processor, which requires a proprietary module. If you want to use credit card payments through scoop, email rusty@kuro5hin.org for help, he has very reasonable rates.
This variable determines whether or not Scoop will provide a link to pay for ads or subscriptions via paypal. The possible values are: 0) do not offer paypal as an option; or 1) offer paypal as an option. The default value is 0.
\nTo use paypal payments, you must have a paypal account. If you will be doing any kind of traffic, you will probably find that their free account is not sufficient, and you have to go with one of their pay accounts.
This variable contains the email address associated with your Paypal account and is used to receive payments from advertising or subscriptions. The default value is an invalid email address.
To set up payment processing, see the Scoop Admin Guide.
This variable is used as the from email address used by Scoop when sending user creation emails. The possible values are any valid email address, or blank. If blank, the email address set in the variable local_email will be used instead.
\nThis email address should probably be one you check regularly. Since members are sent email from this address, they are likely to think that they can send to it as well, if they have any questions. If this email address is not valid, nobody will be able to create accounts.
This variable determines whether or not users will be allowed to create multiple-choice polls (checkboxes) as well as single choice (radio).
','bool','Polls'); INSERT INTO `vars` VALUES ('use_alt_image_dir','1','This variable determines whether or not Scoop will use the alternate image servers listed in the variable image_mirrors. Turning this on when there are no alternate image servers listed will have no effect.
','bool','General'); INSERT INTO `vars` VALUES ('use_ratings','1','This variable turns the entire rating system on and off. FIXME: not implemented yet.
','bool','Comments'); INSERT INTO `vars` VALUES ('image_mirrors','Australia,http://au.example.com/images\r\nEurope,http://www.bigmirrorsite.fi/scoopsite/images','This variable defines the names and URLs of any alternate image servers you may have, so the users can choose an image server closer to them if necessary. This variable has no effect unless the variable use_alt_image_dir is set to 1.
\r\n\r\nThe format for this variable is one image mirror per line; each line consists of a descriptive name, a comma, and the URL of the mirrored image directory, without a trailing slash. The default value is invalid.
\r\n\r\nThe default value for the image directory is set in the User Preferences Admin Tool, in the \'imagedir\' preference.
','tarea','General'); INSERT INTO `vars` VALUES ('first_login_page_order','User Info','This variable determines which prefs page(s) the user sees first when first logging in, if the variable show_prefs_on_first_login is set. The possible values are any list of valid prefs page names, separated by commas. The default value is \'Protected, User Info\'. This value is strongly recommended as it encourages the user to change his password immediately.
','text','General'); INSERT INTO `vars` VALUES ('allow_event_stories','1','This variable determines whether or not events can have stories attached to them. The possible values are: 0) events cannot have stories attached; and 1) events can have stories attached.
Events can have multiple stories attached. Event stories are stored in the section named in event_story_section. Whether or not individual users can attach a story to an event is determined by the specific event\'s permissions. This variable has no effect unless use_calendars is on.
This variable determines whether or not users may have their own personal calendar views, and may subscribe to other calendars. The possible values are: 0) require explicit calendars to be requested; and 1) users may have a personalized calendar view which combines several calendars\' events.
If allow_user_calendars is on or if you are setting up more than one site calendar, turning this on is recommended. If this is off, the calendar named in default_calendar_id is used if no calendar is explicitly selected. This variable has no effect unless use_calendars is on.
This variable determines whether or not users can have their own individual calendars. The possible values are: 0) only admin-created calendars are permitted; and 1) users may create their own calendars as well.
This variable has no effect unless use_calendars is on.
This variable determines whether or not the entire event calendar system is used at all. The possible values are: 0) do not use calendars; and 1) use calendars.
See all of the other Site Controls in the Events category for further configuration.
The number of navigation elements on either side of \"today\" in the calendar views. The possible values are any positive integer. The default value is 4.
The value chosen should be big enough to allow the user to easily navigate the calendar, but small enough that it doesn\'t wrap the navigation in ugly ways. This variable has no effect unless use_calendars is on.
This variable sets the calendar ID number to be used when no calendar ID is specified on the event submission form. The default value is 1 (the site global calendar, included by default).
This variable has no effect unless use_calendars is on.
This variable sets the number of different event properties a user can use in one event search query. The possible values are any positive integer. The default value is 3.
This should be set to a number high enough to allow reasonably flexible searching, but not so high that the search form is over-complicated.
The name of the section used for stories attached to events. The possible values are any internal section name.
If the section named here does not exist, event stories won\'t be posted properly. This variable has no effect unless use_calendars and allow_event_stories are on.
This var can be used to change the formatting style of default dates, such as those displayed in story and comment info. If you\'re happy with the way Scoop does them, then leave this blank. If you want to change them, you may put in a formatting template here which uses the date formatting strings of your database. The formatting codes for mysql are all described here: http://dev.mysql.com/doc/mysql/en/Date_and_time_functions.html (scroll down to the DATE_FORMAT() function). For Postgres, prehaps someone could add a link here to those codes.
\r\n\r\nFor example, the Scoop default formatting template for mysql would be: \"%a %b %D, %Y at %r |zone|\" (or %T instead of %r if you have \"time_24h_format\" set). Note that this will override time_24h_format if you change it -- Scoop will just use whatever you put here.
\r\n\r\nSpecial keys:
\r\nThis var can be used to change the formatting style of short dates, such as those displayed in search results, the admin story list, and a couple other places. If you\'re happy with the way Scoop does them, then leave this blank. If you want to change them, you may put in a formatting template here which uses the date formatting strings of your database. The formatting codes for mysql are all described here: http://dev.mysql.com/doc/mysql/en/Date_and_time_functions.html (scroll down to the DATE_FORMAT() function).
\r\n\r\nFor example, the Scoop default formatting template for mysql would be: \"%m/%d/%Y %r |zone|\" (or %T instead of %r if you have \"time_24h_format\" set).
\r\n\r\nSpecial keys:
\r\nThis var can be used to change the formatting style of \"week month day\" dates, such as those produced by the \"titlesonly\" mode of getstories(). To be honest, I\'m not sure where these are used. If you\'re happy with the way Scoop does them, then leave this blank. If you want to change them, you may put in a formatting template here which uses the date formatting strings of your database. The formatting codes for mysql are all described here: http://dev.mysql.com/doc/mysql/en/Date_and_time_functions.html (scroll down to the DATE_FORMAT() function).
\r\n\r\nFor example, the Scoop default formatting template for mysql would be: \"%W %M %D\".
\r\n\r\nSpecial keys:
\r\n\r\nThis should actually be more secure than the random password method, since if the initial email is intercepted, the attacker still won\'t know the actual account password, and thus will be unable to hijack the account. It should also be easier for users to deal with.\r\n
\r\nIf you are upgrading from an older version of Scoop, and wish to enable this feature, you\'ll want to edit several of the blocks in the Accounts category, to remove the references to changing your password. You\'ll also need to add the box \"signup_password\" to the block new_user_html, and replace the username and password lines in the new_user_email block with the link \"|url|/activate/|pass|\".\r\n','bool','Security'); INSERT INTO `vars` VALUES ('use_diaries','1','Set to one to use diaries on this site.','bool','Stories'); INSERT INTO `vars` VALUES ('tag_threshold_classes','1,tag-popularity-1\r\n5,tag-popularity-5\r\n10,tag-popularity-10\r\n15,tag-popularity-15\r\n','Tag Count Threshholds for altering the font styling for each tag on the all tags page depending on what story count threshold it meets. Each threshold is on a line by itself, and consists of two parts: the number of stories associated with a given tag, and the CSS class name used for that tag. The styling of the CSS classes named here is done in the block main_css.','tarea','Tags'); INSERT INTO `vars` VALUES ('use_tags','0','Turns the \"tag\" categorization system on or off. Tags are user-input freeform story categories. Any story can have any number of associated tags. Tags are input as a simple comma-delimited string of words, and can only consist of alphanumeric characters (a-z, A-Z, 0-9).','bool','Tags'); INSERT INTO `vars` VALUES ('shared_db_tables','users userprefs pref_items','Space Seperated list of tables to be retrieved from master_db if use_shared_database is true','text','Shared Database'); INSERT INTO `vars` VALUES ('use_shared_db','0','Enable use of shared user accounts across two mysql databases on the same server.','bool','Shared Database'); INSERT INTO `vars` VALUES ('shared_db_name','scoop','Name Of the database from which to read the tables listed in shared_tables','text','Shared Database'); INSERT INTO `vars` VALUES ('max_title_len','100','The maximum length in characters a title can be.','num','Stories'); INSERT INTO `vars` VALUES ('min_intro_chars','0','The minimum number of characters that can be used in a story. The default is 0, which disables use of this. It works much the same as min_intro_words. Only one of the two should be used.','num','Stories'); INSERT INTO `vars` VALUES ('min_intro_words','300','The minimum number of words that can be used in a story. The default is 300. 0 disables this feature. It works much the same as min_intro_chars. Only one of the two should be used.','num','Stories'); INSERT INTO `vars` VALUES ('use_editorial_comments','0','Use editorial type comments at all. If unchecked, we won\'t include anything that refers to ed comments.','bool','Comments'); INSERT INTO `vars` VALUES ('require_tags','0','If this var is set, users must submit at least one tag when they submit a story.','bool','Tags'); INSERT INTO `vars` VALUES ('tu_perms','zero_rate','Comma seperated list of special permissions that trusted users can have. \"zero_rate\" is the default provided, but others can be added\nas well.','text','Security'); UNLOCK TABLES; /*!40000 ALTER TABLE `vars` ENABLE KEYS */; -- -- Table structure for table `viewed_stories` -- DROP TABLE IF EXISTS `viewed_stories`; CREATE TABLE `viewed_stories` ( `uid` int(11) NOT NULL default '0', `sid` varchar(20) NOT NULL default '', `lastseen` int(11) NOT NULL default '0', `highest_idx` int(11) NOT NULL default '0', `hotlisted` tinyint(4) NOT NULL default '0', PRIMARY KEY (`uid`,`sid`), KEY `hotlist_idx` (`uid`,`hotlisted`) ) TYPE=MyISAM; -- -- Dumping data for table `viewed_stories` -- /*!40000 ALTER TABLE `viewed_stories` DISABLE KEYS */; LOCK TABLES `viewed_stories` WRITE; UNLOCK TABLES; /*!40000 ALTER TABLE `viewed_stories` ENABLE KEYS */; -- -- Table structure for table `whos_online` -- DROP TABLE IF EXISTS `whos_online`; CREATE TABLE `whos_online` ( `ip` varchar(16) NOT NULL default '', `uid` int(11) NOT NULL default '0', `last_visit` timestamp NOT NULL, PRIMARY KEY (`ip`,`uid`) ) TYPE=MyISAM; -- -- Dumping data for table `whos_online` -- /*!40000 ALTER TABLE `whos_online` DISABLE KEYS */; LOCK TABLES `whos_online` WRITE; UNLOCK TABLES; /*!40000 ALTER TABLE `whos_online` ENABLE KEYS */; /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; /*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */; /*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */; /*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;
%%norm_font%%by %%name%% %%email%% on %%date%%\r\n
%%user_info%%%%edit_user%% %%url%%%%norm_font_end%%\r\n