Repository navigation
Releases: bungakku/Online-Admission-Manager
Releases · bungakku/Online-Admission-Manager
Release list
v1.1.22 — Keep Entries After an Error
- Fixed: when a submission was rejected, the form reloaded empty, so one
typo meant retyping the whole application. The form now comes back
filled in, including every academic-record row. - For security the Aadhar number is not filled back in, and browsers
can't refill file uploads; a note asks the applicant to re-enter the
Aadhar number and choose their files again.
Clear any page cache after updating. No database changes.
Full Changelog: v1.1.21...v1.1.22
v1.1.21 — Visible Form Messages
- Fixed: when the form rejected a submission, the error message appeared
at the very bottom of the page, below the site footer, while the form
reloaded empty, so it looked as though nothing had happened. - Messages now appear directly above the form, the page scrolls to them,
and screen readers announce them (role="alert" / role="status"). - Slightly tidied the phone-number error wording.
Clear any page cache after updating. No database changes.
Full Changelog: v1.1.20...v1.1.21
v1.1.20 — Contact Number Validation
- Fixed: contact-number fields accepted anything (letters, wrong digit
counts, several numbers in one box). Each number is now checked to look
like a phone number: 7 to 15 digits, with spaces, hyphens, brackets and
a leading + allowed. Foreign numbers and pasted numbers work. - WhatsApp remains required; other numbers remain optional. Numbers are
saved exactly as typed.
No database changes.
Full Changelog: v1.1.19...v1.1.20
v1.1.19 — Delete Removes Academic Records
- Fixed: deleting an application removed it and its uploaded files but
left the applicant's academic records behind as orphaned rows in the
database. Deleting an entry now removes its academic records too. - Rows left by deletions made in earlier versions are not removed
automatically; they don't appear in exports or the admin panel.
No database changes.
Full Changelog: v1.1.18...v1.1.19
v1.1.18 — Field Length Limits
- Fixed: form fields had no length limits matching the database, so an
over-long entry could fail the submission with a generic error, be
silently cut off, or (for academic records) be silently lost. - Every free-text field now has a maxlength matching its database column,
enforced in the browser and on the server with a specific message. - Normal entries are unaffected.
No database changes.
Full Changelog: v1.1.17...v1.1.18
v1.1.17 — Invalid Email Validation
- Fixed: an invalid email address on the application form was silently
discarded, so the application saved with a blank email and no
confirmation was sent. The form now shows a clear error instead. - Email remains optional; blank and valid addresses behave as before.
No database changes.
Full Changelog: v1.1.16...v1.1.17
v1.1.16 — Faster CSV/Excel Export
- Performance: CSV and Excel exports no longer run one extra database
query per applicant to fetch academic records. All records are now
fetched in a single batched query (in chunks of 500 applicants). - Export file content is identical to v1.1.15.
No database changes.
Full Changelog: v1.1.15...v1.1.16
v1.1.15 — Excel Export & Readable Academic Records
- Added a new "Export All to Excel" option alongside CSV. Unlike CSV,
which has no concept of column width at all, the Excel file has
genuinely auto-sized columns built in — no manual "auto-fit" step
needed in your spreadsheet app. - Academic records now export as a readable summary (e.g. "HSSCE
(2025) - Division: 1, Marks: 61%, Board: CBSE, Subjects: Physics,
Chemistry") instead of raw JSON, in both CSV and Excel.
No database changes.
Full Changelog: v1.1.14...v1.1.15
v1.1.14 — CSV Export Fix
Fixed CSV export producing a mangled file (the entire admin page's HTML
mixed in with the real data at the end) instead of a clean CSV. The
export now runs through a dedicated endpoint instead of the admin page
callback. No change to the actual exported data.
No database changes.
Full Changelog: v1.1.13...v1.1.14
v1.1.13 — Category & Sex Field Validation
- Category field now has a blank "Select" default, matching Sex.
- Added server-side validation for Sex and Category, accepting only
the exact options shown in the form.
No database changes.
Full Changelog: v1.1.12...v1.1.13