What's new with ClientPress

• Added vertical (left sidebar) navigation layout as an option under Settings → Appearance, set as the new default.
• Added “Complete” as a portal status option alongside Active, Pending, and Archived.
• Updated default tab icons: Dashboard now uses the Layout icon, Tasks uses Checkbox, and Message Board uses List.
• Fixed calendar width setting being ignored — the calendar view now correctly respects the Full Width and Narrow options.
• Various small UI improvements to the portal navigation and settings screens.

• Hubs are now fully functional sub-portals with their own independent files, discussion, tasks, deliverables, board, and tools.
• Added Portal Files admin screen to browse and download all portal files from the WP dashboard.
• Added per-deliverable approval toggle — deliverables can skip the client approval workflow.
• Fixed file and deliverable download 404s caused by missing rewrite rules in the database.
• Fixed portal editor sidebar overflow in the Gutenberg block editor.
• Fixed deliverable upload zone drag-and-drop not working. Fixed portal SVG icons being overridden by theme styles.
• Added image attachments to message board topics and replies. Fixed multiple file uploads only uploading one file at a time.

Added a Multisite check in the activate() method that deactivates the plugin and displays an error message if WordPress Multisite is detected

Renames the changelog_product REST API field to changelog_resolved_product to prevent conflicts with the native WordPress taxonomy field that’s automatically exposed in the REST response.

Problem

The plugin registers a changelog_product taxonomy with show_in_rest => true, which causes WordPress to automatically expose a changelog_product property on post responses containing an array of assigned term IDs. The custom REST field with the same name was overwriting this array with a read-only product object, causing the block editor’s taxonomy selector to crash once a term was assigned.

Changes

• REST API field registration: Renamed the custom field from changelog_product to changelog_resolved_product in includes/class-rest-api.php
• Documentation updates: Updated all references in REST-API.md and HOOKS.md to reflect the new field name
• Version bump: Updated plugin version from 1.0.1 to 1.0.2

Implementation Details

The field remains read-only and continues to return the same product object structure { id, name, slug }. The new namespaced name prevents the collision while maintaining backward compatibility for the native taxonomy field that the block editor depends on.

ClientPress 1.0.0 is the initial public release. This version includes the complete portal system — private per-client portal URLs, primary and sub-client assignment, block editor overview tab, child portals, and post-login redirect — alongside a full task manager with templates and calendar view, private file storage with an authenticated delivery endpoint, a file approval workflow, deliverable approvals with revision tracking, 1-on-1 discussion, a threaded message board, tools and links, category-based guides, portal templates, and a complete notification system with magic login links.

Automation and integration are built in from day one. Outbound webhooks cover 13 portal events with HMAC-SHA256 signature verification. The inbound webhook endpoint supports four actions — create portal, send invite, assign user, and update portal — with per-integration API keys compatible with Zapier, Make, OttoKit, and SureCart. A full read/write REST API is included alongside a complete implementation of the WordPress 7.0 Abilities API, making ClientPress discoverable and executable by AI agents, browser extensions, and the WordPress command palette. Every plan includes all features — the only difference between Personal, Freelancer, and Agency is the number of WordPress site licenses.