Jump to content

Custom homepage

Recommended Posts

I'm hoping someone else out there has had some success with this, or at least some thoughts to lend.


The WebDirect Guide has a simple and rather straightforward instructional page regarding the use of a custom homepage in WebDirect, instead of the default Database Homepage, for a more seamless solution without the WebDirect branding. I have followed the instructions to the letter, making the desired changes to the fmwebd_home.html page in the HTTPServer/conf folder, and even restarting the web publishing engine. However, no matter what changes I make, no change is seen on WebDirect's homepage. Even if I completely remove the fmwebd_home.html file from the folder, as well as the copy of the original, the default Database Homepage still continues to show.


Is this a bug? Is there some caching issue (not on the client end, since it happens even if I connect from a computer that has never connected before)? Where is the actual page that is showing, and most importantly, how can I change it?

Share this post

Link to post
Share on other sites

There is some documentation from FileMaker on this, but it does not work properly.  I found this on another forum and it worked for me:


Using a custom homepage

To replace the default Database Homepage, place an HTML file named fmwebd_home.html in the HTTPServer/conf folder where FileMaker Server is installed (Windows) or in the /Library/FileMaker Server/HTTPServer/htdocs folder (OS X). Web users are returned to this page when they log out of a session or the session times out.

You can use the fmwebd_home.html file that is on the disk image as a basis for your custom homepage. Be sure to make a copy of the original file before modifying it. Or you can create your own homepage, such as one that redirects web users to another page on your website.

If there is no file named fmwebd_home.html in the conf folder (Windows) or the htdocs folder (OS X), FileMaker WebDirect uses the default Database Homepage.

To prevent a custom homepage from loading into the FileMaker WebDirect layout frame when a user logs out via a script or when a session times out, add the following JavaScript to the head section of the fmwebd_home.html file:

if (window != window.top) top.location = "/fmi/webd/#";

You can set top.location to the home URL or any other URL.

Share this post

Link to post
Share on other sites

Unfortunately, that's exactly the instructions from the WebDirect Guide, and I can't get it to work for me. Are you using a Mac server or Windows server, if I may ask?

Share this post

Link to post
Share on other sites

Windows 2008R2


If you using a 2 machine setup, make sure your modifying the worker machine.


There was one other part I forgot to mention that is NOT is FileMaker's documentation:


Got to  (Win) FileMaker ServerWeb Publishingpublishing-enginejwpc-tomcatfmiVAADINthemesdefaultlayouts

            (OSX) /Library/FileMaker Server/Web Publishing/publishing-engine/jwpc-tomcat/fmi/VAADIN/themes/default/layouts(OS X)


I changed the imp_home.html file to the following (make a backup just in case):

<script type="text/javascript">
         top.location.href = "http://<you URL to Redirect Goes Here>";
  • Like 2

Share this post

Link to post
Share on other sites

You, sir, are a genius. I had seen that iwp_home.html file before, on my frustrated searches of the entire FileMaker Server directory, but frankly passed it off as some sort of legacy relic from IWP. This is just what we needed, thank you! Now we can actually move forward with the transition! As a side note, at least in Chrome, it does tend to flash the old page at me briefly, including a strange, bright red "Communications Error" message at the top, but only for a moment, before redirecting correctly. I am ok with this, since users will only see it on the way out, and therefore probably won't be scared off. Thank you again!

Share this post

Link to post
Share on other sites

Glad to help. I have seen the Communication error happen (only in Chrome), but it's so brief that it's more of a half second flash.



Share this post

Link to post
Share on other sites

Thank you both for this discussion, every bit of it applies to me but I have an additional issue: When I apply the suggested Javascript it somehow defeats the CSS in my WebDirect projects and ALL of the pages are different.  It doesn't seem to matter how delicately I preserve the other elements of that page or how completely I obliterate them, this javascript just shuts down all CSS in any WebDirect pages on that site.  


What's up with that?  What core concept am I missing here?  I just want to send some users to a WebDirect Session, and yet send them somewhere else I specify when done.  Any ideas appreciated! :)



Share this post

Link to post
Share on other sites

michaelbbateman, the javascript is only for the home page and does a redirect. It would not affect the CSS after the redirect. Perhaps something else is going on. What comes to mind is a previous modification that caused the issues or a layout that has a classic theme. Classic theme just doesn't work well with Webdirect and causes strange issues.

  • Like 1

Share this post

Link to post
Share on other sites

I did the above, quoted here:

Replaced this file with the on with this code:


