Skip to content

Releases: penxelstudio/pdf-mapper-fluent-forms-addon

Release list

v1.0.0 — First stable release

v1.0.0 — First stable release Latest
Latest

Choose a tag to compare

View all tags
@penxelstudio penxelstudio released this 29 Aug 14:05
v1.0.0
0b9de53

First stable release of PDF Mapper for Fluent Forms.

Upload any PDF as a template, visually place each Fluent Forms field on it, and every submission produces a completed PDF — attached to the notification email and stored where only capability-checked downloads can reach it.

Requirements
WordPress 6.5 or newer (tested to 7.1)
PHP 8.1 or newer
Fluent Forms Free or Pro, installed and active
Browser (admin only) ES module support, for the mapper screen

Repeater bindings need the Repeat Field or Repeat Container element, which Fluent Forms Pro provides. Everything else works on the free version.

Installation

Download pdf-mapper-for-fluent-forms-1.0.0.zip below and upload it through Plugins → Add New → Upload Plugin. Activate Fluent Forms first — the plugin declares Requires Plugins: fluentform, so WordPress will refuse activation without it.

What it does

  • Visual drag-and-map editor powered by PDF.js
  • AcroForm widgets auto-detected, or place pins by hand on a completely flat PDF
  • Text, checkbox, and image bindings — signatures and company stamps, transparency preserved
  • Repeater support with automatic page overflow
  • Several templates per form, each with its own conditional rule
  • Protected document storage, plus regenerate / resend / CSV export
  • Mapping export and import as JSON, to reuse a layout across sites

Security

Every plugin screen and all twelve AJAX endpoints require a nonce and manage_options. There is no front-end surface: no wp_ajax_nopriv handler, no REST route, no shortcode.

Templates are rewritten in the browser to strip active content, then re-validated server-side; anything still carrying JavaScript, launch actions, embedded files or XFA is rejected. Output PDFs are flattened by construction.

If you host on nginx, read SECURITY.md. nginx honours neither .htaccess nor web.config, and WordPress cannot write nginx configuration, so on nginx the protection in front of stored documents is unguessable paths rather than an access rule. The file there gives you the location block to add.

Bundled libraries

Shipped unmodified, verified against upstream:

Library Version Licence
FPDI 2.6.8 MIT
FPDF 1.9.0 Permissive
PDF.js 6.2.108 Apache-2.0
pdf-lib 1.17.1 MIT

Notes

The 0.x series was development and was never released publicly. Full history is in readme.txt.

Assets 3
Loading