@@ -85,7 +85,7 @@ if(uLEVEL > 3) accessDenied();

 				$news->assign("newsdate", date("$dateformat $timeformat", $stories['date']) );

 				$news->assign("oddeven", ($count % 2 ? "even" : "odd"));

 				if($newscomments == "1")

-					$news->assign("newscomments", "<a href=\"news.php?action=newsstory&amp;nid=".$stories['nid']."\">".$stories['comments']." "._COMMENTS."</a>");

+					$news->assign("newscomments", "<a href=\"ffnews.php?action=newsstory&amp;nid=".$stories['nid']."\">".$stories['comments']." "._COMMENTS."</a>");

 				if(isADMIN) 

 					$news->assign("adminoptions", "<a href=\"admin.php?action=news&amp;form=".$stories['nid']."\">"._EDIT."</a> | <a href=\"admin.php?action=news&amp;delete=".$stories['nid']."\">"._DELETE."</a>");

 				$count++;

@@ -26,6 +26,6 @@

 if(!defined("_CHARSET")) exit( );

-dbquery("INSERT INTO ".TABLEPREFIX."fanfiction_blocks(`block_name`, `block_title`, `block_status`, `block_file`, `block_variables`) VALUES('news', 'Site News', '0', 'news/news.php', '');");

-$blocks["news"] = array("title" => "Site News", "status" => "1", "file" => "news/news.php", "num" => "3");

+dbquery("INSERT INTO ".TABLEPREFIX."fanfiction_blocks(`block_name`, `block_title`, `block_status`, `block_file`, `block_variables`) VALUES('news', 'Site News', '0', 'news/ffnews.php', '');");

+$blocks["news"] = array("title" => "Site News", "status" => "1", "file" => "news/ffnews.php", "num" => "3");

 ?>

\ No newline at end of file

@@ -41,7 +41,7 @@ if(!defined("_CHARSET")) exit( );

 		$news->newBlock("newsbox");

 		//assign values

-		if(!empty($blocks['news']['sumlength']) && isNumber($blocks['news']['sumlength'])) $newsStory = truncate_text($stories['story'], $blocks['news']['sumlength'])."<div class='newsReadMore'><a href='news.php?action=newsstory&amp;nid=".$stories['nid']."'>"._READMORE."</a></div>";

+		if(!empty($blocks['news']['sumlength']) && isNumber($blocks['news']['sumlength'])) $newsStory = truncate_text($stories['story'], $blocks['news']['sumlength'])."<div class='newsReadMore'><a href='ffnews.php?action=newsstory&amp;nid=".$stories['nid']."'>"._READMORE."</a></div>";

 		else $newsStory = format_story($stories['story']);

 		$news->assign("newstitle" , $stories['title'] );

 		$news->assign("newsstory" , $newsStory);

@@ -51,7 +51,7 @@ if(!defined("_CHARSET")) exit( );

 		$news->assign("newsid", $stories['nid']);

 		$news->assign("skindir", $skindir);

 		if($newscomments)

-			$news->assign("newscomments", "<a href=\"news.php?action=newsstory&amp;nid=".$stories['nid']."\">".$stories['comments']." "._COMMENTS."</a>");

+			$news->assign("newscomments", "<a href=\"ffnews.php?action=newsstory&amp;nid=".$stories['nid']."\">".$stories['comments']." "._COMMENTS."</a>");

 		if(isADMIN) 

 			$news->assign("adminoptions", "<a href=\"admin.php?action=news&amp;form=".$stories['nid']."\">"._EDIT."</a> | <a href=\"admin.php?action=news&amp;delete=".$stories['nid']."\">"._DELETE."</a>");

 		$count++;

deleted file mode 100644

@@ -1,46 +0,0 @@

-- Ability to remove Featured Story status from Admin panel as well as retire a Featured Story.  You can also now 

-do this when editing a story.

-- Ability to edit and delete news comments from news archive page.

-- Time format in settings.  Removed separate news date format.

-- Added pagination in news.php

-- Ability to set your own classifications in addition to warnings and genres (i.e. Spoilers, Episode Related, 

-Pairings, Language, Story Length, Story Type)

-- Ability to add custom pages from the admin panel.

-- You can now customize the up and down arrows used throughout the script in the same way the other graphics 

-(stars, etc) can be customized.  The variables are $up and $down

-- Added pagination to individual series page.

-- Story counts are back. :)

-- Moved the javascript into header.php so no more problems with the formselect.js not regenerating.  The info will 

-get pulled each time the page loads.

-- Added Table of Contents link to the storyblock and viewstory page for stories.

-- Changed admin links for featured stories in story block to let you either remove or retire the feature.

-- Co-authors :)  Yes. plural.

-- Chapter end notes.

-- Story notes.

-- The validation function in the admin panel now uses storyblock.php for a more consistent look of story information 

-across the site.

-- When previewing a story in the the add/edit story functions, the script now uses storyblock.php for a more consistent 

-look for story information across the site.

-- The default yes and no letters (subject and text) when validating stories can now be customized using {variables} for:

-	{sitename}- the name of the site;

-	{adminname} - the penname of the admin sending the letter (text of letter only)

-	{rules} - a link to the submission rules (text of letter only)

-	{storytitle} - the title of the story

-	{chaptertitle} - the title of the chapter within the story

-- You can now add custom admin panels.

-- The main admin page will now tell you how many stories are in the validation queue. So does the info block.

-- Session and cookie variables will now use a sitekey so that multiple sites on the same domain won't have problems with crossed login info.

-- News comments are now saved under uid instead of penname so that changes in penname will carry over to comment info.

