Please click on one of the support topics below to read more.
DFP – Proof PackageMaker is an online service that allows you to upload one or more PDF-files, and receive zip-packages back that are ready for upload to DFP – Proof
The service will extract images for each page in the PDF and save those for 24 hours. You will need to upload the package to DFP – Proof within that time to ensure that the upload is successful.Open PackageMaker
We currently offer licensed extension panels for Adobe CC that will allow you to integrate with DFP – Proof, and handle the proofing process from within your favourite applications. Please follow the intstructions below to install and configure them.
1. You will need to store the thumbnails of images on a webserver that is publicly reachable from the Internet. This is needed since DFP – Proof fetches these assets when importing the zip-package and image thumbnails that are used to create your Proofing Project.
As we do not currently support authentication we strongly suggest that you store your images in a hard to guess location, and switch off directory browsing on your webserver.
As the extension panels are built for Adobe Creative Cloud you will be able to use the file storage provided in your Adobe CC license. The setup described below shows how you use this service to store your files, but you may use any other webserver of choice. If you intend to use your own webserver you may now skip to step 6.
Make sure that you have logged in to your Adobe CC account.
2. Create a folder with the name "DFP_PROOF" within your Adobe Creative Cloud folder, it may be placed anywhere as long as it is within the Adobe CC folder. This will be the folder where thumbnails and other necessary assets for DFP – Proof are stored.
3. Right click the DFP_PROOF folder and select "View on Webiste".
If your context menu does not show this option you may also use the Adobe CC application shown above and select "Cloud documents"
4. When the Adobe CC web browser opens, click the share icon for the DFP_PROOF folder
5. Get the sharable link. It will be used in the next step, and will also enable public sharing on the DFP_PROOF folder.
6. Unfortunately Adobe has not made it too easy to find the public URL to a shared item, so we will have to do some hard work to locate this. We recomment using Google Chrome as the browser for this exercise. Enable inspection of the Adobe Files web page by right-clicking on the browser window. You may also use ctrl/cmd key click to show the context menu.
8. Click the "Network" tab and then enter the sharable link URL retrieved in step 5. Wait until all data is loaded and enter :metadata in the search field. You should see a find result at the top of the list with the :metadata heading. Click on the text on the row directly under the :metadata heading.
9. Copy the URL to your shared DFP_PROOF folder, excluding the :metadata text at the end. Save this URL for later, as we will use it to configure the extensions later on.
10. Download one of the Adobe CC extension installers available from third party developers. We suggest using zxpinstaller
11. Start the installer and drag the DFP – Proof extension file in .zxp format directly on to the installer window. The extension will be installed to all Adobe CC applications by doing this.
12. Start Adobe Bridge, InDesign, or Illustrator, as these applications support all our extension panels, and open the installed panels from the Window menu -> Extensions.
13. Select Preferences from the extension panels top right corner. The configuration file will open in your systems default text application. Make sure that this is an application that supports editing of text files.
We suggest using BBEdit on OS X, or Notepad++ on Windows.
14. Configure the extension panel. For normal use only the parameters below need to be edited. If you provide the optional user name and password, you will not need to fill these in each time you open the extension panel.
15. If you are installing more than one extension panel, please repeat steps 9 and 10 for each panel. At the time of writing all our panels have an identical set of parameters, so they all share the same config file. This could change at any time, so please review settings for each new extension panel.