=== ClientEdits ===
Contributors: pluginsshop
Tags: client feedback, content review, editorial workflow, content approval
Requires at least: 6.7
Tested up to: 7.1
Stable tag: 2.0.12
Requires PHP: 7.4
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Clients suggest wording through a private link. Review and approve supported edits in WordPress, with conflict checks and Undo.

== Description ==

Send a client a private link to the pages you want reviewed. They can select a passage, propose replacement wording and send it without a WordPress account. In your decision inbox, compare the original with the proposal. Approve to update a supported passage, ask a question, decline it or leave a comment for the editor. All features are free.

* Review a published page or invite a client to see a saved draft in your site's theme. Reviewers can switch to readable text or choose a passage from a list.
* Review ordinary Gutenberg paragraphs, headings, flat lists, buttons and supported Classic text. Selected menu labels, widget text, ACF text fields, WooCommerce variation descriptions and verified builder controls also support direct edits.
* Keep proposals, replies and attachments together. Reviewers can amend pending proposals, mark pages complete and finish a review pass. Editors can export HTML, JSON or CSV.
* Approve one proposal at a time or select specific versions for a bulk decision. ClientEdits checks the saved wording before writing. Undo is available while the relevant saved content still matches the approved change.
* Choose manual publishing or authorize publication of unchanged drafts when a new review reaches its required number of sign-offs. The review shows the outcome for each draft.

= Which builder fields can I approve? =

Verified controls include the classic Heading title in Elementor Free 4.4.1, Heading text in Beaver Builder Lite 2.11.2.2, the plain Heading field in Breakdance 3.0.2 and the plain Text field in Oxygen 6.2.2. Other versions and field shapes default to comments. The bundled reference.txt describes the verified fields, validation rules and adapter settings.

== Installation ==

1. Open Plugins > Add Plugin > Upload Plugin. Select the ClientEdits ZIP, install it and activate it. When upgrading a separately supplied ZIP, choose the option to replace the existing plugin.
2. Open ClientEdits in the WordPress dashboard, or choose Start client review beside an eligible page or post. Select the pages, create the review and copy the invitation link.
3. Open the decision inbox after the reviewer sends feedback. Each proposal shows whether approval can update the page or whether an editor needs to act on the comment.

== Frequently Asked Questions ==

= Who can read a private review? =

Anyone holding an active invitation can review its selected content until the link expires, is revoked or the review closes. A reviewer chooses their display name. For an eligible draft, ClientEdits opens a private theme preview inside the review. Its short-lived address requires the same review cookie. Password-protected, private, pending and scheduled pages use readable text.

= Can signing off publish a draft? =

Publishing is manual by default, including for reviews created before 2.0.9. When creating a review, an owner who can edit and publish the selected drafts can turn on “Publish drafts when reviewers sign off” and choose the number of reviewer invitations that must sign off. Give each reviewer a separate invitation. Multiple people sharing one invitation count as one sign-off.

ClientEdits compares each draft with the version saved when the review was created. A change to its wording, saved fields or assigned terms can make it ineligible, including a suggestion the owner approved during review. In that case, publish manually or open a new review for the revised draft. After an automatic publication, an authorized owner can open the review and choose “Move back to draft” while the published version still matches.

= What happens if someone edits the page first? =

ClientEdits checks the proposal version and saved content. A conflict asks the owner to compare the current wording. On supported content, approving one passage preserves its supported formatting and links. Resolving a comment leaves the page content as it was.

= What if the page preview cannot take clicks? =

Choose Readable text or select a passage from the list. The readable view opens first on browsers that suppress interaction inside the preview. If the draft template fails to render, you can still suggest changes from the saved text. Draft previews load styles, images and fonts from the site itself and disable scripts, forms and external embeds. Public previews can also load theme assets from other hosts.

= Where do attachments and review data live? =

Review records live in your WordPress database. New reviewer files use a private directory outside the public web root. Downloads require an authorized owner or the matching active review invitation. If your host needs a custom location, set CLIENTEDITS_PRIVATE_DIR to an absolute path outside publicly served directories. If upgrading from a version with public reviewer attachments, use the migration notice to move review-only files or keep intentionally public WordPress media. See reference.txt for retention, erasure, prior public URLs and migration details.