-- TinyMCE can now be toggled on/off on the page.

-- Members can now turn tinyMCE and story indexes on/off for themselves

-- Members can choose the default story sort for themselves.

-- Challenges have been made into an optional module you can install and uninstall as you choose

-- Admins can now decide whether or not to allow anonymous challenges

-- The number of responses to a challenge is now listed in the information for the challenge.

-- Maintenance mode.

-- Action log.

-- Stories updated within the time frame of your "recent days" setting will now also be marked as "New!" (you can also define your own text or assign a graphic using $new in variables.php)

-- You can now define what "Top 10's" lists to include and add your own through the admin panel.

-- You can now "hide" skins from regular members through the admin panel.

-- Customized fields in the author profile page.

-

deleted file mode 100644

@@ -1,68 +0,0 @@

-Note: This is not a tutorial on how to update a skin.  It's pretty much my notes on what will eventually have to

-go into a tutorial.  Therefore, there's probably things missing.  We'll be working on a real tutorial.

-Optional additions to listings.tpl for stories:

-

-{toc} - Table of Contents link to story index 

-{count} - The view/read count

-{new} - The text "New!" for new stories or alternately a graphic (use the URL to the graphic from the main directory).

-{featuredtext} - The words "Featured Story" or "Past Featured Story" to use instead of the graphics if you wish

-

-This is already done for you in the default_tpls folder.

-

-Also in listings.tpl you will need to add {comment} to both the seriesblock and storyblock sections.  This 

-will be used for favorite stories to show the member's comments about the story. Style the comment with

-favcomment.tpl.  See the default_tpls folder for an example. 

-

-In viewstory.tpl optional addtion:

-

-{toc} - Table of Contents link to story index

-

-The story and chapter notes (beginning and end) have been moved into blocks in viewstory.tpl  This will let you

-style them any way you wish and also hide those blocks when there are no notes to display.  (See the default_tpls

-for an example)

-

-For any new classifications you add you will need to modify listings.tpl, series_title.tpl, and optionally 

-viewstory.tpl and storyindex.tpl to include those additional classifications.  Optionally, you can use {classifications}

-to include all your classifications at one time.  The default_tpls/listings.tpl uses {classifications}

-

-In reviews.tpl you can now add a quick review form to the bottom of the list of reviews instead of the 

-"Submit a Review" link using the {reviewform} variable.  Already done in default_tpls.

-

-The reviewsblock has been pulled into its own .tpl so it can be reused in places other than the reviews page 

-(such as the user panels)

-

-The profile section of the user page has been pulled into its own .tpl, again so that it can be re-used.  

-It should also make it easier for people modding skins.  There is also now a setting in your admin settings for

-whether or not to show the profile at the top of the view user page all the time or only when it's selected.

-

-In user.tpl you no longer have individual variables for the tabs.  Instead it's been put into a block to 

-allow more tabs to be added dynamically without editing the tpl's each time.

-

-<!-- START BLOCK : paneltabs -->

-<div {class}>{link} {count}</div>

-<!-- END BLOCK : paneltabs -->

-

-You can also use {linkcount} to include the count of items inside the link instead of next to it. You don't have 

-to use <div>'s.  This is just an example.

-

-Rather than have the news archive link hardcoded into the news block at the bottom, I've assigned it to a global 

-link (i.e. {home}) so that you can put it where you want.  It's assigned as {newsarchive}

-

-There are a large number of new links you can add to your skins and the menu block.  The list is in the "Page 

-Links" section of the admin panel.

-

-In default_tpls, we changed the "classification" CSS class to "label".  It's more clear what the purpose is

-and shorter. :)

-

-For the new profile block, if you add new fields to the profile information, you will need to either add the 

-individual links such as {yahoo} or remove the individual links and make use of the new {authorfields} variable

-that displays the complete list of custom fields.  If you're creating skins for the use of others, you're 

-encouraged to use {authorfields} instead of the individual links.

-

-The $current variable for the index page was changed to home to solve a conflict with the variable name for the

-pagelink.  This will affect skins like Romance that use the current setting as the name of a containing div.

-

-For the featured, recent, and random blocks, if you use the .tpl option you'll need to remove the name of the 

-block from each of the variables.  For instance {recenttitle} will now be {title}.  This is because each of

-these blocks now uses the storyblock.php code.  Therefore, you can also add any of the information you can

-use in the listings.tpl to your random, featured, and recent blocks. 

deleted file mode 100644

@@ -1,274 +0,0 @@

-<html>

-

-<head>

-<meta http-equiv="Content-Language" content="en-us">

-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">

-<meta name="ProgId" content="FrontPage.Editor.Document">

-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">

-<title>Converting 1</title>

-</head>

-

-<body>

-

-<p align="center">Converting 1.1 skins to 3.0 skins.</p>

-<p>This file is a work in progress.&nbsp; We'll flesh it out later as we all get 

-  more expertise with converting 1.1 skins to the 3.0 format.</p>

-<p>1.&nbsp; Open a new folder for your converted skin.</p>

-<p>2.&nbsp; Open the default.tpl file in the skin you wish to convert.&nbsp; 

-Everything <i><b>before</b></i> {output} transfer into header.tpl in your new 

-folder then enclose it with start and close tags for the header block.&nbsp; A sample header.tpl might look like this.</p>

-<pre></pre>

-

-</div>

-

-<p style="margin: 0 5%; border: 1px solid #000;">&nbsp;&lt;!-- START BLOCK : header --&gt;<br>

-&lt;body&gt;<br>

-   

-&lt;div id=&quot;<span style="background-color: #FFFF00">{</span><span 

-style="background-color: #FFFF00">page_id</span><span 

-style="background-color: #FFFF00">}</span>&quot;&gt;<br>

