Admin

Blog Tags

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

Choose a task

Open /admin/blog-tags/create on your application domain, using the administrator account for this task.
Find the form containing Auto-fill missing translations, Name, Name. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
Select Save changes. Check the current record, recipients, amount or destination before confirming when those values apply.
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.

Field	What to enter or choose
Auto-fill missing translations	Optional unless the current form requests it. Enable or select this option only when you want the behavior named by the field. When enabled, active languages with auto-translate turned on will be generated for any empty tag names.
Name	Enter the name for this task, using the help or example shown by the form. You can add emoji to the default tag name.
Name	Optional unless the current form requests it. Complete the visible field for the current selection; follow its validation message. Maximum 255 characters.
Slug	Enter the slug for this task, using the help or example shown by the form. Leave empty to generate from the default language name.
Highlight color	Required. Choose a color using the picker. Maximum 32 characters.
Icon class	Optional unless the current form requests it. Enter the icon class for this task, using the help or example shown by the form. Maximum 255 characters.

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

Stay in the same account/workspace and reopen the intended record or result screen.
For saved settings, compare the displayed values with the choices you made. For filters and previews, check the current result scope.
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.

Problem	What to check
The screen or action is missing	Check the correct administrator account, role, enabled app and plan. A hidden action is not fixed by typing an internal endpoint.
A field is rejected	Read 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 empty	Check 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 pending	Check its status/history before repeating it. For messages, publishing, imports and payments, a submitted request can finish later or fail separately.

Role-scoped source references

Pinned commit: 40d27448e4517301d3d8f5a27ca0c7531c51f136

Source-only route information

Unmapped fields — not user instructions

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

Source key	Handler
nameTranslations	modules/AdminBlogTags/Livewire/TagForm.php
nameTranslations.*	modules/AdminBlogTags/Livewire/TagForm.php
slug	modules/AdminBlogTags/Livewire/TagForm.php
icon	modules/AdminBlogTags/Livewire/TagForm.php
color	modules/AdminBlogTags/Livewire/TagForm.php
status	modules/AdminBlogTags/Livewire/TagForm.php
autoTranslateMissing	modules/AdminBlogTags/Livewire/TagForm.php