EditWrx :: Wysiwyg Editor - Content Management System

Servers

InstallPoint will install all EditWrx files in an "editwrx" folder in the domain's root folder. EditWrx runs through one central Perl script named wrx.cgi (wrx.pl). If your server requires you to run cgi scripts from a cgi-bin you will possibly need to move wrx.cgi to the cgi-bin folder with FTP. The purpose of a cgi-bin was made obsolete in 1995. Modern servers allow cgi scripts to run anywhere in the domain. EditWrx recommends that you attempt to run InstallPoint's installer.cgi from an editwrx folder before assuming that your server requires scripts to run from a cgi-bin.
- Apache/Unix
  
  EditWrx v6 requires that the server be running the suExec utility. SuExec is recommended by Apache and is a basic requirement for running any Perl or PHP program that allows users to alter files on the server through the browser. SuExec forces cgi processes to run as the owner of the script file, thereby allowing the process to write to files based on the Owner's permission. SuExec processes can therefore write to files in your domain that have only 0644 permissions. The 0644 permissions also prohibits a cgi script from another domain on the same server from also writing to your files. (more)
- IIS/Windows
  
  EditWrx will run on any Perl enabled IIS server. You may need to have the server administrator enable Execute and Write permissionss for the domain. (screenshot) (screenshot)
Browsers
- Explorer
  
  EditWrx is not a webpage, it is a browser-based interface to a Windows application (mshtml.dll). EditWrx will not run on Apple or Linux operating systems and requires a Explorer 5.5, 6 or 7 browser.
  
  EditWrx uses pop-up dialog windows for many functions. If you have a Pop-Up Stopper running - disable it while running EditWrx or set the Stopper's preferences to always allow Pop-Ups for your domain.
  
  EditWrx is set to run on Explorer's default "Medium" security settings. If you have adjusted security settings you may need to re-set them to the "Medium" default or make your domain a Trusted Site. (instructions)
  
  Set Tools>Internet Options>General>Temporary Internet Files>Settings>Check for newer versions of stored pages to Every visit to the page, or Automatically. (Other settings will prevent the browser from displaying the changed page when you save it.)
- Explorer 7
  
  Explorer 7 has some new security features
  Open a page on the website.
  Then Tools>Internet Options>Security tab
  
  click Trusted sites
  click the Sites button
  Add the website to the list
  If you do not want to have to access the site in https, uncheck Require server verification
  click Custom Level
  1) under Misc enable Allow websites to open windows without address or status bars
  2) under Scripting enable Allow Programmatic clipboard access
  3) under Scripting enable Allow websites to prompt for information using scripted windows
- FireFox
  
  EditWrx requires the browser to support the contentEditable attribute to be able to use editblocks, includeblocks and excludeblocks. FireFox instead uses the DesignMode attribute which references the entire page instead of individual elements. Rather than cobble up a kludgy workaround, like putting editable areas inside messy iframes, we've opted to wait for FireFox to mature.
  
  Although FireFox does support many non-W3C Explorer standards such as innerHTML and scrollIntoView, it does not support others such as outerHTML and contentEditable. Mozilla's claim to be W3C compliant is no more honest than a Presidential press conference.
  
  We hope that FireFox's Version 2 will mature to support more real-world standards. If it does, EditWrx will be re-tooled to run on FireFox.
Although EditWrx will operate only on the Explorer browser on Windows, edits made to pages will validate for HTML 4.0 specs for all browsers on all platforms.


	On December 23, 2004 the Santy Worm attacked the web. It is estimated that Santy defaced millions of web pages on over 500,000 website in less than 3 days. The Santy Worm gained access to servers through a PHP vulnerability. But PHP pages were not the only files that were defaced. On Apache servers that were not running suExec, all files that could be written to by content management systems, bulletin boards, wysiwyg editors, or database processes were also defaced. The Perl, PHP and Apache communities have recommended running suExec for years. With EditWrx suExec is no longer an option - it is a requirement.