Settings Dashboard

Child theme dashboard that provides quick options, current status and general information.

Settings Edit child theme

Edit the current child's theme basic information, like name, version, template and author.

  • Theme name: Name of current child theme.
  • Theme version: Version of current child theme. Used for cache purposes on assets enqueue.
  • Theme description: Short description for current child theme.
  • Theme template: Parent theme used by current child theme. Select any installed theme to use as template.
  • Theme url: Website related to current child theme.
  • Theme auhor: Child theme author name and website.

On update: Child theme base style.scss file will be updated and compiled with new theme information.
On reset: Child theme base style.scss file will be reset and compiled with default settings and template twentytwentyfive

Settings Child theme screenshot

Update the current child theme preview screenshot, used in menu Appearance: Themes.

Click on preview image to select/upload a custom image from the media library.
Recommended image format and size: JPG | 1200 x 900px
On update/reset: Selected/default image will be copied to child theme's folder, replacing current file screenshot.jpg

Settings Status

Child theme and SCSS compiler current status, general information and tools.

Settings Tools: Reset theme mods

Remove current child theme mods fields from database and regenerate with default values.

Select a group type or single theme mod to reset, useful when changing template to remove parent theme related fields.
On update: Selected theme mods will be deleted, and regenerated with default values on next load if required.

Settings Tools: Reset custom fields

Delete custom files and reset to default templates.
Select a group type or single custom file to reset.

All custom files are organized by extension subfolders in the child theme custom folder.: wp-content/themes/dct-child-theme/custom/
Any custom file or extension subfolder deleted with FTP will be regenerated with the default template on next load.
On update: Selected custom files will be deleted and regenerated with default template.

Debugger Debugger options

Enable debug mode to use debugger panel for administrators and related functions during development.

The debugger panel can be accessed only by administrators in frontend and admin panel from the admin topbar button. It contains information about current post queries, theme status, PHP and JS logs and other information.

  • Debug mode: Enables debugger panel for administrators in frontend and admin panel, with PHP and JS logs, post queries, child theme status and other information.
    Recommended only in development.
  • Debug mode advanced: Adds more verbose to PHP and JS logs and enables developer mode in admin panel.
    Recommended only in development, for advanced users.

Debugger How to debug

Use degugger panel log for PHP and JS

Add an entry to the debugger panel log in PHP and JS custom files code:

dct_debug(text, variable, level, advanced);

Use this function to debug any variable type with a custom level when debug mode is enabled. In JS, also logs to the browser console.
  • text: Text to debug. Default: empty.
  • var: Variable to debug (any type). Default: empty.
  • level: Level of log entry, allows filtering. Options: "log" (default), "info", "success", "warning", "error".
  • advanced: Only log when debug mode advanced is enabled. Default: false.
  • var_table: Only for JS. Log variable to console in table format. Default: false.

How to use dct_debug function with custom files code:

Use $dct object in PHP and JS

Object $dct contains information about your child theme, environment and current page that can be used in custom JS and PHP code.


How to use global $dct object with custom files code:

