# Prajesh Content Grid Pro — User Guide

Status: preparing for public launch. Public sales are not open yet.

## Requirements and installation

Use single-site WordPress 6.5 or later, PHP 8.2 or later, and Prajesh Content Grid Free 0.1.2 or later. Keep Free active: Pro is a separate companion, not a replacement. Back up the site and test integrations on staging. InnoDB posts, postmeta and options tables are required for reviewed writes.

Once public sales open, obtain the paid ZIP and license through the purchase confirmation or Freemius customer account. In WordPress open Plugins → Add New Plugin → Upload Plugin, select the paid ZIP, install and activate it. Enter the license in the Freemius activation screen. Never share a license key publicly. Open Tools → Content Grid.

Existing Free users: update Free first, then add Pro. Keep both plugins active. Existing posts, fields and Free history do not require migration. Do not install two copies of the Pro companion. For paid updates, use the WordPress updater when offered; take a backup before updating.

## Named saved views

Choose the content type, search, status and columns in Content Grid. Save the configuration with a meaningful name and reopen it when needed. A view saves those choices, not content edits or record snapshots. Views belong to the signed-in editor and are not shared with other users. Unsaved staged changes must still be reviewed before closing the tab. Deleting the Pro plugin removes its saved views; deactivation preserves them.

## Supported ACF editing

ACF is optional; it is required only for ACF editing. The basic ACF plugin is sufficient for supported text, number and single-select fields. Only existing values with valid ACF field references are editable. Field groups must be assigned using post-type-only location rules. Enable Show in REST API on eligible groups where required by your ACF version. This may expose those group fields through WordPress REST; review the group's permissions and contents before enabling it.

Use the normal post editor to create initial values if a field reference is missing. Reload Content Grid, select the eligible columns, stage changes and inspect the review. Number bounds, select choices and WordPress field permissions apply. Changes use ACF's save API. Repeaters, flexible content, arrays, multi-select, complex or conditional field groups and arbitrary metaboxes are excluded. The native ACF editing path is limited to administrators; explicit registered metadata permissions still apply. Pro does not bypass permissions or make every ACF field editable.

## Teammate approval

Before preparing a batch, open Teammate approval and enter a different eligible editor's WordPress user ID as reviewer. Stage the changes and prepare the review. Share its batch reference through your normal team channel. The reviewer signs in with their own account, opens Tools → Content Grid → Teammate approval, loads the reference, inspects the changes and approves them. The author then reopens the batch in Change history and applies it.

Approval does not apply edits automatically. The author cannot approve their own batch. Both users still need the appropriate permissions. Pending reviews expire for apply after 15 minutes; prepare a new review when expired. Later edits, changed permissions or an active editor lock may still block apply after approval. Approval is optional and does not replace your organization's publishing process. The plugin does not publish, schedule or change post status.

## Review, apply and undo

Preparing a review does not change post values. Inspect before/after values before applying. Changes to a published record become visible when applied. Check each row's result. Undo is available only while the retained batch and record state permit it; it skips records changed subsequently. Ten recent batches per editor are retained for seven days. Undo cannot reverse external actions performed by third-party save hooks and is not a backup.

## Licensing, expiry and site limits

Planned annual USD prices are $45 for one production site or $109 for five production sites. Each plan includes the same Pro features; site allowance differs. Taxes, renewal terms and the final payable total will be shown at checkout when sales open. No lifetime or monthly plan is currently planned.

Freemius manages license activation, purchase delivery and paid updates. Activation sends essential account, site and license information to Freemius. Review its privacy notice before connecting. The Free plugin works without this service. A license is needed to activate Pro. Current plans retain Pro features on expiry while renewal is required for continued paid downloads, updates and support. Cancelling automatic renewal and reaching the license expiry date are different events. Do not expect cancellation to uninstall the plugin or remove saved content.

Free localhost activations are enabled in the plan. Production activations count against the purchased allowance. To move a license, deactivate it on the old installation through its license/account controls before activating on the new one. Contact support if an inaccessible old site occupies a seat. Keep a backup before moving sites.

## Troubleshooting and support

If activation fails, confirm the license belongs to this product, is current, and has an available activation. Check HTTPS connectivity to Freemius. Do not disable SSL verification. If the plugin appears twice, identify the paid companion before removing an inactive duplicate; do not delete the active Free dependency.

If an ACF column is missing, check the supported field type, post-type-only location rules, REST setting, saved ACF reference and user permissions. If a batch expires or conflicts, reload current data and prepare a new review.

Contact prajeshganatra@gmail.com for Pro help. Include WordPress/PHP/plugin versions, steps to reproduce and the non-sensitive error message. Never send passwords or full license keys in public support threads. Refund requests must be made within 14 days of purchase and explain the issue. The Moderate Satisfaction Guarantee covers missing features, unexpected behaviour and technical problems, including plugin or theme conflicts. We may try to resolve the issue first; if we cannot resolve it satisfactorily, we will process a full refund. Change of mind without a reasonable explanation is not covered.

## Launch notice

The public Customer Portal Downloads flow is still being investigated. Do not treat this guide as confirmation that public checkout or customer delivery is open. Public launch will be announced after the remaining sales and delivery checks are complete.
