Using the built-in File Browser

The insert image dialog box of the FlashTextEditor contains a "Browse" button that allows users to select a file (JPG or SWF) to insert into the editable text field. By setting the FileBrowser option in the Component Inspector panel to "true", you instruct the FlashTextEditor to use the built-in FileBrowser. In the event that you are using the FlashTextEditor in a non-web environment, you would probably disable this feature. In this case, when the "Browse" button is pressed the editor will dispatch a "browse" event as explained in Actionscript Reference.

The FileBrowser works by communicating with a script on the server which sends the file structure of a predefined directory. Before using the FileBrowser you will need to upload the backend files that were supplied with the download of this component, on your server. This will also allow you to upload images and swfs.

Note: Flash players prior to version 8 can only load non-progressive JPGs. Flash player 8 can load both JPEG formats, PNG and GIF files.

In order for the FileBrowser to function correctly you will need to set the FileBrowser parameters in the FlashTextEditor properties panel

To customize the appearance of the FileBrowser window use the popUp event handler as explained in the ActionScript reference.

Instructions on setting PHP/Apache backend

Flash Text Editor v1.5 and higher:

Requirements:

- Apache web server allowing .htaccess override
- PHP 4.1+

We recommend using FTP software to upload the files.

1. Upload the entire FileBrowser folder from your hard drive to your webserver.
2. Change CHMOD of FileBrowser/imgRoot folder to 777 (this is needed for uploading the files).

Flash Text Editor v1.1:

Requirements:

- Web server running Apache and PHP 4+
- optional (recommended): GD extension for PHP for creation of thumbnails and converting JPEGs to non-progressive

We recommend using FTP software to upload the files.

To setup your php backend, please follow these steps:

1. Upload the entire FileBrowser folder from your hard drive to your webserver.
2. Change CHMOD of FileBrowser folder to 777 (this is needed for uploading the files).
3. Enter the URL of the newly created folder in your browser's address bar (for example http://flashloaded.com/FileBrowser/)
4. Follow installation instructions

Once everything has been set up correctly, you should see a username/password dialog at the same address (for example: http://flashloaded.com/FileBrowser/). After entering the FileBrowser you will be able to upload your files to the server as well as preview and delete files and manage the folder structure. The exact same folder and file structure will also appear inside the FileBrowser of the FlashTextEditor.

Instructions on setting .NET backend

Requirements:

- Microsoft Windows 2000 or higher (Windows Server 2000 or higher recommended)
- Microsoft .NET Framework 1.1 (Microsoft .NET Framework 1.1 Service Pack 1 recommended)
- Internet Information Services 5.0 or higher (IIS 6.0 recommended)
- Virtual Directory or Web Site created

Edit web.config file located in the web application root folder. Only IMPERSONATION node needs to be configured.

Step 1: Find the following line in the configuration file

<identity impersonate="true" userName="Administrator" password="password" />

Step 2a: Type in the username that have enough rights to list, create and delete folder and files. Type in the user's password. This is usually the same user that is allowed to login via FTP server. Restart IIS if required.

Step 2b: If the web application is granted read/write access that may be configured from IIS snap-in, impersonation needs to be disabled by changing the impersonate value from "true" to "false". In that case username and password will be ignored.

Enter the in name of the the directory where the uploaded files will be stored. The root folder is a relative path of the existing directory to the application root folder. The default value is imgRoot.

Allowed extensions should be configured here. Type in the extensions of the files you wish to allowed to be uploaded (comma-separated values).

In case of errors, the application may return an error message. All the messages can be configured or translated in the errors node.