Where does the Forms/form directory reside? I do not see this in IIS or Windows. I can access it in a browser and I can see network traffic visiting this directory when working with LF Forms.
Question
Question
Replies
If you mean the site/application files, the default install folder is
C:\Program Files\Laserfiche\Laserfiche Forms\Forms
In IIS, if you go to Sites > Default Web Site > Forms
Then select "Advanced Settings" it will show you the physical path.
Hi Jason
Yes, within this directory there is another directory named "form" that can be reached in the browser, but I do not see it in IIS or a physical folder for it. This is a first for me, in my experience with web design you must have a folder in the web directory in order to reach a new sub directory in the browser.
I'm not sure exactly what you mean.
Keep in mind that web applications are not exactly the same as Web Sites. In a web application, URL paths contain Controllers, not just site directories/pages.
In an MVC .NET application, you could have a controller called "test" and the URL might be "http://server/test" but there wouldn't have to be a matching directory folder.
The main site would have a physical path and entry in IIS, but "test" would not have an associated directory as it is an application controller, not necessarily a path to a file.
Ok, it must be a controller then, since there is no physical directory.
I am trying to troubleshoot a problem where /Forms/form/lookup can't be found, preventing lookups from running.
I couldn't even find it myself since I couldn't find the form folder. I am not sure how to troubleshoot controllers that go missing.
What’s the exact error message you’re getting and what is prompting it?
A controller should not be “missing” as it is part of the application code.
In the browser it is just the classic 404 error, in the Forms Event Operational logs it is just a PageExpired error.
So something in the controller is expiring the page, which is causing IIS to return 404 (not found)
I tried finding a method to override page expiration settings in IIS, but nothing seems to work. I think Laserfiche has code built in to force expiration.
If you enter a form that has a lookup and use the trigger fields, then check the console, you will see calls being made to this site /form/lookup.
If you try to use 2 separate forms at the same time, from the same tab, and they both have lookups, the second form causes the first forms /form/lookup to turn into a 404 page.
It's not really supported functionality but was looking to try to find a workaround.