=== Scene Relay ===
Contributors: scattersky
Tags: events, event calendar, calendar, music, directory
Requires at least: 6.7
Tested up to: 7.0
Requires PHP: 8.1
Stable tag: 1.4.4
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Build a polished community event directory with organizer-submitted events and artist, venue, and organizer profiles.

== Description ==

Scene Relay turns WordPress into a focused local events publication. It gives visitors a fast event calendar and public profiles, gives organizers a front-end workspace, and gives site owners a purpose-built moderation console.

= Included in Scene Relay Core =

* Editorial event homepage, searchable discovery, weekend view, artist directory, and venue directory.
* Public event details and artist, venue, and organizer profile pages.
* WordPress-native organizer registration and sign-in, profile management, event drafts, and event submissions.
* External ticket links with a validated redirect that keeps raw third-party URLs out of form actions.
* Review-safe moderation: edits to published listings remain staged until approved, so the public URL stays stable.
* Categories, genres, neighborhoods, audiences, venues, timezones, admission labels, featured images, and organizer/artist relationships.
* Basic identity, brand colors, hero copy, footer copy, sender identity, and policy settings.
* Read-only REST endpoints for public event and profile collections and details.
* WordPress privacy-tool integration, conservative uninstall behavior, demo data, and Multisite-aware installation.
* A documented, versioned extension contract for add-ons.

Scene Relay Core does not process ticket purchases or store payment-card details. An event can link to the organizer's existing ticket provider.

= Optional Scene Relay Pro add-on =

Scene Relay Pro is a separately installed add-on for operators who need memberships and usage limits, promotion inventory, advanced homepage modules, analytics, newsletters, CSV imports, galleries, artist video, venue maps, advanced white-label controls, payment integrations, optional WooCommerce-native event tickets, and protected commercial updates. Core remains fully usable without Pro, and both editions use the same established `scenre_` data model so enabling or disabling the add-on does not convert or delete content.

Pro's direct Stripe, PayPal, and Square modules are for organizer memberships and promoted placements sold by the site owner. A separate optional WooCommerce module in Pro 1.5.1 can provide native ticket inventory, checkout, passes, refunds, and check-in. In this release all ticket funds go to the site owner's WooCommerce gateways; there are no split payments or organizer payouts.

== Installation ==

1. Install and activate **Scene Relay**.
2. Choose a non-plain permalink structure under **Settings > Permalinks**.
3. Open **Scene Relay > Launch Center** and complete identity, page, policy, and publishing setup.
4. To offer organizer registration, enable **Anyone can register** under **Settings > General**, choose **Scene Member** as the new-user default role, and then enable the native registration link in Scene Relay.
5. Optionally load the idempotent showcase under **Scene Relay > Demo Content**.

To add Pro, keep Core active, upload Scene Relay Pro, activate it, and then use **Scene Relay > License** for protected Pro updates. Pro refuses to boot against a missing or incompatible Core version.

Activation creates marker-owned system pages. Scene Relay never adopts or overwrites an unrelated page merely because it uses a preferred slug. Existing `scenre_` content, options, metadata, roles, capabilities, tables, and page markers are preserved during upgrades.

== Frequently Asked Questions ==

= Does Core take payments? =

No. Core links an event to an organizer-supplied external ticket URL. It does not collect card details, hold ticket inventory, or settle funds.

= Can organizers submit their own events? =

Yes. Scene Relay hands account creation and sign-in to WordPress’s standard screens so security and registration plugins remain in control. Enable WordPress registration, choose Scene Member as the default role, and then show the registration link from Scene Relay. Site owners still control whether event and profile submissions publish directly or enter moderation.

= Will adding Pro replace or migrate my data? =

No. Pro registers against Core and extends the same `scenre_` storage contract. Activating or deactivating Pro does not delete or rewrite existing records.

= How do I upgrade from the earlier combined package? =

Back up the database and `wp-content`, then replace/update the existing `scene-relay` package in place with Core. Do not uninstall or delete it first. Once Core is active, install and activate Scene Relay Pro. Check public pages, plans, memberships, placements, and the Pro License screen before reopening the site.

