Did you had any luck with this, I'm currently trying to do this for Filemaker 15, but still any luck.
Thanks for any help.
I don't think there is a way to do this in Web Direct itself yet (maybe in 16?), but I have done this using a simple web page (easy for me since we're running CWP on the same server). I've created a web page that I give to the users as the url. On that web page is a link to the Web Direct database that uses the homeurl parameter to make sure they are returned to the same web page when they log out. So, if you have a database named "My Database" on server "FMServer.mycompany.com" linked from the web page "mycompany.com/wdlink", the url for the link to the Web Direct database would look like:
Also, if you (for example) wanted to run the script "Find-selected-record" to find the record with the id "34324-E8YT9-458614" on open, you could add the script parameter:
It took me a while to figure out about adding the script, since the FM docs don't give an example of using both the homeurl and script parameters in the same url.
Users would still get the standard Web Direct authentication dialog, but they would no longer see the Web Direct landing page, just your "mycompany.com/wdlink" page.
I'm struggling with the same issue.
I can setup and configure a custom web page, but that is not my issue.
I want to have the standard home url (https://myserver.com/fmi/webd) go to my custom web page, and I want the user to be returned to that page when they logout or time out.
I can drop them on custom web page (https://myserver.com/mycustompage.html), no problem, but the homeurl trick doesn't seem to get them back to my custom page. If that worked, it would be an acceptable solution. I can program an on Application close trigger to go to a certain URL, but it pops a new window with that URL and the original webpage goes back to the original default WebDirect page.
If anyone has a good solid solution to this, I'm willing to pay for some time to get a reliable solution working.
Thanks, that did indeed have useful info. The trick was modifying the iwp_home.html page to reference my custom login page.
Always seems simple after you figure it out!