# 19.2 now available

**URL:** <https://the.fmsoup.org/t/19-2-now-available/1542>\
**Category:** Claris\
**Created:** [December 16, 2020, 5:53pm UTC](https://the.fmsoup.org/t/19-2-now-available/1542 "2020-12-16T17:53:10Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bobino](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/bobino/32/194_2.png) [@Bobino](https://the.fmsoup.org/u/Bobino)\
**Post date:** [December 16, 2020, 5:53pm UTC](https://the.fmsoup.org/t/19-2-now-available/1542/1 "2020-12-16T17:53:10Z")

</div>

Hi everyone,

Claris said we would see product updates more often. With this in mind, here are a few links to the newly available 19.2 releases notes:

FMS - [ClarisPKB](https://support.claris.com/s/answerview?anum=000035415&language=en_US)  
FMP - [ClarisPKB](https://support.claris.com/s/answerview?anum=000035376&language=en_US)  
FM Cloud - [Claris FileMaker Cloud 2.19.2.1 Release Notes](https://help.claris.com/en/cloud-release-notes/index.html)

The desktop product can be downloaded here: [Download Claris FileMaker updates and resources](https://www.claris.com/resources/downloads/)

The server product can be downloaded via your Electronic Software Download page (or from the Claris Customer Console).

# Important

Server 19.2.1 on Windows: PHP is no longer installed with FileMaker Server. After an upgrade, the folder \FileMaker Server\Web Publishing\publishing-engine\php\ is no longer present. To preserve your existing PHP installation, back up the PHP folder and restore it after the upgrade is complete.

\*there could be other elements to pay attention to, I simply chose to outline this one. Make sure to read the release notes before installing the software.

---

<div class="post-metadata">

**Author:** ![Malcolm](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/malcolm/32/196_2.png) [@Malcolm](https://the.fmsoup.org/u/Malcolm)\
**Post date:** [December 16, 2020, 8:45pm UTC](https://the.fmsoup.org/t/19-2-now-available/1542/2 "2020-12-16T20:45:01Z")

</div>

The advice to preserve the settings in HTTPServer would have been a helpful note for many versions back 😄

---

<div class="post-metadata">

**Author:** ![Torsten](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/torsten/32/1574_2.png) [@Torsten](https://the.fmsoup.org/u/Torsten)\
**Post date:** [December 16, 2020, 8:59pm UTC](https://the.fmsoup.org/t/19-2-now-available/1542/3 "2020-12-16T20:59:21Z")

</div>

Anyone knows where the link for the server update can be found...?

Ok, found it in ‘Details’.

---

<div class="post-metadata">

**Author:** ![Malcolm](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/malcolm/32/196_2.png) [@Malcolm](https://the.fmsoup.org/u/Malcolm)\
**Post date:** [December 16, 2020, 9:05pm UTC](https://the.fmsoup.org/t/19-2-now-available/1542/4 "2020-12-16T21:05:20Z")

</div>

More on the PHP, this time for MacOS, from the FMS 19.2.1 notes:

> FileMaker Server supports HTTP/2, which provides faster web performance for web publishing including Claris FileMaker WebDirect®, FileMaker Data API, and XML. HTTP/2 is enabled by default on all versions of Windows and Linux. HTTP/2 is available on macOS Catalina or higher but must be enabled with the Enable\_HTTP2.sh script, which is located in /FileMaker Server/HTTPServer/.  
> Note: HTTP/2 is not supported on earlier versions of macOS.
> 
> If you’re using HTTP/2 on the Mac platform, be aware of the following:
> 
> Apache HTTP Server (httpd) processes may fail when using the FileMaker Data API.  
> PHP web publishing is not supported.  
> Use the default installation directory since custom locations are not supported.

---

<div class="post-metadata">

**Author:** ![xochi](https://avatars.discourse-cdn.com/v4/letter/x/0ea827/32.png) [@xochi](https://the.fmsoup.org/u/xochi)\
**Post date:** [December 17, 2020, 12:07am UTC](https://the.fmsoup.org/t/19-2-now-available/1542/5 "2020-12-17T00:07:31Z")

</div>

> - When FileMaker clients cancel finds in hosted files, finds are now halted quickly. Previously, canceled finds continued to run on the host and failed to stop promptly on clients.

Hallelujah! I can't tell you the number of times I've kicked off a find, realized it was using unstored calcs and going to take hours to run, Canceled it, had nothing happen, and eventually gave up an force-quit FMPro, losing my flow completely (and silently praying I wasn't corrupting the database in the process).

---

<div class="post-metadata">

**Author:** ![anon45965781](https://avatars.discourse-cdn.com/v4/letter/a/13edae/32.png) [@anon45965781](https://the.fmsoup.org/u/anon45965781)\
**Post date:** [December 17, 2020, 1:23pm UTC](https://the.fmsoup.org/t/19-2-now-available/1542/6 "2020-12-17T13:23:42Z")

</div>

Thanks, I would not have known about this update if it weren't for your posting. 🙂

---

<div class="post-metadata">

**Author:** ![jormond](https://avatars.discourse-cdn.com/v4/letter/j/35a633/32.png) [@jormond](https://the.fmsoup.org/u/jormond)\
**Post date:** [December 17, 2020, 3:27pm UTC](https://the.fmsoup.org/t/19-2-now-available/1542/7 "2020-12-17T15:27:23Z")

</div>

Update notifications emails typically happen a few days after the release. The in-app notification can be a few days to a few weeks later.

Trying to see if they can post these notifications somewhere more helpful. The post on the community gets buried most often.