-       

-&lt;div id=&quot;header&quot;&gt;<br>

-           

-&lt;div id=&quot;banner&quot;&gt;<br>

-               

-&lt;div id=&quot;skin&quot;&gt;<span style="background-color: #FFFF00">{</span><span 

-style="background-color: #FFFF00">skinchange_content</span><span 

-style="background-color: #FFFF00">}</span>&lt;span style=&quot;padding: 15px;&quot;&gt;<span 

-style="background-color: #FFFF00">{</span><span 

-style="background-color: #FFFF00">rss</span><span 

-style="background-color: #FFFF00">}</span>&lt;/span&gt;&lt;/div&gt;<br>

-           

-&lt;/div&gt;<br>

-           

-&lt;div id=&quot;menu_container&quot;&gt;<br>

-<span style="background-color: #FF00FF">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 

-{home}&amp;nbsp;{recent}&amp;</span><span style="background-color: #FF00FF">nbsp;{catslink</span><span 

-style="background-color: #FF00FF">}&amp;nbsp;{authors}&amp;nbsp;{titles}&amp;nbsp;{help}<br>

-                

-&amp;nbsp;{search}&amp;nbsp;{login}&amp;nbsp;{logout}&amp;nbsp;{adminarea}</span><br>

-           

-&lt;/div&gt;<br>

-       

-&lt;/div&gt;<br>

-   

-&lt;div id=&quot;mainpage&quot;&gt;<br>

-&lt;!-- END BLOCK : header --&gt;</p>

-<p>The {page_id} variable was new to 2.0.&nbsp; This variable gives you a unique 

-  name to use in the css for each page.  In the example above it's used as 

-  a containing tag.  

-<p>The {rss} variable 

-defines where the orange rss image link appears.

-<p>The other variable highlighted in yellow is a mod some people had previously 

-  installed.  If you have previously added the skin change mod change {skinform} 

-  to {skinchange_content} to include that block.  You will also need to activate 

-  that block and set it to the correct status in the blocks page in the admin 

-  area.

-<p>The links highlighted in pink are still available in 3.0.&nbsp; You can convert 

-  these links to the new menu block if you wish or leave them as is.

-<p>3. From your original default.tpl again, select everything <i>

-<b>after</b></i> {output} and place it in your footer.tpl<p>&nbsp;<p style="margin: 0 5%; border: 1px solid #000;">&lt;!-- START BLOCK : 

-footer --&gt;<br>

-   

-&lt;/div&gt;<br>

-       

-&lt;div id=&quot;footer&quot;&gt;<span style="background-color: #FF00FF">{footer}</span>&lt;/div&gt;&lt;/div&gt;<br>

-       

-&lt;div id=&quot;footermenu&quot;&gt;<span style="background-color: #FFFF00">{</span><span 

-style="background-color: #FFFF00">tos}{rules}{contactus</span><span 

-style="background-color: #FFFF00">}</span>&lt;/div&gt;<br>

-&lt;!-- END BLOCK : footer --&gt;<p>The {footer} variable is the same as in 1.1<p>

-The other three variables you see in yellow are new page links added in 2.0. <p>&nbsp;<div 

-align="center">

-  <center>

-  <table border="1" cellpadding="3" cellspacing="0" 

-  style="border-collapse: collapse" bordercolor="#111111">

-    <tr>

-      <th width="100%" colspan="2">New Page Links in 2.0</th>

-    </tr>

-    <tr>

-      <td width="50%">{tos}</td>

-      <td width="50%">Terms of Service</td>

-    </tr>

-    <tr>

-      <td width="50%">{rules}</td>

-      <td width="50%">Submission Rules</td>

-    </tr>

-    <tr>

-      <td width="50%">{contactus}</td>

-      <td width="50%">Contact Us</td>

-    </tr>

-    <tr>

-      <td width="50%">{featured}</td>

-      <td width="50%">Featured Stories</td>

-    </tr>

-    <tr>

-      <td width="50%">{members}</td>

-      <td width="50%">Members</td>

-    </tr>

-    <tr>

-      <td width="50%">{series}</td>

-      <td width="50%">Series</td>

-    </tr>

-    <tr>

-      <td width="50%">{challenges}</td>

-      <td width="50%">Challenges</td>

-    </tr>

-    <tr>

-      <td width="50%">{tens}</td>

-      <td width="50%">The Tens</td>

-    </tr>

-  </table>

-  </center>

-</div>

-<p>&nbsp;<div align="center">

-  <center>

-  <table border="1" cellpadding="3" cellspacing="0" 

-  style="border-collapse: collapse" bordercolor="#111111">

-    <tr>

-      <th width="100%" colspan="2">Changed from 1.1</th>

-    </tr>

-    <tr>

-      <td width="50%">{authors}</td>

-      <td width="50%">Authors (was members list)</td>

-    </tr>

-  </table>

-  </center>

-</div>

-<p>3.&nbsp; In your new skin folder create a new file called variables.php.&nbsp; 

-As this is a conversion from 1.1 to 2.0 you will want to set some options in the 

-blocks settings.</p>

-<p style="margin: 1em 5%; border: 1px solid #000;">&lt;?php<br>

-$blocks[&quot;info&quot;][&quot;status&quot;] = '1'; <br>

-$blocks[&quot;info&quot;][&quot;style&quot;] = '1';<br>

-$blocks[&quot;login&quot;][&quot;status&quot;] = '1';<br>

-$blocks[&quot;news&quot;][&quot;status&quot;] = '1';<br>

