Extension:BoilerRoom

Installation

 * 1) Extract this extension to the extensions subdirectory of your MediaWiki installation directory. It should be contained in a BoilerRoom subdirectory within extensions.
 * 2) If your wiki has custom namespaces using the indexes 450 and 451, add the following line to LocalSettings.php (changing xxx to an unused even index, ensuring that the following index is also unused):
 *  $wgbrNamespaceIndex = xxx; 
 * 1) Add the following lines to LocalSettings.php. Due to the unique nature of the &lt;boilerplate&gt; tag used by this extension, it is advisable to include this line before any other extension includes to prevent unexpected interactions (but make sure it is placed after the $wgbrNamespaceIndex</tt> line if that is needed):
 *  require_once( "{$IP}/extensions/BoilerRoom/BoilerRoom.php" ); </tt>

Note: Versions 0.92 and earlier used namespace indexes 300 and 301 as the defaults. If you are upgrading from those versions and you were using the default, you should add the following line before the require_once</tt> line:
 *  $wgbrNamespaceIndex = 300; </tt>

Alternatively, if you are comfortable manipulating the database directly, you can update the namespace indexes of the page. Another option is to create a temporary custom namespace at index 300 and move them to new Boilerplate namespace manually.

Configuration

 * $wgbrNamespaceIndex</tt>
 * Sets the index at which the Boilerplate namespace will be created.
 * As of version 0.93, this is 450 by default. The Boilerplate talk namespace will be created at the following index, which is 451 by default.
 * In earlier versions, this was 300 by default, with the Boilerplate talk namespace being created at 301 by default.


 * $wgbrUseLargeSelector</tt>
 * Available in 1.0, this option allows you to use a large version of the four-button selector that appears above the standard toolbar rather than to the right of it by setting this option to true</tt>.

Overview
BoilerRoom is a dynamic text preloading extension that has the ability to load text from boilerplate pages into the edit textbox of new pages. With AJAX enabled on the server and JavaScript enabled on the user's browser, boilerplate text can even be loaded on existing pages. The extension provides a boilerplate selector on edit pages for this purpose. It also allows you to create input boxes on wiki pages that allow users to input a title and open a new page for edit with the boilerplate text preloaded into the edit box.

BoilerRoom is different in its approach from similar extensions in that it was designed to allow the creation of boilerplate text without any need for text escaping. It deliberately does not respect &lt;includeonly&gt;</tt>, &lt;onlyinclude&gt;</tt>, and &lt;noinclude&gt;</tt> tags, instead providing its own mechanism through the special behavior of the provided &lt;boilerplate&gt;</tt> tag. This behavior simplifies certain situations, such as creating boilerplates for templates, where unusual escape mechanisms like &lt;include&lt;includeonly&gt;only&gt; would be necessary to achieve the same effect. Even other &lt;boilerplate&gt;</tt> tags can be place inside without any need for an escape mechanism.

Creating boilerplate articles
The &lt;boilerplate&gt;</tt> tag is used to define the start and end of boilerplate articles. This is a unique, deliberately non-compliant tag with special behavior designed to prevent the need for any kind of text escaping within the boilerplate content. It's more of an extended syntax than a true tag. Specifically, it has the following behavior:


 * You must use &lt;boilerplate&gt;</tt> and &lt;/boilerplate&gt;</tt> exactly as written here. Though spaces are permissible inside a compliant XML tag, this isn't a compliant tag.  It is also case-sensitive.
 * Only the first &lt;boilerplate&gt;</tt> tag and last <tt>&lt;/boilerplate&gt;</tt> tag on the page are considered.
 * This allows you to place even <tt>&lt;boilerplate&gt;</tt> tags into the content.
 * Additionally, tags such as <tt>&lt;includeonly&gt;</tt> and <tt>&lt;noinclude&gt;</tt> don't require any unusual escaping. They are treated as plain-text content within <tt>&lt;boilerplate&gt;</tt> tags.
 * The boilerplate content opens at the first line after the <tt>&lt;boilerplate&gt;</tt> tag and closes at the end of the final line before the <tt>&lt;/boilerplate&gt;</tt> tag. Content on the same lines as the tags is simply ignored if it is between the tags.

Or to show this information visually: <div style="font-family: monospace,'Courier New'; padding: 1em; border: 1px dashed #2f6fab; background-color: #f9f9f9;"> Header text describing the boilerplate may be placed here, as well as any other wikicode.

It will appear when directly viewing boilerplates and when transcluding them like templates.

&lt;boilerplate&gt; Text here is simply ignored and will not appear.

This line is where the boilerplate text begins.

&lt;boilerplate&gt;

Since only the first opening and last closing tags are considered,

boilerplate tags inside the boilerplate text are treated as plain text and will be