= Do Pro payment gateways sell event tickets? =

The direct Stripe, PayPal, and Square modules do not; they collect the site owner's organizer-membership and promoted-placement fees. Pro 1.5.1 has a separate optional WooCommerce module for native ticket sales. Sites can keep external links only, use native tickets only, or offer both.

= Is WooCommerce required? =

No. Core always uses external ticket links and Pro defaults to that same mode. WooCommerce is needed only when the site owner explicitly enables Pro's native ticket option.

= Does Core contact a license server? =

No. Core has no commercial updater or license client. Licensing and vendor-delivered updates belong only to the separately installed Pro add-on.

= What happens when I deactivate the plugin? =

Deactivation preserves data. Uninstall also preserves data unless the site owner explicitly enables the delete-data setting first.

== Screenshots ==

1. Publish a branded local-events homepage with featured discovery and a focused search handoff.
2. Help visitors browse upcoming events with practical date, category, genre, and neighborhood filters.
3. Present complete event details with venue, organizer, admission, and external ticket information.
4. Give artists, venues, and organizers polished public profiles connected to their upcoming events.
5. Let organizers see their listings, public identities, and review status in a dedicated front-end workspace.
6. Guide organizers through a structured event editor with a live preview and clear publishing steps.
== Changelog ==

= 1.4.4 =

* Replaced the short internal prefix with the WordPress.org-compliant `scenre_` prefix and added an idempotent legacy-data migration.
* Replaced authentication-salt reuse with a private, non-autoloaded Scene Relay email-hash key.
* Removed custom public user creation and credential handling in favor of WordPress-native registration and sign-in.
* Audited every Core mutation handler for nonce, capability, and ownership enforcement.

= 1.4.3 =

* Released 2026-07-26.
* Added the extension hooks and Core/Pro boundary required by Scene Relay Pro 1.5.0's optional WooCommerce ticket module.
* Kept Core ticketing external-only and free of WooCommerce, payment-gateway, native-ticket, and payout dependencies.

= 1.4.2 =

* Released 2026-07-23.
* Changed public, organizer, and operator button labels from all caps to Title Case.

= 1.4.1 =

* Released 2026-07-21.
* Restored the intended hero content overlay and compact Core search layout.
* Added the complete responsive presentation for Core-only operator and organizer workspace screens.

= 1.4.0 =

* Completed the independently operable Core boundary for the separately installed Pro add-on.
* Added the shared capabilities and lifecycle cleanup contract required by Pro's customer-site payment module.
* Kept Core free of licensing, protected-update, gateway-credential, checkout, and vendor-server payment code.

= 1.3.0 =

* Established the independent WordPress.org-safe Core package and versioned extension API.
* Preserved the original `lsc_` storage contract during the Core/Pro package split.
* Kept public discovery, organizer submissions, moderation, basic branding, REST, privacy, and demo capabilities in Core.
* Moved commercial licensing, memberships, promotion, advanced presentation, analytics, newsletters, imports, and rich profile media to Scene Relay Pro.

== Upgrade Notice ==

= 1.4.4 =

Security and WordPress.org compliance update. Existing Scene Relay data is migrated in place; account creation and sign-in now use WordPress’s standard screens.

= 1.4.3 =

Required by Scene Relay Pro 1.5.0. Core remains external-ticket-only; WooCommerce is optional and belongs to the separately installed Pro add-on.

= 1.4.2 =

Polishes button capitalization across the public site, organizer workspace, and operator console.

= 1.4.1 =

Restores the intended public homepage hero, Core-only admin presentation, and organizer workspace layouts. Scene Relay Pro 1.4.0 remains compatible.

= 1.4.0 =

This Core release is required by Scene Relay Pro 1.4.0. Existing content and settings are retained; update Core before activating the matching Pro build.

= 1.3.0 =

The package split was non-destructive. The 1.4.4 upgrade migrates those legacy `lsc_` records to the current `scenre_` contract in place.