-$blocks[&quot;news&quot;][&quot;tpl&quot;] = '1';<br>

-$blocks[&quot;recent&quot;][&quot;status&quot;] = '1';<br>

-$blocks[&quot;recent&quot;][&quot;tpl&quot;] = '1';<br>

-$blocks[&quot;categories&quot;][&quot;status&quot;] = '1';<br>

-$blocks[&quot;categories&quot;][&quot;columns&quot;] = '0';<br>

-$blocks[&quot;categories&quot;][&quot;tpl&quot;] = '1';<br>

-$blocks[&quot;featured&quot;][&quot;tpl&quot;] = '1';<br>

-$blocks[&quot;featured&quot;][&quot;status&quot;] = '1';<br>

-?&gt;</p>

-<p>Technically, this is probably overkill.&nbsp; You will definitely want to set 

-"tpl" to 1 for categories, recent, and featured if your skin uses them. If 

-in the past you used {totalstories} and {totalauthors}, activate the info block 

-and set the style to 2.  Note that this will also give you {totalmembers} 

-to include.  All of these blocks should be set to a "status" of 1 to 

-include them only on the index page.   

-If your skin doesn't use them, I suggest you set the status to 0.  It will 

-make the page load a tiny bit faster, but for busy sites tiny bits will add up.</p>

-<p>4. Copy the 1.1 index.tpl skin into your new folder and open it.&nbsp; Locate 

-the point where your header information stops.  Delete everything before 

-that and replace it with:</p>

-<p>&lt;!-- INCLUDE BLOCK : header --&gt;</p>

-<p>Find where your footer information starts and replace everything below it with</p>

-<p>&lt;!-- INCLUDE BLOCK : footer --&gt;</p>

-<p>We took care of all the blocks except news in the previous step.&nbsp; Find 

-where your news is included in the index.tpl  and replace the block with {news_content}  

-You can also remove {newspageprev} and {newspagenext} as those are replaced by 

-the newsarchive link and are included in {news_content}.  To style the news 

-archive link use #newsarchive in your style.css.  The #newsarchive id is a 

-div around the archive link.</p>

-

-<p>5. Copy your newsbox.tpl file into the new folder.&nbsp; No changes need to 

-be made to that.  Note however that the style will be carried over to the 

-news archive.</p>

-

-<p>6. Open your style.css and style the following elements.&nbsp; The 

-information after the dash is suggested styles to match 1.1 where possible or 

-just general ideas</p>

-

-<p>#pagetitle - text-align: center; font-size: 150%; margin: 1ex;<br>

-#alphabet, #pagelinks - text-align: center; margin: 1em;<br>

-LABEL - font-weight: bold;<br>

-#sort - text-align: center; margin: 1ex;&nbsp; (Sort options on categories.php)<br>

-#profile #sort - text-align: right;   (Sort options on the viewuser 

-page)</p>

-

-<p>.sectionheader - text-align: center; font-weight: bold;&nbsp; (this is the 

-&quot;Series&quot; and &quot;Stories&quot; sub-headers)<br>

-#titleblock&nbsp; - margin: 0 10%; border: 1px solid #000;&nbsp; <br>

-(this is the title block at the top of the series and challenges pages when a 

-single series/challenge is listed)</p>

-

-<p>To convert the tabs in the viewuser page from 1.1 to 2.0 you'll need to add 

-the #tabs style group to your style.css.  This is the tabs information for 

-the skin in default_tpls. It's a good place to start.  2.0 gives you more 

-options in styling this section of the viewuser page, but this styling will be 

-close to what you previously used in 1.1 with some tweaking.  The #active 

-styling is the tab currently active in the window.  In 1.1 this would have 

-been the table cell with the background color.</p>

-

-<p>#tabs {<br>

-padding: 0;<br>

-margin: 0;<br>

-clear: both;<br>

-border-top: 3px double #000;<br>

-border-bottom: 3px double #000;<br>

-}<br>

-<br>

-#tabs DIV{ <br>

-width: 33%;<br>

-float: left;<br>

-color: #000;<br>

-text-align: center;<br>

-background: #CCC; <br>

-font-size: 11pt;<br>

-}<br>

-<br>

-#tabs #centertab {<br>

-background: transparent;<br>

-border-right: 3px double #000;<br>

-border-left: 3px double #000;<br>

-width: 98%;<br>

-}<br>

-<br>

-#tabs a { color: #000; }<br>

-#tabs a:active, a:hover { text-decoration: none; color: #555; }<br>

-<br>

-#tabs #active { background: #555; width: 34%; color: #FFF; }<br>

-#tabs #active a { color: #FFF; }<br>

-#tabs #active a:active, a:hover { text-decoration: none; color: #555; }</p>

-

-<p>7. The last thing you'll probably need to do is convert your storyblock.tpl.&nbsp; 

-If you wish, you can rely on the default and set the appearance of both the 

-stories and series blocks through your style.css.  The default uses the .listbox 

-class with child classes of .title, .tail, .adminoptions, .content, and 

-.classification.  You can also use .odd and .even to alternate style of 

-blocks every other one.</p>

-

-<p>/* Formatting for the divs for series and stories.&nbsp; */<br>

