=== Sitetrail Studio Bridge ===
Contributors: sitetrail
Requires at least: 6.2
Tested up to: 7.1.4
Requires PHP: 7.4
Stable tag: 1.2.5
License: GPL-2.0-or-later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Two separate Google Workspace Studio connectors: WordPress content and WooCommerce store actions.

== Description ==
One shared bridge for Studio Connector for WordPress and Studio Connector for WooCommerce by Sitetrail. Open the plugin to choose two large, separate modules. WordPress works without WooCommerce installed or active. Each connector has its own subscription, connection and permissions.
Plugin downloads and updates are free. Useful operation of the Google connector
cards requires a separate paid subscription tied to your verified Google account
and registered site. No customer licence key and no License-Manager dependency.

Your content and image files travel directly between Google's workflow runtime
and your WordPress site. Sitetrail's separate service handles identity, account
access, site-connection metadata and billing. The bridge verifies short-lived
signed action permissions locally and enforces the selected WordPress user's
current capabilities.

Use Prepare WordPress action -> native Send a webhook -> Read WordPress result.
Installing this bridge does not grant your organisation access to Google's
native webhook feature or override administrator approval policies.

== Installation ==
1. Upload the ZIP through Plugins -> Add Plugin -> Upload Plugin and activate.
2. Open Google Workspace Studio Connector directly in the WordPress sidebar,
   then choose Connect this site.
3. Confirm the site and Google account, then return to WordPress.
4. Open the connector dashboard, confirm Studio prerequisites and subscribe.
5. Follow the three-step mapping guide and explicitly run a draft test.

Setup: https://studio-connector-wp.sitetrail.com/
Guide: https://studio-connector-wp.sitetrail.com/help
Privacy: https://www.sitetrail.com/software/studio-connector-for-wordpress/privacy/
Support: support@sitetrail.com

== Actions and limits ==
Create posts/pages as draft (default), pending review or private; update title,
content, status or custom URL slug; read/list content, including scheduled items;
explicitly publish now or schedule publication with a timezone-aware date/time;
accessible-image import, media metadata, categories/tags and term assignment.
Publishing, scheduling and changes to published/scheduled content require the
Publication option (off by default) and the selected user's WordPress permissions.
Use the separate publication card: publish + PUBLISH, or future + SCHEDULE and
an ISO date/time with an explicit offset, such as 2027-01-10T09:00:00+02:00.
Choose a time over one minute ahead. WordPress WP-Cron runs the schedule;
hosting traffic or cron configuration can delay publication. Disabling bridge
publication access does not cancel schedules already accepted by WordPress.
Use a new update action with draft/pending/private status to cancel a schedule
while publication access is enabled, or manage it directly in WordPress.
Blank status on create means draft; omitted update fields remain unchanged.
WordPress normalises slugs and resolves collisions. Read the actual slug,
publication date (UTC), status and permalink from Read WordPress result.
Images: accessible HTTPS JPEG/PNG/WebP, 5 MB and 24 million pixels maximum.
Private Drive files, WooCommerce actions, custom post types, SEO fields and
WordPress event starters are outside the initial release.
There is no monthly Sitetrail operation allowance; platform/hosting and
protective request limits still apply.

== Updates ==
Use normal WordPress Update now or enable its optional per-plugin automatic
updates. Updates and downloads do not require an active subscription.
No setting forces automatic updates. Update checks use only the independent
public Sitetrail Studio Bridge feed.

== Recovery ==
After a webhook error, inspect WordPress and retry the whole flow with the same
reference and original inputs. Completed writes return their previous result.
An uncertain or partial write is held for inspection, never blindly repeated.
Disconnecting the site revokes access; it does not cancel the Stripe subscription.
Deactivation/uninstallation retains customer-created content and connection
settings; contact support for account/data removal.

== Changelog ==
= 1.2.5 =
Preserve existing legacy event starters on first bridge pairing, unless the owner
has explicitly chosen to disable events. Brand-new direct-only sites still default off.

= 1.2.4 =
Separate WordPress and WooCommerce modules with direct product, gallery and variation
image actions. Optional WooCommerce event starters default off for new connections;
existing paired stores retain their choice. Pausing events leaves direct actions,
WordPress and other integrations intact. Reconnecting safely refreshes event secrets.
Canonical signed inputs, saved image progress, native webhook correlation and
content-free diagnostics protect retries. WordPress features remain independent.

= 1.1.1 =
Distinct original Sitetrail monogram across bridge and app branding; features,
connections and publication controls are unchanged.

= 1.1.0 =
Adds draft/pending/private status controls, custom slugs, timezone-aware scheduled
publication and actual slug/publication-date results, with updated help.

= 1.0.3 =
Persist verified connections, connection checks and local revocation separately
from editable settings; confirm storage before reporting success.

= 1.0.2 =
Keep third-party notices outside the connector header and clarify content direction.

= 1.0.1 =
Standalone Google Workspace Studio Connector sidebar entry, original Sitetrail
interface, clear permissions and reliable server-rendered settings forms.

= 1.0.0 =
Initial direct-content bridge with pairing, capability checks, signed permissions,
retry protection and independent native updates.

WordPress is a trademark of the WordPress Foundation. Google Workspace is a
trademark of Google LLC. Independent software by Sitetrail; no endorsement.

== Separate WooCommerce connector ==
WooCommerce direct actions cost $9/month per store with explicitly authorised team access.
WordPress costs $9/month separately. Both are $18/month; plugin downloads/updates are free.
Direct WooCommerce actions have no Sitetrail monthly operation cap. Starters and legacy
backend actions retain the combined 10,000 monthly operation allowance. Protective
request/file/time limits and Google's and the host's limits still apply.

Use Prepare WooCommerce action -> native Send a webhook -> Read WooCommerce result.
Product content/results go directly between Google and the site; the site downloads
accessible images directly. Sitetrail checks account/payment/site and signed input
hashes. Existing Woo starter events and legacy actions still pass through Sitetrail.
Enable optional event starters in the WooCommerce permissions panel only when needed.
Those hooks send store event records even without a listening flow, including events
from direct actions. New connections default off; previously paired stores retain
events. Turning this off pauses only this connector's hooks; queued events may finish.

Create/update simple products, variable parents and variations, including featured,
ordered gallery and variation images. Images use accessible HTTPS URLs or local Media
Library IDs. Private Drive files/raw binary uploads are not included. Retry partial
image operations with the same reference and original inputs; inspect uncertain writes.

Woo setup/help: https://studio-connector-wc.sitetrail.com/bridge
Woo privacy: https://www.sitetrail.com/software/studio-connector-for-woocommerce/privacy/

== 1.2.3 ==
Content-free store diagnostics for native webhook failures.

== 1.2.1 ==
Large, independent WordPress and WooCommerce choices, clearer setup and responsive interface. WordPress works without WooCommerce installed. Separate connections, subscriptions and permissions.

== 1.2.0 ==
- Large, clearly separate WordPress and WooCommerce module choices.
- WordPress remains fully independent of WooCommerce's presence and activation.
- Separately authorised WooCommerce direct actions, typed results and image support.
- Canonical input-digest verification, operation checkpoints and revision correlation.
- Independent subscription and usage explanations; existing WordPress protocol retained.
