Jump to content

jaboda

Members
  • Content count

    54
  • Joined

  • Last visited

  • Days Won

    2

jaboda last won the day on April 18 2011

jaboda had the most liked content!

Community Reputation

3 Neutral

About jaboda

  • Rank
    member

FileMaker Experience

  • FM Application
    16 Advanced

Platform Environment

  • OS Platform
    Windows
  • OS Version
    Windows 10

Recent Profile Visitors

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

  1. That seems to have fixed the problem on my test server, and I'll try it again on our production server in the next few days. Pity this wasn't released a day or two ago 😯. Thanks for the quick turnaround!
  2. So last week I spun up a Microsoft Azure VM to test FMS 17 and it was working well. Last night started migrating our second server and all was good. One of the final things was to install ScriptMaster. Didn't work and stupidly didn't test it last week. Had to roll back to FMS 16 and wasted several hours of work (my mistake for lack of QA)! Today I tried it again on a new VM and could reproduce the issue so it's not specific to our build. Here's what I did to reproduce the issue: Create an Azure VM running Server 2016. Change the language to UK. Install FMS 17. Install Web Sockets (an issue my Colleague sussed out here). Copy the ScriptMaster Plugin into the Extensions folder and try to enable it. I got the following events in the FMS log: Additionally the Event Viewer had two events - A 701 error with the same description as above and the following: Hope this gets sorted soon as I need to roll out FMS 17 :(.
  3. If you're using the 'Register ScriptMaster' FileMaker script (in the example above) then I've made a couple of improvements/bug fixes: The version check should be: SMVersion = "?" or Int ( SMVersion ) < 4 Personally I check for 4.42 as 4 is quite old - but it might be a good idea to check for 5. The HTMLEmail function does not require the GUI, and apparently it performs better without it. Therefore I'd recommend changing the last line of the RegisterGroovy function to: return true;¶" ; "isGui=false" )
  4. Hi Gastion, If you are using the example form then use the FileMaker formatting toolbar - the HTMLEmail command in the example uses the GetAsCSS command to convert it to HTML. Alternatively edit the script to remove the GetAsCSS command and then you can enter HTML directly into the example form. Hope this helps.
  5. jaboda

    Webdirect Rendering Bug

    It seems the problem doesn't exist in Chrome 60, which I've now updated to. So this means it affects IE, older versions of Chrome on Windows/Mac and possibly Edge.
  6. jaboda

    Webdirect Rendering Bug

    Just tried in Chrome 59 on Android which works as expected FileMaker have reproduced the bug and have forwarded it to their Quality and Assessment team for further testing and information
  7. I've noticed a small rendering bug with WebDirect on FileMaker Server 16.0.2. Steps to reproduce the bug: Create a layout with a Top Navigation layout part. Add objects to the Body part. Open a browser and ensure the vertical height is smaller than the layout height. View the layout in Webdirect and there's a horizontal scrollbar, which shouldn't be there. The problem is not caused by a Bottom Navigation part but if one exists it makes the above look much worse. I have created a very simple example database, which is attached. Tested on FileMaker Server 16.0.2 running on Microsoft Azure Windows Server 2016 and Chrome or IE on Windows 7 (all latest versions). Has anyone else noticed this issue? WebDirect Bug.zip
  8. jaboda

    Insert Calculated Result Bug

    It's in 16.0.1 and 16 0.2.
  9. jaboda

    Insert Calculated Result Bug

    I've got a support case open with FileMaker.
  10. jaboda

    Insert Calculated Result Bug

    After further testing it seems the bug is limited to Date fields and is still there. See the updated test DB. FileMaker Server Bug.zip
  11. jaboda

    Insert Calculated Result Bug

    I've just tested it with a clean database (see attached) and it works correctly on 16.0.2. So I'm assuming this was a bug specific to 16.0.1... FileMaker Server Bug.zip
  12. jaboda

    Insert Calculated Result Bug

    It didn't work on 16.0.1, but did on 15 which suggests a bug.
  13. jaboda

    Insert Calculated Result Bug

    The reason I was using Insert Calculated Result is because it was an old script written 9 years ago which was working fine. This is what I was using: Go to Layout [ “Event Log Table” (Event Log) ] Enter Find Mode [ ] Insert Calculated Result [ Event Log::Date; "<" & Get ( CurrentDate ) - 90 ] [ Select ] Perform Find [ ] If [ Get ( FoundCount ) > 0 ] Delete All Records [ No dialog ] End If I have since changed it to Set Field and it works fine again. I have not tried this on 16.0.2.
  14. There seems to be a bug with FileMaker Server 16. Server scripts or scheduled scripts do not work when using the 'Insert Calculated Result' script step as part of a find, but it does on FileMaker Pro. A workaround is to use the 'Set Field' script step, which is fine, but this bug caused us some issues and will no doubt cause others problems.
  15. jaboda

    HTTP POST in WebDirect 16

    I've got some updates about this. Creating a form works by using /fmi/webd/[DB Name] as the form action. Unfortunately it redirects to an invalid URL if an incorrect username/password are entered. It's possible to customise the login dialog, by editing login.html in C:\Program Files\FileMaker\FileMaker Server\Web Publishing\publishing-engine\jwpc-tomcat\fmi\VAADIN\launchcenter (or equivalent folder on Mac OS). However if homeurl is used the generic VAADIN dialogue box is presented to the user. Due to the issues with the custom login form I've gone with the second option for now.
×

Important Information

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