When I first saw WebDirect I thought it was a great replacement for IWP for my database needs, but the devil is in the details.

 

1. I wanted my users to be able to enter the database without having to go through the Filemaker WebDirect login page. Right now I have a CWP solution where the client logs in and if they have forgotten their login info it will pop-up. Not in the WebDirect login page. I tried using the WebDirect_Params.fmp12 solution which worked fine in Chrome and Firefox, but the WebDirect login page appeared again in Safari.

 

2. I have my database hosted with triple8 and they do not allow custom home pages on the virtual host, so that on reason I tried using WebDirect_Params.fmp12. They also have a 1 hour timeout period which is too long for my needs. I wanted the user to be logged out after 15 minutes of inactivity. Can not seem to get that to work properly in WebDirect.

 

3. Which leads me to the last reason which is go to url on logout. If someone has block pop-up windows turned on, the go to url script does not work and the user is returned to the WebDirect login page. 

 

If anyone has come up with solutions to these 3 issues, I would be very interested in hearing them.

 

All the Best - Sam

When I first saw WebDirect I thought it was a great replacement for IWP for my database needs, but the devil is in the details.

1. I wanted my users to be able to enter the database without having to go through the Filemaker WebDirect login page. Right now I have a CWP solution where the client logs in and if they have forgotten their login info it will pop-up. Not in the WebDirect login page. I tried using the WebDirect_Params.fmp12 solution which worked fine in Chrome and Firefox, but the WebDirect login page appeared again in Safari.

2. I have my database hosted with triple8 and they do not allow custom home pages on the virtual host, so that on reason I tried using WebDirect_Params.fmp12. They also have a 1 hour timeout period which is too long for my needs. I wanted the user to be logged out after 15 minutes of inactivity. Can not seem to get that to work properly in WebDirect.

3. Which leads me to the last reason which is go to url on logout. If someone has block pop-up windows turned on, the go to url script does not work and the user is returned to the WebDirect login page.

If anyone has come up with solutions to these 3 issues, I would be very interested in hearing them.

All the Best - Sam

For #1, I do this:

• Database is set to auto-login with [Guest] account.
• A custom dialog box opens for the actual login asking for username + password. Many browsers will properly remember u/p and autofill them.
• The Relogin script step then logs the user in as themselves.

No idea about #2.

For #3:

Option A: I'm guessing you can't edit iwp_home.html ? If you could, you could simply add

<script type="text/javascript">        top.location.href = "https://example.com/";</script>

Alternatively:

Option B: You could include a WebViewer that uses the "data:text/html" url which can then hold a simple <a href> link to the page you want them to go to. It won't actually log them out, but if you have a short enough timeout that's not a problem.

Option C: use the "homeurl" feature described here

http://fmforums.com/forum/topic/91311-closing-the-webdirect-window-on-app-exit/

I agree with the above... I also use triple8 and the homeurl feature works well.... E.g your link to your database might be:

https://FM63.triple8.net/fmi/webd/?homeurl=http://www.yourdomain.com/YourExitScreen.htm#YourDatabase

That will take you straight to the database login and then on exiting go to your exit screen....

Thank you both. You have given me hope.

 

 

 

For #1, I do this:

• Database is set to auto-login with [Guest] account.
• A custom dialog box opens for the actual login asking for username + password. Many browsers will properly remember u/p and autofill them.
• The Relogin script step then logs the user in as themselves.

 

I have done the above, but there does not seem to be a way in WebDirect to create a "Remember Me" for the user name and password fields for autofill. If either of you know how to do that, I would be greatly appreciative.

 

 

 

Option B: You could include a WebViewer that uses the "data:text/html" url which can then hold a simple <a href> link to the page you want them to go to. It won't actually log them out, but if you have a short enough timeout that's not a problem.

 

I have done the above. One thing to watch out for is to make sure is to make sure the Web Viewer points to https. Triple8 FM hosting is secure so if http is the address in the Web Viewer it will be blank.

 

 

 

Option C: use the "homeurl" feature described here
http://fmforums.com/...ow-on-app-exit/

 

I maybe wrong on this, but this option seems to only work if I am serving the database through my own Filemaker Server. If I am wrong, how would this work fi the FM Server is remote like on Triple8.

 

Again thanks for the pointers, I am making some progress.

 

Sam

Hi Sam,

The 'homeurl' can be to any web page you want - it doesn't have to be on triple8 servers....

Sky

Thanks Sky,

 

I will give it a try.

 

Would you have any idea as to how to create  a "Remember Me" for the user name and password fields for autofill on the FM login page?

 

Sam

Thanks Sky,

 

I will give it a try.

 

Would you have any idea as to how to create  a "Remember Me" for the user name and password fields for autofill on the FM login page?

 

Sam

 

This feature is browser-dependent.  For example, in Safari, the user would go to Preferences / Passwords and check the box "AutoFill user names and passwords".  

 

I've noticed a slight bug in this feature in Safari 7.1.3 :  If the user begins typing the username and then hits ENTER or RETURN to select the autofill, the password field doesn't get filled.  If, however, they use the Mouse to click on the autofill option, then it works.  

Xochi

 

Could you tell me what kind of login form you are using because I have tried my form in Safari and Chrome and neither autofills.

 

I am using a layout from my database as the form, but the user name and password fields are global fields so no records show when a user enters it. The global fields are then set to the regular user name and password fields and re-login script is run.

 

Thanks for your help - Sam

Rather than using fields on a layout, I'm using the "Show Custom Dialog" script step, which allows the password field to be properly secured (check the "Use • character" on the Input fields option).

Thank you - I learn something everyday when it comes to Filemaker.

Xochi,

 

I am working on a Mac and with Safari, the user name and password are remembered.

 

They are not remembered in Chrome and Firefox even though I have Remember passwords for site checked.

 

Am I missing something?

You may be surprised to learn that Firefox is technically not a supported browser for WebDirect  (I know I hadn't expected this myself).  In my (brief) testing with WebDirect, Firefox works OK but there are formatting issues, especially with Center-aligned text boxes.

 

I just ran a test with FF and I, too, and not seeing it remember and store passwords, unfortunately.  I've not tested Chrome yet.

Thank you for the info. As much as I hate to go this way, I may try to convert my old CWP for fp.7 to 12. I am finding too many gotchas with WebDirect. 

I agree with the above... I also use triple8 and the homeurl feature works well.... E.g your link to your database might be:

https://FM63.triple8.net/fmi/webd/?homeurl=http://www.yourdomain.com/YourExitScreen.htm#YourDatabase

That will take you straight to the database login and then on exiting go to your exit screen....

Hello there, bumping up this topic, when you used triple8 to host your db set to autologin, did it propely load the db when you used the direct link of it? Mine always says "Database not available." and goes back to login, even my file set to auto log in Guest. Right now I am not receiving any response from triple8 support on my tickets either.

Thanks!

Found the issue, you can't have spaces in the db name, simple!