Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


jaboda last won the day on April 18 2011

jaboda had the most liked content!

Profile Information

  • Location
    Findhorn, Scotland

FileMaker Experience

  • FM Application

Platform Environment

  • OS Platform
  • OS Version
    Windows 10

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

jaboda's Achievements


Enthusiast (6/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges



  1. It seems the same problem exists with the BaseElements Plugin as well (using BE_ExecuteSystemCommand).
  2. I'm using RunShellScript to run a Ping on WIndows. This works well if the host is working, but if it times out it pops up a ScriptMaster error and returns 'ERROR' instead of the Ping output. I'm not good with Groovy but it looks like it's not trapping the error output. Is there a way to do that with RunShellScript? Alternatively has someone created a Ping script for ScriptMaster?
  3. I'm trying out the new Rich Text Editor and one thing which doesn't seem to work is 'Go to Object' with it. It doesn't work in FileMaker (Windows) or WebDirect. Does anyone have any idea how to get it working? I tested Go to Object with a standard Web Viewer and it worked fine so it seems to be an issue with Quill.
  4. I don't think that's strictly correct. For example I may allow users to delete records, but I don't want them to use the 'delete all' menu item and possibly delete thousands of records at once. As it happens I generally restrict record creation/deletion to my scripts (and therefore check the validity of the action within the db) as per your third point, but as users can edit records they can perform an import and update many records at once. This will have unintended consequences and probably cause some data corruption. I do not want them to be unable to edit records, but want them to be unable to do so via an import. Therefore I think it's still valid to be able to remove this menu item in WebDirect.
  5. I've made some progress on this. Take a copy of jwpc.jar in FileMaker Server\Web Publishing\publishing-engine\jwpc-tomcat\fmi\WEB-INF\lib and rename it to jwpc.zip. Unzip the contents. In the archive are the following xml files, which can be edited to remove the Import Records (or any other) menu item: com\filemaker\jwpc\iwp\ui\statusarea\menubar\main-menu.xml <menuitem name="IMPORT_RECORDS"> <menuitem name="FILE_DOT" /> </menuitem> <separator /> com\filemaker\jwpc\iwp\ui\statusarea\menubar\menu.xml <menuitem name="IMPORT_RECORDS"> <menuitem name="FILE_DOT" /> </menuitem> Update the files in jwpc.jar (taking a backup first) and restart FileMaker Server and you should be good to go. Unfortunately this doesn't work - and causes WebDirect to fail to start. Any ideas on why this is? I'm assuming there's a CRC check on jwpc.jar or some other issue.
  6. I don't know how short the minimum is but I assume that whatever it is .001 should cover it. The main problem is if the user interacts during the pause. The Yellow bar can be suppressed by using the following script: You may not need the Refresh Window, dependent on your use case. As with most things of this nature testing is important, especially as it might change with new Web Direct versions (though this has been fairly stable as far as I recall).
  7. I suspect it is a font issue, but how can that be rectified in Web Direct? The only way I can think is to use a web viewer which would cause massive slowdown in this solution. Also I couldn't get the Emojis to display correctly in Chrome in https://typezebra.com, though they did in Firefox so not sure that'd even fix it.
  8. I think I've found the issue. On Chrome/Edge those Emojis don't display properly - even though they do in Emojipedia, and in Firefox. Not sure if there's a workaround apart from using different Emojis that work 😒.
  9. Yes it does and it's working now I've upgraded to 19.2.1.
  10. This is a strange one. I use Emojis in WebDirect and I thought it was working when I developed it but testing it again and it doesn't. The '⬅️' and '➡️' Emoji work fine but the '↔️' and 'ℹ️' Emojis look very different (like they do in FileMaker Pro on Windows). I'm using FileMaker Server 19.2.1 accessed via Chrome 89. Any ideas?
  11. WebDirect usually does not update the window when scripts are running, and far less reliably than FileMaker Pro. Refresh Window also usually doesn't work - instead I use a Pause/Resume script step for 0.001 seconds and this fixes many issues.
  12. Found a small bug with this export. When exporting the fields the above examples either use the Quote function or add \" to add a double quote to the start and end of fields. Unfortunately if the field contains double quotes this is not compliant with RFC-4180, which specifies that they should be escaped with a ". The above examples either leave them as is or use the FileMaker standard of \". The fix is easy though - use the following custom function instead of the Quote function:
  13. My reply perhaps wasn't clear. Yes if the self-extractor created 'FMS' instead of 'FileMaker Server 19' that would resolve many of the issues if it's run from a folder without a space in it (for example 'C:\users\admin\Downloads'). However if it's run from 'C:\Users\John Smith\Downloads' or 'C:\FIleMaker Installers' then it would still fail. Therefore they should fix the original issue. 19.1.2 worked properly so why not 19.2.1?
  14. That wouldn't resolve the issue - if the installer is extracted in a folder with spaces in the name then it would fail. I suspect they've missed out quotes when referring to the FMS msi package, which is just bad testing.
  15. After an e-mail exchange with Claris they provided a fix which might be useful to others. By default the installer extracts to "FileMaker Server 19". However the Setup in that folder won't work if there are any spaces in the path name. To fix the issue move the contents of that folder to somewhere without spaces in the name (for example C:\users\admin\downloads\FMS not C:\users\admin\downloads\FileMaker Server 19). I am amazed and quite annoyed that this simple issue got through testing. I expect better from Claris. However thankfully the fix is simple.
  • Create New...

Important Information

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