Vexal Documentation by WileyLabs

Comm Dock Module

Module

Current version: 1.1.003

Updated:

Comm Dock is the Vexal communication / popup dock Module. It is the canonical successor to legacy popup packages.

Purpose

Present communication dock and popup display modes on WordPress frontends without taking over the theme.

Requirements

  • WordPress site with administrator access
  • WordPress plugin package vexal-comm-dock

Installation

Install and activate the Comm Dock WordPress plugin package via the Plugins screen (or WileyLabs update channel).

Configuration

Configure dock/campaign options in the module’s admin screens after activation.

User roles

Administrators configure the module; visitors experience frontend shortcodes.

Data owned

Module settings and migration state (vexal_comm_dock_migration_version). No dedicated Hub Workspace cards yet.

Frontend entry points

Shortcode [vexal_comm_dock] and documented aliases (legacy popup aliases may exist for migration).

Hub / Workspace

Not registered with Hub Module Manifest yet. Future registry key may use communication-dock.

Health checks

Admin diagnostics for migration/schema; shared Hub health contract not yet implemented for this module.

Dependencies

Optional soft integration with Intake shortcodes. No hard WordPress plugin dependency.

Upgrade behavior

Migrator advances vexal_comm_dock_migration_version toward target 2.

Uninstall policy

No dedicated uninstall.php in current packages—data is generally preserved when the WordPress package is removed. Confirm on a disposable site before production deletes.

Security model

Admin mutations require capability checks; keep shortcodes theme-agnostic and namespaced.

Troubleshooting

  • Confirm the package is active on the Plugins screen.
  • Verify the shortcode page is published and not cached stale.
  • Prefer Comm Dock over deprecated vexal-popup compatibility packages.

Changelog

See the module’s WordPress package readme / release notes for version history.

See also