Current $dct object contents:
{
    "debug": {
        "enabled": true,
        "advanced": false,
        "maintenance": false
    },
    "scss_compiler": {
        "minify": false,
        "autocompile": false
    },
    "colors": [],
    "fonts": [],
    "sizes": [],
    "assets": {
        "css": [
            "style-admin-scss",
            "dct-style"
        ],
        "js": [
            "codemirror-dct-bundle-min-js",
            "gsap-min-js",
            "dct-base-js",
            "custom-js"
        ]
    },
    "customizer": {
        "preloader": false,
        "admin_panel": true,
        "login_page": false
    },
    "theme": {
        "Name": "DCT for WP",
        "Version": "1.1.0",
        "Description": "Dynamic Child Theme for WordPress v1.1.0",
        "ThemeURI": "https://www.dctforwp.com",
        "Author": "Estudi FGH.net",
        "AuthorURI": "https://www.estudifgh.net",
        "Template": "Divi",
        "TextDomain": "dct",
        "DomainPath": "",
        "Status": "publish",
        "Stylesheet": "dct-child-theme",
        "StylesheetURI": "https://www.dctforwp.com/wp-content/themes/dct-child-theme"
    },
    "post": {
        "post_title": "Help",
        "post_id": 37,
        "post_type": "page",
        "post_status": "publish",
        "post_date": "23/04/2026",
        "post_author": ""
    },
    "user": {
        "user_login": false,
        "user_id": 0,
        "user_name": false,
        "user_email": false,
        "user_roles": null
    },
    "conditionals": {
        "is_admin": false,
        "is_blog_admin": false,
        "is_login": false,
        "is_front_page": false,
        "is_home": false,
        "is_singular": true,
        "is_single": false,
        "is_page": true,
        "is_archive": false,
        "is_category": false,
        "is_tag": false,
        "is_date": false,
        "is_attachment": false,
        "is_author": false,
        "is_page_template": false,
        "is_paged": false,
        "is_post_type_archive": false,
        "is_search": false,
        "is_404": false,
        "is_ssl": true
    },
    "environment": {
        "Site URL": "https://www.dctforwp.com",
        "Theme basepath": "https://www.dctforwp.com/wp-content/themes/dct-child-theme",
        "Theme name": "DCT for WP",
        "Theme version": "1.1.0",
        "Wordpress version": "6.9.4",
        "PHP version": "8.2.30"
    },
    "language": {
        "locale": "en_US",
        "user_locale": "en_US"
    }
}

Debugger Debugger panel options

Set options for debugger panel, available in frontend and admin panel when debug mode is enabled.

The debugger panel can be accessed only by administrators in frontend and admin panel from the admin topbar button. It contains information about current post queries, theme status, PHP and JS logs and other information.

Debugger Maintenance mode

Enable maintenance mode to disable the website for all users except administrators with a customizable page during development.
Recommended only in development.
Site will be disabled to users.


On update: Related theme mod will be updated. If maintenance mode is enabled, site will be disabled for all users except administrators.
On reset: Related theme mod will be reset to default values. Maintenance mode will be disabled.

Designer SCSS Compiler options

Set options for the SCSS compiler of child theme custom styles files.

  • SCSS Compiler minify: Minify CSS output when compiling SCSS files.
    Recommended in production.
  • SCSS Autocompile: Check for SCSS files updates and compile CSS output if required. Useful for editing custom files in an external editor and update them with FTP.
    Recommended only in development.

Designer Global variables: Colors

Add & edit global color variables to use in customizer and child theme custom files code.
Optionally add automated color shades (light & dark versions) and complementary color.


On update:
Basic mode: New code will be generated to update the related partial SCSS file and all CSS will be compiled. Related theme mod will be updated.
Advanced mode: Editor code will be used to update the related partial SCSS file and all CSS will be compiled. Related theme mod will not be updated.

On reset:
Variables will be deleted.
Related partial SCSS file will reset to default template and all CSS compiled. Related theme mod will reset to default values.
How to use global colors variables with custom files code:

Designer Global variables: Fonts

Add & edit global fonts variables to use in child theme custom files code.
Optionally add @import rule on top of SCSS code, useful if font is not already imported.


On update:
Basic mode: New code will be generated to update the related partial SCSS file and all CSS will be compiled. Related theme mod will be updated.
Advanced mode: Editor code will be used to update the related partial SCSS file and all CSS will be compiled. Related theme mod will not be updated.

On reset:
Variables will be deleted.
Related partial SCSS file will reset to default template and all CSS compiled. Related theme mod will reset to default values.
How to use global fonts variables with custom files code:

Designer Global variables: Sizes

Add & edit global sizes variables to use in child theme custom files code.


On update:
Basic mode: New code will be generated to update the related partial SCSS file and all CSS will be compiled. Related theme mod will be updated.
Advanced mode: Editor code will be used to update the related partial SCSS file and all CSS will be compiled. Related theme mod will not be updated.

