Permissions are based on module paths, which correspond to the sections and actions inside the admin panel. Each role contains two rule lists:

• Allow list - explicitly grants access
• Deny list - restricts or overrides access

Vvveb checks the allow list first, then applies deny rules to limit or block specific actions.

Understanding Module Paths

Every admin page or action has a module path.
For example:

• Posts list: content/posts
• Post editor: content/posts/edit
• Product list: product/list
• Plugin settings: plugins/contact-form

You can see the module path directly in the URL when navigating the admin panel.

Allowing or Denying Access

To control access:

• Add a module path to the allow list to grant permission
• Add a module path to the deny list to block permission

This gives you fine‑grained control over what each role can do.

Using Wildcards

Wildcards (*) let you apply rules to entire groups of modules or actions.

Examples

Allow access to all content modules

content/*

This covers posts, pages, categories, menus, and more.

Deny delete actions for all content modules

content/*/delete

Users can still view and edit content, but cannot delete anything.

Deny delete actions globally

*/delete

Blocks delete actions across the entire admin panel.

Allow access to all plugin settings

plugins/*

Allow or deny access to a specific plugin

plugins/contact-form

How Allow and Deny Rules Interact

Vvveb processes rules in this order:

1. Allow list - grants access
2. Deny list - restricts or overrides access

This means you can allow broad access, then selectively block sensitive areas.

Example

Allow full access to products:

product/*

Then deny delete and category management:

product/*/delete
product/categories

This gives users access to products and orders, but prevents them from deleting items or modifying categories.

Practical Use Cases

Content‑only roles

Allow:

content/*
editor/*
media/*

Deny:

content/*/delete

Ecommerce manager

Allow:

product/*
order/*

Deny:

settings/*
tools/*

Restricted demo account

Allow:

content/*
product/*

Deny:

*/save
*/delete
settings/*
tools/*

Summary

Admin roles give you powerful control over who can access what inside Vvveb.
Using allow/deny rules and wildcards, you can build roles tailored to:

• Editors
• Authors
• Ecommerce managers
• Developers
• Demo users
• API integrations

This ensures your site stays secure while giving each team member exactly the access they need.

Creating a token

1. Go to Admin → Auth tokens Click Add, select the user the token acts as
2. Save - the generated token string is shown once; copy it immediately

Using a token

Send it with requests, e.g. as Authorization: Bearer <token> (or per integration instructions). Requests run with the permissions of the linked admin user.

Security

• Treat tokens like passwords - revoke any token you can't account for
• Delete tokens that are no longer used from the list
• All token usage appears in logs like normal admin activity

With the ActivityPub plugin installed, your Vvveb website functions as a federated profile, along with profiles for each admin user.

If your website is example.com, then the profile can be found at @example.com@example.com, and authors like Joe would have their individual profiles at @joe@example.com

Once you follow Jane’s @jane@example.com profile, any blog post she crafts on example.com will show in your Home feed.

1. Install the ActivityPub plugin.
2. Go to Mastodon or another federated platform, and search for your profile and follow it.
3. Your profile will be in the form of either @your_username@example.com eg @admin@demo.vvveb.com.
4. On your site, publish a new post.
5. From Mastodon, check to see if the new post appears in your feed.

Plugin repository https://github.com/Vvveb/activitypub.

Recommended microblogging microblogging theme https://themes.vvveb.com/products/manny.

The plugin works with the following tested federated platforms, but there may be more that it works with as well:

• Mastodon
• Pleroma
• Akkoma
• friendica
• Hubzilla
• Pixelfed
• Socialhome
• Misskey

It may take a few minutes for the new post to show up in your federated feed.

Once ActivityPub is installed, only new posts will be available in the fediverse.

Users will never see previously published posts in their feed.

With ActivityPub, if someone follows your site, they will only receive new blog posts you publish from then on.

Plugin repository https://github.com/Vvveb/editor-js.

Plugin repository https://github.com/Vvveb/sun-editor.

Plugin repository https://github.com/Vvveb/minify.

Plugin repository https://github.com/Vvveb/catalog-mode.

Plugin repository https://github.com/Vvveb/hide-language-selector.

Plugin repository https://github.com/Vvveb/dicebear.

Example plugin that adds a menu entry in the admin dashboard and a new page on frontend with a list of products.

Plugin repository https://github.com/Vvveb/graphql.

Plugin repository https://github.com/Vvveb/tinymce-plugins

Used in production on docs.vvveb.com.

Behavior

• Scans post content for headings and generates anchor links
• Clicking an entry scrolls to the section; the current section is highlighted while scrolling
• Long posts become easier to scan, which also helps search engines show jump links

Uses adminer for database management.

Usage

1. Activate the plugin
2. Open its settings page (Settings link on the Plugins list)
3. Paste code in Header scripts and/or Footer scripts Save - snippets are injected site-wide on every page

Common use cases: Google Analytics / Tag Manager, Facebook Pixel, cookie consent widgets, schema markup.

Plugin repository https://github.com/Vvveb/file-manager

Modules

The plugin is modular - enable only the feature areas you need from Settings → SEO → Modules:

Core (v1)

• On-page SEO & Content Score - focus keywords, SERP preview, real-time score in the editor
• Schema Builder - per-page structured data without writing JSON-LD
• XML Sitemaps - auto-generated /sitemap.xml plus section sitemaps
• Redirections & 404 Monitor - redirect manager with automatic slug-change suggestions
• SEO Audit - site-wide technical checks with a prioritized fix list
• Setup Wizard - guided configuration flow

Local, ecommerce & AI (v2)

• Local SEO, Ecommerce SEO, Search Console & Rank Tracker, llms.txt, AI Content Assist, Instant Indexing, AI Search Tracking

Documentation

• Plugin settings

Shows a debug bar on the bottom of the page with sql queries, filters etc

Plugin repository https://github.com/Vvveb/brevo-email.

Popup can be customized from page builder

Settings

Open Plugins > AI Assistant > Settings and save once after enabling. The three fields that matter most are provider, key and model - the rest have working defaults. Bulk-translation overrides (provider, model, key, glossary) live on the separate Translate tab; writer voice, disclosure and stock covers live on the Writer tab.

Provider

Type to search all providers from the models.dev catalog (around two hundred, e.g. OpenAI, Anthropic, Google, DeepSeek, Groq, Mistral, xAI, OpenRouter, OpenCode Zen, NVIDIA NIM). The dropdown option shows the display name and model count.

Unknown slugs stay typable on purpose: a brand-new models.dev provider works for chat immediately, and rebuilding the catalog below adds it to the list with full metadata.

API key

One key for the active provider - the placeholder hint follows the selection (sk-ant-…, AIza…, …). Switching providers keeps each provider's key server-side; only the active one is ever used. Installations that saved per-provider keys before keep working: the old key is carried over the first time you save.

Model

Type to search the selected provider's models. Picking a known model auto-fills context size and max tokens from the catalog and stores a metadata snapshot used at runtime. The info line under the field shows context window, max output, per-1M pricing, reasoning support (including which API dialect a routed model uses, e.g. via responses API), attachment kinds and tool support. Free text stays allowed for ids missing from the catalog - the manual context fields apply then.

Refresh fetches the live model list through the proxy (or directly from the provider in direct mode). Catalog rebuilds the whole local catalog from models.dev on the server (php cli.php admin module=plugins/ai-assistant/settings action=buildModels does the same from the command line) and reloads the current list.

Endpoint override (Url)

Optional custom endpoint for the active provider, e.g. a self-hosted gateway speaking its API. Empty means the catalog endpoint. Changing provider empties the field automatically with a notice, so a stale override can never silently misroute the new provider.

General tab - connection, model, shared behavior

• Api mode - proxy relays requests through the site backend so keys never reach the browser; direct calls the provider from the browser (the key travels client-side, and the provider must allow the browser origin - e.g. OLLAMA_ORIGINS for Ollama). For a local server: direct reaches the LLM on your own computer, proxy reaches the LLM on the web server.
• Proxy URL - the address the browser calls for relayed requests. Leave the default unless the admin path is customized; only used in proxy mode.
• Session header - upstream header carrying the chat session id on proxied requests (default x-vvveb-session), so provider-side logs correlate with a conversation. It never lands in the provider body; empty disables it.
• System prompt - appended to every chat request to set assistant behaviour. Keep it short; bulk jobs use their own task prompts plus this line.
• Temperature - sampling randomness for chat (0 = deterministic). Omitted automatically for reasoning models that reject it; bulk translate/write set their own values (0 and 0.7).
• Context size / Max tokens - auto-filled from the catalog when you pick a known model. Context size drives the usage bar and auto-compact; max tokens caps each answer and is clamped to the model's own output limit, so an oversized value fails safe instead of 400ing upstream.
• Image model / provider / key / size - the editor's Generate image from text button and writer cover art. Provider and key empty inherit the main ones above (e.g. chat locally, images via OpenAI); local servers have no images API, so covers need a compatible provider here. Size examples: 1024x1024, 1792x1024.

Translate tab - bulk translation overrides

All four fields are optional and share one rule: empty inherits the main setting (provider → model → key, in that order; task keys resolve server-side so secrets never travel). The classic setup is a cheap fast model here while chat stays on the strong one. Precedence for keys everywhere in the plugin is task key, then active key, then legacy per-provider keys from older versions.

• Translate provider / model / key - used by Bulk Translate, the write → translate pipeline, and translation cron. A model with a catalog entry also brings its output cap and pricing into estimates.
• Translate glossary - one Original = Replacement per line (e.g. checkout = checkout), always used exactly: bulk translation, pipeline translations, and article writing all inject it. Brand and product names belong here.
• Translate reasoning - Off by default. Sends reasoning_effort: none/minimal only when the model's catalog entry declares it and only on bearer chat dialects, retrying plain if a gateway rejects it. Field translation needs no chain of thought, and you stop paying output rates for discarded thinking.

Writer tab - article voice, disclosure, stock covers

• Tone presets - one Name | instruction per line (e.g. Playful | Write with light humor and vivid examples). The names appear in the writer's Tone dropdown; the text is appended server-side, so clients can only pick, never inject.
• AI disclosure text - appended as a footer when Disclose AI is ticked on a run; empty uses the default reviewed-by-editors sentence. Opt-in per run, never silent.
• Stock provider - source order for Stock link covers: Auto tries each configured API key in order with the keyless Unsplash search last; explicit Unsplash/Pexels API or scrape-only are also selectable.
• Unsplash / Pexels keys - free tiers (Unsplash developers: 50 requests/hour) enable the official search APIs; empty skips straight to the next source. Every candidate is host-allowlisted, IP-checked, downloaded and image-verified before it touches a post.
• Write reasoning - On by default (model behavior unchanged). Turn off once outlines carry your planning - same suppression mechanics as Translate reasoning above.

Using the assistant

• Thinking level (Off/Low/Medium/High) follows the selected model: provider-specific effort values where the catalog defines them, generic levels otherwise, disabled with an explanation when the model cannot reason. Reasoning blocks and tool calls render as collapsible cards with a Running/Done/Failed status pill: thinking streams open and collapses when finished, tool calls stay collapsed throughout (a manual expand pins a card open), errors stay open, and everything hides behind the thinking/tools toggles.
• Attachments - the file picker only offers formats the model takes; anything else is refused with a message naming what is supported. Text files (.txt, .md, .csv, …) are inlined as text so they work on every model including text-only ones; long files are truncated with a marker. Image-capable models also receive page screenshots as vision.
• Costs - every assistant message shows its estimated cost from catalog pricing; the usage footer totals the session and shows cache-hit savings. Encrypted reasoning never renders - it is preserved invisibly so multi-turn tool calls keep working.
• Failures - dropped connections and overloaded providers retry automatically with backoff (1s → 2s → 4s, longer for rate limits) and a live countdown; Stop cancels the wait. Deterministic errors (bad key, unknown model, full context) surface immediately with guidance instead.
• Sessions survive reloads and sync server-side; Compact shrinks a long conversation into a summary when context runs out. When browser storage nears its quota, sessions upload automatically and older local copies trim to metadata (reloaded on open) - a warning replaces the old silent failure.
• The assistant UI follows the admin language through the CMS-wide Vvveb.i18n runtime (public/js/libs/gettext.js, gettext-compatible plurals): sidebar, manager and editor strings translate from the same catalogs as the backend (translators add the msgids from plugins/ai-assistant/system/i18n-data.php to locale/<lang>/LC_MESSAGES/vvveb.po; English always works untranslated).
• Article writer (Plugins → AI Article Writer) turns a topic list (one per line, up to 200) into draft posts: pick language, site, categories (multi), tags, length (short/medium/long) and status (draft default - bulk AI content never auto-publishes), preview the call/token estimate, then run the resumable stepper with per-topic results. Uses the active chat model (writing wants the strongest model) with temperature 0.7, JSON mode + repair retry, and core post creation (headline, HTML body, excerpt, meta description/keywords, cover alt, slug, site link). Re-running the same topics skips already-written ones (topic-hash ledger, reported with the original post id). Outlines runs a cheap planning pass first - tick approved topics and Start writes only those. Completion notices report tokens used; the last run summary persists on the page. Cover image switch: No cover, AI-generated (paints one cover per article via the image task settings), or Stock link. Stock mode resolves sources through a provider registry (system/stock.php - implement StockProvider and add one line to register the next one): the Stock provider setting picks Auto (every configured API key in order, keyless scrape last), Unsplash API, Pexels API, or scrape-only. API results carry photographer credit into the run log; a random hit from the first 10 is verified and stored, failures fall through to a model-suggested URL and then to generation, each step logged. Every candidate is validated (allowlisted CDN host, public IP, real image ≥200×200) before it touches a post; anything suspicious is rejected down the chain. Covers save under media/ai-assistant/; a failed cover still saves the post, imageless, with a warning. Stock photos carry the source URL in the log - check the license before publishing.
• Drip publishing. Set Publish from + Every N days and articles are created scheduled with staggered dates on the ledger instead of the chosen status. Release due (also checked automatically at each run start) flips due posts to published - never overriding a status you changed by hand. Cron it with php cli.php admin module=plugins/ai-assistant/generate action=release for hands-free drip.
• Unattended jobs (cron). Three idempotent CLI actions, safe on a schedule: …/generate action=release (publish due drip), …/generate action=refreshcron language=1 limit=5 (rewrite the oldest posts), …/translate action=translatecron source=1 targets=2,3 limit=10 (translate the newest missing items). CLI skips CSRF (no session exists there); every step lands in the runs ledger with a cron-YYYYMMDD job id.
• Write → translate pipeline. Also translate to fans every finished article out to more languages in the same run (same provider call path as bulk translate, translations linked on the ledger so re-runs skip them).
• Grounded writing. Source URLs are fetched once per run and injected as background material (budget-capped) so articles can cite real facts instead of hallucinating them.
• Refresh stale posts. Switch to Refresh mode, Find stale posts lists candidates by age with checkboxes, Start rewrites the checked ones in place (slug untouched, honors tone + budget).
• Internal linking. After a write, Add links appends a related-reading block (keyword search over published posts, idempotent marker, skipped when nothing related).
• Social pack. Tick Social pack for an X thread, LinkedIn post and newsletter teaser per article, with copy buttons right in the result row.
• AI performance report. The writer page reports AI-written vs human posts and views over the ledger (proving whether any of this earns its keep).
• Upstream timeouts. A step failing with Upstream request failed … timed out … 0 bytes received means the provider never started answering within 180s (queue, reasoning prefill, cold model, huge prompt) - not a stalled download, so raising max_tokens won't help. The item fails individually and resumes on re-run; check provider status, trim grounding sources, switch reasoning off, or try a faster model before reaching for longer timeouts.
• Token budgets. A per-run token cap on both bulk pages halts the stepper (stays resumable) with a notice; the server double-checks the client-reported spend.
• Writer extras. Tone presets (Settings, Name | instruction lines), per-topic model tags merged with run-wide tags, alternative headlines in each result, multi-site fan-out, CSV topic upload, multi-category, auto-categorize (the model files each article from your category list, validated server-side), QA sieve (thin/tell flags in the log), series mode (part numbering + series plan in every prompt), and a translate glossary (Original = Replacement lines in Settings) for consistent bulk translation.
• Reasoning toggles. Chain-of-thought is pure overhead on strict bulk tasks (you pay output rates for tokens nobody reads). Translate reasoning defaults off and Write reasoning stays on; either sends reasoning_effort: none/minimal only when the model's catalog entry declares it, only on bearer chat dialects, and silently retries without the flag if a gateway rejects it.
• Product writer. The writer's Write switch covers products: descriptions with meta, disabled-by-default (publish = enable explicitly), covers, pipeline translation and social on the same runner. Scheduled drip and categories are post-only; product duplicates ledger separately.
• Refresh, SEO, links. Refresh mode rewrites stale posts in place (slug untouched); SEO backfill fills only missing excerpt/meta. Add links appends related-reading blocks found by keyword search. Every overwrite records a content revision first, so the editor's revision history is your undo.
• Review & bulk publish. Needs review lists recently written posts and products from the ledger with editor links; tick and Publish listed flips drafts/scheduled (or disabled products) live, skipping anything already published. Every bulk overwrite records a content revision first, so the editor's revision history is your undo.
• Product writer & parity. The Write switch covers products end-to-end: descriptions, disabled-by-default, covers (+gallery from extra stock hits), pipeline translation, social, refresh, SEO backfill and internal links all branch on post/product, with separate duplicate ledgers and a product performance report.
• Cost & transparency. Preview shows a dollar forecast at the active model's catalog rates; completion notices report tokens used; every bulk step lands in the Recent bulk runs ledger; an opt-in Disclose checkbox appends the configured AI note (Settings → AI disclosure text).
• Runs ledger & report. Every bulk step records calls + tokens grouped by job id (Recent bulk runs table); the performance card compares AI vs human posts/views with click-through drill-down to the actual posts; Upcoming drip lists scheduled releases (posts and products). Script tags carry mtime cache-busting so fixes actually arrive in the browser.
• Social viewer. Saved packs rehydrate per post: the result-row Social button expands the full channel texts with copy buttons, backed by the ai_social table instead of the volatile run response.
• Prompt playground. Settings page lab for trying system/user prompts against the active model (templates included for every job shape: chat, writer, translate, outline, SEO, social), with token usage per run. Nothing is saved.
• Product SEO preview. The stale/SEO finder and all runners honor the post/product switch, so backfill and refresh cover catalogs too. Note: scraping is against Unsplash's ToS (they prefer the API); if they block it, stock mode degrades gracefully to suggestion → generation.
• Bulk translate (Plugins → AI Translate) translates posts and products across languages in resumable steps: filter by type, status, site, category (with children), date and title, preview the missing-translation matrix with a call estimate, then run with progress, per-item skip-and-report errors, stop/resume, and bulk JSON export. Only empty translations are touched by default. Oversized documents translate piece by piece (block-boundary chunking) instead of skipping via the old context guard. Uses the translate provider/model/key settings, so a cheap model keeps it affordable; strict tasks request JSON mode with automatic fallback.
• Sessions manager (Plugins → AI Sessions) lists every chat with title search (or Everywhere mode, which also scans message text), sorting and paging; sessions open at #uuid links for sharing. Each row opens a read-only transcript each row opens a read-only transcript with the same collapsible thinking/tool cards plus a message/token/cost summary priced at the session's own model when known, and offers rename, fork (independent copy under a fresh id), pin (per-browser favorites sort first), delete (bulk included), single or bulk JSON export (with an attachments checkbox for a small text-only file) and Continue in sidebar, which hands the session to the site-editor sidebar. Sessions living only in the browser (never synced - e.g. from installs predating the server store, which self-creates on first use) are flagged with a one-click Sync to server banner instead of silently missing.
• Sidebar sessions can be filtered from the dropdown itself and pinned favorites always list first.

Troubleshooting

• 401 / invalid key - re-enter the key for the active provider and save.
• 404 / no such model - the id was retired or mistyped; Refresh the list or pick from the dropdown.
• 429 / rate limit - the assistant waits and retries on its own; lower pace or raise quota for persistent limits.
• Context full - use Compact, start a new session, or lower max tokens.
• Attachment refused - the message names the supported kinds; switch to a multimodal model for images, PDFs or audio.
• Empty model list - rebuild with the Catalog button (or the CLI command above).
• 500 from the upstream gateway - almost always a dialect mismatch: a chat-shaped body (messages/max_tokens) sent to a /responses endpoint, or the reverse. It happens with unrouted model ids plus a stale endpoint override. The proxy now rejects these with a plain-language 400 before relaying; fix by re-selecting the model in settings (stores its route) and saving, or by pointing the override at the matching endpoint.

Plugin repository https://github.com/Vvveb/stripe.

Builtin honeypot anti spam filter.

Contact form component allows visual customization of forms from the page builder, add any fields visually.

This plugin is included and activated by default

Plugin repository https://github.com/Vvveb/openapi.

Plugin repository https://github.com/Vvveb/two-factor-auth.

Plugin repository https://github.com/Vvveb/transliterate.

Configuration

1. Activate the plugin and open its settings page
2. Enter your CDN base URL (e.g. https://cdn.example.com)
3. Save - theme and product images are served from the CDN domain

Point the CDN hostname at your site origin (pull mode) or upload media/ separately (push). Keep paths identical to the local ones so URLs map 1:1.

Builtin honeypot anti spam filter.

Contact form component allows visual customization of forms from the page builder, add any fields visually.

This plugin is included and activated by default

Categories are created automatically based on directory structure.

This plugin is used to import markdown documentation from https://github.com/Vvveb/docs into http://docs.vvveb.com/.

Plugin repository https://github.com/Vvveb/remove-google-fonts.

The layout

The admin uses a left sidebar grouped by area:

First steps

1. Configure your site - title, description, logo
2. Write your first post
3. Set up languages if needed
4. For stores: add products, then a payment plugin
5. Run the SEO plugin's setup wizard

Where to go next

• Build pages visually with the page builder
• Extend functionality with plugins
• Keep your site safe with backups

What's on the dashboard

• Recent activity cards - new orders, comments, reviews and questions with quick links to moderate or process them
• Update status - notification when a new Vvveb version is available, with an update shortcut
• Quick actions - view the live website, clear cache, open settings, edit your profile

After installation

If you just installed Vvveb, start here:

1. Review Site settings - title, description, logo
2. Set up localization if your site is multilingual
3. Publish your first post
4. If you run a store, configure products and payment/shipping plugins

Navigation tips

• The left sidebar groups everything by area: content, products, sales, settings, tools
• Use the admin search (magnifier icon) to find any admin page by name
• The user menu (top right) holds your profile and logout

How shipping works

1. Plugins provide methods - flat rate, weight-based, carrier rates etc. Install them from Plugins; each has its own configuration
2. Region rules - combine methods with region groups so only valid destinations see a method
3. Cart data drives cost - weight (weight classes), destination (countries) and cart totals feed the calculation

Configuration

Open Settings → Ecommerce → Shipping to set store-level options (origin address defaults, handling) and enable/disable installed methods.

Related: Shipping statuses track the fulfillment state of an order (not shipped / shipped / delivered).

Changing price/interval affects new subscriptions only; active subscriptions keep the terms they started with unless your payment provider supports mid-term updates.

Managing tax types

From Settings → Ecommerce → Tax types you can add custom types (e.g. Reduced rate goods) and assign each type a sort order for display.

Rates are then configured per region in tax rates; a product is taxed according to the tax class it belongs to (see tax classes).

Creating a plan

1. Go to Settings → Ecommerce → Subscription plans Click Add Configure:
   • Name - shown on the product page
   • Billing period & interval - e.g. every 1 month, every 12 months
   • Price - recurring amount (can differ from the product price)
   • Trial / cycle limits - optional trial length or maximum cycles
2. Save

Using plans

Attach one or more plans to a product; when a customer buys it, checkout starts a subscription instead of a one-time order line. Payment plugins that support recurring billing handle the charges; subscription state changes are tracked in subscription statuses.

Default type

The built-in product type covers standard store items. Plugins can add more - e.g. a subscriptions plugin registers types tied to subscription plans, a digital-products plugin ties types to digital assets.

Why types matter

• Templates - themes can render each type differently (product/<type>.html)
• Checkout flow - digital types skip shipping; subscription types create recurring plans
• SEO & sitemaps - schema and title templates per type via the SEO plugin

Manage the list under Settings → Ecommerce → Product types.

Payment methods themselves (Stripe, PayPal, Mollie, bank transfer…) are provided by plugins - install and configure them from the plugins pages; this page ties them to the checkout flow.

Typical configuration

• Guest checkout - allow ordering without an account
• Order statuses on success/failure - which order status is assigned when payment completes or fails
• Terms / minimum order - enforce conditions before checkout

Payment plugins

After installing a payment plugin (each has its own settings page under Plugins), it becomes available at checkout. Disable a plugin to remove its method from checkout without uninstalling.

Related pages: Shipping, Order statuses, Discounts.

Common states

• Active - billing normally
• Pending - started, first payment not confirmed
• Canceled - terminated by customer or admin
• Expired - reached its cycle limit or end date
• Suspended - temporarily paused (e.g. failed payment retry window)

Manage the list under Settings → Ecommerce → Subscription statuses; payment plugins translate provider events (webhooks) into these states automatically.

Default payment statuses

• Pending - payment initiated, not confirmed yet
• Completed / Paid - funds received
• Failed - provider declined or error occurred
• Refunded - money returned to the customer
• Partially refunded - part of the amount returned
• Canceled - abandoned before completion

Managing statuses

From Settings → Ecommerce → Payment statuses you can rename, add, edit or remove entries to match your providers' vocabulary. Payment plugins map their own states onto these entries.

Typical fields:

• Type key - machine name used in URLs and templates
• Plural name - shown in menus and listings
• Icon - sidebar icon
• Comments enabled - whether the type supports comments

Custom types contributed by plugins show their source here; changing keys of built-in types (post, page) is not recommended since themes reference them.

Settings

• Default Value

The default value shown when creating a new post.

• Required

Prevents the field from accepting empty values.

• Instructions

Shows instructions for entering data for the input.

• Placeholder Text

Appears within input when no value exists.

• Prepend

Adds the text before the input.

• Append

Adds the text after the input.

Creating a field group

1. Go to Custom Fields → Field groups Click Add and give the group a name (e.g. "Book details")
2. Add the fields that belong to the group - any type from Text to Gallery or Relationship
3. Choose which content type(s) the group applies to
4. Save

How groups appear in the editor

When editing a post/product that matches the group's content type, the group shows up as a separate section with all its fields. Editors only see groups relevant to what they are writing.

Displaying values in themes

Field values are stored per post and can be rendered in themes through template variables or components, keyed by the field slug. See the individual field type docs for output details.

Each field type defines how data is entered in the admin panel and how it can be displayed in your theme. All fields share a consistent set of settings, making them predictable and easy to configure.

How Custom Fields Work

A Custom Field consists of:

• A field type (e.g., Text, Image, Gallery, Date, Product)
• A label (what editors see)
• A slug (used to retrieve the value in templates)
• Optional settings (default value, required, instructions, etc.)

When a field is added to a post type, it appears in the editor and stores its value in the database. You can then display it in your theme using components or template variables.

Shared Field Settings

All field types include the following settings:

• Default Value - The value shown when creating a new post or product.
• Required - Prevents saving if the field is empty.
• Instructions - Helper text shown to editors.
• Placeholder Text - Text displayed when the field has no value.
• Prepend - Text displayed before the input.
• Append - Text displayed after the input.

These settings ensure consistency across all field types and make the editing experience intuitive.

Field Types

Each field type is designed for a specific kind of data. The following list summarizes the purpose of each field type.

Accordion Field

Creates an accordion-style input for storing expandable/collapsible list items.
Useful for FAQs, feature lists, or structured content sections.

Checkbox Field

Stores a true/false value using a checkbox input.
Ideal for toggles such as “Featured”, “Published”, or “Show in menu”.

Color Field

Provides a color picker for selecting HEX/RGB values.
Useful for theme settings, UI customization, or product color attributes.

Date Field

Stores a date value using a calendar picker.
Commonly used for events, schedules, or publication dates.

Date Time Field

Stores both date and time.
Useful for appointments, event start times, or timed promotions.

Email Field

Validates and stores email addresses.
Useful for contact information or form submissions.

File Field

Allows uploading files that can be downloaded on the website.
Useful for PDFs, documents, or downloadable resources.

Gallery Field

Stores multiple images as a gallery.
Ideal for product galleries, portfolios, or image collections.

Google Map Field

Stores map coordinates or addresses using a Google Maps input.
Useful for locations, stores, or event venues.

Image Field

Stores a single image.
Used for featured images, banners, or thumbnails.

Link Field

Stores a URL or internal link.
Useful for buttons, CTAs, or external references.

Message Field

Displays a static message in the editor (info, warning, instructions).
Does not store data.

Month Field

Stores a month value (YYYY‑MM).
Useful for archives, billing cycles, or monthly scheduling.

Number Field

Stores numeric values.
Useful for quantities, prices, ratings, or measurements.

Oembed Field

Accepts media URLs and automatically embeds them (YouTube, Twitter, etc.).
Ideal for rich media content.

Password Field

Stores password values (masked input).
Useful for protected content or integrations.

Post Field

Autocomplete selector for choosing a post.
Useful for related posts, featured posts, or linking content.

Product Field

Autocomplete selector for choosing a product.
Useful for cross‑selling, related products, or product references.

Radio Field

Displays a list of radio buttons for selecting one value.
Useful for predefined options such as sizes, types, or modes.

Range Field

Creates a slider for selecting a numeric value within a range.
Useful for ratings, filters, or adjustable settings.

Select Field

The Select field displays a dropdown list of predefined options, allowing the user to choose a single value. It is ideal for categories, types, modes, or any controlled vocabulary.

Tab Field

The Tab field stores tabbed content, enabling editors to organize information into multiple labeled sections. This is useful for product specifications, multi-section content blocks, or structured layouts.

Taxonomy Field

The Taxonomy field links a post to a taxonomy item, such as a category, tag, or custom taxonomy. It is essential for organizing content and enabling taxonomy-based filtering.

Telephone Field

The Telephone field stores phone numbers using a tel input. It is suitable for contact information, business listings, or user profiles.

Text Field

The Text field provides a simple single-line input for short strings. It supports an optional character limit and is one of the most commonly used field types.

Textarea Field

The Textarea field stores multi-line text, making it ideal for descriptions, notes, summaries, or any longer content that does not require rich formatting.

Time Field

The Time field stores time values using a time picker. It is useful for schedules, opening hours, or event times.

Toggle Field

The Toggle field stores true/false values using a switch-style UI. It is a more visual alternative to the Checkbox field and works well for enabling or disabling features.

URL Field

The URL field stores website addresses and validates them as URLs. It is useful for external links, social profiles, or reference resources.

User Field

The User field allows selecting a user from the system, storing a relationship between the post and a user account. It is useful for authorship, ownership, or assigning responsibility.

Week Field

The Week field stores week values (year + week number). It is useful for scheduling, weekly reports, or time-based categorization.

WYSIWYG Field

The WYSIWYG field provides a full rich-text editor, identical to the editor used for posts and products. It supports formatted text, images, embeds, and multimedia.
This field is ideal for long-form content, flexible layouts, and any scenario where editors need full control over formatting.

A combined reference table helps compare all Vvveb CMS custom field types at a glance and clarifies when each one is most appropriate. The table below summarizes every available field type, including its purpose and ideal use cases.

Custom Fields Reference Table

Using Custom Fields in Themes

Custom field values can be displayed in templates using components or Vtpl selectors. For example:

<span data-v-post-custom_field_slug></span>

Or inside a component:

<div data-v-product-custom_field_slug></div>

This makes it easy to integrate custom data into any theme layout.

Custom Fields are one of the most powerful ways to tailor Vvveb CMS to different content models. They allow you to build flexible, structured, and editor‑friendly content types without writing custom code.

Deleting a group moves its members back to the default group; the default group itself cannot be deleted.