About developer
Your content goes here. Edit or remove this text inline or in the module Content settings. You can also style every aspect of this content in the module Design settings and even apply custom CSS to this text in the module Advanced settings.
Assets enqueue
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.
Custom local assets
Custom 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.
Registered post types
All registered post types (core WP and custom) are listed in sidebar panel.
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.
Registered taxonomies
All registered taxonomies (core WP and custom) are listed in sidebar panel.
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.
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);
Private custom fields (with field key starting with underscore) will not be shown in the admin UI and visual builders.