On reset:
Variables will be deleted.
Related partial SCSS file will reset to default template and all CSS compiled. Related theme mod will reset to default values.
How to use global sizes variables with custom files code:

Developer Enqueue assets

Enqueue local or external assets with a version cache to the child theme frontend pages and admin panel.

Allowed assets types to enqueue: JS, CSS and local SCSS (will be compiled to CSS).

Select custom url, a local asset (uploaded to child theme custom assets folder) or a CDN url. Assets will be enqueued in order before child theme custom files, so enqueued assets can be used in custom code. Useful to add external libraries that can be used in JS custom code, or styles that can be overwritten in SCSS custom code.
Asset options:
  • Asset source: Upload your custom assets to use them as local assets, use a external CDN or custom url.
  • URL: Asset URL or relative path to custom assets folder.
  • Asset version: Asset version, which is added to the URL as a query string for cache busting purposes.
  • Enqueue on frontend: Enqueue asset on frontend, used for public site.
  • Enqueue on admin panel: Enqueue asset on admin panel, used for administrators.

On update:
Basic mode: New code will be generated to update the related PHP file. Related theme mod will be updated.
Advanced mode: Editor code will be used to update the related PHP file. Related theme mod will not be updated.

On reset:
No assets will be enqueued.
Related PHP file will reset to default template. Related theme mod will reset to default values.

Developer Custom local assets

Upload allowed assets to use them as local assets in assets source selector.

Upload your own SCSS / CSS / JS files or folders to child theme custom assets folder:: wp-content/themes/dct-child-theme/custom/assets/

Developer Post types

Register custom post types and edit options and labels.


Post type options:
  • Post type label: Name of the post type shown in the menu. Usually plural.
  • Post type key: Key name of the custom post type. Will be sanitized, must not exceed 20 characters. Leave blank to generate from post type label.
  • Description: Short descriptive summary about this post type.
  • Post type supports: Core feature(s) the post type supports.

Post type parameters:
  • Hierarchical: Whether the post type is hierarchical. Enable to create pages. Disable to create posts.
  • Public: Whether a post type is intended for use publicly either via the admin interface or by front-end users.
  • Publicly queryable: Whether queries can be performed on the front end for the post type as part of parse_request().
  • Show UI: Whether to generate and allow a UI for managing this post type in the admin.
  • Show in REST: Whether to include the post type in the REST API. Enable for the post type to be available in the block editor.
  • Show in navigation menus: Makes this post type available for selection in navigation menus.
  • Has archive: Whether there should be post type archives.
  • Can export: Whether to allow this post type to be exported.
  • Exclude from search: Whether to exclude posts with this post type from front end search results.

Post type rewrite:
  • Rewrite: slug: Customize the permastruct slug. Leave blank to default to post type key.
  • Rewrite: feeds: Whether the feed permastruct should be built for this post type.
  • Rewrite: with front: Whether the permastruct should be prepended with WP_Rewrite::$front.
  • Post type capability: The string to use to build the read, edit, and delete capabilities Leave blank for default post / page.

Post type menu:
  • Menu icon: The icon for the post type in admin menu.
  • Menu name: Label for the menu name. Default is same as post type name (plural).
  • Menu position: The position in the menu order the post type should appear. Set to 0 for default position.

Post type labels:
  • Post type name (plural): General name for the post type, usually plural. Default is same as post type label.
  • Post type name (singular): Name for one object of this post type. Default is "Post" / "Page".
  • Add new: Label for adding a new item. Default is "Add Post" / "Add Page".
  • Add new item: Label for adding a new singular item. Default is "Add Post" / "Add Page".
  • New item: Label for the new item page title. Default is "New Post" / "New Page".
  • Edit item: Label for editing a singular item. Default is "Edit Post" / "Edit Page".
  • View item: Label for viewing a singular item. Default is "View Post" / "View Page".
  • View items: Label for viewing post type archives. Default is "View Posts" / "View Pages".
  • All items: Label to signify all items in a submenu link. Default is "All Posts" / "All Pages".
  • Archives: Label for archives in nav menus. Default is "Post Archives" / "Page Archives".
  • Search items: Label for searching plural items. Default is "Search Posts" / "Search Pages".
  • Not found: Label used when no items are found. Default is "No posts found" / "No pages found".
  • Not found in Trash: Label used when no items are in the Trash. Default is "No posts found in Trash" / "No pages found in Trash".
  • Parent item: Label used to prefix parents of hierarchical items. Not used on non-hierarchical post types. Default is "Parent Page".

