All guides
Admin

Themes

Screen guide

Before you start

Use an administrator account with permission to manage this feature. The feature also needs to be enabled for this installation and plan.

Open this feature
  1. Open /admin/themes/frontend on your site.

Steps

Use Import settings

  1. Open /admin/themes/backend on your application domain, using the administrator account for this task.
  2. Find the form containing Import JSON. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Import settings. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
Import JSONEnter the import json for this task, using the help or example shown by the form.

Use Import settings

  1. Open /admin/themes/frontend on your application domain, using the administrator account for this task.
  2. Find the form containing Import JSON. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Import settings. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
Import JSONEnter the import json for this task, using the help or example shown by the form.

Fields and choices

Field descriptions appear beside each task above so that separate forms are not mixed together.

Check the result

  1. Stay in the same account/workspace and reopen the intended record or result screen.
  2. For saved settings, compare the displayed values with the choices you made. For filters and previews, check the current result scope.
  3. For queued or external work, inspect its status/history and provider result where applicable. A successful save does not by itself prove message delivery, publication, payment completion or provider approval.

Common problems

ProblemWhat to check
The screen or action is missingCheck the correct administrator account, role, enabled app and plan. A hidden action is not fixed by typing an internal endpoint.
A field is rejectedRead its validation message, choose from the offered options and check the relevant format or limit. Do not substitute a database ID for a displayed choice.
A list is emptyCheck the selected workspace, search text, date range and status filters. Clear one filter at a time before concluding that records are missing.
A request is still pendingCheck its status/history before repeating it. For messages, publishing, imports and payments, a submitted request can finish later or fail separately.

Technical reference

Role-scoped source references

Pinned commit: 0a97c2b1d8022981713b1f32874690236dcf1610

Source-only route information
MethodSource-default route
GET/admin/themes/frontend
GET/admin/themes/frontend/export
PUT/admin/themes/frontend
GET/admin/themes/backend
GET/admin/themes/backend/export
PUT/admin/themes/backend
Unmapped fields — not user instructions

These fields belong to this role’s source handler, but their screen labels were not confirmed.

Source keyHandler
backend_thememodules/AdminThemes/Livewire/BackendThemePage.php
backend_navigationmodules/AdminThemes/Livewire/BackendThemePage.php
frontend_thememodules/AdminThemes/Livewire/FrontendThemePage.php
frontend_thememodules/AdminThemes/Http/Controllers/AdminThemeController.php
backend_thememodules/AdminThemes/Http/Controllers/AdminThemeController.php
backend_navigationmodules/AdminThemes/Http/Controllers/AdminThemeController.php