Users can login to EditWrx from wrx.cgi. Users can also login directly from a page if the page is set-up for Direct Login. To login from this page tap the ESC key on your keyboard three times (AOL users type &edit). This Direct Login feature is inactive once a page has been loaded into the editor.

This page contains a Direct Login Prompt in it's source code
<script language=javascript src="/editwrx/wrx.cgi?prompt"></script>
You can place a Direct Login Prompt on pages to allow logging in to EditWrx from the page.

To toggle the editor On/Off click the icon. To reload/refresh the page click the icon.

A Super User editing a page with Blocks will initially be able to edit the page in Full Page Mode. Non-Super Users will be able to edit the page in only Block Editoing Mode. To switch to Block Editing Mode, a Super User can click the icon.

In Block Mode borderless tables are outlined and links are disabled only inside of editable blocks. There are three types of blocks. Blocks are created by attributes in either DIV or SPAN tags. Conforming to basic HTML usage, a block can not begin in one element and end in another element.

Because this page contains code for blocks in the visible text, this page can not be saved.


When one or more editblocks are on a page the areas inside of the editblocks are editable. When the page is saved only the block areas are sent to the server (not the entire page). The server side of EditWrx then replaces those blocks in the file with the contents from the browser. The closing comment after the closing div or span tag is essential and must contain the same attribute as in the opening tag. Example:

<div editblock="one">
  page content
</DIV> <!-- editblock="one" -->


An includeblock encloses an SSI - ASP - PHP include tag that imports content from an external file. The purpose of an includeblock is to be able to edit the contents of the block and write that content to the imported external file instead of to the page. The path in the includeblock attribute begins with a slash (/) and routes from the domain's root folder to the imported file. An includeblock does not require a closing comment. Examples:

<div includeblock="/path/">
  <!--#include virtual="/path/" -->

<div includeblock="/path/">
  <? include("../path/navigation.php") ?>

Note that a PHP inclide() requires a relative path to the file while the SSI-ASP virtual requires a virtual URI path to the file. In both cases, the path in the includeblock value must be the virtual URI path.


Content inside of an excludeblock can not be edited. JavaScripts containing document.write() functions or calculations, and SSI - ASP - PHP includes providing dynamic content can be placed inside of Excludeblocks. An Excludeblock must contain a closing comment after the block's close tag. Example:

<div excludeblock="two">
  page content
</div><!--excludeblock="two" -->