Solution: Components do not display in Preview. Publish your site remotely or locally to see the components work properly. To view DynaButtons, Message Board, or Forms Handler, publish to a functioning Web server because these components work in conjunction with the Web server or they have security issues which require that they be viewed through a Web server.

2. Problem: I opened a NetObjects Fusion 2.02 site that contained an AutoForm or Form Handler component. When my site visitors submit data using the component, they get a Not found message from the browser.

Solution: Sometimes the component loses its success and error links when the site file is upgraded from 2.0.2 to 3.0. Simply reassign the Success URL and Error URL parameters on the Form Handler Properties palette in NetObjects Fusion and republish the site.

3. Problem: I placed a Message Board or Form Handler component in my site and published to a machine running Microsoft Internet Information Server 4.0. I cannot get either component to work although I followed the instructions in the documentation.

Solution: If your Web server is Microsoft IIS 4.0 and you wish to use the NetObjects Fusion 3.0 Message Board or Form Handler Components, you need to download the IIS4_Update.zip file from ftp://support.netobjects.com/Public/IIS4_Update/

4. Problem: When site visitors using a Macintosh visit my site and use my Message Board component, they are unable to use the Next and Previous buttons to view postings.

Solution: There is a known problem with the Next and Previous buttons for the Message Board component on a Macintosh. Tell your Macintosh site visitors to click on each message they want to view instead of using the buttons.

5. Problem: I placed the Form Handler component on a page and published to a Web server running on Windows NT 4.0. I then tested the Form Handler by filling out the form and submitting the data. Although the Form Handler sent me to the Success URL, I cannot find the text file that contains the data on the Web server.

Solution: Some computers have security issues which prevent the output directory from being created. If you look on the Web server and cannot find the directory that is supposed to contain the text data file, create the directory path manually and test the Form Handler component again.

6. Problem: I placed the Form Handler component and published to a UNIX Web server. I configured Form Handler to write the contents of the form to a file named webinfo.txt inside a directory named webdata (the default values). When a site visitor clicks the Submit button, a message appears saying This server has encountered an internal error which prevents it from fulfilling your request. The most likely cause is a misconfiguration… or a similar message appears.

Solution: On UNIX, when the Perl executable and the Web server run under different users, the Web server might not have the necessary permission to run the Perl executable. If this is the case, you must grant Read and Execute permissions for the Forms-Handler.cgi file to users in the Other category (the rest of the world), and assign Write and Execute permissions for the directory that contains the data file to users in the Other category. Follow the steps below:

1. Log onto your UNIX system as a user who can change permissions.

2. Go into the cgi-bin directory that contains the Forms-Handler.cgi.

3. Type the following: chmod 755 Forms-Handler.cgi

4. Go into the directory that contains your directory where your data file will be written. You can check the directory name and location by looking at the Storage Directory parameter in the Form Handler Properties palette. The default name is webdata.

5. Type the following, replacing webdata with the correct directory if you changed the default:

chmod 733 webdata