Question 1

Why are user roles not translated in the Gibbon Planner module?

Accepted Answer

This was a bug in versions before v29.00.00 where the role string was not passed through the translation function. The fix is to upgrade to Gibbon v29 or later. If upgrading is not immediately possible, manually edit modules/Planner/planner_view_full.php and change line 1291 from $cell->addContent($person['role']); to $cell->addContent(__($person['role']));

Question 2

How to fix 'Undefined variable $families' and TypeError current() null error on Gibbon Manage Applications Edit page?

Accepted Answer

This is a known bug in Gibbon v30.0.01 (FamilyFields.php) that occurs when an admissions account is linked to a family (gibbonFamilyID set) but no person (gibbonPersonID NULL) — typically caused by accepting a form without a Parent 1 field while 'Create Family' is on. The Edit/Add application page then shows no form and logs 'Undefined variable $families' plus 'TypeError: current(): Argument #1 ($array) must be of type array, null given'. Fix: upgrade to Gibbon v31, where it is patched (PR #2191). As a manual workaround, edit src/Forms/Builder/Fields/FamilyFields.php: initialize `$families = [];` before use; when only gibbonFamilyID is set, load the family with `getByID()` and branch on `!empty($families)`; and in `shouldValidate()` return false when either gibbonPersonID or gibbonFamilyID is set so hidden address fields are not required.

Question 3

Why is the 'Submission Email: An email was sent to...' line missing from the applicant's results page in Gibbon?

Accepted Answer

This is a known bug in Gibbon v30.0.01 (and the dev branch) affecting forms with Send Submission Email enabled but no Parent 1 email field. The confirmation email is still sent — only the result line is hidden for applicants, while staff see it because their read-only view also checks stored results. Fix: upgrade to Gibbon v31, where the issue is resolved (PR #2190). For v30.0.01, patch `SendSubmissionEmailView::display()` (around line 72) in `src/Forms/Builder/Process/SendSubmissionEmail.php` by replacing the check with: `if (!$data->hasResult('submissionEmail') && !$data->has('submissionEmail') && !$data->has('parent1email')) return;` so the result is read from stored results as well as form data.

Question 4

How to make Surname, Preferred Name or Official Name optional fields in Gibbon?

Accepted Answer

Upgrade to Gibbon v31, which adds this capability via the existing Personal Data Field settings. A school admin can configure personal data fields (such as surname and preferredName) to be required, optional, or hidden. Note: firstName and officialName remain required by default, while other fields can be made optional. This resolves the inconsistency where student imports allowed blank surnames but the Edit User form still required them. See PR #2180 for implementation details.

Question 5

Why does my Gibbon form number field reject decimal values and show 'Must be in format %1$s'?

Accepted Answer

This is a known bug in Gibbon v28.0.01 where the HTML step attribute is not set on number inputs with decimal places, causing the browser's default step of 1 to reject decimals. The error message 'Must be in format %1$s' appears from the custom validation fallback. To fix, edit src/Forms/Input/Number.php and implement step logic: add a step property and set it to '0.' followed by (decimalPlaces-1) zeros and '1' (e.g., step='0.1' for 1 decimal place). If a custom step is set via a new step() method, use that value instead. Until the patch is merged, a temporary workaround is to use a text input with pattern validation or override the step attribute using JavaScript.

Gibbon Core

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects