DOCSEARCHbyAlgolia
Submit Docs

Verbb Craft Plugins

website·Indexed 33 days ago

https://verbb.io/craft-plugins/abandoned-cart/docs

Documentation and changelogs for a suite of Craft CMS plugins, including Back in Stock, Xero, Readability, Scheduler, Video Picker, Snipcart, Queue Monitor, Footnotes, Squeeze, Concierge, Element Index Defaults, Metrix, Single Cat, Button Box, AutoLogin, Calendar Links, and Cloner.

Tokens
1.2M
Snippets
5K
Records
9.6K
Agent score
64%

What's inside Verbb

  1. Overview of Events for Craft Commerce

    Events is a full-featured event management and ticketing system for Craft Commerce (compatible with Craft 3, 4, and 5). It allows developers to model events as Craft elements, enabling the use of familiar queries, permissions, custom fields, and authoring patterns. Key capabilities include selling tickets via Craft Commerce Lite or Pro, managing event types with unique templates/URLs, and importing event content using Feed Me workflows.

  2. Overview of Single Cat for Craft CMS

    Single Cat is a plugin for Craft CMS (compatible with versions 4 and 5) that replaces the standard element selector with a compact dropdown when a content model requires exactly one category. This ensures authors have a familiar, unambiguous control for single-value selection while keeping the relationship native to Craft. The selected value remains a standard Craft category element, meaning it retains its title, URL, custom fields, and supports standard Twig, GraphQL, and element-query behavior.

  3. Overview of Social Feeds for Craft CMS

    Social Feeds is a plugin for Craft CMS (compatible with versions 4 and 5) that allows developers to fetch selected content from supported social accounts and combine multiple sources into a single aggregated feed. The plugin features background caching to optimize performance by avoiding redundant API requests on every page view. Content can be presented on the front-end using Twig or GraphQL.

  4. Overview of Craft CMS Modules

    Modules are site-specific PHP containers consisting of models, views, controllers, and supporting components. They function as 'mini-applications' used to extend Craft project behavior. Unlike plugins, modules are not intended for redistribution and are tied directly to a specific project. They are technically based on Yii modules.

  5. Overview of Video Picker for Craft CMS

    Video Picker is a field type plugin for Craft CMS (compatible with Craft 4 and Craft 5) that allows content editors to select videos from external providers. It supports YouTube and Vimeo at launch and utilizes the Verbb Auth module to enable additional providers. Users can either paste a video URL directly into the field or use the Video Explorer to browse folders, channels, and feeds, or perform source-wide searches with built-in previews.

  6. Overview of supported OAuth providers in Consume v1

    v1
    Consume v1 supports over 80 pre-configured OAuth providers, including major services like Google, Facebook, GitHub, and Shopify. For providers not officially supported, users can utilize the Generic OAuth client or refer to the Custom Provider documentation to implement their own support.

  7. Introduction to Kint PHP Debugger

    v3
    Kint is an interactive debugger for PHP applications. Unlike some debugging tools, it can be run outside of devMode (though it is not recommended for public production environments). Key features include interactivity, keyboard shortcuts for expanding/collapsing objects, and the ability to separate content from methods.

  8. Overview of Default Dashboard for Craft CMS

    Default Dashboard is a plugin for Craft CMS (compatible with versions 4 and 5) that allows administrators to define a shared set of dashboard widgets. This ensures new users have useful shortcuts, guidance, and information immediately upon their first login, rather than starting with an empty dashboard. Key capabilities include:

    • Group-specific layouts: Assign different source dashboards to different user groups with a global fallback.
    • Personal layout control: Choose whether the shared dashboard serves as a one-time starting point or is continuously enforced after user changes.
    • Admin exclusions: Prevent the shared layout from affecting administrator accounts that require a different operational view.

  9. Overview of the Formie Submission Workflow

    v4
    The submission workflow is a pipeline of stages and tasks that handle a form submission. Developers can extend this pipeline by adding custom logic to specific stages or tasks to ensure code runs at the correct point in the request lifecycle (e.g., before saving or after validation).

  10. Overview of Formie Element integrations

    Formie provides Element integrations that allow you to automatically populate or create Craft CMS elements when a form is submitted. These integrations can be configured globally at the plugin level or customized on a per-form basis. Supported elements include:

    • Entries
    • Users
    • Commerce Products (Single Variant)
    • Events
    • Solspace Calendar Events

  11. Introduction to Prism Syntax Highlighter for Craft CMS

    v3
    Prism provides a specialized field type called "Prism Syntax Highlighter" for Craft CMS entries. This field allows developers to input code blocks with syntax highlighting for over 170 different programming languages. The code blocks are fully themeable, supporting 8 default themes and the ability to add custom themes via the settings area. It is compatible with Live Preview, Matrix fields, and Super Table.

  12. Overview of the Vizy Content API for embedded values

    v4

    Vizy blocks store custom fields inside a document rather than as independent Craft elements. The Content API allows developers to inspect or replace these embedded values (raw serialized data) without opening the editor or relying on the current field type. It can traverse Vizy documents inside Hyper links and vice versa if both plugins provide content adapters.

    Key Distinction: Use the Content API for source-data conversion, inspections, and focused repairs. Use standard Craft element saves when you need field normalization, validation, propagation, and save hooks. Raw API operations do not invoke editing behaviors or validate replacements; the developer is responsible for producing the correct serialized value.