On update:
Basic mode: New code will be generated to update the related PHP file. Related theme mod will be updated.
Advanced mode: Editor code will be used to update the related PHP file. Related theme mod will not be updated.

On reset:
No custom post types will be registered.
Related PHP file will reset to default template. Related theme mod will reset to default values.

Developer Taxonomies

Register taxonomies (categories and tags) and edit associated post type, options and labels.


Taxonomy options:
  • Taxonomy label: Name of the taxonomy shown in the menu. Usually plural.
  • Taxonomy key: Key name of the taxonomy. Will be sanitized, must not exceed 32 characters. Leave blank to generate from taxonomy label.
  • Description: Short descriptive summary about this taxonomy.
  • Associated post types: Post types with which the taxonomy should be associated. Single, multiple, and empty values are allowed.

Taxonomy parameters:
  • Hierarchical: Whether the taxonomy is hierarchical. Enable to create categories. Disable to create tags.
  • Public: Whether a taxonomy is intended for use publicly either via the admin interface or by front-end users.
  • Publicly queryable: Whether the taxonomy is publicly queryable.
  • Show UI: Whether to generate and allow a UI for managing terms in this taxonomy in the admin.
  • Show in REST: Whether to include the taxonomy in the REST API. Enable for the taxonomy to be available in the block editor.
  • Show admin column: Whether to display a column for the taxonomy on its post type listing screens.
  • Show in menu: Whether to show the taxonomy in the admin menu. If enabled, the taxonomy is shown as a submenu of the object type menu. If disabled, no menu is shown.
  • Show in navigation menus: Makes this taxonomy available for selection in navigation menus.

Taxonomy labels:
  • Taxonomy name (plural): General name for the taxonomy, usually plural. Default is same as taxonomy label.
  • Taxonomy name (singular): Name for one object of this taxonomy. Default is "Tag" / "Category".
  • Add new item: Label for adding a new singular item. Default is "Add Tag" / "Add Category".
  • New item: Label for the new item name. Default is "New Tag Name" / "New category Name".
  • Edit item: Label for editing a singular item. Default is "Edit Tag" / "Edit category".
  • View item: Label for viewing a singular item. Default is "View Tag" / "View Category".
  • Update item: Label for updating a singular item. Default is "Update Tag" / "Update Category".
  • Back to items: Label displayed after a term has been updated. Default is "Back to tags" / "Back to categories".
  • All items: Label to signify all items in a submenu link. Default is "All Tags" / "All Categories".
  • Search items: Label for searching plural items. Default is "Search Tags" / "Search Categories".
  • Not found: Label used when no items are found. Default is "No tags found" / "No categories found".
  • Parent item: This label is only used for hierarchical taxonomies. Default is "Parent Categoriey".
  • Menu name: Label for the menu name. Default is same as taxonomy name (plural).

On update:
Basic mode: New code will be generated to update the related PHP file. Related theme mod will be updated.
Advanced mode: Editor code will be used to update the related PHP file. Related theme mod will not be updated.

On reset:
No taxonomies will be registered.
Related PHP file will reset to default template. Related theme mod will reset to default values.

Developer Custom fields

Register custom fields metabox and edit associated post type, options and fields.


Meta box options:
  • Meta box title: Title of the meta box with custom fields group.
  • Associated post type: Post type with which the meta box and custom fields should be associated. Only one meta box for post type is allowed.
  • Meta box context: The context within the screen where the box should display. Available contexts vary from screen to screen.
  • Meta box priority: The priority within the context where the box should show.