= Will uninstalling remove approved changes? =

Approved wording is saved as ordinary site content. Review records are kept by default. Administrators can opt to remove those records on uninstall in ClientEdits > Settings.

== External services ==

Reviewing and applying wording works on your WordPress site without a service account. Notifications are optional and start only when configured.

* Slack. If an administrator enters an incoming webhook URL, releasing a publishing hold queues a message containing the event name and site address. Each delivery has a random delivery ID. Suggested wording, attachments and reviewer email addresses are excluded. See [Slack incoming webhooks](https://docs.slack.dev/messaging/sending-messages-using-incoming-webhooks/), [Slack terms](https://slack.com/main-services-agreement) and [Slack privacy policy](https://slack.com/trust/privacy/privacy-policy).
* Generic HTTPS webhook. If an administrator enters a destination URL, the same event sends that endpoint the event name, site address, timestamp and review ID, with a delivery ID and optional signature. The administrator selects the recipient and its applicable terms and privacy policy. WordPress validates the destination. Private addresses and nonstandard ports can be refused. Retries use WordPress Cron. Changes to the configured URL cancel outstanding deliveries to its former address.
* Email. Reviewer email verification, reply alerts, owner notifications and the optional digest use the site's WordPress mail configuration. An administrator can also send a test email. Email delivery depends on the site's configured mail provider. Alerts exclude proposed wording.

== Screenshots ==

1. A reviewer selects wording from a page and proposes a replacement.
2. The owner's decision inbox shows the saved passage and the proposed wording before approval.

== Changelog ==

= 2.0.12 =
* Count each reviewer API operation once toward its invitation limit when WordPress checks permissions more than once.
* Check only the relevant pages when loading reviewer feedback or saving a reply. Batch the history and attachment reads on busy reviews.
* Reserve owner feedback alerts before calling the mail transport so one slow send does not block alerts from other reviews.
* Wait for a pending history refresh and pause background polling when the reviewer tab is hidden.

= 2.0.11 =
* Speed up review and suggestion dashboards, review exports, and sign-off checks on large sites.
* Open long conversations in windows of 50 replies and browse earlier replies on demand.
* Reduce the work needed to find legacy review media and check large Elementor drafts.

= 2.0.10 =
* Recheck which pages a guest invitation can access when showing feedback or accepting a change to it.
* Validate dashboard form inputs and require a POST request for actions that change review data.
* Count simultaneous reviewer requests against a single invitation limit and exclude expired invitations when checking a manual publishing hold.
* Process privacy and retention tasks in smaller batches. Preserve shared media sizes when migrating an attachment.

= 2.0.9 =
* Add optional publication of unchanged drafts after the required reviewer sign-offs. Recheck the owner's publishing permissions, active invitations, outstanding feedback and publishing holds before posting.
* Record the outcome for each draft. Owners can cancel the authorization or move an eligible published version back to draft from the review.

= 2.0.8 =
* Show the active theme for an invited draft and offer its saved wording when the theme cannot render the page.
* Check the review session and the signed preview address on every draft preview request. Publishing remains an owner action.

= 2.0.7 =
* Remove an unused AI integration and its stored settings.
* Validate webhook destinations through the WordPress safe HTTP API. Explain optional notifications on the settings screen and in the readme.
* Keep existing invitation links working and authenticate REST integrations with a header or an authenticated reviewer session. Update integrations that pass tokens in URLs.
* Improve translations, delivery-history queries and private file handling.
* Verify native builder requests before recording an editor session used to detect stale saves.
* See changelog.txt for earlier releases and upgrade notes.

== Upgrade Notice ==

= 2.0.12 =
This update improves the performance of concurrent reviewer and owner sessions.

= 2.0.11 =
This release improves performance on sites with large review histories and media libraries.

= 2.0.10 =
This update adds database fields for per-invitation request limits. Existing reviews and sign-off settings carry forward.

= 2.0.9 =
Existing reviews keep manual publishing. Choose publish on sign-off when creating a new review to authorize its saved drafts.

= 2.0.8 =
Reload an open draft review to see the new theme preview. You can still select Readable text at any time.

= 2.0.7 =
Existing invitation links still work. Send REST bearer tokens in X-ClientEdits-Review. Check any private-network webhook and reload open review tabs.
