Error reference¶
When Midsummer hits a known problem it shows a friendly error panel that links here. Each code below explains what happened and what to do, split into the three audiences that the in-app panel shows:
Audience |
Read the |
|---|---|
Attendees / Users |
green For attendees / users block |
Event Organizers |
amber For event organizers block (most config errors are fixed here) |
Event Technical Staff |
red For event technical staff block |
Tip
The codes use the form E:<MODULE>:<NUMBER> (for example E:REG:1).
Midsummer’s error panel links to this page using the lowercased,
dash-separated anchor — e.g. E:REG:1 → Error e-reg-1.
Error codes¶
Code |
Meaning |
Jump to |
|---|---|---|
|
The app asked for an error code it does not know. |
|
|
An unexpected, uncaught error occurred. |
|
|
The requested resource was not found. |
|
|
No default registration form is configured. |
|
|
No default vendor application form is configured. |
|
|
The schedule submission category was not found. |
|
|
A registration is required before applying to vend. |
Reference¶
E:MID:0 — UIError: Unexpected Error Code¶
The application tried to look up an error code to display and could not find one. This is the fallback shown when an error code is missing or unrecognized.
For attendees / users
An unexpected error occurred. Please try again later.
For event organizers
This issue is caused by an unexpected error that occurred during the execution of the application. Please contact Midsummer Development Staff.
For event technical staff
The frontend could not fetch the error code it was asked to display. This is almost always a Midsummer defect — file a bug with the console message.
E:MID:1 — UncaughtError: How did we get here?¶
An unexpected error slipped past the application’s handlers.
For attendees / users
An unexpected error occurred. Please try again later.
For event organizers
This issue is caused by an unexpected error during execution. Please contact Midsummer Development Staff.
For event technical staff
There was an internal issue that caused this error to render, and it is not a configuration problem. This is most likely a Midsummer bug — file a report with the console output (the panel’s Copy Error button captures it).
E:MID:404 — 404Error: Not Found¶
The requested resource (a form, vendor type, schedule category, or similar) does not exist for this event.
For attendees / users
The requested resource was not found. Please check the link or URL and try again. If the problem persists, contact the event organizers.
For event organizers
This happens when the requested resource does not exist for the event (for example, a form or event that was deleted or never published). Confirm the resource exists and that the attendee is using the correct link. Midsummer Development Staff cannot resolve this.
For event technical staff
The API call succeeded but the resource was not found — this is not a Midsummer configuration issue. Verify the resource exists for the current event and the URL the user reached is correct. Midsummer Development Staff cannot resolve this.
E:REG:1 — ConfigError: No Form Available to Render¶
The Register app needs a default registration form for the event, and none is set.
For attendees / users
Registration is not fully configured for this event yet, and this was not caused by anything on your end. Please contact the event’s organizers for assistance and try again later once it is resolved.
For event organizers
The Register app has no default registration form. To fix it, either create a registration form with Default Registration Form checked, or edit an existing form and check that option. Only one form should be the default. Midsummer Development Staff cannot resolve this.
For event technical staff
The API call to fetch the default registration form succeeded but returned
nothing. This is an event configuration issue (no
primary_registration_form), not a Midsummer defect. Have an organizer
with Registration Form Management permission set the default form.
E:VEN:1 — ConfigError: No Vendor Form Available to Render¶
The Vendor app needs a default application form for the vendor type, and none is set.
For attendees / users
Vendor applications are not fully configured for this event yet, and this was not caused by anything on your end. Please contact the event’s organizers for assistance and try again later once it is resolved.
For event organizers
The vendor type has no default application form. Create or edit a vendor application form and mark it as the default for the relevant vendor type so that the application page can render. Midsummer Development Staff cannot resolve this.
For event technical staff
The API call succeeded but the vendor type’s default form was null.
This is an event configuration issue, not a Midsummer defect. Have an
organizer set a default vendor application form.
E:SCH:1 — ConfigError: Schedule Category Not Found¶
The schedule submission form references a category that does not exist for this event.
For attendees / users
The panel submission form could not load because its category is not set up. This was not caused by anything on your end. Please contact the event’s organizers and try again later once it is resolved.
For event organizers
The schedule submission form is attached to a category that does not exist. Create the missing category (or re-point the form at an existing one) in the Schedule settings. Midsummer Development Staff cannot resolve this.
For event technical staff
The category lookup for the submission form returned nothing. This is an event configuration issue, not a Midsummer defect. Confirm the category exists for the current event.
E:VEN:REG_REQUIRED — Registration Required to Vend¶
This is not shown through the standard error panel. When a vendor type requires a paid registration, Midsummer stops the application and shows a plain “Registration Required” card instead.
For attendees / users
You must have a paid registration for this event before you can submit a vendor application. Register for the event first, then return to this page to apply.
For event organizers
The vendor type has registration required enabled, and this applicant has no paid registration for the event. This is working as intended. If you want to let un-registered people apply, turn off the require registration option on the vendor type.
For event technical staff
Returned as HTTP 403 with error_code: E:VEN:REG_REQUIRED from the vendor
submission endpoint when vendor_type.require_registration is true and the
user has no paid registration. Expected behavior — no bug to file.