Custom field options:
  • Custom field label: Label of the custom field input in meta box.
  • Custom field key: Key name of the custom field, used to display the field value on the front end. Will be sanitized. It is recommended to use post type as a prefix. Add an underscore in first place to make this custom field private and not shown in the admin UI. Leave blank to generate from post type & label.
  • Type: Type of input for this custom field. Available tpes: Text, Textarea, Number, Date, Color, Image / File, Select option, Checkbox list.
  • Options list: Comma separated list of options for select and checkboxes custom field types. Option 1, Option 2, Option 3

On update:
Basic mode: New code will be generated to update the related PHP file. Related theme mod will be updated.
Advanced mode: Editor code will be used to update the related PHP file. Related theme mod will not be updated.

On reset:
No custom fields will be registered.
Related PHP file will reset to default template. Related theme mod will reset to default values.

Developer How to use custom fields

To display the custom fields for each post, you have to use a template tag that customizes your theme.
get_post_meta($post->ID, $field_key, true);

In visual builders, use dynamic content and custom field name to display the value.
Private custom fields (with field key starting with underscore) will not be shown in the admin UI and visual builders.

Customizer Preloader

Show a customizable preloader when loading frontend pages.

Enable page preloader to customize background, border, image and animations.
On update:
Basic mode: New code will be generated to update the related partial SCSS file and all CSS will be compiled. Related theme mod will be updated.
Advanced mode: Editor code will be used to update the related partial SCSS file and all CSS will be compiled. Related theme mod will not be updated.

On reset:
Preloader will be disabled.
Related partial SCSS file will reset to default template and all CSS compiled. Related theme mod will reset to default values.

Customizer Admin panel

Customize admin panel colors, logos and other options.

Enable to customize admin panel sidebar colors and logo, admin topbar styles and admin panel footer info and credits.
On update:
Basic mode: New code will be generated to update the related partial SCSS file and all CSS will be compiled. Related theme mod will be updated.
Advanced mode: Editor code will be used to update the related partial SCSS file and all CSS will be compiled. Related theme mod will not be updated.

On reset:
Admin panel will reset to default styles.
Related partial SCSS file will reset to default template and all CSS compiled. Related theme mod will reset to default values.

Customizer Dashboard custom widget

Add a custom widget panel with html contents to admin panel dashboard.

Enable dashboard custom widget to edit custom panel html contents.
Useful to add quicklinks to admin panel or forntend pages.
On update: Dashboard custom widget will appear in admin panel dashboard when enabled. Related theme mod will be updated.
On reset: Dashboard custom widget will be disabled and contents reset to default html. Related theme mod will reset to default values.

Code editor Add & edit custom code

Use the code editor to update any child theme custom file.

Select default child theme SCSS, JS or PHP file from the top submenu to add your custom code.
Select any custom file from the child theme custom files panel to edit the code directly.
All custom files are organized by extension subfolders in the child theme custom folder.: wp-content/themes/dct-child-theme/custom/
Any custom file or extension subfolder deleted with FTP will be regenerated with the default template on next load.
On update: Custom file will be updated with code editor contents.
On reset: Custom file will be deleted and regenerated with default template.

Code editor File selector

Select child theme file to edit with code editor or reset contents to default template.

All custom files are organized by extension subfolders in the child theme custom folder.: wp-content/themes/dct-child-theme/custom/
Any custom file or extension subfolder deleted with FTP will be regenerated with the default template on next load.

Code editor Child theme functions and variables

All custom files are organized by extension subfolders in the child theme custom folder.: wp-content/themes/dct-child-theme/custom/
Any custom file or extension subfolder deleted with FTP will be regenerated with the default template on next load.
How to use global colors variables with custom files code:

How to use global fonts variables with custom files code:

How to use global sizes variables with custom files code:

How to use dct_debug function with custom files code:

How to use global $dct object with custom files code: