Don't you get an error message that you can't do this because you have layouts that aren't classic?
It was my understanding that you'll get that error message if even one layout in the file is not classic--even if it is not accessed by IWP users.
How to Setup FileMaker Server for Remote Access | HomeBase Software
FileMaker Instant Web Publishing, Part I: Is IWP Right For You? | the beezwax buzz
FileMaker Instant Web Publishing, Part II: Five Top Tips for Success | the beezwax buzz
FileMaker - How to Setup a Network Router for FileMaker Remote Access
Open Port Check Tool - Test Port Forwarding on Your Router
Port Forwarding Software - Easy But Very Powerful
FileMaker Instant Web Publishing
Top 10 Instant Web Publishing No-No’s | GEEKSHARKS
IWP Outside of Network . Using FileMaker Pro . Forum . FileMaker Forums
Port Forwarding Information | FileMakerSpecifying a port number for Instant Web Publishing | FileMakerWeb Publishing | FileMaker Pro 12Instant Web Publishing with FileMaker 12 | FileMaker
Troubleshooting FileMaker Web Sharing in FileMaker Pro | FileMakerInstant Web Publishing with FileMaker 12 | FileMaker
Top Instant Web Publishing Answers | FileMaker
FileMaker Web Publishing: A Complete Guide to Using the API for PHP | Allyson Olm, Stephen Knight, Michael Petrov | digital library BookOS
Day 10 - FileMaker Instant Web Publishing - MightyData - YouTube
How to use set up FileMaker IWP (Instant web publishing) for public accessFileMaker Databases on the iPad and iPhone by Arthur Evans
How to Setup FileMaker Instant Web Publishing for Neo Code Software Internet Web Hosting
FileMaker Server and FileMaker Server Advanced port numbers | FileMaker
Yes, that is the message I get. I do not get that message if I convert the theme of the default landing page to classic, even if that is the only layout that is classic. But when I try to script the IWP user to the correct menu page, I get the message. The user cannot ignore the message--they are unable to get into the database.
PhilModJunk commented that I would get the result I am getting if any layout in the database is not in classic mode. However, I have seen on YouTube people explaining the use of the if ( PatternCount ( Get (ApplicationVersion) to direct the web user to the correct layout which works on the web. I'm a novice, so my conclusions are often wrong, but I'm concluding this is doable, but I've not been able to get it to work. Nevertheless, thank you PhilModJunk and DavidAnders for taking the time to try to help me.
By the way, my database is hosted by MacUSA using Filemaker Server Advanced if that sheds any light on my problem. Thanks to PhilModJunk for pointing out that I need to be more explicit in explaining my problem. My problem is that the user connecting to the database, after putting in user and password, gets the message "The layout is not supported for Instant Web Publishing because it does not use the Classic theme. See the database administrator." I do not get that message if I convert the theme of the default landing page to classic, even if that is the only layout that is classic. But when I try to script the IWP user to the correct menu page, I get the message. The user cannot ignore the message--they are unable to get into the database.
My sample app worked just fine using the following script under the OnFirstWindowOpen Script Trigger.
I used the following script :
Go to Layout["IWPLayout"]
Go to Layout["RegularThemeLayout"]
Under File, File Options, Scrip Trigger, OnFirstWindowOpen select the above script.
I finally figured it out. The script I was focusing on was within another opening script. The problem was in the first script. It was trying to set a value to a field in a layout that was not in classic theme. That was apparently the problem. It is working now. Thanks for all of the help!
Interesting. Please note that my earlier comment about themed layouts was phrased as a question. I've seen posts here that suggested that you would get this error even if an unused layout was not classic themed and others, like this one, that indicate otherwise. Your post suggests a posible explanation as to why that might have appeared to be the case for some others that have posted here.