tentapress/forms

Maintainers

Package info

github.com/tentaplane/plugin-forms

pkg:composer/tentapress/forms

Statistics

Installs: 0

Dependents: 0

Suggesters: 0

Stars: 0

Open Issues: 0

Security

Advisories: 0

Aikido package health analysis

v0.4.3 2026-02-27 16:38 UTC

Requires

MIT 9f902f201b1d0db7431423f71cb1868e0025efe1

This package is auto-updated.

Last update: 2026-03-28 07:38:13 UTC

README

Forms block and submission targets for TentaPress.

Plugin Details

Field Value
ID tentapress/forms
Version 0.4.3
Provider TentaPress\Forms\FormsServiceProvider

Features

  • Registers a forms/signup block in the block registry.
  • Renders configurable form fields (email, text, textarea, checkbox, select, hidden).
  • Submits to a local endpoint with CSRF protection, honeypot, and minimum elapsed-time spam checks.
  • Supports provider configuration props for Mailchimp, TentaForms, and Kit.
  • Applies rate limiting to form submissions to reduce abuse.

Dependencies

  • tentapress/blocks

Public Routes

Method Path Name
POST /forms/submit/{formKey} tp.forms.submit

Data Handling

  • Submission payloads are forwarded to destination providers.
  • PII is not stored in plugin database tables in MVP.
  • Logs store metadata and optional hashed email for diagnostics.

For Site Owners (No Code)

You can connect a signup form to Kit in a few minutes:

  1. Open the page in the editor and add the Form block.
  2. In the block settings, choose Provider = Kit.
  3. Paste your Kit API Key and Kit Form ID.
  4. Optional: add a Kit Tag ID if you want new subscribers auto-tagged.
  5. Publish the page and submit a test entry to confirm it works.

Where to find these values in Kit:

  • API Key: Kit account settings -> API.
  • Form ID: the numeric ID for the form receiving subscribers.
  • Tag ID: optional numeric ID for the tag to auto-apply.

If something fails, the form will show a friendly error and your visitor's typed values are kept so they can retry.

Quick Provider Notes

  • Mailchimp: use Action URL (+ optional list/GDPR fields).
  • TentaForms: use form ID (+ environment).
    • In local/testing, TentaForms uses safe stub mode by default unless explicitly disabled.
  • Kit: use API Key + Form ID (+ optional Tag ID).

Rollout and Fallback Guidance (Operators)

Recommended rollout:

  1. Start with one low-risk form (for example, newsletter signup).
  2. Submit test entries and confirm subscribers appear in your provider.
  3. Roll out to additional forms once the first form is stable.

If a provider has issues:

  • Keep the same form fields and switch Provider to a known-good destination.
  • Keep a clear fallback message in error_message so visitors know to retry.
  • For local/testing environments, TentaForms stays safely stubbed by default.

Diagnostics in logs:

  • forms.submission.result for all attempts.
  • forms.submission.failed for failed attempts.
  • Useful fields include attempt_id, provider, status_code, and failure_category.

Release Notes

0.4.3

  • Expanded Pest regression coverage for submission flows and migration command behavior.
  • Added Mailchimp destination fake-HTTP regression tests.
  • Completed release-readiness validation pass for forms test suite.

0.4.2

  • Added structured diagnostics logs for provider submission failures.
  • Added operator rollout and fallback guidance.

0.4.1

  • Added named forms submission throttling policy.
  • Hardened TentaForms default stub behavior by environment.

0.4.0

  • Added Kit destination support (API mode) with provider configuration fields.
  • Added baseline Kit destination tests and updated site-owner setup guidance.

Development

php artisan tp:plugins sync
php artisan tp:plugins enable tentapress/forms
php artisan tp:forms:migrate-newsletter --dry-run
php artisan tp:forms:migrate-newsletter