EditWrx is designed to maintain content on existing webpages. It's easy-to-learn, easy-to-use interface makes it ideal for site designers delegating maintenence to their clients, organizations delegating maintenace to employees or members, and community websites. End users need no knowledge of HTML, cgi, or scripting to maintain or create highly interactive websites.
- Wysiwyg Editor
EditWrx adds a wysiwyg toolbar to the Explorer browser. The site admin can customize which tools appear for different users. EditWrx is integrated through Explorer to use the same MSHTML engine used by MSWord. If end users are familiar with the MSWord word processor, they will instantly feel at home with EditWrx.
- Site Maintenance
The most common use of EditWrx is for routine maintenance of websites. Don't be misled by the wealth of other possibilities, if delegating maintenance chores is all you need, EditWrx is the simplest to setup wysiwyg available. If you are a web designer offering the freedom of site maintenance to your client, you'll love EditBlocks - you get to decide what parts of a page are editable!
- Organizational Manager
EditWrx is ideal for companies, clubs, churches, and other organizations that need to delegate particular page maintenance to various individuals. Users can be assigned editing capabilities to a list of pages throughout the website. The users can login directly from their pages. You can mark off what parts of a page are editable, even assign different parts of a page to different users. And if you want, you can set up individual users as Authors who save to pending files instead of live files. Then delegate a Publisher to review the Author's work and publish it to live files, swiftly and easily controlling the changes before the public gets to see them.
- Community Builder
Complex file managers and databasing of content are things of the past. Assign users to a folder, salt the folder with your site template, and turn them loose to create. Templates can contain sitewide navigation that you can edit but members can't. You can designate a common folder that all users can access as though it was inside their folder. EditWrx even has a built-in automatic signup utility that lets new users signup and get started on their own.
No more editing configuration files by hand or having to learn computer programming languages just to get your software installed and running correctly. InstallPoint will guide you through your installation, testing your server for configuration, installing files and writing initial setup files. In just a few minutes you'll be ready to login and begin editing web pages. • [ InstallPoint Tutorial] 2min 
EditWrx is an application that runs in the browser. That's why we've designed it to look, feel, and work like the Windows application interface instead of a collection of web pages. You're not going to waste time trying to figure out where things are at or how they work, distracting you from the task of maintaining your web site. You don't need to learn to think like your editor's designer, we've designed EditWrx to function the way you expect mature software to function. EditWrx is an interface that actually turns the Explorer browser into a wysiwyg editor by accessing the same mshtml.dll that MSWord, Outlook and FrontPage use for wysiwyg editing. We then added features that Microsoft's never thought about to produce the web's most mature browser-based editor. • [ Sub-Feature Details]
Unlike other wysiwyg editors, EditWrx does not need a separate file manager, over on some page away from the work at hand. You access files the same way you would in any application - when you need access to them. For example, you need to create a new folder when using the SaveAs to create a new file - you can do that from inside the SaveAs Dialog instead of leaving the editor to do it on some file manager page. This may be a bit disorienting to web designers who've used less mature content management systems and learned to plan ahead for such things. But teaching the average user to plan for the software's shortcommings is not something we want to do - right? Attention to user-friendly workflow not only increases productivity, it greatly reduces the learning expense of the application.
• [ Flash Demo]
We're all familiar with how the web works, click on something and a new page loads in the window. But that's not how an application is supposed to work. One of the first things you'll notice about EditWrx is that tool wizards don't reload when they are communicating with the server in response to your actions. It's what we've affectionaly called the hole-in-the-page-trick since we first used it in 1999 on WebSitePad. It's since become known as Remote Scripting and we're surprised that other "web applications" still work like annoying Netscape2.02 web sites instead of like real applications. 
EditWrx isn't a toy. It is a powerful tool for managing, or defacing, your web site. That's why your EditWrx password is not sent to the server in plain text, the way it is when logging in with FTP, Basic Authentication or to other content management systems. Watch the browser's status bar when you click the Login button. You'll notice two transmissions via Remote Scripting. The first one requests a session key for encrypting your password and the second one sends your encrypted password. This sequence uses Unix grade MD5 hashes to build an unbreakable wrapper around your password.
EditWrx6 will not install on Apache servers that are not running the SuExec utility. No content management system, or BBS, written in Perl, PHP, or ASP/Apache should ever be run on an Apache server that is not running SuExec (just ask the tens of thousands of people who's sites were defaced by the Santy/PHPBB worm in Dec 2004). SuExec is one of the requirements checked for by InstallPoint during installation.
If you're installing EditWrx on your own site, InstallPoint probably set up EditWrx the way you want it. But if you are a designer installing for your client, or using EditWrx on a community, corporate, church, or other multi-user site, the Admin Control Panel makes management an easy chore. No config files to edit or programming to tweak, EditWrx management is point-n-click simple. • [ Control Panel Flash Demo] 
The Admin Control Panel makes setting up users too easy. Select the type of user, then fine-tune the defaults for that type of user. You can determine what tools a user has accesss to and what files or folders they have access to. Determine whether a user is limited to block editing only or can edit from the body open tag to the body close tag. Allow users to create backups before saving, what files they can see for making links, etc. • [ More Details]
- Super User - A Super User has the following privileges not allowed to other Users
- Has access to open files in all folders
- Allowed to upload files into a virtual common folder
- Has full page editing on all pages even if Editblocks are present.
By default, Super User has Site-Wide privileges. If there is only one user on the domain, use Super User for that user.
- Site-Wide - If admin is a web designer offering editing to their client, the designer should be set up as a Super User and the client as a Site-Wide user. A Site-Wide user has full navigation of the site for editing without the Super User privilages. This User type has access to use files in a virtual common folder but cannot upload files into the common folder or SaveAs into the common folder. The common folder appears in the domain's root folder.
- Folder Restricted - This type of User is not allowed to navigate outside of their base folder to find pages to edit. This type of user can login from pages inside their base folder or from wrx.cgi. If the User logs in from a page outside of their base folder, the page will refuse to load into the editor. This User type has access to a virtual folder named common. The common folder appears in the User's base folder. User templates may therefor be stored for this type of User in the common folder. You can set a maximum MB in a Folder Restricted user's folder tree to control file upload allowance.
- File Restricted - This type of user is restricted to editing only files listed for the user. The User's files may be in any folder. A file restricted User should not be allowed to use the Open Files dialog to find files to edit or the SaveAs feature. Instead, this type of user should login from the page they want to edit - see Login Prompt. If this User logs into a page they are not authorized to edit, logs in at wrx.cgi, or follows a link to a page they are not authorized to edit, a page listing the files they are allowed to edit will load into the editor instead.
- Author - If you designate a user as an Author the user's edits can not be saved to the regular web page. Instead, edits will be saved in the same folder to a file of the same name with "_pending" appended to the file name ("index.html" will be saved as "index_pending.html"). Whenever a user saves to a pending file a notation is recorded in a Publisher's Change Log.
- Publisher - A Publisher has an additional
 icon on their toolbar. Clicking that icon will load a linked list of pending files into the editor for the Publisher to chose from. The Publisher should load pending pages into the editor and approve or change them. When a Publisher saves a pending page the regular web page is automatically overwritten with the change, the pending file is deleted and the Publisher's Change Log updated. A Publisher may have a list of Authors to publish for.
- <INS> & <DEL> Tags - Authors have an additional
 icon for inserting <ins>(insert) or <del>(delete) tags. These tags are authorized by W3C for wysiwyg content management systems. The W3C spec also authorizes the CITE attribute within these tags as containers for explainations for the insertion or deletion. EditWrx is the only wysiwyg content management system which fully utilizes this W3C specification. The <ins> tag automatically underlines the enclosed content while the <del> tag places a strikethough line on enclosed content. Publishers can easily review the CITE explainations and remove the tags prior to publication of the page.
Mark off areas of the page for editing with Editblocks. Enclose an SSI/ASP/PHP tag in an Includeblock and edits get saved to the included files instead of to the page. Enclose an area in an Excludeblock and the area can not be edited at all. With Userblocks you can even allow multiple users on the same page to edit only their own blocks. • [ More Details]
- Full Page Editing - Wysiwyg editability extends from the page's open BODY tag to the close BODY tag. The page's file on the server is overwritten by the content of the page in the editor. Pages do not need any pre-congifuration. If the page contains JavaScript document.write functions, or SSI - ASP - PHP server side includes, do not use Full Page Editing.
- Block Editing
- Editblock - An EditBlock is an area of content on the page that is directly editable. The content of the EditBlock in the browser overwrites the corresponding EditBlock in the page's file on the server. Once an EditBlock is on a page only areas inside of EditBlocks or IncludeBlocks can be edited unless the user is a Super User. An Editblock must contain a closing comment after the block's close tag. [sample]
<div editblock="one">
page content
</div><!-- editblock="one" -->
- IncludeBlock - An IncludeBlock contains a SSI - ASP - PHP server side include. The content of the IncludeBlock in the browser overwrites the included file. An Includeblock does not require a closing comment after the block's close tag. [sample]
<div includeblock="/path/navigation.inc">
<!--#include virtual="/path/navigation.inc" -->
</div> (this virtual SSI references an include file in the home folder regardless of where the page is at)
<div includeblock="navigation.inc">
<!--#include file="navigation.inc" -->
</div> (this file SSI references an include file in the same folder as the page)
- Excludeblock - An Excludeblock cannot be edited by any user including a Super User. 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. [sample]
<div excludeblock="one">
page content
</div><!--excludeblock="one" -->
- Userblock - An Editblock can also contain a Userblock attribute. If the user is the username identified in the Userblock attribute that Editblock will be editable. All other Editblocks on the page will not be editable for that user. If any Userblocks are on the page, and the page does not have a Userblock attribute for that user, the page is not editable - unless the user is also a Super User. [sample]
<div editblock="two" userblock="sally">
sally's content
</div><!--excludeblock="two" -->
<div editblock="three" userblock="sam">
sam's content
</div><!--excludeblock="three" -->
<div editblock="four" userblock="sam,sally">
content that can be edited by sam or sally
</div><!--excludeblock="four" -->
Let your users login directly from the web page instead of through the main login page. A particularly useful trick for File Restricted users because it lets you eliminate the Open File and SaveAs icons from those user's toolbars. Simply add a snippet of code to the page's head section that watches a visitor's keyboard keystrokes - if they tap their ESC key three times a login prompt will appear (AOL users need to type "&edit" instead). Go ahead, try it - a login prompt snippet is watching your keystrokes on this page. • [ Sample Code]
<script language=javascript src="/virtual_url_to/wrx.cgi?prompt"></script>
So what if an editor lets you insert form elements on the page. Unless there's a process on the server to handle the form submission the form is merely a decoration. In addition to letting you use custom cgi scripts, EditWrx also has two types of built-in submission handlers. The first one databases submissions, the second one emails submissions to you. And it's all automatic - no programming required, or allowed! • [ Forms Flash Demo]
Use a generic blank button image to create buttons for your site. Button Maker can overlay text on the button. You then position the text, select it's font, color, text size and even a rollover color for the text. After you've applied a link to the button and inserted it into the page you can then copy/paste to clone more buttons, easily changing the text and link for the cloned buttons. The Sample button is an example. Click the Sample button to view the code.
<A id=sample style="DISPLAY: block; FONT-WEIGHT: normal; FONT-SIZE: 12px; BACKGROUND-IMAGE: url(/resources/button.gif); WIDTH: 58px; COLOR: #00FFFF; PADDING-TOP: 5px; BACKGROUND-REPEAT: no-repeat; FONT-STYLE: normal; FONT-FAMILY: arial; HEIGHT: 24px; TEXT-ALIGN: center; TEXT-DECORATION: none" onmouseover='this.style.color="#F5F5F5"' onmouseout='if(location.pathname.indexOf(this.pathname)==-1){this.style.color="#00FFFF"}' href="features.html" target="">Sample</A>
You're in the Yucatan visiting Mayan ruins, doing research for your local rare seed collecting society. And you're keeping notes on your laptop in MS Word. When you get back to the hotel you want to transfer those notes to a page on the web site. Login to EditWrx on your site, open the page in EditWrx. Then open the document in Word - highlight the section you want to transfer and drag it right out of Word and onto the page where you want it to be. Viola! • [ More Details]
EditWrx uses the same MSHTML engine that Word uses. As you drop the dragged content, or paste copied content, MSHTML magically re-codes the word processor syntax into HTML syntax. Tables, fonts, lists, etc are converted into HTML format directly from the binary Word format. No need to save the document in HTML or to run it through a parser, the conversion is instantaneous.
Paste an entire document onto a page with an empty body, or just move sections into an existing page, even drag Excel spreadsheets into a page and watch it convert to a table layout. You did keep track of the rare seeds you found in a spreadsheet, didn't you?
Word processors are notorious for producing bloated code; empty font tags, orphaned span tags, etc. EditWrx automatically cleans the page up when you save it. If you plan on tweaking code with the TagEditor you may want to cleanup that bloat before pasting into the page - just paste through the EditWrx  Paste-Word wizard and the cleaup is done before the content enters the page. If the Word document contains images you need to upload them to the web site and insert them into the page - both can be done through the  Image wizard. 
The web's main feature - being able to jump from page to page with the click of a link - can also be it's most annoying feature. Jumping out of the middle of one page to another just to see an enlarged image or short explaination can be disorienting to users. So what if you could do this inline - right on the page? Click the images and links in the Examples to see the web work the way you thought it would work before you got used to the way it does. • [ Examples] [ Flash Demo] 
Want to make a photo gallery on your web site? It's so EASY with EditWrx you'll want to make more than one! Upload images to a folder on the server. Then use this Create A Gallery tool to embed a special tag on a web page. When the page loads EditWrx reads the folder. If ImageMagick is installed on the server EditWrx creates new high quality, fast loading thumbnail images to the width and height the tag specified. If ImageMagick is not available EditWrx creates image tags with the width and height specified. EditWrx then displays the photo gallery with each image linked to display the full sized version right in the center of the page. • [ Example Gallery] 
PayPal has enabled thousands of websites to make sales. Yours can be one of them. With no programming experience required, PayPal & EditWrx can help you ship product by the end of the week! • [ PayPal Flash Demo] 
Create and manage password protect folders with EditWrx. Add or remove members through EditWrx or create specialized forms for adding members - with or without a subscription payment interval. Simple-to-use interface is built-in to EditWrx, no need to create htaccess or htpasswd files through the commandline or server's control panel. • [ More Details]
Simple Password Protection - Load a page into EditWrx from the folder you want to protect. Click the  icon and enter a default member name and password so you can login to the folder. EditWrx automatically creates password protection. To add more members, or delete members, again load a page from that folder into EditWrx and click the icon.
Forms Signup - Once you've created the password protection (first step above), you'll also have the option to build a form so visitors can automatically add themselves to the list of members for the folder. Complete instructions are in the wizard.
Pay-For-Access - The above Forms Signup has a separate routine that allows you to take payment during the signup process. You can use PayPal or any other payment gateway for taking either recurring subscription payments or one time fee payments. The EditWrx routine guarantees that only one member name can be added per payment, and only for the correct folder, without complex tracking by the payment gateway.
This feature uses Apache's Basic Authentication system. Windows IIS servers do not natively support membership password protection for folders.
From the very beginning EditWrx has been designed for creating and managing community websites. It's a natural, community members need only a browser to participate in creating and managing the community. Version 6 takes this concept to the max! Automatic signups, shared folders, improved security, even shared navigation systems.... • [ More ....]
Automatic Signup - The Add-User wizard will guide you through creating the forms necessary for offering automatic signups on your site. - Visitors check to see if their choice of a username is available, submit a password and their email address (yes - if they forget their password EditWrx will email them a new one!) and then automatically create a default editing account, a folder with their username, populate their new folder with the files and folders you specify, and land them on your instruction page - ready to begin editing as an active member of your community. That all happened while you were at the coffee house gossiping about the people in Your Community!
- Pay-Per-Join Got a hot idea for a community? Hot enough for people to pay to join it? (Hint, EditWrx users can sell from their community folder....) The Add-User wizard has a subroutine just for Pay-Per-Join signups. The visitor first checks the availability of their username and EditWrx sets an encrypted cookie on their computer. They are then routed to a PayPal form for either one-time payment or subscription payment/setup (see Add E-commerce above). When they've paid at PayPal they are routed back to a page that automatically validates the encrypted cookie and records their password while setting up their account and folder. And you're picking up the tab for your friends at the coffee house with your PayPal debit card!
Shared Folders - One of the problems with a community website is how to let members use shared resources while keeping them barricaded in their part of the website. Common Folder to the rescue! The site admin can specify any folder at the domain's root to be a common folder (it can be named anything). The common folder becomes a virtual folder that appears in the base folder of any folder restricted user. The user can not Upload or Save or SaveAs into the common folder but all files there can otherwise be used. It's a great place to store images, Flash files and templates. The admin Super User can of course use the common folder without restriction.
Shared Navigation - When you populate your member's folders with a template for them to use, you can seed the template with an SSI/ASP/PHP include that is outside of EditBlock areas or is inside an ExcludeBlock area. The include can contain a site-wide navigation that the members can not edit. But it's also on a page you can access and there it's inside of an IncludeBlock so you can edit it. Use multiples of this concept for a basic site navigation bar and a linked list of all your member's folders. See the Full Page Editing Demo for an example of a navigation bar in an ExcludeBlock.
Improved Security -
We've all done it. Forgotten our password to a website, or needed to access from a different computer than the one storing our password. EditWrx now requires all users to record an email address so EditWrx can email the user a new, random generated, password. So what's unique about that? Many web servers (Windows) do not have standard email servers, and to discourage spam attackers other servers have isolated their email servers from cgi-scripts. So, on each request, EditWrx creates an email server in memory, sends out the email, and then erases the email server from memory. The server has been pre-configured to only send out emails to registered EditWrx users and only a registered EditWrx user can initiate an email request.
If you have another program on your website that users login to, that login can be carried forward as an automatic login to EditWrx. This auto-login can open EditWrx with a partricular page in the editor or open to an empty editor. • [ More Details.]
If you have another program on your website that users login to you will need to first add their username and password from that program to EditWrx by creating an EditWrx user with that same username and password. Once the user has logged in to the other program you may use either of the two methods below:
- Method 1 (Recommended) - Create two cookies:
| • Cookie Name: | AUTO_LOGIN | Cookie Value: | UserName:Password |
| • Cookie Name: | LOAD_PAGE | Cookie Value: | Full URL of the page to load into EditWrx |
The LOAD_PAGE cookie is optional, if it does not exist EditWrx will load with no page in the editor.
The username and password are separated by a colon (:) and are transmitted in plain text and are stored on the cookie in plain text. The cookie may be a session or persistent cookie.
You then need to redirect or link to your URL for wrx.cg with a query string of autologin. Example:
http://domain.com/editwrx/wrx.cgi?autologin
- Method 2 - Send a query string
http://domain.com/editwrx/wrx.cgi?autologin=UserName=Password=URL_of Page_to_Load
This method is not recommended if the user's browser may also be used by untrusted persons. The user's plain text password will remain in the browser's history.
If you want EditWrx to open in a new window, you must explicitly create that window as a target for the redirect or link to load into.
Some times you just need to get at the code. Some users may need to only see the code - other users may need to edit it. Either way, it's important to be able to find the code quickly and easily on the page. Simply put your cursor on the page where you want to see the code, click the  icon and the Tag Editor/Viewer opens to that tag's code. But that's just the beginning.... • [ More...]
Full Page Editing Mode
The Tag Editor/Viewer displays the tag and contents of the tag the cursor was in. Click the Expand button to view the tag and contents of the next outer tag. You can continue Expanding to display outer tags out to the body tag. The body tag itself will not be displayed. Clicking the Shrink button will roll the display back inwards one tag at a click until you return to the original display. Only the tag tree that you are in will be included in the Expand/Shrink sequence.
|
Block Editing Mode
The Tag Editor/Viewer displays the contents of the tag the cursor was in. Click the Expand button to view the contents of the next outer tag (which now displays the tag itself). You can continue Expanding to display outer tags out to the editblock or includeblock you are in. The actual editblock or includeblock tag itself does not display, preventing a user from mistakenly changing the editblock or includeblock value. Clicking the Shrink button will roll the display back inwards one tag at a click until you return to the original display. Only the tag tree that you are in will be included in the Expand/Shrink sequence.
|
Edit or View
The User Setup allows admin to determine if a user can edit code in the Tag Editor/Viewer or merely be able to view the code. Sometimes being able to just see the underlying code is valuable even for users that are untrusted for editing code.
|
|
Affiliate Program
Admin Manual
Demos
Forums
Language Packs