included as part of the boilerplate without modification.

&lt;/boilerplate&gt;

&lt;includeonly&gt; and similar tags are also treated as plain text within the

boilerplate tags and will be included in boilerplate text without modification, so it

even works well for providing a boilerplate (or multiple) for templates.

&lt;/includeonly&gt;

This line is where the boilerplate text ends.

Whereas this text is simply ignored. &lt;/boilerplate&gt;

You can place any footer text here you wish, and this is a good spot for any categories

you want to include the boilerplate article itself in. That can be done in the header as

well.

The four-button selector
The four-button BoilerRoom selector, shown below, appears above the edit textbox on every page if the wiki has AJAX enabled and the user has JavaScript enabled. There are two different versions of the selector. The first is the small selector which is used by default in version 1.0:



Optionally, by setting <tt>$wgUseLargeSelector</tt> to true, a wiki can opt instead for the large selector:



Note: In versions before 1.0, the large selector was the only one available. Additionally, it was only a three button selector, as shown here.

It shows only the articles available within the Boilerplate namespace, excluding any redirects. As you can see, it does not display the <tt>Boilerplate</tt> portion of the title. Note, though, that even articles without <tt>&lt;boilerplate&gt;</tt> tags will be displayed as options, but nothing will happen when a user tries to include text from these pages; therefore, you should avoid allowing any non-boilerplate articles within the Boilerplate namespace.

As shown above, users have the ability to load boilerplate content before any existing text, after any existing text, or over existing text by replacing it. Be warned that most browsers will not record this as an undoable action, and as such, the extension asks for confirmation before replacing the existing text.

Note that the four-button selector is the only way BoilerRoom provides for using boilerplates on existing pages.

The one-button selector
The one-button BoilerRoom is shown when AJAX is not enabled on a wiki, or when a user does not have Javascript enabled. This selector only appears and functions on new pages, and unlike the other selector, it must reload the page to function. It does not function dynamically and cannot load boilerplate text over or into existing content.



The BoilerRoomBox
BoilerRoom also provides the BoilerRoomBox, shown below, which functions very similarly to the one-button selector described above. The most important difference is that the BoilerRoomBox is not automatically displayed anywhere, but is included on pages through the use of the <tt>&lt;boilerroombox&gt;</tt> and <tt>&lt;brbox&gt;</tt> tags or the <tt> </tt> and <tt></tt> parser functions. (<tt>brbox</tt> and <tt>boilerroombox</tt> are synonyms for each other and function identically.)



The usage of either the tag or the parser function is a matter of preference most of the time, but if you want to include a BoilerRoomBox as a parameter to a template, you'll need to use one of the two parser functions. The interactions between the tag form and the parser function may also differ with the tags and parser functions of other extensions, and this is why both forms are included.

The syntax for each is similar, as shown here side-by-side. Tag form &lt;boilerroombox&gt; boilerplate= title= label= align= width= &lt;/boilerroombox&gt; Parser function form

For the tag form, each parameter needs to be on its own line, with the end of line signifying the end of a value. For the parser function version, the pipe symbol signifies the end of the value and must be used between each parameter.

All of the parameters, explained below, are optional.


 * <tt>boilerplate</tt>
 * This identifies the article to preload into the edit box. It only loads content defined by <tt>&lt;boilerroom&gt;</tt> as explained above.  If a namespace isn't included, the Boilerplate namespace is assumed.  To use an article in the Main namespace, prefix the title with a colon .  If none is including, this simply opens the requested page for normal editing and may be handy for skipping the search page when one wishes to proceed directly to the edit page.


 * <tt>title</tt>
 * This is the default title that appears in the box. It is probably best used to indicate a suggested prefix or suffix for the type of article it is used to create.  The default is an empty box.


 * <tt>label</tt>
 * This is the text that appears on the button which opens the requested page for editing. The default label is "Edit".


 * <tt>align</tt>
 * The align can be <tt>left</tt>, <tt>right</tt> or <tt>center</tt>. This is applied as a CSS rule, so <tt>inherit</tt> is also a valid value.  There is no default; if not included, no <tt>text-align</tt> rule is applied.


 * <tt>width</tt>
 * The size of the title entry box measured in number of characters. The default is 30.

Note that like the one-button selector, this cannot automatically load boilerplates on existing pages. It does, however, automatically select the requested boilerplate in the three-button selector if the conditions are right for that selector to appear (AJAX and Javascript enabled).

Selectors don't clear floats
Issue has been fixed in version 1.0 and the workaround below is unnecessary for all but earlier versions.

There is a simple workaround for this issue. Paste the following CSS into MediaWiki:Common.css on your wiki: .boilerRoomFieldSet { clear: both; }