Use Default Versus Custom Frontend Design Scopes
This article explains the Use Defaults/Customize behavior and how saved custom values are preserved while a scope temporarily inherits defaults.
Where this fits in QC Support Ticket
Frontend Design and Frontend Text change presentation and wording only. They do not bypass customer ownership, Agent Department scope, ticket workflow, or server-side permissions, so functional testing should be completed before and after appearance changes.
Primary location: Joomla Administrator → Components → QC Support Ticket → Frontend Design.
How to do it
- Open Frontend Design and select the scope.
- Use Use Defaults when the scope should inherit QCST's default/shared design.
- Choose Customize to activate the saved scope-specific values.
- Save and compare the frontend. Switching back to defaults should not be treated as a request to erase previously saved custom values unless the interface explicitly says so.
How inheritance works
The Default Frontend Design is the base. Customer Support Portal and Agent Queue each have a Use Defaults / Customize toggle. When a specific scope uses defaults, QCST resolves its displayed values from the default design. When Customize is enabled, that scope uses its own saved values.
Why saved custom values are retained
Switching a scope back to Use Defaults is an inheritance choice, not a request to erase the scope’s previous custom values. This lets an administrator temporarily return a portal to the shared design and later re-enable Customize without rebuilding the old settings. Use Restore Original Defaults only on the Default Frontend Design when you actually intend to restore the original default formats.
Verify the result
- With Use Defaults, the Customer Support Portal or Agent Queue follows Default Frontend Design values.
- Re-enabling Customize restores that scope’s saved custom values.
- Restore Original Defaults affects the Default Frontend Design only when deliberately used.
Inheritance makes global changes predictable
If both Customer Support Portal and Agent Queue are using defaults, a change in Default Frontend Design can affect both at once. If one scope is customized, that scope retains its own saved values instead. Before a broad brand refresh, note which scopes are customized so you know which pages will inherit the default change and which require separate edits.
Community Discussion
For practical QC Support Ticket workflows and discussion with other Joomla site owners, visit the QC Support Ticket Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.