Path: C;//Library/FileMaker Server/Web Publishing/publishing-engine/jwpc-tomcat/fmi/VAADIN/themes/default/layouts/iwp_home.html

<script type="text/javascript">




There are still some issues, once deployed:

If you “cancel” when prompted to logon, the server will re-direct to something like “http://192.168../fmi/webd#, and leave you on a blank page.

When you logout, also, the server will re-direct to something like “http://192.168../fmi/webd#, and leave you on a blank page.


This is not acceptable to the client who wants branding.

Can someone explain how to error trap for the re-direct?





Share this post

Link to post
Share on other sites

I think solution may be in specifying the home URL.  We produce the following redirect which always puts a user in the correct place and could be modified (I assume) to point them to the custom homepage:


https://<your domain here>/fmi/webd?homeurl=https://<yourdomain here>/#DATABASE

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By Donald Clark
      I have a FileMaker server 13.v10 database solution that changed somehow during development and now does not display several WebDirect objects properly.
      For starters, the text shows up as white on a white background, which it did not do before.  We have been and are using the Cool Grey theme.
      Other problems with display:
      1.  3 value lists will not display:  One a regular list from a set of values, another list from a related layout, and a third a filtered list from another layout.  Another value list works normally
      2.  A picture in a container field (locally stored, not external yet) does not show.
      3.  A filtered, sorted portal does not show the records, nor are they accessible in the portal. The filtering and sorting are straightforward.
      We have tried several things to correct the issue:
      1.  Made a new layout, grouped everything together and paste it on the new layout.
      2.  Made a new layout and made the fields and portal from scratch.
      3.  Simplified and changed the relationships to the portal
      4.  Substituted simplified relationships for the value lists (just for testing.
      5.  Tried the db on FM Server 16 and made most of the changes above, nothing was different.
      6.  Used Dropdowns, Popups, and radio buttons, no change in behavior
      7.  We had FMDiff examine the db for corruption, but they found no problems, so file corruption is not an issue.  We also compacted the db in order to reindex all indexed fields, but that did not help.
      Everything works fine using FM client.  Only WebDirect has problems.
      A photo showing the problems on WebDirect is attached, as is a photo showing the fields properly displayed in FileMaker Client.  Please forgive the look and feel; the photos show the layout as we made changes and are troubleshooting.
      Has anyone seen this before?  Do you have any ideas how to fix it?
      Thanks for your help.

    • By xochi
      Suppose you have a WebDirect database that has both a [Guest] account and regular user accounts.  Is there any way with a special URL or JavaScript to do an automatic [Guest] login that bypasses the filemaker web direct login screen?
      Basically, I want to have a Public area of the site which never asks for authentication, and a members-only are which does, but I don't want to confuse the Public by making them click the [Guest] button ever.
    • By Morenomdz
      Hello there, I've set few text boxes per layout that work as "tutorials", with one button called "help" that changes one global field [tutorial] from Yes to No (and vice versa), commits the record.
      When the global field "tutorial" is set to yes, all the "text boxes" should hide, when it is set to no they should apear. It works perfectly in the fm client but when I got to the web even if I change the field to Yes or No in the client and save the record, the web still shows all the text boxes.
      It looks like the the "hide when" is simple not working. Using 
      table::tutorial = "yes"
      Did a test having the a tex field for the tutorial showing on the layout, it looks like the webdirect is not seeing the field content at all. It shows as empty on web and Yes or No on the client.
    • By jorfasan
      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??
      - Windows 7 professional, SP1 
      - Chrome: Versión 41.0.2272.118 m
      - Firefox:  36.0.4
      - FM Server:
    • By paul.s
      So, We have a unix admin working on our Mac OSX server. I specifically instructed them not to break our Filemaker 13 Apache install. Well it looks like they worked on the machine but broke one thing.
      Does anyeone know where I should look to fix this?
      What works:
      Webserver servers files fine from the Filemaker HTTP Folders.
      Filemaker WebDirect works fine.
      PHP is working.
      PHP is indicated as ON in FMSA Admin.
      Admin pages at http://localhost:16001/admin-consolework fine.
      Admin screen shows green on Webserver. Indicates PHP is enabled.
      This is the only thing that is not working:
      Previous PHP pages which has successfull connection to databases no longer connect to the database.
      I assume that a reference to filemaker somehow got removed from one of the php config files, but I don't know where.
      Can anyone give me an idea where to look?
  • Who Viewed the Topic

    1 member has viewed this topic:

Important Information

By using this site, you agree to our Terms of Use.