Installation

Before you start

VX Modules is an add-on. It needs VX Framework — Free or Pro — already installed and active. VX Pro is a separate plugin that replaces VX Free, so VX Modules checks for VX at runtime rather than pinning a plugin slug; either build satisfies it.

Requirement	Minimum
WordPress	6.9
PHP	8.1
VX Framework	1.0.0-beta.1, Free or Pro

Install the plugin

1. Download the plugin zip from your Code Wattz account.
2. In wp-admin, go to Plugins → Add New → Upload Plugin and choose the zip.
3. Install, then Activate.
4. A new VX Modules menu appears in the admin sidebar.

If VX Framework is missing or too old, VX Modules says so on the Plugins screen and stays out of the way until VX is there.

Turn on what you need

Open VX Modules → Modules. Every module is a switch with a short description and, where it has one, its requirement — Elementor, FluentCart, WooCommerce. Only Columns is on out of the box.

A module that is off is never booted: no hooks registered, no scripts enqueued, no abilities published. Leaving seven of the eight switched off costs nothing at runtime, so turn on only what the site uses.

Some modules add their own screen to the VX Modules submenu as soon as they are on:

Module	Screen it adds
Columns	Columns
Sheet	Sheet
Forms	Forms, Entries

One store at a time

FluentCart and WooCommerce publish the same dynamic tags and the same rule ids on purpose, so a site that moves between the two keeps its pages and rules working. The flip side is that only one of the two modules can run at a time.

From the command line

wp vxm modules list
wp vxm modules enable elementor
wp vxm modules disable elementor

The module keys are elementor, spreadsheet, columns, validation, forms, wpai, fluentcart, and woocommerce.

Updates

Updates arrive through your Code Wattz account license, the same as every other Code Wattz plugin. Keep VX Framework current too — VX Modules reaches VX classes through guards, but a module gated on a VX Pro feature needs that feature present to do anything.

Uninstalling

Deactivating leaves everything in place. Deleting the plugin removes its own vxm:* options — module states, form definitions, column layouts, validation rules, and settings. It never touches VX's fieldsets, your posts, or their field values; those belong to VX.

Form entries survive the plugin

Standalone form submissions are stored as a hidden post type. Deleting VX Modules removes the option rows that define the forms, but the entries themselves stay in the database until you delete them. Export them first if you want to keep them.

Next

• The admin screens — what each screen under the VX Modules menu does
• Importing from ACF, Meta Box, and Pods — if the site's fields live somewhere else today