- Getting Started
- The Main Class
- Create a Signature Field
- Signature Appearance Modules
- Signature Modules
- Timestamp Modules
- Asynchronous Signature Workflow
- Sign Several Times
- Signing PDF Forms
- Long-Term Validation (LTV)
- Trust Settings
- LTV (pre-release)
- API Reference
Getting Started System requirements, installation and loading the SetaPDF-Signer component
Table of Contents
Additionally the Signer component requires following PHP extensions to be enabled:
The SetaPDF-Signer component makes use of classes and methods of the SetaPDF-Core component. The Signer component itself is integrated into the same structure and is fully covered by the autoload function of the Core component.
Loading the SetaPDF-Signer component is that simple:
The SetaPDF-Signer component must be able to save temporary files in the filesystem. This is done with the help of the
SetaPDF_Core_Writer_TempFile class. This class acts like a proxy around the
SetaPDF_Core_Writer_File class but will work on a temporary file that will be deleted in its
Temporary files are needed because most signature modules and/or their internal signature functions require the data that should to be signed is accessible through a local file path. Another reason and benefit is that this solution will allow you sign very large PDF files without hitting any memory limit.
The class uses the path returned by sys_get_temp_dir() as its default folder for temporary files (as of revision 809). If you want to configure this individually or if you want to control if the temporary files should be deleted automatically or not, following static methods are available:
Get the file prefix for temporary files.
Get whether files should be kept or deleted automatically when an instance is destructed.
Get the current temporary directory path.
Set the file prefix for temporary files.
Set whether files should be kept or deleted automatically when an instance is destructed.
Set the temporary directory path.