We have a development that if accessed by regular Filemaker Pro the button (via Open URL) that links to a document (word file) it does open the application (MS word) resulting a very satisfactory behaviour for users.

 

But the same stuff when running with WebDirect the Chrome gets an 

"not capable of opening the window; please deactivate the popup window blocker and try again". Well needless to say that that blocker is not active (under preferencies) and the IS manager of the net also verifies it is not blocked at her level. 

 

Also firefox, same machine, is not able to open the application; in this case with no alarm / action at all. 

 

Any clues??

 

Thanks!!

 

 

Client

- Windows 7 professional, SP1 

- Chrome: Versión 41.0.2272.118 m

- Firefox:  36.0.4

- FM Server: 13.0.5.520

 

IIRC from the release of Version 13 and WebDirect™ this is a known limitation resulting from design choices for WebDriect.  Also, Firefox is not a supported browser for WebDriect.

 

Steven

Yap! Firefox is out of the issue, sorry!

 

The v13 scripts reference manual stands (p. 253) that Open URL is a supported step for WebDirect. 

 

The description is rich enough to state this:

 

Windows:

Open URL supports http, https, ldap, ldaps, ftp, file, and mailto URL types. For example, if the URL starts with http, FileMaker Pro opens the user's web browser and processes the URL.

Note FileMaker Pro uses the preferences stored in the Windows system file URL.DLL to determine the application to handle the URL. The URL is then passed to ShellExecute for execution. 

 

And as we have experienced it works flawlessly with FMPro but in the supposedly supported (oops!) web direct doesn't. 

 

Perhaps any change after manual writing?

 

In my tray: I have to try it with mac (just to see the issue) although the system is only Win. 

 

Also if this helps: when connecting to web direct page access menu the web address appears strikethrough https: