Theme Reference

Sections

• Admin Panel — Gutenberg toggle, admin bar, dashboard widgets
• Security — XML-RPC, REST API, version hiding, login URL
• Extensions — Forms handler, SMTP, Telegram, reCAPTCHA
• WooCommerce — WooCommerce-specific settings
• Theme Settings — Field backend (SCF/ACF), migration tools
• Search — Search page configuration

From a PHP template (Query Presets)

Build a preset in the Post/Term Query Presets sub-tab, give it a Query Code, then call it from template code:

• Posts: $q = new WP_Query(tf_get_query('your-code'));
• Terms: $terms = tf_get_term_query('your-code');
• Auto-apply: attach a preset to a post-type or taxonomy archive on the Auto-apply tab and it overrides the main query automatically (via pre_get_posts) — no template edit needed.

From HTML attributes (Custom Queries)

Name a query in the Custom Queries / Term Queries sub-tab, then reference it on the loop element — or write the arguments inline. Only the first child element is used as the repeating template.

• Named: <div wp-select="catalog"> … </div> (alias: wp-query-name)
• Inline: <div wp-query="'post_type'=>'product','posts_per_page'=>8">
• Term list: <div wp-term-query="'taxonomy'=>'product_cat','parent'=>0"> · wp-term-select="name"
• WooCommerce: <div wp-product-query="get_related_products(4)">

Inside the loop — fields

On elements inside the loop, output values with WordPress attributes or ACF/SCF field attributes:

• WordPress: wp="post-title", wp="post-image", wp="post-link", wp="term-title", wp="term-link"
• ACF / SCF: fld-text, fld-image, fld-link, fld-loop (Alternative format: f_text, f_image, f_loop)

Compatibility

The runtime reads three sources in priority order: TF presets, then Query Master (older imported sites), then the legacy configurator queries. New presets are always saved to TF storage; existing data keeps working.

Custom Post Types

Each row maps to register_post_type(). The Name field is the post-type key (lowercase Latin, no spaces). Set the plural/singular/menu labels, a Dashicons icon, the supported features (title, editor, thumbnail, …), the archive URL slug, REST/Gutenberg, public queryability, a Public archive toggle (turn the /slug/ feed off for service types) — and an optional Archive landing page that makes the archive editable (see the "Archive landing pages" section below).

Custom Taxonomies

Each row maps to register_taxonomy(). Choose Hierarchical (like categories) or Flat (like tags), link it to one or more post types, and set the slug and REST visibility.

How they connect

New post types and taxonomies appear automatically in the Query Presets dropdowns. Permalinks refresh on save. Templates follow WordPress conventions: single-{type}.php, archive-{type}.php, taxonomy-{taxonomy}.php.

How it works

On the archive page of your Webflow project (archive-post, archive-product, archive-{type}) place field attributes OUTSIDE the listing loop — that is, outside the element marked wp="posts" / wp="products". Those fields automatically attach to the landing page in the admin and render from it on the archive URL.

• Any single-value field works outside the loop: fld-text, fld-image, fld-link, fld-bg-image, fld-editor and the rest of the fld-* family — plus wp="post-title" and wp="post-content", which print the landing page's own title and content.
• Fields INSIDE the loop keep their normal meaning: they read each listed post, exactly as before.
• Multilingual sites resolve the landing page per language automatically (Polylang / WPML): each locale edits its own translation of the landing page.
• SEO: for custom post type archives the landing page also feeds Yoast — the archive gets the page's SEO title and a correct canonical URL, including paginated pages.

Blog

The blog landing is the native WordPress "Posts page". Create a page (for example /blog/), assign it in Settings → Reading, and the fields you placed outside the loop on the archive-post template attach to that page — no extra setup.

WooCommerce catalog

The shop catalog uses the WooCommerce Shop page as its landing. Fields placed outside the product loop on the archive-product template attach to the Shop page and render on the catalog URL.

Custom post types

A custom post type archive has no native landing in WordPress, so ThemeForge adds one: create a page whose URL matches the archive slug (for example /portfolio/ for a type with archive slug "portfolio"), then select it in the post type's row in the Theme Panel. The archive URL keeps rendering the feed template, and the selected page carries its editable fields. If the archive template in your Webflow project declares a fields group, ThemeForge creates (or adopts) the landing page automatically — in every site language, the same way WooCommerce creates its Shop page.

The bound page OWNS the archive URL: rename the page and the archive moves with it (the Slug field hides while a page is bound). Without a bound page the slug comes from the Theme Panel. The page itself is never shown directly — it is the editing surface behind the archive.

Good to know

• Group fields outside the loop (repeater, group, flexible content, gallery) are read from the landing page just like single-value fields. The one exception is a group with loop-mode="0" — the project's Logs tab flags it as "archive-scope-unsupported".
• A field placed INSIDE a listing loop belongs to the posts being listed — declare it on the corresponding single-{type} template so it appears on those posts' edit screens.
• If no landing page is configured, nothing breaks: the archive renders exactly as before, and the fields simply stay global-less. You can add the landing page at any time without regenerating the theme.

Features

• SMTP email sending (default: smtp.gmail.com:465/SSL)
• reCAPTCHA v3 / v2
• Telegram notifications
• Spam protection without keys — on for new sites
• Auto-reply to form submitter
• JustValidate client-side validation
• CPT tf_form_entry — submission storage in WordPress
• CSV export

Spam protection

Works without keys or outside services. On a new site it is on from the start; on a site that already receives leads, turn it on with "Basic spam protection" under Forms → Settings.

• Filters out submissions that fill a hidden trap field, arrive without the page script, are sent faster than a person can type, carry several links, or skip the image captcha. How often one address can send is limited.
• Filtered submissions are not sent anywhere: they stay in the Spam folder of Submissions for 30 days, and one filtered by mistake can be restored with "Not spam".
• WordPress’s own forms are covered by a separate switch, “Spam protection for WordPress forms”, on by default: comments and product reviews, registration and password reset. A comment a bot sends without opening the page is refused and never stored; a borderline one goes to Comments → Spam; a suspicious registration or reset request is refused with a request to try again. The login form and logged-in users are not checked.
• The image captcha speaks the page language: texts are set per language, and it draws only characters a visitor can type without switching keyboard layout (Ukrainian, Russian, Latin letters or digits).

Against bots built to imitate a person, use reCAPTCHA with Google keys — it is enabled in the same settings.

wp-field — a field key that survives a rename

By default a form field is submitted under the label you typed in Webflow. Rename that label later and the mail template and any delivery mapping that referenced it stop matching — silently, because the submission still arrives. Mark the field (or its wrapper with the label) and the key stops depending on the caption.

<input type="tel" wp-field="phone">

<div class="row" wp-field="phone">
  <label for="tel">Phone</label>
  <input type="tel" id="tel">
</div>

The key is written into the field when the theme is generated, so nothing needs configuring afterwards. Use Latin letters, digits, _ and -; names reserved by the form pipeline are refused and listed in the project log. Fields whose name is fixed by WordPress or WooCommerce — comments, reviews, checkout — use their own marks instead.

Two engines, one data format

Secure Custom Fields is the default — a free WordPress.org plugin that auto-updates and provides every ACF PRO field type, with no license. Prefer your own licensed ACF PRO? Install it and the theme detects it automatically.

How It Works

The theme detects Polylang or WPML and loads the appropriate integration automatically.

• Auto-detection: Polylang (pll_current_language) or WPML (ICL_SITEPRESS_VERSION)
• Per-locale storage: each language gets its own set of option values
• Fallback: empty locale fields inherit values from "All (default)"
• Custom flags: upload custom language flags from Media Library

Managing Options by Language

Use the language switcher bar on the Options page to edit values for each language.

Auto-Translate Fields

Built-in machine translation for field values. Available in the sidebar on post edit and options pages.

• Per-field "Translate" button next to each text field label
• "Translate All" button in sidebar — translates all fields at once, including hidden tabs and repeaters
• Link fields auto-skipped (detected by field name and URL value pattern)
• No API key required — uses Google Translate free endpoint
• WYSIWYG (rich text) fields supported — HTML structure preserved

• user-functions.php — Custom PHP functions
• css/user.css — Custom CSS styles
• js/user.js — Custom JavaScript

CSS load order: main.css → themeforge.css → user.css. Use user.css to override any theme styles.

Import Actions

Page Title Source

When creating WordPress pages during import, the page title is taken from the source HTML in priority order:

1. <meta property="og:title"> — Open Graph
2. <title> — HTML title tag
3. Template name (e.g. "About" from page-about)

Image Filename Resolution

The import system resolves Webflow image filenames to WordPress attachment IDs using a fallback chain:

• URL-decode filename (handles Cyrillic: %D0%94%D0%B5... → Десерт...)
• Strip 24-hex Webflow hash prefix (695a454c..._ → original name)
• sanitize_file_name() + DB LIKE query for robust matching

Locale-Aware Import

Add &lang=xx to import data for a specific language. The import metabox on page edit screens auto-detects the page language.

Usage

• Wraps fields into a named group (metabox in admin)
• Multiple wp-fields-group groups per page supported
• On theme-options page: all groups merge into one options container
• Without wp-fields-group: fields generate PHP only (no admin UI)

Usage

• Place on <body> tag — by default, editor is hidden on page templates with fields
• Use together with wp-fields-group when the page needs both custom fields AND the_content()
• Does not apply to single-post templates (single, single-product) — they always keep the editor

wp-menu

Simple menu rendering. Extracts link/dropdown classes from Webflow HTML structure. Outputs Webflow-compatible markup.

wp-menu-tree

Recursive menu with custom template. First child element = template for each menu item. Supports unlimited nesting.

wp-menu-tpl

Explicit template markers inside wp-menu-tree. "link" = simple items, "drop" = dropdown items with children. Generates if/else on menu_children.

Same fields, same data

Switching the engine never migrates or rewrites your content — both engines read the same field keys from wp_postmeta / wp_options. Existing ACF data from another theme or a manual setup is picked up by field name, regardless of which engine created it.

Existing & third-party ACF data

If ACF (or SCF) data already exists — from another generator, a previous theme, or a manual field group — the theme reads it as-is by field name. Nothing to import or convert; the values appear in the editor under whichever engine is active.

General Hooks

WooCommerce Hooks

Define these functions in custom.js. Legacy wfp_ prefixed names are also supported for backward compatibility.

Post Query

Set up in Theme Panel → Custom Queries. Each query has: name, post type, posts per page, pagination, taxonomy filters.

Term Query

Set up in Theme Panel → Custom Term Queries. Each query has: name, taxonomy, hide_empty, orderby, order.

General

WooCommerce