There's a PDF you can read about web publishing that comes with your copy of FileMaker. You can find it in the documents sub menu under Help.
No script trigger can be tripped directly by user actions via a Web Browser. The only way a script trigger can be tripped from a web browser is if the user performs a script that in turn trips the trigger.
Example: User clicks a button to perform a script. Script includs the script step go to field to put the cursor in a field set up with the OnObjectEnter script trigger. The sript will trip the trigger, but clicking on field displayed in the web browser will not.
It's working only with button trigger, I was read the PDF contents but I dont have the answer
So, I need to use layout script trigger like OnRecordLoad with every click navigation button between records
I try OnRecordLoad and all script trigger but it's not working with IWP . Is there any idea about it ?!?!
If you are using a button to perform the script, why do you also need the trigger? Why not include the steps from the triggered script as part of the script performed from the button?
I have to make script every load page to security issues and to make sure is current user cannot see other form that has not related with it
I don't see why you wouldn't use buttons with script to control this for your web published layouts. Then there is no need for a trigger. You may need to hide the status area and replace a few controls in it with controls you create to do the same thing.
If there is any way to disable status bar every thing after that will be OK
but I know I can just hide status bar.
Our customers are not normal users , they are profissional user, So I cannot use hide/show with them
I can create 2 button to use them like navigation button but the status bar still hide not disable, any time the user can show the status bar I dont
want to show it again after hide.
thanks my friend .
I would use Show/Hide Status Area [Lock ; Hide ]
To hide and lock the status area whether they are "professional users" or not. If needed, controls shown in this status area can be replaced with similar controls added directly to the layout to provide the missing functionality.