Saving a form's settings keeps every line of its extra blanks, which 1.17.0 joined into one. Automator's "Any form" is the business's forms only.<\/p>","1.17.0":"
A form's answers for your own code and for Uncanny Automator recipes, asked for when a document completes. The plugin stores none of them.<\/p>","1.16.2":"
Stylesheets and scripts in files of their own, output escaped as it is printed, and no token on the plugin's public page.<\/p>","1.16.1":"
Nonces on the forms the plugin draws for visitors and on Amelia's question; fewer admin notices.<\/p>","1.16.0":"
Amelia and Simply Schedule Appointments: the person who booked signs on the page, Amelia before it books.<\/p>","1.15.0":"
An optional "Signed with SignSealer" line under the signing button, off unless you turn it on.<\/p>","1.14.5":"
Connecting finishes by itself when SignSealer did not answer at first, and the signing button keeps its business after the token is refreshed.<\/p>","1.14.4":"
Security and reliability fixes from a review: no unserializing of form answers, one token refresh at a time, and a limit on agreements started by one visitor.<\/p>","1.14.3":"
Wording on SignSealer \u2192 Bookings, and new screenshots.<\/p>","1.14.2":"
No change in what it does: Plugin Check reports nothing at any severity.<\/p>","1.14.1":"
Start here: a card and a guide for each of Amelia, LatePoint and Simply Schedule Appointments.<\/p>","1.14.0":"
Bookly: an appointment booked on its form can now start its agreement.<\/p>","1.13.0":"
MotoPress Hotel Booking: a confirmed stay can now start its rental agreement.<\/p>","1.12.0":"
FluentBooking: a meeting or lesson booked on its pages can now start its agreement.<\/p>","1.11.0":"
Booking Calendar: a booking on its calendar can now start its agreement.<\/p>","1.10.0":"
Events Manager: a booking for an event can now start its waiver or agreement.<\/p>","1.9.0":"
Event Tickets: an RSVP or a ticket for an event can now start its waiver or agreement.<\/p>","1.8.0":"
Forminator, MetForm, Everest Forms and JetFormBuilder: a form submission in each can now start a signing, before or after the form is sent. Amelia, LatePoint and Simply Schedule Appointments: a booking can start its agreement.<\/p>","1.7.1":"
A rental agreement's pickup and return boxes, filled in by the sender, are listed with the form's other blanks.<\/p>","1.7.0":"
Formidable Forms, Ninja Forms and SureForms. A form can sign before it is sent. Form settings move into each form plugin, the shop's into WooCommerce \u2192 Settings. A template's extra blanks are answered by you or asked of the person. The link to sign is a button.<\/p>","1.6.3":"
WooCommerce no longer marks the plugin incompatible with its block cart and checkout.<\/p>","1.6.2":"
With signing before payment, the cart sends customers to sign first, and the signing page looks like part of your shop.<\/p>","1.6.1":"
An order's agreement no longer shows as "draft" for a moment after it is sent.<\/p>","1.6.0":"
Customers can ask for the signing link by text as well as email, at checkout or on a form, when your SignSealer plan includes texting.<\/p>","1.5.1":"
The Sign button is styled on block themes, and the thank-you page asks for the signature once, near the top.<\/p>","1.5.0":"
SignSealer moves from Settings to its own menu item, with a Start here page that explains each integration. Old links still work.<\/p>","1.4.2":"
Deleting the plugin now removes everything it stored.<\/p>","1.4.1":"
Gravity Forms submissions now go straight to the signing page, and spam entries start nothing.<\/p>","1.4.0":"
WooCommerce can require the agreement to be signed before payment.<\/p>","1.3.2":"
Reconnecting no longer adds a duplicate webhook endpoint.<\/p>","1.3.1":"
The block's editor script updates with the plugin and can be translated.<\/p>","1.3.0":"
Connecting no longer asks for an application id and secret. Already\nconnected sites are unaffected.<\/p>","1.2.0":"
WooCommerce Bookings and Contact Form 7. Nothing changes for a site that uses\nneither.<\/p>","1.1.0":"
WooCommerce, Gravity Forms, WPForms and Fluent Forms integrations, and the\nsigner is sent back to your site afterwards. Nothing changes for a site that\nuses none of them.<\/p>","1.0.1":"
Three screens that told you something untrue. One of them, if you did what it\nsaid, registered a second webhook endpoint and doubled what you were billed\nfor deliveries.<\/p>","1.0.0":"
First release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3753388,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3753388,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3753388,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3753388,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":{"signsealer\/sign":{"$schema":"https:\/\/schemas.wp.org\/trunk\/block.json","apiVersion":3,"name":"signsealer\/sign","title":"SignSealer agreement","category":"widgets","icon":"edit-page","description":"A button that sends a visitor to sign a SignSealer form.","textdomain":"signsealer","attributes":{"workflow":{"type":"string","default":""},"label":{"type":"string","default":"Sign now"}},"supports":{"html":false,"align":["left","center","right"]},"editorScript":"file:.\/editor.js","render":"file:..\/render.php"}},"tagged_versions":["1.17.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3753388,"resolution":"1","location":"assets","locale":"","width":1996,"height":2300},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3753388,"resolution":"2","location":"assets","locale":"","width":1996,"height":1196},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3753388,"resolution":"3","location":"assets","locale":"","width":1996,"height":1168},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3753388,"resolution":"4","location":"assets","locale":"","width":2400,"height":1640},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3753388,"resolution":"5","location":"assets","locale":"","width":2400,"height":1640}},"screenshots":{"1":"SignSealer \u2192 Start here: connected to the business, with a card for each\nintegration and its steps.","2":"SignSealer \u2192 Bookings: the agreement each accommodation type starts, and\nthe answer to a blank the booking does not fill.","3":"SignSealer \u2192 Templates: the business's forms and templates, with the\nshortcode for each.","4":"With Before payment, the cart sends the customer to sign the agreement\nfirst.","5":"The signing page on your own site, in your theme."}},"plugin_section":[],"plugin_tags":[1902,147709,147615,723,57747],"plugin_category":[],"plugin_contributors":[287401],"plugin_business_model":[],"class_list":["post-380014","plugin","type-plugin","status-publish","hentry","plugin_tags-agreement","plugin_tags-contract","plugin_tags-esignature","plugin_tags-signature","plugin_tags-waiver","plugin_contributors-mashdunllc","plugin_committers-mashdunllc"],"banners":{"banner":"https:\/\/ps.w.org\/signsealer\/assets\/banner-772x250.png?rev=3753388","banner_2x":"https:\/\/ps.w.org\/signsealer\/assets\/banner-1544x500.png?rev=3753388","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/signsealer\/assets\/icon-128x128.png?rev=3753388","icon_2x":"https:\/\/ps.w.org\/signsealer\/assets\/icon-256x256.png?rev=3753388","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/signsealer\/assets\/screenshot-1.png?rev=3753388","caption":"SignSealer \u2192 Start here: connected to the business, with a card for each\nintegration and its steps."},{"src":"https:\/\/ps.w.org\/signsealer\/assets\/screenshot-2.png?rev=3753388","caption":"SignSealer \u2192 Bookings: the agreement each accommodation type starts, and\nthe answer to a blank the booking does not fill."},{"src":"https:\/\/ps.w.org\/signsealer\/assets\/screenshot-3.png?rev=3753388","caption":"SignSealer \u2192 Templates: the business's forms and templates, with the\nshortcode for each."},{"src":"https:\/\/ps.w.org\/signsealer\/assets\/screenshot-4.png?rev=3753388","caption":"With Before payment, the cart sends the customer to sign the agreement\nfirst."},{"src":"https:\/\/ps.w.org\/signsealer\/assets\/screenshot-5.png?rev=3753388","caption":"The signing page on your own site, in your theme."}],"raw_content":"\n
Your site sends somebody a document to sign, and later wants to know whether they signed it. That is the whole job of this plugin.<\/p>\n\n
Everything that makes a signature worth having happens on SignSealer: consent recorded as its own event before the signature is accepted, the document's exact text fingerprinted into every entry on the trail, and a hash chain that breaks if any entry is altered. A certificate can be checked afterwards by anyone holding its code, without an account.<\/p>\n\n
You need a SignSealer account.<\/strong> This plugin is a client for it. See https:\/\/signsealer.com.<\/p>\n\n These are limits on purpose, not features that are missing.<\/p>\n\n It never renders a signature pad.<\/strong> Signing happens on SignSealer's own pages. A drawing captured in WordPress and posted to an API would make every claim on the certificate untrue \u2014 the certificate says what the signing engine observed, and it cannot observe something that arrived as a form field.<\/p>\n\n It never stores evidence.<\/strong> Document ids, a status and a link. If you restore a six-month-old backup of this site, nothing about any signature changes, because nothing about any signature was here.<\/p>\n\n It never holds a master credential.<\/strong> The connection is OAuth 2.0 with PKCE, scoped to one business, and you can end it from your own SignSealer account without touching WordPress. There is no key here that reaches two accounts.<\/p>\n\n SignSealer's signing pages refuse to be framed ( Every verified delivery fires an action:<\/p>\n\n The signature is checked before this fires, so a handler can trust what it is handed.<\/p>\n\n Once a document completes, its signers' answers to your form's questions\nare handed to tick box is This plugin connects to the SignSealer API at What is sent, and when:<\/strong><\/p>\n\n What is received:<\/strong> access and refresh tokens, your business's name, address and branding, this site's webhook registration and its secret, template and workflow lists, a form's questions, document ids and statuses, whether a signer has signed, signing links, a completed document's answers when asked for as above, and whether your business can send texts, with the wording for the box.<\/p>\n\n SignSealer is operated by Mashdun LLC.\nTerms: https:\/\/signsealer.com\/legal\/terms\nPrivacy policy: https:\/\/signsealer.com\/legal\/privacy-policy\nSubprocessors: https:\/\/signsealer.com\/security\/subprocessors<\/p>\n\n\n Sign in to SignSealer (or create an account there), choose the business this site belongs to, and approve. You are brought straight back.<\/p><\/li>\n Back on Start here, pick the integrations you want. Each card has its three steps and a link to a step-by-step guide at https:\/\/signsealer.com\/wordpress.<\/p><\/li>\n<\/ol>\n\n The plugin registers itself with SignSealer, registers its own webhook endpoint, and signed statuses start arriving with nothing to copy or paste. Your site must be on https: SignSealer checks the plugin is really running there before it connects, and https is also how it posts signed statuses back.<\/p>\n\n\n Two reasons. Before SignSealer connects a site it fetches a small page the plugin serves, to check the plugin is really running there and that the request came from this site; it will only do that over https, so nobody can register an application in your site's name. And once connected, SignSealer posts signed statuses back to your site, which must also be over https so those deliveries are private and verifiable.<\/p><\/dd>\n Yes. This plugin talks to the SignSealer API; it is not a standalone signing tool.<\/p><\/dd>\n On SignSealer, with its certificate and audit trail. This site keeps the document's id and its status so a page can say whether it is signed.<\/p><\/dd>\n No, and that is deliberate. See \"Three things this plugin refuses to do\" above.<\/p><\/dd>\n Not unless you ask it to. Under SignSealer \u2192 Settings \u2192 The sign button there is a setting, off by default, that puts a small \"Signed with SignSealer\" line under the signing button block and the Nothing at SignSealer. Your documents, evidence and certificates are unaffected. Deactivating does not revoke the connection \u2014 end that in SignSealer under Developers \u2192 Connected apps.<\/p><\/dd>\n Yes. On a product's edit screen, under General, choose the SignSealer agreement<\/strong> that product needs. When an order containing it is paid \u2014 or placed, under WooCommerce \u2192 Settings \u2192 SignSealer \u2014 the document is started for the customer, offered on the thank-you page, in their order email and under My Account, and its status appears on the order screen and in the order notes as SignSealer reports it. Works whether your orders live in posts or in WooCommerce's own order tables.<\/p><\/dd>\n Yes. Under WooCommerce \u2192 Settings \u2192 SignSealer choose Before payment<\/strong>. While a customer's cart holds a product whose agreement is unsigned, the cart's checkout button reads Sign the agreement<\/strong> and goes to a page of your site, in your theme, that shows SignSealer's signing page in a frame; a customer who reaches the checkout some other way is sent back to it. The classic checkout and the checkout block both refuse to place the order until SignSealer confirms it is signed, and the order then carries that signed document. SignSealer shows its signing page in a frame only on sites the business has proven, and the site you connected is one.<\/p><\/dd>\n A template blank that nothing fills \u2014 Yes. A bookable product is a product, so mark it the same way. A booking you confirm starts its agreement at once, whether or not it has been paid, because the agreement is wanted before the day. The booking's date, time, number of people and resource go to the template as Yes, since 1.8.0. Open SignSealer \u2192 Bookings, which lists the services in each (in Simply Schedule Appointments, its appointment types), and choose the workflow a booking of each starts. A booking made through the plugin's booking form, or by staff, starts that workflow for the person who booked, and SignSealer emails them the link; LatePoint's confirmation step shows a button to sign too. Since 1.16.0 the person signs on the page in the other two as well. Amelia's booking form opens the agreement over itself when the person presses Book, and makes the booking once it is signed (a booking Amelia takes payment for through Stripe or WooCommerce is made first, and the agreement opens just after). Simply Schedule Appointments opens it over the page as soon as the booking is made, or on the page its form sends people to afterwards. Closed without signing, a button to sign stays on the page, and the email has the link. In Simply Schedule Appointments an appointment waiting on payment starts its agreement once it is booked. The booking fills in Yes, since 1.9.0: its RSVPs (the ones Event Tickets 5.30 makes, and the older kind a site has not moved over yet) and its Tickets Commerce tickets, free or paid. Open SignSealer \u2192 Bookings. Under Event Tickets, the first row is every ticket and RSVP; each ticket of the events still to come is listed under it, for any that should start a different workflow. Whoever RSVPs or buys is emailed the link to sign: one agreement for each ticket in their order, saying how many people it is for, because Event Tickets asks one name and email an order. A logged-in visitor's RSVP is under their account's email, as Event Tickets records it. The event fills in Yes, since 1.10.0. Open SignSealer \u2192 Bookings. Under Events Manager, the first row is every event; each event still to come is listed under it, with its date, for any that should start a different workflow (each date of a recurring event is an event of its own). A booking starts its agreement for the person who booked, one agreement a booking with Yes, since 1.11.0, with the free Booking Calendar's calendar. Open SignSealer \u2192 Bookings and choose the workflow every booking starts. A booking made on the calendar, or added in its admin, starts that workflow for whoever booked, and SignSealer emails them the link; Booking Calendar's own message after booking shows a button to sign too (with its \"message\" setting for after booking; with its own thank-you page, the email is the way). Its form's fields are read by name: Yes, since 1.12.0. Open SignSealer \u2192 Bookings. Under FluentBooking, the first row is every event type; each active event type is listed under it, by its calendar, for any that should start a different workflow. A booking starts its agreement once it is scheduled: booked on its page, added by the host, or, for one waiting for the host's confirmation or a payment, once confirmed or paid. SignSealer emails the person the link, and FluentBooking's confirmation (and its receipt page) shows a button to sign. The booking fills in Yes, since 1.13.0, with the free MotoPress Hotel Booking Lite (and the paid version, which has the same hooks). Open SignSealer \u2192 Bookings. Under MotoPress Hotel Booking, the first row is every accommodation type; each type is listed under it, for any that should start a different rental agreement. A booking starts its agreement once it is confirmed: by the guest's email link (its default), by you, or by a payment. SignSealer emails the guest the link, and its Booking Confirmed page (and Reservation Received after a payment) shows a button to sign. The booking fills in Yes, since 1.14.0, with the free Bookly (and Bookly Pro, which adds to it). Open SignSealer \u2192 Bookings. Under Bookly, the first row is every service; each service is listed under it, for any that should start a different workflow. A booking starts its agreement once it is approved: as it is made, which is Bookly's default, or, for one left pending, when you approve it, when its approve link is followed, or when it is paid for. A booking your staff add in Bookly's calendar starts one too. SignSealer emails the customer the link, and the last step of Bookly's booking form shows a button to sign. The booking fills in Yes. Open the form's SignSealer settings, in its own plugin: Gravity Forms' form Settings, WPForms' builder Settings, Fluent Forms' Settings & Integrations, or Contact Form 7's SignSealer tab (SignSealer \u2192 Forms lists every form with a link there). Choose a workflow and say which of its fields hold the email address and the name (and the last name, when the form asks for it in a field of its own). Every other blank the workflow's document asks is listed, and for each you choose the field that answers it or type the answer to use; one left with neither is asked of the person on a page of your site just before they sign. After they submit, the person is sent straight to the signing page, or the form's own confirmation gains a button to sign \u2014 your choice per form. The entry keeps the document's id, title and status, and a note on it says what was sent and what happened. Contact Form 7 keeps no entries, so there the link is carried to its own script and shown under the form's message.<\/p><\/dd>\n Yes, since 1.7.0. In Formidable Forms the settings are in the form's Settings, under SignSealer; in SureForms, in the form's Form Settings, under SignSealer, with a Save button of its own. In Ninja Forms SignSealer is an action: open the form's Emails & Actions, add SignSealer, and fill in the person's email and name with merge tags, the way the form's own email is set up. Each answers the agreement's blanks and sends the person on to sign the same way as the plugins above. These three keep the entry as they always have; see who signed in SignSealer.<\/p><\/dd>\n Yes, since 1.7.0. In a form's SignSealer settings, under When they sign<\/strong>, choose Before the form is sent<\/strong>. Pressing the form's own button then opens the agreement over the form, on your page; once it is signed, the form is sent by itself and its entry carries the signed document. Somebody who closes it without signing sends nothing, and no entry is kept. The check is made by your site asking SignSealer, not by the browser, so it cannot be skipped. SignSealer emails them the link as well, as it always does.<\/p><\/dd>\n Since 1.14.4 one visitor's address may start 20 agreements an hour, before payment or from a form: enough for anybody signing their own, and a limit on a script sending your agreements to address after address. Your staff, logged in, are not counted. A form sent past the limit keeps its entry, with a note saying nothing was sent. To change the number, return another from the Yes, since 1.8.0. None has a place in its own screens for another plugin's settings, so a form's SignSealer settings are a page of this plugin's: open SignSealer \u2192 Forms and press Open settings beside the form. MetForm's, Everest Forms' and JetFormBuilder's lists of forms also have a SignSealer link under each form. Everest Forms and JetFormBuilder work whether a form sends with AJAX or reloads the page; a JetFormBuilder form that signs first is sent with AJAX, so the signing can open over it. Both answer the agreement's blanks, can sign before the form is sent, and send the person on to sign the same way as the others. MetForm shows its messages as plain text, so the button to sign appears under the form rather than in its message.<\/p><\/dd>\n Yes, with Uncanny Automator (free). Make an Everyone recipe with the trigger\nSignSealer \u2192 \"A document from a form is signed\", choose the form, and choose\nthe answer it waits for, such as \"Are you married? \u2192 Yes\". Make a second\nrecipe for \"No\". Each question on the form is also a token for the recipe's\nactions. Developers can use the Not yet. Start here names it if it finds it on your site, with the way round it until then: give the form you want signed a public address in SignSealer, and set your form's confirmation to redirect to it (or to a page with the SignSealer agreement block). The person types their name and email again, and nothing is recorded on the entry.<\/p><\/dd>\n Since 1.5.0 SignSealer has its own item in the admin menu, with Start here, Forms, WooCommerce, Templates and Settings under it. Old bookmarks to the Settings pages still work: they take you to the same page in its new place. Since 1.7.0 a form's settings are with the form, in its own plugin, and the shop's under WooCommerce \u2192 Settings \u2192 SignSealer; SignSealer's Forms and WooCommerce items take you there.<\/p><\/dd>\n Yes, when your site is on https. After signing, the page offers a way back to the order they came from, or the page the form was on. SignSealer only sends people to sites a business has proven it holds, and connecting this plugin proved this one.<\/p><\/dd>\n\n<\/dl>\n\n\nThree things this plugin refuses to do<\/h4>\n\n
Why a link, and a frame only where the site is proven<\/h4>\n\n
frame-ancestors<\/code>) on any site the business has not proven is its own. A signing page inside another site's frame is a clickjacking target, and the thing being clicked is a signature. So the block, the shortcode and the forms send the signer to SignSealer's own page, where they can see whose address bar they are signing on. The frames are where signing comes first, on this site: WooCommerce's Before payment<\/strong>, a form set to be signed before it is sent, and Amelia's and Simply Schedule Appointments' signing before the booking. Connecting the plugin proves the site to SignSealer, which is what lets its signing page be shown here.<\/p>\n\nWhat it does<\/h4>\n\n
\n
signsealer_event<\/code> action your own code can hook.<\/li>\n[signsealer_sign workflow=\"your-form\"]<\/code> if you prefer a shortcode.<\/li>\nFor developers<\/h4>\n\n
add_action( 'signsealer_event', function ( $event, $payload ) {\n if ( 'signing.completed' === $event ) {\n \/\/ $payload['document']['id'] has signed.\n }\n}, 10, 2 );\n<\/code><\/pre>\n\nsignsealer_document_completed<\/code>, asked for from SignSealer\njust after the delivery. This plugin stores none of them; what your own code\ndoes with them is up to it:<\/p>\n\nadd_action( 'signsealer_document_completed', function ( $document ) {\n if ( 'Yes' === ( $document['answer']['married'] ?? '' ) ) {\n \/\/ \"Are you married?\" was answered Yes.\n }\n} );\n\n$document['answer'] has one value per question, by the question's key; a\n<\/code><\/pre>\n\nYes<\/code> or No<\/code>. A question more than one person answered (two\nsigners, each person in a party) holds every different answer, sorted and\njoined with a comma: Yes<\/code> means everyone said Yes, No, Yes<\/code> that they\ndiffered. answers_text<\/code> is every answer,\none line each, for an email; answers<\/code> has each one with who gave it.\nSensitive answers are masked, as your staff see them. To ask for a\ndocument's answers yourself: signsealer_get_answers( $document_id )<\/code>.\nIt runs from WP-Cron, so on a site that runs WP-Cron from the server it\nwaits for the next run.<\/p>\n\nExternal services<\/h3>\n\n
https:\/\/api.signsealer.com<\/code> \u2014 the service it is a client for. It is required for the plugin to do anything.<\/p>\n\n\n
\/wp-json\/signsealer\/v1\/site<\/code> on this site, confirm the plugin is running here, and register an application for this site. Then the PKCE challenge, once, as the browser is sent to approve, and, when you have approved, the code SignSealer hands back with the PKCE verifier and this site's application id and secret, exchanged for an access token and a refresh token. The refresh token is exchanged again whenever the access token runs out.<\/li>\n\/wp-json\/signsealer\/v1\/webhook<\/code>, named \"WordPress: \" and this site's host) for SignSealer's events. The Settings screen lists that registration, and can ask for a new webhook secret.<\/li>\nsignsealer_document_completed<\/code> action): a request for that document, by its id, tried again up to four more times over about fifteen minutes if SignSealer cannot be reached. Its title, status, your reference and its signers' answers come back, sensitive answers masked, and are handed to that code or recipe. This plugin stores none of it; Uncanny Automator keeps each run's tokens in its own log, as it does for every trigger.<\/li>\n\n
\n
Why does my site need to be on https?<\/h3><\/dt>\n
Do I need a SignSealer account?<\/h3><\/dt>\n
Where is the signed document kept?<\/h3><\/dt>\n
Can I collect the signature on my own page?<\/h3><\/dt>\n
Does the plugin add a link or a credit to my site?<\/h3><\/dt>\n
[signsealer_sign]<\/code> shortcode, linking to signsealer.com. Only a button to your own business's form gets it: nothing else the plugin shows, and not a shortcode pointed at another business. A business with white label is not offered it.<\/p><\/dd>\nWhat happens if I deactivate the plugin?<\/h3><\/dt>\n
Does it work with WooCommerce?<\/h3><\/dt>\n
Can the customer sign before they pay?<\/h3><\/dt>\n
My agreement asks for something the order does not know<\/h3><\/dt>\n
{{location}}<\/code> on a photo release, say \u2014 would make SignSealer refuse to start the document. So on the product's edit screen, under its SignSealer agreement, each such blank has a box: fill it in to answer it for every order of that product, or leave it empty and the customer is asked. Before payment they are asked on the signing page, beside their name and email. After payment the order's Sign link \u2014 on the thank-you page, in the order email and under My Account \u2014 opens a page of your site that asks, and the agreement is sent once they have answered. The order notes say when an agreement is waiting for that.<\/p><\/dd>\nDoes it work with WooCommerce Bookings?<\/h3><\/dt>\n
booking_date<\/code>, booking_time<\/code>, persons<\/code> and resource<\/code>, and the booking's own screen shows where the agreement stands.<\/p><\/dd>\nDoes it work with Amelia, LatePoint or Simply Schedule Appointments?<\/h3><\/dt>\n
booking_date<\/code>, booking_time<\/code>, service_name<\/code>, persons<\/code> and staff<\/code>. Any other blank the agreement asks is listed under the service: choose what of the booking answers it (a location<\/code> blank is given the booking's location, when the plugin has locations set up), or type the answer to use for every booking of that service. A booking saved again \u2014 rescheduled, confirmed, paid \u2014 starts nothing a second time, and a canceled one starts nothing. If a booking could not start its agreement, SignSealer \u2192 Bookings says which and why.<\/p><\/dd>\nDoes it work with Event Tickets?<\/h3><\/dt>\n
service_name<\/code> (the event's name), ticket_name<\/code>, booking_date<\/code>, booking_time<\/code>, persons<\/code>, location<\/code> (its venue) and staff<\/code> (its organizer); an RSVP on a page rather than an event fills in the page's name, the ticket and how many. The RSVP's \"received\" message and the order page show a button to sign. An RSVP of \"not going\" starts nothing, and a ticket starts its agreement once its order is completed. Event Tickets Plus, the paid add-on that sells tickets through WooCommerce, has not been tested.<\/p><\/dd>\nDoes it work with Events Manager?<\/h3><\/dt>\n
persons<\/code> the spaces they took, and SignSealer emails them the link; Events Manager's own message after booking shows a button to sign too. A booking waiting for your approval starts it; one waiting on a payment starts it once it is approved; a rejected or cancelled one starts nothing; approving a booking later starts nothing a second time. The event fills in service_name<\/code> (the event's name), ticket_name<\/code>, booking_date<\/code> and booking_time<\/code> (in the event's own time zone), persons<\/code> and location<\/code>. Events Manager Pro's payments and forms have not been tested.<\/p><\/dd>\nDoes it work with Booking Calendar?<\/h3><\/dt>\n
firstname<\/code> (or name<\/code>) and secondname<\/code>, email<\/code> (or any email field), phone<\/code>, and adults<\/code> and children<\/code> (or visitors<\/code>) for persons<\/code>. The booking fills in booking_date<\/code> (its first day) and booking_time<\/code> for a time slot. A booking waiting for your approval starts its agreement, and an edited booking does not start a second one. The paid editions' separate resources are not listed yet: their bookings start the one workflow.<\/p><\/dd>\nDoes it work with FluentBooking?<\/h3><\/dt>\n
service_name<\/code> (the event type), booking_date<\/code> and booking_time<\/code> (in the calendar's time zone), persons<\/code>, staff<\/code> (the host) and location<\/code> for an in-person place, with the person's name, email and phone. In a group event each person has a booking of their own and signs their own. FluentBooking Pro's group, round-robin and multi-slot bookings have not been tested.<\/p><\/dd>\nDoes it work with MotoPress Hotel Booking?<\/h3><\/dt>\n
booking_date<\/code> and booking_time<\/code> (the check-in date and the site's check-in time), check_out_date<\/code>, nights<\/code>, service_name<\/code> (the accommodation types booked) and persons<\/code> (the adults and children in all of them), with the guest's name, email and phone. A booking with several accommodations starts the first one's workflow. A booking imported from another site's calendar (Airbnb, Booking.com) has nobody to sign and starts nothing.<\/p><\/dd>\nDoes it work with Bookly?<\/h3><\/dt>\n
service_name<\/code>, booking_date<\/code> and booking_time<\/code>, persons<\/code> and staff<\/code> (the staff member), with the customer's name, email and phone. Bookly Pro's recurring appointments start one agreement for the series. A booking whose time has already passed starts nothing. Bookly's free version announces nothing to other plugins, so SignSealer looks for the bookings Bookly approved as each of its requests ends; a booking made some other way, such as Bookly Pro's WooCommerce add-on, is not seen yet.<\/p><\/dd>\nDoes it work with Gravity Forms, WPForms, Fluent Forms or Contact Form 7?<\/h3><\/dt>\n
And Formidable Forms, Ninja Forms or SureForms?<\/h3><\/dt>\n
Can they sign before the form is sent?<\/h3><\/dt>\n
A visitor was told \"Too many agreements have been started from your connection\"<\/h3><\/dt>\n
signsealer_starts_per_hour<\/code> filter (0 for no limit). If your site is behind a proxy that does not pass the visitor's address on, every visitor looks like the proxy: return the address your proxy vouches for from the signsealer_visitor_ip<\/code> filter.<\/p><\/dd>\nAnd Forminator, MetForm, Everest Forms or JetFormBuilder?<\/h3><\/dt>\n
Can WordPress do something different depending on an answer?<\/h3><\/dt>\n
signsealer_document_completed<\/code> action\ninstead (see For developers).<\/p><\/dd>\nWhat about Elementor Pro Forms?<\/h3><\/dt>\n
Where did Settings \u2192 SignSealer go?<\/h3><\/dt>\n
Does the signer come back to my site afterwards?<\/h3><\/dt>\n
1.17.1<\/h4>\n\n
\n
signsealer_document_completed<\/code> no longer warns on\na form without the question it reads.<\/li>\n<\/ul>\n\n1.17.0<\/h4>\n\n
\n
1.16.2<\/h4>\n\n
\n
wp_enqueue_style()<\/code> and wp_enqueue_script()<\/code>,\nand given what they need as data. The sign button's colour, which you\nchoose, is the one style still written on the page.<\/li>\n1.16.1<\/h4>\n\n
\n
1.16.0<\/h4>\n\n