Jump to content

Donald Clark

  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Donald Clark

  • Rank

Profile Information

  • Gender
  • Location

FileMaker Experience

  • Skill Level
  • FM Application
    16 Advanced

Platform Environment

  • OS Platform
  • OS Version

Recent Profile Visitors

2,296 profile views
  1. FileMaker Go Bug?

    Hi everyone, We are using sliding panels as a major interface feature. In the development process, we discovered a FileMaker Go Bug: 1. We stack slider panels on top of each other 2. A panel with a portal is underneath a different slider and the top slider is not hidden with "Hide Object When" feature 3. The bottom panel is called with the "Go to Object" script step to show the panel with the portal. 4, The user cannot scroll the panel with a finger swipe unless the panel is hidden. Buttons, popovers, and fields are all accessible, just not the ability to scroll. 5. Scrolling on FMP client works fine. Only Go is affected. How to replicate: Put a panel on a layout. Add a portal with several records (enough to scroll on an iPad). Add a second, invisible (Slider Panel set to no background and no line color) slider on top of the first. Save and test on a Mac (no issues) then on an iPad. The panel will not scroll. Workaround (if any): Use the HIde Object When" command to hide the sliding panel. When there are several panels, the logic gets a bit tricky. Product and version: FileMaker Pro 16.0.4 and Go 15 OS and version: iOS 9.3.5 and 11.2.5 Browser and version (for WebDirect only): N/A Hardware: iPad 3 and iPad Pro (2017) I have attached an .mp4 showing the problem. If anyone can think of a work around that does not include hiding the slider, I'd like to hear about it. We've tried all the Nav and Window commands. It just doesn't work the same as it does on Client. Thanks, Don
  2. Getting only a "?" back in the $result query

    Got the answer at 'FileMaker community: For any kind of web-publishing, it should be installed at: "C:\Program Files\FileMaker\FileMaker Server\Web Publishing\publishing-engine\cwpc\Plugins" If the plugin is in the wrong place, it won't be active and then you'll also get "?" returned on any call to it. Placed the plugin there, restarted the server, worked great. Thanks to HTH over there for helping.
  3. Hi, Yesterday I had tested the CC not present script (somewhat modified) that comes with Plastic from a WebDirect connection. The script worked perfectly 20 or so times over several hours and in previous tests over the past few months. This morning, the FM client still gets the proper results but the WebDirect connection never seems to connect to Authorize.net. Both are using the exact same script from the same layout. Instead of a response with some message or error in it, all I get in the $result variable (and raw response, etc.) is a question mark (?). I'm not sure what that means - is the request not making it to Authorize.net? If not, why not? You can see what I mean at this link: https://monosnap.com/file/OPmsuOmK1IBxIh8Yt9dCnXkBldHtxi I am using FM client 16 on a Mac running High Sierra using Chrome. I also tested it from Chrome on Windows. Again, it runs fine from the client, so I think it is a WebDirect issue. The server is FM 16.3.304 (the latest) running Windows 2012R. The server is running Plastic 2.33, but I upgraded it to V 3.06 on the server to see if that would fix it (no luck, obviously). I also double checked the java version (144), the firewalls and the security setting on the AWS server. All is normal. Any help is appreciated, as this db goes live on Tuesday morning. I have been testing this for a couple of months without any issues. Thanks, Don
  4. WebDirect display problems

    Thanks for your feedback. It's a single file solution, so no related file and now authentication needed. Also, it works fine in Client, just not in WebDirect. Solved! It seems we did not try enough alternate themes to the Cool Gray theme. The Vibrant theme fixed all the major problems, but still has some minor issues, such as Italic text on WD not present in FileMaker, and the need for a black background with white text for one of the portals. Other than that, functionality is 100%!
  5. WebDirect display problems

    Thanks for your feedback. It's a single file solution, so no related file and now authentication needed. Also, it works fine in Client, just not in WebDirect.
  6. WebDirect display problems

    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.
  7. System Script Aborted by User

    Hi Jesse- I am trying to make this work, too, but can't get the scripts to stop aborting. I pasted this into the etc/sudoers file using sudo visudo: Host_Alias FMSHOST = yourhostname Defaults:fmserver targetpw, timestamp_timeout=0, passwd_tries=1 fmserver FMSHOST = (ALL) /Library/FileMaker\ Server/Data/Scripts/*, /bin/kill and changed the hostname to the name returned by running the hostname command. At what point in the sudoers file did you put this command? I have tried it on the end and after the Alias HostName line. Also, did you put your password where it says "taargetpw" or did you leave that there? I have tried changing permissions on all of files I am accessing from the applescript I am running. I have tried using different passwords and usernames. I have tried fmserver user name and password explicitly. All for naught. The script keeps saying user aborted. Do you have any other ideas, perhaps? Thanks- Don
  8. Hi Jesse, I just installed on Mac Mini running 10.9.5 and FM server 14 and got this error: "Installation worked but Web Server forwarding is not working. You will need to access MirrorSync at the direct connect URL:". Do you have any ideas about how to fix it? Thanks, Don Clark
  9. I have two (sometimes more) clients using IWP on a dedicated, shared FM 12 Advanced server running on Win 2008. I rewrote the imp_home.html, imp_auth.html, and the imp_home.css pages, and added websites to IIS, so that each client had a custom index.html home page with their logos and a link to their database. When they logged out, they were returned to their custom home page. This worked flawlessly in FileMaker 11. I cannot seem to make it work in FileMaker 12 except for the default domain, possibly due to some security changes in FM 12 - at least I have found similar code online that broke with FM 12. The client home page link (http://website/fmi/iwp/cgi?-db=dbName&-startsession, for example) returns a 404 Page not found. FileMaker only responds to the default website address or the raw ip. The problem with that is the modified imp_home.html page redirects the user back to the website address in the original link, so the only place they can go on logout is to the default website index.html page on the server, not to their custom home page. Does anyone know what could cause this change or if there is a work-around? Thanks- Don
  10. Enter Find Mode, type Hello in the text field. Make a new find request and type Hi There. Perform the find and all parent records with both of those criteria will show. And, yes, you can script it. Don't feel bad-sometimes we can't see the forest for the trees. Happens to everyone.
  11. Excluding certain records from Value List?

    Check out the Magic Value List example at FileMakerhacks.com. Using ExecuteSQL, you can easily make a dropdown list without a relationship and call exactly what you want. For example (insert your field names below): MVL_Dropdown ( ExecuteSQL ( "SELECT ChartName FROM All Charts WHERE NOT Status = ?" ; "" ; "";"Retired") ) The example file does not give a great explanation, but with a bit of work, you can set it up for any file. Essentially, you use a combination of custom functions, SQL, a couple of scripts, script triggers, and a global field to generate drop down lists, checkboxes, and radio buttons, as well as conditional lists based upon input from other fields. Take the time to learn this technique and you won't regret it.
  12. FYI - no help needed. This post is just to help out others. I had a situation where I was running FM 12 Advanced with RemoteScripter on a Windows 2008 Server. RemoteScripter requires a "robot" file running on FileMaker Pro Client (not server) that can handle the run script requests from IWP clients or web pages via URL. Running the client on the server was the only viable solution for my client. The problem was, what happens if the server restarts unexpectedly or if you have it restarting routinely after installing patches? The FileMaker client "robot" needs to be running for RemoteScripter to function, so I needed to find a way to start the client and the database automatically. Here's how to do it. First, make a windows shortcut file to open your database from the desktop (see here for more info). Here's an example: fmp://AcountName:Password@IPAddress/MyDatabase.fmp12 Copy that line into a web browser and click on the little icon to left of the address and drag it to the desktop (again, see here for more info). Double click the icon to make sure it opens the file. Next, move that shortcut to the following folder: C:\Users\username\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup Now when you login into your server, your database will start. Finally, set up your windows server to auto login on startup - click here to learn how to do that. It's not hard. That's it - when your server restarts, windows will login and your database starts automatically. One note of warning - if anyone has access to your physical machine, they will be logged on automatically on startup or restart. My machine was in the cloud, so that was not a problem. I also tried to remote desktop into it with just the ip number, but needed the user name and password to do that successfully. Consider the security implications before implementing this solution. Enjoy! Don Clark FM Database Consulting
  13. Avoid iwp homepage on entry and exit

    See this thread: http://fmforums.com/forum/topic/85096-custom-login-page-for-database-homepage-default/page__hl__windows%20auto%20start%20file%20server#entry395809 It may be what you are looking for... Don Clark
  14. MAC Custom login page for 'Database HomePage' default?

    Use dsghs's info to get to the imp_auth.html and imp_home.html files. Make a new imp_home.html file with this content: <script type="text/javascript"> document.write(location.protocol); if(location.protocol == "http:"){ window.location = "http://" + window.location.hostname; } else { window.location = "https://" + window.location.hostname; } </script> Make a new iwp_auth.html and change the reference css file (located just above the </head> tag: <link href="/fmi/iwp/res/iwp_home1.css" rel="stylesheet" type="text/css"> Make a file named imp_home1.css and copy this into it: /* copyright: © Copyright 2003-2010 FileMaker, Inc. All Rights Reserved */ .databasehomepage { color: #CCCCCC; font-style: normal; font-size: 16px; font-family: Arial, Helvetica, Geneva, Swiss, SunSans-Regular } .bannerWhite { color: #CCCCCC; font-size: 28px; font-family: Arial, Helvetica, Geneva, Swiss, SunSans-Regular; letter-spacing: -.5px } .links { color: #3333CC; font-size: 16px; font-family: "Times New Roman", Arial, Helvetica, Geneva, Swiss, SunSans-Regular } #relativeBannerBox { position: relative; left:0; top:0; width: 100%; height: 60px; visibility: hidden; display: block; overflow:hidden;} #bannerBox { background-color: #FFFFFF; position: absolute; left:0; top:0; width: 100%; height: 30px; visibility: visible; display: block; overflow:hidden;} #fmBox { text-align: right; position: relative; top: 20px; left: 0px; width: 100%; height: 35px; visibility: hidden; display: block } #homeBox { text-align: right; vertical-align: bottom; position: absolute; top: 40px; left: 0px; width: 100%; height: 25px; visibility: hidden; display: block } #iwpBottomBox { position: absolute; top: 17px; left: 17px; width: 550px; height: 40px; visibility: visible; display: block } #iwpTopBox { position: absolute; top: 15px; left: 80px; width: 550px; height: 40px; visibility: hidden; display: block } #linksBox { position: absolute; top: 250px; left: 15px; right: -15px; height: 100%; visibility: visible; display: block; } A { color: #3333CC; font-size: 16px; font-family: "Times New Roman", Arial, Helvetica, Geneva, Swiss, SunSans-Regular } .db { vertical-align:text-bottom; } Rename your original files (and back them up) and put these new files in the folder. When you logon to your website index page, put a link to your database. Clicking that takes you to a mostly blank login page (no graphics, although you could modify that with css), and when the user logs off it will take them back to the index page. This works with multiple websites (including https) and multiple databases.

Important Information

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