Basics of Communication

YearbookFusion communicates directly with your FTP server.

The YearbookFusion order form includes the following fields, which will be used by all installed licenses of YearbookFusion that are associated with your RepID:

FTP server	Example: 123.123.123.123 Example: ftp.yourcompany.com
Port	Example: 21
User ID	Note: this user must have full control over the folder including the ability to create and enter subfolders
Password
Default path	Example: “/ybf”
Preferred upload format for flattened projects	Example: JPG, PSD, PDF

Please ensure that you have provided LumaPix with this information.

Server Ping Overview

When an end user is ready to upload a package to the publisher, they choose 'upload to Publisher' from the file menu. The following things take place:

• The current project is archived (referenced materials are pulled into a single file)
• A script on the publisher's server is called, indicating that an upload is imminent
• The upload takes place via FTP
• A script on the publisher's server is called, indicating that upload is complete

This communication gives the publisher's back-end processes an opportunity to prepare for content - for example, to offer a storefront / accept credit cards / verify shipto details / etc.

Responding to the ping is optional- publishers using a 'hot folder' approach can ignore the ping (and this example script).

Sample script

A sample script is available for publisher IT staff to examine and modify.

It demonstrates how to interpret the incoming XML file, present a page offering some of those details, and act on the description of the incoming project.

Contents:

• a sample XML file (representative of what is sent prior to upload)
• a sample PHP script (intended to be replaced with publisher-specific actions)
• a readme file

Click here to download the sample package (Zip)