-.listbox { margin: 0 5%; border: 2px solid #900; margin-bottom: 1em; background: 

-#FFF; background-position: 0 5px;}<br>

-.listbox .title { font-weight: bold; padding: 4px; color: #900; border-bottom: 

-3px double #900;}<br>

-.listbox .title a:link { color: #900; text-decoration: underline;}<br>

-.listbox .title a:visited { color: #C66; text-decoration: underline;}<br>

-.listbox .title a:hover { color: #900; text-decoration: underline overline; }<br>

-.listbox .content { padding: 5px; padding-top: 10px; padding-bottom: 10px;}<br>

-.listbox .tail, .listbox .respond { border-top: 3px double #900;}<br>

-.listbox .classfication { font-weight: bold; }<br>

-/* End listbox formatting. */</p>

-

-<p>If you don't want to use the default, I suggest you copy listings.tpl from 

-the default_tpls folder then paste the contents of your storyblock.tpl into the 

-storyblock section then replicate it for the series section.  Pay attention 

-to the additional information for the story block.  You may now include 

-challenges and series information.  There are also adminoptions to be 

-included as well.  If you don't use the default you will also need to 

-separately style the challenges block (if you choose to use challenges on your 

-site).  

-Copy challenges.tpl from the default_tpls folder and style it as you wish. 

-<u>Do<b><i> NOT </i></b>save it back to default_tpls. </u><b>&nbsp;</b>Save it 

-to your skin's folder.</p>

-

-<p>That's a basic conversion from 1.1 to 2.0.&nbsp; You can further define other 

-areas of the script such as the title blocks in series and challenges.  If 

-you wish to change the look of these areas, copy the applicable .tpl from 

-default_tpls and make your changes.  Then save that .tpl to your skin 

-folder NOT back to the default_tpls.&nbsp; </p>

-

-</body></html>

\ No newline at end of file

deleted file mode 100644

@@ -1,110 +0,0 @@

-<html>

-

-<head>

-<meta http-equiv="Content-Language" content="en-us">

-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">

-<meta name="ProgId" content="FrontPage.Editor.Document">

-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">

-<title>Creating Blocks</title>

-</head>

-

-<body>

-

-<h2 align="center">Creating Blocks</h2>

-<p>For those that want to create their own blocks to share with others or just 

-  tweak the ones included already, here's the basics.  There are two files 

-  needed for each block: blockname.php an init.php.  Technically, if you 

-  added the block manually, you wouldn't need the init.php file.  It is only 

-  used when the block is first initialized, and can be deleted afterward.  

-  Though I would suggest keeping a backup somewhere, just in case.</p>

-<p>The init.php file is very simple composed simply of a mysql statement that 

-  adds the block tot he database.&nbsp; As in the example below.</p>

-<p>&lt;?php<br>

-  dbquery("INSERT INTO ".TABLEPREFIX."fanfiction_blocks(`block_name`, 

-  `block_title`, `block_status`, `block_file`, `block_variables`) VALUES('categories', 

-  'Main Categories', '0', 'categories/categories.php', '');&quot;);<br>

-  ?&gt;</p>

-<p>This also shows the basic parameters needed for a block: name, title, status, 

-  file, and variables.  The title can be an empty string if you don't need 

-  a title for that particular block. If the block doesn't need any variables, 

-  that too can be left empty. The file should be a subfolder/file of the blocks 

-  folder for the sake of consistency. The status should generally start off as 

-  0 for inactive.&nbsp; There are 3 status options for blocks: </p>

-<div align="center">

-  <center>

-  <table border="1" cellpadding="5" cellspacing="0" 

-  style="border-collapse: collapse" bordercolor="#111111">

-    <tr>

-      <th colspan="2">Status</th>

-      <th>&nbsp;Associated .tpl file</th>

-      <th>Appears</th>

-    </tr>

-    <tr>

-      <td>0</td>

-      <td>Inactive</td>

-      <td>The block is off. </td>

-      <td>nowhere</td>

-    </tr>

-    <tr>

-      <td>1</td>

-      <td>Active</td>

-      <td>The block is on.</td>

-      <td>anywhere</td>

-    </tr>

-    <tr>

-      <td>2</td>

-      <td>Index only</td>

-      <td>index page only.</td>

-      <td>anywhere on the index page.</td>

-    </tr>

-    </table>

-  </center>

-</div>

-<p>&nbsp; </p>

-<p>Any default configuration you want for the block can be included in the init.php 

-  as well.  The variables are an array encoded using PHP's serialize function. 

-  For instance, the categories block currently has two options: one column and 

-  multiple columns.  The default is a single column lists.  If I were 

-  to change the init file as follows, the default would then become a multiple 

-  column list.</p>

-<p>&lt;?php<br>

-  dbquery("INSERT INTO ".TABLEPREFIX."fanfiction_blocks(`block_name`, 

-  `block_title`, `block_status`, `block_file`, `block_variables`) VALUES('categories', 

-  'Main Categories', '0', 'categories/categories.php', '".serialize(array("columns" 

-  =&gt; &quot;1&quot;)).&quot;');&quot;);<br>

-  ?&gt;</p>

-<p> When you change any of the settings for the blocks from the admin panel the 

-  information stored in the database about the block is updated.</p>

-<p>The block.php file creates the content that is placed inside the {blockname_content} 

-variable.  This content is placed inside a variable $content which is then 

-assigned to {blockname_content}  So a very simple example of a block would 

-be:</p>

-<p>&lt;?php<br>

-$content = &quot;Hello World!&quot;;<br>

-?&gt;</p>

-<p>There are two other optional files.&nbsp; The first is an admin file which 

-will be called from the admin panel to make changes to the settings in the 

-block.&nbsp; Creating one of those is for another day. </p>

-<p>The second file (or multiple files) is a language file that defines any text 

-you use in your block.  These files take the same format as the main 

-language file in the languages folder and are named similarly.  So for 

-instance, an English language file would be named en.php.  For Spanish, it 

-would be es.php. </p>

-<p>Most often, you might need to define some wording for your admin.php file.&nbsp; 

-If you need to add a language file, use the following code in either admin.php 

-or blockname.php</p>

-<p>if(file_exists(&quot;blocks/categories/{$language}.php&quot;)) include_once(&quot;blocks/categories/{$language}.php&quot;);</p>

-<p>The if(...) isn't technically necessary, but it will prevent errors if the 

-  file ends up missing.  For instance, the site's language is set to Russian, 

-  but the block doesn't have a Russian translation.  You might also want 

-  to include an else statement to load a default language file you have created 

-  if the site's chosen language is missing.</p>

-<p>if(file_exists(&quot;blocks/categories/{$language}.php&quot;)) include_once(&quot;blocks/categories/{$language}.php&quot;);<br>

-  else include_once(&quot;blocks/categories/en.php&quot;);</p>

-<p>To keep your block files secure from hackers you are strongly encouraged to 

-  include this line at the top of each file just under the &lt;?php</p>

-<p>if(!defined(&quot;_CHARSET&quot;)) exit( );</p>

-<p>&nbsp;</p>

-</body>

-

-</html>

\ No newline at end of file

deleted file mode 100644

@@ -1,973 +0,0 @@

-<html>

-

-<head>

-<meta http-equiv="Content-Language" content="en-us">

-<meta name="GENERATOR" content="Microsoft FrontPage 5.0">

-<meta name="ProgId" content="FrontPage.Editor.Document">

-<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">

-<title>Creating Skins</title>

-<style type="text/css">

-<!--

-.sample {

-	background-color: #CCCCCC;

-	margin: 1em;

-	border: 1px solid #000000;

-	padding: 1ex;

-}

-.sampleLabel {

-	margin-bottom: -1em;

-	margin-left: 1em;

-	font-weight: bold;

-}

-</style>

-</head>

-

-<body>

-

-<h2 align="center">Creating Skins - WIP</h2>

-<p>In theory, there is no limit to the number of skins you can create for your 

-site.  If you have created skins for eFiction 1.1, you won't find many differences.  The number and names of the .tpl files have changed 

-some though.  

-A complete skin will include the following files.</p>

-<div align="center">

-  <center>

-    <table border="1" cellpadding="5" cellspacing="0" 

-  style="border-collapse: collapse" bordercolor="#111111">

-      <tr> 

-        <th width="50%">.tpl file</th>

-        <th width="50%">Related pages</th>

-      </tr>

-      <tr> 

-        <td><a href="#browse">browse.tpl</a></td>

-        <td>Browse Pages</td>

-      </tr>

-      <tr> 

-        <td><a href="#categories">categories.tpl</a></td>

-        <td>Browse Categories</td>

-      </tr>

-      <tr> 

-        <td><p><a href="#comments">comments.tpl</a></p></td>

-        <td>News</td>

-      </tr>

-      <tr> 

-        <td><a href="#default">default.tpl</a></td>

-        <td>Most pages</td>

-      </tr>

-      <tr> 

-        <td><a href="#favcomment">favcomment.tpl</a></td>

-        <td>Favorites Lists</td>

-      </tr>

-      <tr> 

-        <td><a href="#footer">footer.tpl</a></td>

-        <td>All pages</td>

-      </tr>

-      <tr> 

-        <td><a href="#header">header.tpl</a></td>

-        <td>All pages</td>

-      </tr>

-      <tr> 

-        <td><a href="#index">index.tpl</a></td>

-        <td>Index</td>

-      </tr>

-      <tr> 

-        <td><a href="#listings">listings.tpl</a></td>

-        <td>Any page listing stories or series</td>

-      </tr>

-      <tr> 

-        <td><a href="#newsbox">newsbox.tpl</a></td>

-        <td>News &amp; news block</td>

-      </tr>

-      <tr> 

-        <td><a href="#printstory">printstory.tpl</a></td>

-        <td>View Story (Printable)</td>

-      </tr>

-      <tr> 

-        <td><a href="#profile">profile.tpl</a></td>

-        <td>User Profile</td>

-      </tr>

-      <tr> 

-        <td><a href="#reviewblock">reviewblock.tpl</a></td>

-        <td>Reviews</td>

-      </tr>

-      <tr> 

-        <td><a href="#reviews">reviews.tpl</a></td>

-        <td>Reviews</td>

-      </tr>

-      <tr> 

-        <td><a href="#seriestitle">series_title.tpl</a></td>

-        <td>View Series</td>

-      </tr>

-      <tr> 

-        <td><a href="#storyindex">storyindex.tpl</a></td>

-        <td>Story Table of Contents</td>

-      </tr>

-      <tr> 

-        <td><a href="#user">user.tpl</a></td>

-        <td>User Profile/Info</td>

-      </tr>

-      <tr>

-        <td><a href="#viewstory">viewstory.tpl</a></td>

-        <td>View Story</td>

-      </tr>

-    </table>

-  </center>

-</div>

-<p>Now, to quote Douglas Adams...Don't Panic!&nbsp; That's the most number of 

-  files a skin would use.  Most skins will consist of quite a few less.  

-  If you install add-on modules, those modules may require additional .tpl files 

-  which will be included with the module. </p>

-<p>Within the script files is a folder called default_tpls.&nbsp; It includes 

-  a very basic complete skin that will be used if for whatever reason your site's 

-  default skin or your member's chosen skin are missing.  If any of these 

-  .tpl files (except for header.tpl and footer.tpl) are missing the script will 

-  fall back on the files in the default_tpls folder.  Many of the tpl files 

-  are generic enough that they can easily be left to the ones in default_tpls 

-  and styled using CSS.  In addition to the .tpl files you will have a style.css 

-  file and optionally, a variables.php file.  The variables.php file allows 

-  you to override certain universal settings for this skin such as where blocks 

-  load and the graphics used for your ratings and featured stories.</p>

-<p>A fewimportant things to pay attention to when modifying the template files:</p>

-<ol>

-  <li><b>Variables</b>: Items in curly brackets are variables, i.e. {output} or 

-    {authors}. This contains the actual content that will be printed out on the 

-    page. You can surround these attributes with any kind of html that you want 

-    -- font tags, tables, whatever. Some variables are required on some of the 

-    template pages and some are optional.&nbsp;</li>

-  <li><b>Blocks</b>: These are items that generate multiple instances of content 

-    in a loop -- for example, in your index.tpl template file, you only need to 

-    indicate where the news items should display on the page with the following:<br>

-    &lt;!-- INCLUDE BLOCK : newsbox --&gt;<br>

-    This line is telling the script to include the newsbox.tpl file, and the template 

-    files will understand that it should print out several news stories in a loop, 

-    with just that one line of code. Another kind of block you may see is the 

-    following:<br>

-    &lt;!-- START BLOCK : categoriesblock --&gt;<br>

-    <br>

-    Content goes here, which will also include attributes, such as {category} 

-    or {description}<br>

-    <br>

-    &lt;!-- END BLOCK : categoriesblock --&gt;<br>

-    This is similar to the included block, except that rather than pulling in 

-    the block from another file, as in the case of the newsbox.tpl, this one is 

-    just defining the block at this very moment. As you read through the individual 

-    template file instructions below and look at the actual templates, all of 

-    this will make more sense. <b>&nbsp;Block declarations should go on lines 

-    by themselves.</b></li>

-  <li><b>Blocks vs. Blocks:&nbsp; </b>The template blocks in the .tpl files are 

-    not the same as the blocks you configure in the admin panel.  The blocks 

-    in the admin panel are "blocks" of code that generate content they 

-    place inside template variables.  The blocks in the .tpl files are "blocks" 

-    of content.  While there is some overlap, thinking of them as being separate 

-    from each other will help you keep things straight.  Each "code 

-    block" will generate two "content blocks": {blockname_title} 

-    and {blockname_content}.  You may or may not include the {blockname_title} 

-    variable in your skin.  It's up to you.  However, using the {blockname_title} 

-    in your skin means if you ever want to change the title of the block you only 

-    have to do it in one place instead of in each skin.  You assign where 

-    the block will be assigned to in the admin panel.  There are 3 choices: 

-    <br>

-      

-    <div align="center"> 

-      <center>

-        <table border="1" cellpadding="5" cellspacing="0" 

-    style="border-collapse: collapse" bordercolor="#111111">

-          <tr> 

-            <th width="50%">Status</th>

-            <th width="50%">&nbsp;Associated .tpl file</th>

-          </tr>

-          <tr> 

-            <td width="50%">Inactive</td>

-            <td width="50%">The block is off. </td>

-          </tr>

-          <tr> 

-            <td width="50%">Active</td>

-            <td width="50%">The block is on. Can appear on every page.</td>

-          </tr>

-          <tr> 

-            <td width="50%">Index Only</td>

-            <td width="50%">Appears on the index page only.</td>

-          </tr>

-        </table>

-      </center>

-    </div>

-    <p>You may also override these settings for an individual skin by placing 

-      information for that block in the variables.php file. More on that later.</li>

-  <li>The .tpl files do not have some of the usual tags at the beginning, such 

-    as <head> or <title>. That is because those tags are included 

-    in the header file. Most of the template files begin with the header block 

-    and end with the footer block except for a couple of the blocks (newsblock.tpl, 

-    comments.tpl and listings.tpl)</li>

-  <li>Using &quot;hooks&quot; various 3rd party and included modules (such as 

-    challenges) can add their own variables to these templates. Check the documentation 

-    for the modules for specific additions. &nbsp;</li>

-</ol>

-<p>Feel free to use the files in the default_tpls/ folder as templates for your 

-  own skins.  Copy the files into a new skin folder and modify them there. 

-  <strong><font color="#FF0000">Do not modify the files in default_tpls/ if at 

-  all possible. They're often used for diagnostic purposes if the site isn't functioning 

-  as expected.</font></strong>&nbsp; <u>Also, you are in no way limited to CSS 

-  for the layout of your skins.  Feel free to use tables to your heart's 

-  content.&nbsp; </u></p>

-<hr>

-<p><a name="browse"></a>browse.tpl</p>

-<p>This file controls the look of the browse pages (categories, classifications, 

-  etc.) The header, footer, and listing blocks are included in this file along 

-  with a block for the sort form that is displayed when there are story results. 

-  In addition you will want to include two other variables:</p>

-<p>You will need to start by including the header block.</p>

-<p class="sample">&lt;!-- INCLUDE BLOCK : header --&gt;</p>

-<p>And end by including the footer block.</p>

-<p class="sample"> &lt;!-- INCLUDE BLOCK : footer --&gt;</p>

-<p>{output} - Miscellaneous information on the pages including the page title.<br>

-  {otherresults} - The list of other results (challenges, series, etc.) that fit 

-  the criteria for the page.</p>

-<p>Within the sort form the following variables are used:</p>

-<p>{sortbegin} - the beginning of the sort menu form<br>

-  {charactermenu1} - A list of characters to choose from<br>

-  {charactermenu2} - A second list of characters<br>

-  {classmenu} - A dropdown list for each of the site's classification types (genres, 

-  warnings, etc.)<br>

-  {ratingmenu} - A list of ratings<br>

-  {sortmenu} - Choose how the stories will be sorted alphabetically or by most 

-  recently updated<br>

-  {completemenu} - Choose all stories or only completed stories<br>

-  {sortend} - the end of the sort menu form</p>

-<p>You may include all or none of these and in whatever order you wish, except 

-  the {sortbegin} and {sortend} variables must be at the beginning and end of 

-  the list of variables in the form.</p>

-<p class="sampleLabel">Sample: </p>

-<p class="sample">&lt;!-- INCLUDE BLOCK : header --&gt;<br>

-  {output}{otherresults}<br>

-  &lt;!-- START BLOCK : sortform --&gt;<br>

-  <div id="sortform">{sortbegin}{categorymenu} {charactermenu1} 

-  {charactermenu2} {ratingmenu} {classmenu} {sortmenu} {completemenu} {sortend}&lt;/div&gt;<br>

-  &lt;!-- END BLOCK : sortform --&gt;<br>

-  &lt;!-- INCLUDE BLOCK : listings --&gt;<br>

-  &lt;!-- INCLUDE BLOCK : footer --&gt;</p>

-<p><a name="categories"></a>categories.tpl</p>

-<p>The categories.tpl controls the look of the individual category on the categories 

-  browse page. <strong>Note:</strong> The appearance of the categories block is 

-  controlled separately through the block's admin panel. </p>

-<p>The block must start with:</p>

-<p class="sample">&lt;!-- START BLOCK : categoryblock --&gt;</p>

-<p>and end with:</p>

-<p class="sample">&lt;!-- END BLOCK : categoryblock --&gt;</p>

-<p>The following variables are available to use in the block:</p>

-<p>{image} - The image associated with that category. Note: The name of the image 

-  is set in the Categories admin panel. The image file must be in the skin's directory. 

-  If the script can't find the image it will display nothing. (In 1.1 a broken 

-  image was displayed.)<br>

-  {link} - The link to the category's browse page.<br>

-  {count} - The count of stories within that category.<br>

-  {description} - The category's description.</p>

-<p class="sampleLabel">Sample:</p>

-<p class="sample">&lt;!-- START BLOCK : categoryblock --&gt;<br>

-  {image} {link} {count} {description}<br>

-  &lt;!-- END BLOCK : categoryblock --&gt;</p>

-<p><a name="comments">comments.tpl</a></p>

-<p>This block controls the display of comments on the news.php page for a single 

-  story.&nbsp; </p>

-<p>You must start the file with:</p>

-<p class="sample">&lt;!-- START BLOCK : commentbox --&gt;</p>

-<p>and end it with:</p>

-<p class="sample">&lt;!-- END BLOCK : commentbox --&gt;</p>

-<p>This information should be placed on separate lines.&nbsp; Between these two 

-  lines the following variables should be included.</p>

-<p>{comment} - The comment from the member.<br>

-  {uname} - The member's name as a hyperlink to their profile.<br>

-  {date} - The date the comment was made.<br>

-  {adminoptions} - Options visible to the administrator when viewing the page.</p>

-<p>The variable {oddeven} is optional, you can use it to assign alternating styles 

-  to each comment.</p>

-<p class="sampleLabel">Sample:</p>

-<p class="sample">&lt;!-- START BLOCK : commentbox --&gt;<br>

-  &lt;div class=&quot;comment {oddeven}&quot;&gt;<br>

-  {comment}<br>

-  &lt;div class=&quot;commentsig&quot;&gt;- {uname} on {date}&lt;/div&gt;<br>

-  &lt;div class=&quot;adminoptions&quot;&gt; {adminoptions}&lt;/div&gt;<br>

-  &lt;/div&gt;<br>

-  &lt;!-- END BLOCK : commentbox --&gt;</p>

-<p><a name="default">default.tpl</a></p>

-<p>The majority of pages use this for their layout.&nbsp; Most likely you won't 

-  need to include it in your skin at all.</p>

-<p>You must include the <a href="#header">header</a>, <a href="#listings"> listings</a>, 

-  and <a href="#footer">footer</a> block as seen below and include the {output} 

-  variable BEFORE the listings block.  The {output} variable provides various 

-  text like the page title and alphabet list for titles. You will probably not 

-  need to replicate this file in your skin since there's nothing much to change 

-  really.</p>

-<p class="sampleLabel">Sample:</p>

-<p class="sample">&lt;!-- INCLUDE BLOCK : header --&gt;<br>

-  {output}<br>

-  &lt;!-- INCLUDE BLOCK : listings --&gt;<br>

-  &lt;!-- INCLUDE BLOCK : footer --&gt;</p>

-<p></p>

-<p><a name="favcomments"></a>favcomment.tpl</p>

-<p>In eFiction 3.0 when favorites are turned on by the admin, members have the 

-  option of not only marking a story as a favorite, but also including a comment 

-  as to why it is their favorite. The favcomment.tpl us used to display these 

-  comments in the user's profile.</p>

-<p>The block must start with:</p>

-<p class="sample">&lt;!-- START BLOCK : comment --&gt;</p>

-<p>and end with:</p>

-<p class="sample">&lt;!-- END BLOCK : comment --&gt;</p>

-<p>In addition the following variables can be used within the block:</p>

-<p>{comment} - The member's comment<br>

-  {commentoptions} - Options concerning this comment for admin and the person 

-  who commented<br>

-  {oddeven} - This variable can be used to style alternating comments differently.</p>

-<p class="sampleLabel">Sample:</p>

-<p class="sample">&lt;!-- START BLOCK : comment --&gt;<br>

-  &lt;div class=&quot;comment{oddeven}&quot;&gt;<br>

-  {comment}<br>