Opening your SeedCode files in FileMaker 13
Most Things Just Work
Most FM12 files will work in 13 with no issues or with only slight cosmetic adjustments required.
Solutions that aren’t designed for Web Direct won’t work there unless they are extremely simple. Web Direct is a bit like IWP (Instant Web Publishing) in that sense. Since none of our products were designed to work in Web Direct, they likely won’t. You’ll need to make new, simpler layouts specifically for Web Direct to take advantage of it with existing solutions. We’re psyched to see what we can do in Web Direct going forward, so stay tuned.
FileMaker 13 Ready Products
Notes follow for the latest versions of each SeedCode product…
|Free Calendar||No Issues|
|Pro Calendar||Minor Cosmetic Issues|
|SeedCode Complete||Minor Cosmetic Issues|
|GoZync||Minor Cosmetic Issues, Pricing Changes when Go Connects to FileMaker Server|
|GoMaps & Pro Maps||Minor Cosmetic Issues, Pricing Changes when Go Connects to FileMaker Server|
|SeedCode Subscribe||New Install Location. Note, Subscribe does NOT require concurrent licensing.|
|fmSearchResults||Minor Cosmetic Issues|
|FM Chat||Minor Cosmetic Issues|
|Zulu||New Install Location, New Version|
|SQL Explorer||New Version, Minor Cosmetic Issues|
Cosmetic Issues – most likely hidden text is peeking through. Read up on how to correct this here: hiding objects in FileMaker 13.
Install Location – FileMaker 13 changes some of the locations used in web publishing. Read up on each specific product below.
Notes on each product
Pro Calendar. You’ll see some previously hidden orange text peeking through. Just change the font size on the conditional formatting from 300pt to 500pt as described here.
SeedCode Complete. Some of the conditionally formatted text on the “browse” tab of time tracking will need to have it’s text height adjusted in layout mode. All other layouts are without issues.
GoZync. Like the Pro Calendar, some previously hidden orange text may peek through on the configuration tab of GoZyncHosted. Just change the font size on the conditional formatting from 300pt to 500pt as described here and reduce the height of the object a few px. The “home” layouts in our Quick Contact example have the same issue: just change the conditional formatting size of the orange text and tab names to 500pt.
FileMaker Server 13 now charges for concurrent connections from FileMaker Go. The idea is that paid clients (like FileMaker Pro) get free access to FileMaker Server while free clients (like Go and Web Browsers) pay for access. Learn more about purchasing concurrent connection licenses from FileMaker here.
GoMaps & ProMaps. Some previously hidden orange text may peek through; wherever your see this, simply change the font size on the conditional formatting from 300pt to 500pt as described here. If you’re using Go Maps, FileMaker Server 13 now charges for concurrent connections from FileMaker Go; learn more here.
SeedCode Subscribe. When you install SeedCode Subscribe on FileMaker Server 13 you’ll install it in a slightly different place than you did in FM12’s Server. See “Step 2” in “Installation Details” here: Installing SeedCode Subscribe. Subscribe does NOT require concurrent licensing as it uses custom web publishing (PHP) not Web Direct. More on concurrent licensing here.
fm Search Results. If you’re using the “retro” skin (green text on a black background) you’ll want to change the line height as the very tops of subsequent lines will show up otherwise.
FM Chat. Some previously hidden orange text may peek through; wherever your see this, simply change the font size on the conditional formatting from 300pt to 500pt as described here.
Zulu. 360Works, our co-authors on Zulu, are now providing support for Zulu. Folks using FileMaker Server 13 will need to install Zulu manually as 360Works hasn’t finished the FMs13 installer yet: follow the “manual installation” instructions here. For more info, please contact 360Works.
SQL Explorer. Some previously hidden notes and tips will peek through. Adjust their conditional formatting as described here. We have a new version of SQL Explorer which addresses these cosmetic issues and fixes some bugs users reported after opening the solution in Mavericks. Download the new version.