FP Extensions - Hover Class Buttons

[Mike G]

Running my site on IIS local server, but the hover buttons, form handlers and
other FP extension (Yes these are enabled) are not visible/working when I
view the site at http://local host. Any ideas why? Thanks

 

[Ronx]

Did you create the site as a server based web (using http://localhost
as the website name) or did you publish the site to http://localhost
from a disc based web? If the site was created as a disc based web
and has not been published, the forms will never work.
Hover Buttons are Java applets which may not work at all on PCs
running Windows XP or using IE6. Java requires a Java Virtual Machine
which must be downloaded from Sun's site at www.java.com. It is best
to avoid Java applets (Hover Buttons) and use JavaScript image
rollovers instead.

 

[MikeR]

Java VM not installed? Javascript not enabled?
MikeR

 

[Mike G]

Hi - Thanks for the help.
I will try changing to FP link buttons instead of hoverclass and see how
that goes.
I created site in FP, I actually published to http://inetpub/wwwroot/myfile
should rename and publish to http://localhost or a different name? Also, why
don't the FP2003 forms and forms handlers work? Sorry I am a little tangled
up in the naming conventions.
Thanks

 

[Ronx]

How did you manage to publish to http://inetpub/wwwroot/myfile ?
This is a disc location with a http:// prefix, and any attempt to
publish would normally generate errors, such as "no server at.....".
This location would generally be referred to as
c:\inetpub\wwwroot\myfile. (It can be done with a suitable amendment
to the Hosts file.)

The correct locations to publish to are
http://localhost/myweb
http://127.0.0.1/myweb
http://machinename/myweb
where myweb is the name of the subweb you are publishing to, and
machinename is the network name given to your PC. All of these will
place the files in C:/inetpub/wwwroot/myweb as a server based web.

The FrontPage form handlers will not work unless you have HTTP
published to a server running the extensions. Since you may have
corrupted the extensions on localhost (using that file location) check
and repair the extensions (method depends on the extensions version)
then republish to http://localhost/myweb