drupal / mutamad_forms
Forms for Mutamad: Webform with a ready Contact form, ALTCHA, Honeypot and Antibot spam protection, Webform's option lists, and form-building permissions for content editors.
Package info
git.drupalcode.org/project/mutamad_forms.git
Type:drupal-recipe
pkg:composer/drupal/mutamad_forms
Requires
- drupal/altcha: ^1.1
- drupal/antibot: ^2.0
- drupal/core: ~11.4.0
- drupal/honeypot: ^2.1
- drupal/mutamad_roles: ~1.0.0
- drupal/webform: ^6.3.1
Requires (Dev)
None
Suggests
None
Provides
None
Conflicts
- drupal/captcha: <2.0.7
Replaces
None
This package is not auto-updated.
Last update: 2026-11-16 06:05:11 UTC
README
Mutamad Forms
Forms for Mutamad — a drupal-recipe, applied by the
mutamad_starter site
template on every Mutamad install.
Built and maintained by iSpectra — Imagine. Implement. Inspire. See iSpectra on drupal.org.
It sets forms up as Drupal CMS Forms does — the same modules, settings and spam protection — and adds Mutamad's form setup on top, with its own Contact form. It does not apply Drupal CMS Forms: a recipe that changes the form another recipe ships loses the change on a site installed in Arabic, where translation puts back the shipped original.
What you get
| Feature | Details |
|---|---|
| Webform and Webform UI | Drupal's standard form builder |
| Contact form | /form/contact-form, after DGA's Contact Us Template: name, Saudi mobile number, email, category, subject, message and up to three attachments, kept in private files; submissions are emailed to the site address |
| Page rating | "Was this page useful?" (page_rating), after DGA's Rating Section Template: Yes or No, why (several reasons may be chosen), gender (optional) and comments; the page it was sent from is recorded, no IP address. Mutamad's site template places it under every page |
| Service rating | "Rate this service" (service_rating), as DGA's Service Page Template shows it: one to five stars; the service it was sent from is recorded, no IP address. Mutamad's site template places it on every service, with the service's average and how many rated it |
| ALTCHA | Proof-of-work CAPTCHA bundled in the module — no outside service, Arabic included |
| Honeypot | On every webform, and the password-reset, registration and comment forms |
| Antibot | On every webform, new ones included: a form is sent only from a browser running JavaScript, once a person has moved the mouse, touched the screen or pressed Tab or Enter. Its limits are described in Mutamad Security |
| Option lists | Webform's ready-made choices: countries, months, yes/no, Likert scales… |
| Editor permissions | Content editors can see the forms list, create forms and edit the forms they own |
| Submission log | On for every form, new ones included: each submission's history — created, changed, emailed, and by whom |
| Site administrator | Reads every form's submissions and their log, and can download results; cannot edit, delete or clear them |
| Inline Form Errors | On every form of the site: each error next to its field, and a summary at the top linking to each one (WCAG 3.3.1) |
Who sees submissions
Contact messages hold people's names, emails and messages. The site administrator reads them, to answer a personal-data request under Saudi PDPL and as evidence; nothing it does changes them. A content editor manages the submissions of a form they built themselves — reads, edits and deletes them — and sees no others, the Contact form's included. Every form's submissions are changed only by the administrator.
Two things Webform decides, not Mutamad:
- Reading results and downloading them are one permission, so the site administrator can export them — which a personal-data request needs anyway.
- The site administrator sees a submission's history on the form's Log tab, where each entry carries the submission number, not on the submission's own Log tab, which Webform opens only to people who can edit the form.
When a submission is deleted, Webform deletes its history with it. The deletion itself, and who made it, is kept in the site log (Reports > Recent log messages).
Webform's external libraries
Webform can load optional JavaScript libraries from public CDNs — input masks,
phone numbers, signatures, ratings, searchable selects, code editors,
tooltips. This recipe turns all of them off. Mutamad's Content Security Policy
(mutamad_security)
blocks scripts from other sites, and allowing a public CDN would let anything
hosted there run on the site.
What that changes:
- Building forms: plain select boxes instead of searchable ones, text areas without code highlighting, help text instead of tooltips.
- Public forms: no input masks, no international telephone widget and no live character counter (the limit is still enforced).
- Not available: the Rating and Signature elements.
To bring one back, host it under /libraries — which also suits a closed
network — and remove it from libraries.excluded_libraries in Webform's
settings.
Honeypot and Antibot are on for every webform, new ones included. Antibot is turned on through Webform's own setting, which protects the first page of a multi-page webform and leaves its later pages alone.
Adding a webform to the distribution
- Build it in the Webform UI on a development site.
- Export it:
drush config:get webform.webform.<name>. - Remove the
uuidand_corelines. - Save it here as
config/webform.webform.<name>.yml.
Requirements
Mutamad Roles, for the job roles; the recipe applies it first. It installs Antibot itself, for Webform's Antibot setting; Mutamad Security, on a Mutamad site, protects the other public forms.
Apply it to an existing site
drush recipe ../recipes/mutamad_forms
Maintainers
Built and maintained by iSpectra (on drupal.org).
