MicroPayments – Fans Paysite: Paid Creator Subscriptions, Digital Assets, Wallet

By videowhisper

★ 4.2/5 (5 ratings)10+ active installationsVersion 4.29.1

Build your own fans paysite for one or many creators, with digital content sales, memberships and creator subscriptions.

Description

Build your own fans paysite with WordPress. MicroPayments – Fans Paysite provides the foundation for a complete creator-content business: sell videos, pictures, audio, documents and posts through individual purchases, site memberships and creator subscriptions. Create a dedicated home for one creator or a platform where multiple creators manage their own work and fans discover whom to support.

Designed for site owners, entrepreneurs and developers, the solution brings the main journeys together: creators publish and offer content, fans join and buy access, and administrators configure accounts, payments and moderation. Connect the optional Video Share VOD and Picture Gallery plugins for dedicated video and picture management; the included catalog, wallets and content workspaces also work independently.

A self-hosted site gives you control of your content, customer data, branding, editorial rules and monetization choices. You operate your own platform rather than depend on a creator platform’s revenue-sharing and editorial model. There is no mandatory VideoWhisper revenue share for using this plugin; hosting, payment processing and any commission you configure for your own site remain separate.

Key features and benefits

  • Bring your library together: present posts, videos, pictures, audio and documents in Styled tiles, Cards, List, Creator feed or Justified layouts, with search, filters and ordinary page navigation.
  • Choose how to sell access: offer creator subscription tiers, individual purchases or optional site memberships through WooCommerce. Fans can separately authorize continuation from the native token wallet, with clear price, duration and purchase terms.
  • Package related content: administrators can review fixed-price native-wallet bundles with a frozen item list, timed or lifetime access and clear terms for buyers who already own some items.
  • Give creators a working studio: manage their own content, drafts, prices, subscription offers and announcements from dedicated frontend workspaces.
  • Help fans find their way back: optional creator profiles, approved local avatars, free following and a private Following feed connect discovery with returning visits. Bookmarks and playback memory are separate opt-ins.
  • Start solo or grow a community: review Single creator or Multiple creators setup choices before applying them. Keep existing pages, roles, wallets and access settings.
  • Welcome each role clearly: optional dedicated fan signup, creator applications, login and password recovery work with native WordPress accounts. Leave them off when another system manages accounts.
  • Keep publishing under your control: review creator content, allow selected trusted roles or grant revocable future-publishing approval to a creator. New member content can optionally open on a calendar date or after elapsed days from its own current membership payment.
  • Make previews useful: show approved promotional images, independent public audio/video samples, duration and current offers. Add stars, likes or both with Rate Star Review.

Try the interactive content demo | Documentation and shortcodes | WordPress.org support

Popular ways to use MicroPayments

  • A single creator’s library: combine public previews, creator membership offers and individual video, picture or document purchases.
  • A multi-creator community: give creators their own profiles and studios while fans browse one mixed-media catalog or follow favorite creators.
  • A members’ resource library: sell one-time access to explicitly selected resources, with clear duration, purchase terms and private membership history.
  • An audio and download collection: present format, verified duration and file size, with separately approved click-to-play samples and optional access-checked full audio.

From first setup to returning fans

  1. Choose your creator model. Open Creator setup, review the preview and select the pages and presentation your site needs.
  2. Prepare a small library. Add native posts/downloads, or connect Video Share VOD and Picture Gallery for dedicated media management. The optional Media Capture plugin adds uploads, video/audio recording, webcam photos and screenshots.
  3. Review the offer and audience. Configure the native price or membership rules, purchase terms and publishing approval. Use the destination editor to confirm the final item.
  4. Publish and test as a fan. Check approved previews, discovery, the configured checkout and access with a separate permitted account. Fans can then return through their own purchases, membership history or Following feed.

Native catalog block and reviewed draft releases

In the WordPress editor, insert Fans paysite catalog and choose layout, content type, creator, category and visitor controls in the block sidebar. Its preview uses the existing published catalog; open the page to test filters as a separate fan. Existing [videowhisper_content_list] shortcodes continue to work. Blocks never select private buyer or creator workspaces.

Administrators can use MicroPayments > Draft release calendar to preview calendar or paid-start rules for up to 20 eligible new drafts. Assign site plans first and confirm the exact rows; changed content, permissions or terms require another review. This saves member-access rules, not WordPress publication dates. Publish or submit separately through the native editor. The batch adapter requires core wpdb, InnoDB content tables and no persistent object-cache drop-in; individual editors remain available on other setups.

Memberships, wallets and checkout

The included wallet, catalog and content workspaces work independently. Configure creator tiers with labels, descriptions, prices and durations; an item can also have its own purchase price. Donations, goals and supported credit-package workflows are available alongside content access.

Optional WooCommerce integration adds product checkout and one-time fixed-term site memberships. Each purchase retains its own payment start and expiry; overlapping purchases do not stack unused time or enroll a fan in renewals. A separate opt-in native-wallet offer can continue an existing paid site plan after the fan reviews and authorizes its fixed token price and term. Current paid status, ownership, refunds and expiry control access. Existing wallet, role and creator-subscription rules remain separate. WooCommerce sales do not automatically credit a creator’s token wallet.

For new member content, optional calendar or elapsed-day availability affects only the site-membership route. It does not schedule WordPress publication, approve content or extend a purchase’s expiry. Existing content is not migrated. Review and explicitly save member access before publishing; after publication, release rules can move earlier or be disabled, but cannot become more restrictive. Detailed setup and access cases are in the FAQ.

Brief purchase wording, expandable details and a selectable complete-terms page help buyers understand an offer. Native WooCommerce checkout acceptance remains authoritative. Available gateways, supported countries, fees and merchant eligibility depend on the selected extensions and provider. Qualify your site’s checkout before opening sales.

Optional wallet continuation

Yes, optionally. Open MicroPayments > Wallet renewals as an administrator, enable the service, choose an active site plan and native token price, then preview and apply the exact settings. Fans with a current paid site-plan term open their membership history, review the offer and explicitly authorize future funding. Enabling takes no payment immediately. Fans can stop future funding without losing already paid terms or independent purchases. This continuation option uses the native MicroPayments primary wallet; initial site-plan checkout remains WooCommerce. It does not require WooCommerce Subscriptions and does not charge a card automatically.

Existing completed WooCommerce token-package purchases can fund the native wallet. At the paid-through date, a confirmed wallet debit creates one new fixed term. Insufficient balance creates no access or overdraft; enabled funding can retry after funds arrive. A late payment starts one new term then, with no arrears or stacking. Newer independent paid terms defer the charge. Price, duration, label or wallet-unit changes require fresh review. Each paid term keeps its own elapsed-day content-release clock; continuous or cumulative tenure is not included.

Low-funds warnings and reminders

Wallet renewal settings include separate on-page warning and email toggles, a lead of 0–30 days (default 7), public funding/account pages and plain-text warning, subject and message templates. Allowlisted placeholders show the plan, due date, price, balance, shortfall and links. Email requires the fan’s separate opt-in; the fan can change this preference without stopping wallet funding. One reminder is handed to WordPress mail per due cycle, with bounded retries for known failures; acceptance does not prove delivery. Warnings use the balance when checked and do not reserve funds. Use the existing token-package funding page and reliable server cron in production; visit-driven WP-Cron cannot guarantee timing.

Wallet renewal operation and retention

The first wallet adapter requires the native MicroPayments primary wallet, core wpdb, InnoDB users/usermeta/options/native ledger tables and no persistent object-cache drop-in. It refuses an unsupported configuration without changing paid access. The debit, native ledger and signed paid term commit together. Interrupted or uncertain attempts stop for administrator review without automatic recharging. Inspect native transactions before reconciliation; do not delete consent records to retry. Deactivation pauses future funding and retains paid history; review settings to resume. Back up the database, including its private wallet signing option. Keep account pages outside full-page caching.

Reviewed wallet credits with access retained

Native administrators can separately enable Renewal health > Wallet credits, select a current saved proposal, preview a partial or full credit and explicitly confirm it. Cumulative limits and retained uncertain attempts protect the original debit’s budget. Credit adds wallet units; original paid dates, access, consent, purchases, approvals and files remain. It is not a card/bank refund. Execution starts off and needs a site-reviewed retention notice, compatible InnoDB storage and request-local caching. See the wallet-credit FAQ for qualification and failure handling.

Creator profiles and content presentation

Choose eligible public-profile roles separately from publishing permissions. Opted-in profiles can show an introduction, biography, creative focus, website, approved promotional cover/avatar, collections, native content and current offers. Initials remain the default avatar. Following is free and grants neither paid access nor an email subscription.

Separate buyer views explain recorded purchases, completed WooCommerce orders and supported content currently included with creator subscriptions. Private membership status shows verified current order or wallet terms first, with original order history and future wallet funding kept separate. The optional FansPaysite theme supports live light/dark/system presentation; other compatible themes remain usable.

Public previews use separately approved promotional media. Full content keeps its native audience, approval, channel, purchase and delivery checks. A hidden page does not make an ordinary public file URL private; configure protected delivery at the storage origin when needed.

Reviewed editorial suggestions

Use Agent assistance to preview a clearer title and excerpt. With Site Manager 1.27.0 or later and the separately enabled content review/write tools, choose Create private WordPress review, open its before/after comparison and approve the exact fields there. The proposal expires after ten minutes and does not itself update content. Changed items and revoked permissions require a fresh review. Read-only agent advice never grants saving or publishing authority; each plugin remains usable without Site Manager. SEO uses the active provider and its separate Site Manager review workflow.

Optional integrations

  • Video Share VOD and Picture Gallery: dedicated video and picture management, including explicit site-membership adapters.
  • Media Capture: a shared upload/record/review workflow. Each destination keeps its own permissions and originals.
  • WooCommerce: optional product checkout, one-time memberships, credit-package products and completed-order history.
  • TeraWallet and myCRED: optional wallet/points integrations with their own configuration and applicable extensions.
  • Rate Star Review: optional stars, likes and rating-based sorting.
  • Broadcast Live Video and Paid Videochat: optional live-content integrations with their own streaming requirements. BuddyPress/BuddyBoss and PeepSo integrations remain optional.

External services and privacy

Google reCAPTCHA is optional and is configured with the site’s reCAPTCHA keys for the guest content-upload form. When enabled and that form is rendered, the visitor’s browser loads Google’s reCAPTCHA JavaScript from https://www.google.com/recaptcha/api.js . Google receives the browser connection information, including IP address, and processes browser/device and interaction information under its policies to assess abuse. When the visitor submits the form, this plugin sends the generated response token and the site’s verification secret to Google’s verification service at https://www.google.com/recaptcha/api/siteverify . The upload’s content file, title, description and email fields are not included in that verification request. With no reCAPTCHA site key configured, the guest form does not load this Google integration.

Service information: https://developers.google.com/recaptcha/ . Privacy policy: https://policies.google.com/privacy . Terms: https://policies.google.com/terms . Site owners should explain this optional service in their own privacy/consent notices before enabling it.

Frontend account forms have their own disabled-by-default reCAPTCHA switch and keys under Accounts and creators. When enabled, the visitor explicitly checks the Google verification notice and submits before this integration loads Google. Verification sends the response token and server-held secret to the same fixed service; account passwords, email fields and profile text are not included in that verification request. The browser still sends connection and interaction information to Google. Configure keys for the site’s hostname and review current Google service terms/limits. The plugin does not create a Google account automatically.

Frontend forms use an essential, short-lived HttpOnly guest-session cookie to bind security nonces; native WordPress cookies maintain authenticated sessions. Temporary request limits use site-salted hashes and expire after fifteen minutes rather than storing raw addresses in plugin records. Creator applications retain a minimal current status/request/review timestamp. Public profile fields and private follows are scoped to the current WordPress site. Native privacy export/erasure includes these profile, application and follow records; erasure removes that presentation/community data without deleting original media, accounts, native roles, purchases, subscriptions or wallets. Deactivation retains data. WordPress controls password storage, account deletion and shared network users.

Optional payment/wallet extensions communicate with the processors the administrator configures when their checkout, funding or billing features are used. Those extensions control the payment-data requests; review their documentation and privacy/terms for the actual provider. Optional wallet renewals store site-scoped signed consent, payment terms, reminder receipts and native ledger references. Reminder email uses WordPress mail only when the administrator enables it and the fan opts in. Personal-data erasure stops future wallet funding and reminders while retaining minimal financial/paid-access evidence. No automatic customer enrollment or external recurring gateway is added.

MicroPayments stores site content, user, wallet, subscription, purchase and transaction records in WordPress; third-party extensions may retain additional records.

The included catalog and workspaces run on the WordPress site. Media storage and streaming integrations retain their own configuration requirements. Application paywalls and preview cards do not make an ordinary public media URL private; private media needs independently protected delivery at its storage/streaming origin.

Reviewed fixed bundles

Sell a fixed collection of up to 200 eligible published items from one seller through the native wallet. Administrators review the item list, price and duration before publishing an immutable offer. Partial owners acknowledge the full price; all-owned checkout stops. Withdrawal stops new sales while retaining purchased scope and expiry. Bundles do not include future items, copy individual receipts or override other viewing rules. See the bundle FAQ for supported content and limits.

Installation

For optional account pages, open MicroPayments > Accounts and creators. Review the toggles, low-privilege roles and after-login destinations. Create the missing account/feed pages or assign existing published pages. Enabling frontend registration does not change WordPress’s registration setting. Keep the account toggles off when a community or membership plugin owns that workflow.

Account shortcodes: [videowhisper_login], [videowhisper_register_fan], [videowhisper_register_creator], [videowhisper_recover], [videowhisper_account]. The existing [videowhisper_register] becomes a chooser when dedicated pages are assigned and retains its legacy form otherwise. Password recovery requests a native email reset link; password selection/reset remains on WordPress’s native screen. On a network installation, registration links to native network signup rather than creating another identity system.

Community shortcodes: [videowhisper_follow_creator creator="123"] and [videowhisper_following_feed]. Follow controls also appear on opted-in creator profiles and directory cards when multi-creator following is enabled. Configure the creator home first; following is omitted in single-creator mode.

  1. Install and activate MicroPayments on WordPress 6.9 or newer with PHP 8.2 or newer. Prefer a currently supported newer PHP hosting branch where available.
  2. Open MicroPayments > Creator setup. Choose the creator mode and presentation, preview changes, then apply the reviewed setup or skip it. Configure the allowed creator, buyer and moderator roles, content types, wallet and monetization options for your site.
  3. If you will accept external payments, install/configure the required WooCommerce, TeraWallet or myCRED components and verify merchant eligibility before using real payments.
  4. Use Setup Pages to review/create the frontend pages you need, or add the documented shortcodes to existing pages. Review visibility, ownership and the destination of each page before making it available to users.
  5. Under MicroPayments > Listings, choose the public catalog layout and buyer/creator workspace layout independently. Styled tiles and Classic workspaces remain available; a shortcode can override its page’s layout.
  6. Add sample content and independent promotional featured images. The native editor’s Public preview box and the existing frontend content editor can approve a small public copy for subscription-library cards. Review the public-preview notice before saving. Check a visitor, an unentitled member, a buyer and a creator before opening the site for purchases.
  7. Configure guest submissions/reCAPTCHA and the site’s terms/privacy notices only if you intend to offer guest content upload. Public credits can be enabled or disabled in settings.
  8. On multisite, network-activate MicroPayments before using Network Admin > Settings > Legacy commerce. Activation only on a subsite does not provide this Network Admin workflow; the plugin never activates itself automatically. Ask a network administrator to review retained records there. Verify the target site, ownership/access terms and credit units before adopting records. Do not distribute one historical balance or grant to multiple sites.
  9. For a confirmed shared myCRED or TeraWallet account, use MicroPayments > Shared wallets on the relevant site as a network administrator. Review the provider account and units before approval. Unknown configurations remain unavailable; verify the intended site and provider before real transactions.
  10. Sign in as a test buyer in a modern workspace and open Included with subscriptions. Check an allowed item, an expired subscription and an item declined by its media provider. Purchase history and completed orders remain separate. Verify the hosting/provider requirements below, native navigation without JavaScript and that private workspace responses are not cached publicly.

FAQ

How can administrators review renewal evidence?

Fans inspect their own [videowhisper_renewal_health]; native administrators inspect permitted site accounts under MicroPayments > Renewal health. Read-only reports examine at most twenty relevant orders and one hundred lines each, link native records and never process packages, retry payment or change access. A pending purchase is not available balance; package credit is not membership renewal.

Reconciliation evidence compares retained intent, native debit and signed paid terms. Missing, conflicting or unavailable proof cannot authorize correction. New native renewals capture structured cycle/consent/transaction/date receipts; legacy records are retained without invented proof. Review timeline previews and explicitly saves proposals only, with ten-minute session/evidence/history checks. Native privacy export excludes staff notes; erasure redacts optional notes/IDs while retaining minimal proof. Proposal writing requires core wpdb, InnoDB and request-local caching, with forty cases and ten proposals each per account. Limits never evict history.

Wallet credits is a separate opt-in review and confirmation. Package/gateway refunds and access cancellation are excluded. Never cache personalized reports.

How do administrators investigate a held credit?

Open Wallet credits, expand the operation and choose Inspect credit evidence. This read-only view compares the signed operation, bounded native transaction candidates, original debit identity and cumulative budget. A held intent stays held even if a candidate agrees. Failed, missing, changed or conflicting evidence cannot authorize retry or hold release. Refresh stores nothing; original access and records remain.

How do wallet credit limits and uncertain outcomes work?

Only a verified native renewal debit, its signed paid term, structured receipt and current saved possible-credit proposal qualify. The original amount and wallet unit set the cumulative ceiling; partial credits do not reset the term. All operations against that debit count across cases and reasons, including held amounts. Missing audit rows are checked against the native credit ledger. Other manual adjustments or external refunds are not inferred from reference text: investigate those separately before approving compensation.

The first store retains at most 100 operations per original debit, with paginated account history and no eviction. A full, inconsistent or unqualified store refuses execution. The held intent survives failure before or around commit. There is no automatic retry, release of reserved budget or source repair. Credit, balance and committed receipt use one native transaction; a lost acknowledgement is not shown as success until current receipt/ledger evidence verifies it. An existing operation is never blindly applied again.

Financial audit facts remain in a separate site-owned database table. Privacy export includes the fan’s own credit/held-operation facts without private staff notes or identifiers. Erasure redacts optional notes and staff identifiers in those operation records while retaining minimum financial proof and unresolved holds. Original native ledger and access records keep their separate retention rules. Select the site’s accounting/dispute retention notice before enabling execution; the plugin does not impose a universal legal period or automatically delete records. Back up the database and private signing options. Disabling or deactivating retains these records.

Can fans renew from the token wallet?

Yes. A separate opt-in offer continues an existing paid site plan using the native wallet. Configure MicroPayments > Wallet renewals, then let each fan review and authorize the price and term from membership history. Optional low-funds warnings and fan-requested emails have customizable templates and a default seven-day lead. No immediate payment or automatic customer enrollment occurs. See the wallet continuation, operation and retention sections above; external recurring card billing is separate.

How do searchable categories and editor presets work?

Native category dropdowns include initial choices and the current selection. Type at least two characters to search the site’s public WordPress category API, with up to 20 matches per request. Categories outside the initial 100 remain searchable. Searches do not create categories. Existing creator, playlist and access filters still apply. If remote search fails, the control returns to its loaded native category list and retains the selection. Editor presets change presentation and visitor controls; they retain creator, category and access selections.

Can an agent publish or change access through the assistance tools?

No. Optional Site Manager integration provides permission-scoped readiness reports and plain-text editorial suggestions. Read-only proposals do not save content. Separately enabled review/write tools can create a private comparison for explicit native approval; they do not automatically publish, approve media or change prices, memberships or access. Site, role, personal and exact connection permissions remain required. Private PHP abilities add no public REST shortcut. Installing MicroPayments does not connect an AI service or send content to one.

How do I prepare my first publication?

Open MicroPayments > Publication readiness, or First publication in the creator studio. Follow setup, upload/capture, draft review, separate public promotion, native publication and a separate fan-view check. Administrators see the next configuration review linked to its existing settings.

The private release-readiness timeline shows up to 12 recent editable items per page, native publication state, recent shared preparation, selected site-plan labels and calendar/paid-start conditions. It links native editors and highlights current configured term mismatches. It does not certify playback or fan entitlement, change restrictive rules, publish, approve previews, retry jobs or alter purchases/originals. Creators see their own currently editable items; administrator status still requires native object permission.

Use [videowhisper_publication_readiness] on a private creator workflow page when needed. The report uses the current account, sends no new external-service data and creates no progress or payment records.

Can I customize purchase terms and help fans find their plans?

Open MicroPayments > Purchase terms for brief plain-text wording, expandable details and a public complete-terms page. A separate purchase page is optional; otherwise the selected site terms, existing WooCommerce terms or existing public terms page is used. Actual offer price, duration and renewal facts stay visible. The disclosure appears on site-plan offers, native wallet/creator-membership confirmations, Woo product pages and classic/Blocks checkout. Native checkout acceptance and existing purchase/access records remain unchanged.

Signed-in account and buyer workspaces include separate expandable site-plan discovery and private membership history. Current access is identified before another purchase; the original source expiry remains visible. Creator subscriptions and item purchases keep their separate views. No account page, global role or billing migration is created automatically.

Full audio and private playback memory

In MicroPayments settings, open Downloads and enable the optional full-audio player. Existing verified local audio downloads can then play for signed-in users whose current native purchase, membership, collection and paid-channel checks allow access. Full audio uses an access-checked endpoint; separately approved promotional samples remain public.

Each fan chooses video memory and audio memory separately. Both default off. A prior video-memory choice does not enable audio history. Continue playing links to native item pages; Resume seeks only after the fan presses it and does not autoplay. Clear/reset and WordPress personal-data export/erasure cover private reader state while retaining purchases and other sites’ records.

The endpoint supports local files up to the existing audio metadata limit, GET/HEAD and single byte ranges. External storage/player adapters, queues and DRM are not included. Existing files are not relocated: configure private origins on your host before treating an original URL as private. An already public source URL or previously downloaded bytes cannot be revoked by this feature. Detected source changes invalidate old player URLs and positions; refresh audio metadata after replacing a file.

Private audio and video workflow

Use Add media, Review and Save in the optional shared creator workspace. Video and audio can use private originals when hosting is configured; photos and screenshots retain the native image workflow with an explicit standard-storage choice. Choose a title and content type, preview your accepted audio/video, save for native review, then set the price and audience in the destination editor. Review mode remains the default. Direct publishing still requires existing native permissions and a playback-ready source.

Private storage requires a host-configured VIDEOWHISPER_PRIVATE_MEDIA_ROOT outside public web roots and aliases. Existing upload-extension restrictions remain; permit WebM before recording audio. Trusted local FFmpeg/FFprobe tools prepare recorder duration and seeking metadata without transcoding. Missing tools retain originals privately and block handoff until preparation and review are possible. See the hosting requirements below.

Creators and authorized staff can preview private drafts using native read/edit permissions; this does not allow staff to claim another creator’s original. Draft review is excluded from playback history. Private delivery supports qualified local progressive media using current native item access on each GET/HEAD or byte-range request. Public samples and posters require their own separate, approved files. Existing public originals are not moved, removed or made private by enabling this feature. Private HLS, CDN/remote delivery, older-source migration and universal browser/codec support are not included. Files already received cannot be recalled.

What happens to media workflow data in a privacy request?

Use WordPress Tools > Export Personal Data or Erase Personal Data. Exports include your site-local job and approval details without server paths, credentials, source tokens or other people’s content. Erasure minimizes redundant workflow titles/descriptions and actor references, revokes individual future-publishing approval and stops pending work. Minimal ownership/source references and necessary public-approval evidence remain. Physical originals, prepared media, native posts, prices, purchases and access grants are retained for separate native ownership and retention review.

Settings > Media workflow links to these tools and the privacy policy guide. Workflow details are kept by default. Administrators can review and enable minimization of finished-job details after 30, 90 or 365 days. Active jobs are excluded. A retained job cannot retry or recreate a publication; use its native item or retained original for further review.

What does private media hosting require?

The host must configure VIDEOWHISPER_PRIVATE_MEDIA_ROOT outside all public web roots and aliases. WebM preparation and video promotional generation require host-configured local FFmpeg and FFprobe executables. Durable jobs need WordPress cron or a hosting scheduler; the settings show an action notice when automatic WordPress cron is disabled. Server quotas, current creator permissions and native content access still apply. Existing public originals are not migrated by enabling private storage. Browser codec support varies; a native download remains available where appropriate.

How do media approval and background preparation work?

Open Settings > Media workflow to review approval modes. Existing plugin review settings remain effective until an administrator explicitly saves a shared mode. Recommended selected roles are administrators and editors. An administrator with user-management permission can approve a creator’s future publishing and revoke that approval from the user’s profile. Existing drafts are not automatically published. Native capabilities, seller/upload lists and content access rules still apply.

Private video/audio intake through the optional shared creator workspace is saved as a durable job. WordPress cron runs preparation; configure a hosting cron when automatic WordPress cron is disabled. Results and errors survive navigation. Check Preparation in the workspace, the native editor or Settings > Media workflow before retrying. Originals are retained. Interrupted native creation or public-copy approval may require manual review rather than repeated creation.

What does Creator setup change?

The wizard previews a separate creator home, its featured creator/content emphasis/layout and any missing shortcode pages before saving. Existing pages are reused without rewriting their content. It does not select your global homepage, install a theme, edit menus, grant seller privileges or configure payment providers. Follow the linked settings and offer-editing prerequisites before inviting buyers. You can skip or resume the preview. Undo restores only the latest setup fields; later edits block replacement. Created pages are retained, with unchanged pages returned to draft where they are not already assigned as a homepage, privacy page or menu item. When custom block navigation exists, published setup pages are conservatively retained.

How do I add an audio sample?

Open the download’s native editor or frontend content editor. Save to refresh verified duration, format and size. Upload a separate promotional audio file to Media Library, enter its attachment ID under Audio download and sample, and explicitly approve its public use. The limit is 60 seconds and 8 MiB. Samples use deliberate click-to-play controls; full paid files are not used as a fallback. Shared or cached public samples cannot be recalled by changing approval. Full-source inspection supports compatible MP3, M4A, OGG/Opus, WAV, FLAC and audio-only WebM files up to 512 MiB; browser playback depends on the encoded format. No conversion, listening queue or private podcast feed is added.

How does recorded audio become a download?

With a supported VideoWhisper recorder active, accept an audio capture and open Recorded audio drafts from your creator studio, recording page or eligible Media Library row. Review the title, description and original-file notice, then confirm creation. The bridge copies an eligible owned recording into a new unpublished download, retains the recorder original and reuses its receipt on retry. It requires existing seller, native creation and download-sharing permissions and an enabled file extension. The bridge supports a local download store under this site’s uploads and recordings up to 100 MiB. Existing recording pages are not rewritten; add [videowhisper_recorder_drafts] below the recorder shortcode if needed.

Recordings already associated with comments, activity or posts stay in their original workflow. Interrupted attempts and missing/trashed drafts retain receipts for administrator review instead of silently creating replacements. A paid draft does not make an already-public recorder original private.

Which shortcodes should I start with?

Public content discovery:

  • [videowhisper_content_list id="store" layout="grid" perpage="12" perrow="3"] – aggregate configured content types and creators.
  • [videowhisper_content_list id="creator-42" layout="feed" author_id="42" menu="0" tabs="0"] – one creator’s catalog; replace 42 with an existing creator ID.

Signed-in workspaces:

  • [videowhisper_content layout="list"] – the current buyer’s purchase history; use source=”subscriptions” for the separate Included with subscriptions view.
  • [videowhisper_content_seller layout="feed"] – the current creator’s asset studio.
  • [videowhisper_content_edit] – existing frontend item editing workflow for permitted content owners.

Wallets, subscriptions and memberships:

  • [videowhisper_wallet_memberships] – own private wallet renewal offers, reviewed consent and controls; also included in membership history.
  • [videowhisper_my_wallet] – configured wallet and funding options.
  • [videowhisper_wallet] – compact configured wallet display.
  • [videowhisper_client_subscribe] – author subscription options.
  • [videowhisper_client_subscriptions] – the current buyer’s subscription records/settings.
  • [videowhisper_provider_subscriptions] – creator subscription setup.
  • [videowhisper_membership_buy] – site membership packages.

Content and file tools:

  • [videowhisper_content_upload] – permitted-user content upload with available media integrations.
  • [videowhisper_content_upload_guest] – optional guest submission form; configure its owner, terms and submission policy first.
  • [videowhisper_downloads], [videowhisper_download], [videowhisper_download_preview] – downloadable-file listing, item and preview tools when Downloads are enabled.
  • [videowhisper_download_upload], [videowhisper_download_import] – permitted file upload/import workflows.
  • [videowhisper_creator_stats] – creator statistics.
  • [videowhisper_donate], [videowhisper_donate_progress] – configured donations and goal/progress displays.

Use a unique id for each catalog on a page to keep shared links stable. Layout values are grid, list, feed and legacy. Public catalog filters include creator, configured content type, category, tags, title and configured access/offer categories. The refresh="30" option enables periodic refresh; static catalogs do not poll by default.

Does Feed include follows or recommendations?

No. Feed is a one-column layout honoring the selected catalog and ordering. It does not create a social network, personalized recommendations, follows or an independent chronological-post service.

How do purchases and subscription-included content differ?

Content purchases shows recorded item purchases, including expired or unavailable records without exposing a newly private title/poster. Completed orders shows the current customer’s completed WooCommerce orders. Included with subscriptions is a separate modern-workspace view of supported, published content currently allowed by both the buyer’s native MicroPayments creator subscription and the content provider. My subscriptions remains the place to review subscription records and settings. A purchase, site role or external subscription does not automatically add an item to Included with subscriptions.

What does Included with subscriptions require?

Use a modern buyer workspace layout: Cards, List or Feed. If Classic is the configured or requested layout, Included with subscriptions automatically uses Cards for that view. Saved defaults and purchase/order views are unchanged. Configure supported content types and native MicroPayments creator subscription tiers. PHP must have OpenSSL enabled with AES-256-GCM support for private navigation links. The site must permit private, uncached workspace requests; JavaScript is optional.

Each media plugin must provide a qualified complete access check. Public Video Share VOD 3.1.9 cannot qualify videos for this view. Its composed check requires version 3.1.10 or later; use its current qualified release and supported provider configuration. Picture Gallery keeps its own access rules and final veto, so an entitlement recognized by MicroPayments may still be declined by Gallery. Missing or unsupported provider checks do not grant access. Ask the site administrator to review configuration when expected items are absent; do not change a buyer’s grants merely to fill the listing.

Library cards use an explicitly approved small public preview or a placeholder, plus the item link. They do not expose the private body, original image, player, manifest or download URL. Playback, protected file delivery and external-platform subscription synchronization remain separate features.

How do I add or stop using a public library preview?

Choose a separate promotional featured image for the content item. In the native WordPress editor, use Public preview; in the existing frontend content editor, use Show a public preview in subscription libraries. An authorized save creates a separate JPEG up to 480 by 270 pixels. Reads do not generate images. Known VOD, Gallery and download source files, and Gallery-owned source attachments, are refused for this option. Local JPEG, PNG and WebP sources are supported by the preview processor when the server’s image editor supports them; the frontend uploader retains its documented upload types. This preview workflow requires local uploads served from the same origin as the WordPress site; external storage or CDN URL rewriting needs a separately qualified adapter. Ask the administrator to check uploads and image-editor support if approval fails.

That generated preview is public to anyone with its link. Turning the option off stops its use in new cards; previously shared or cached copies can remain public. Replacing a featured image requires a new approval. Public catalogs and existing purchase/creator cards retain their established featured-preview behavior and prefer an approved small preview when available. This option does not make a private-media-origin guarantee.

What happens when many candidates are declined by the provider?

The library checks a bounded candidate window and offers Continue checking if more work is needed. It does not claim the library has ended just because that window is full. Native Gallery access rules and its final veto still run for every candidate. A narrow cache optimization reuses a proven empty Gallery term inventory; custom or nonempty term queries keep their native behavior. Hosting, plugin filters and the amount of content affect response cost; no universal throughput guarantee is made.

Why does the subscription view ask me to continue checking?

The site checks content in groups and applies the current subscription and content-access rules before showing results. Continue checking looks for more matching items; it does not buy or renew anything. A view with no items may still have more items to check. Start again if an old navigation link no longer works.

Can creators keep using bulk management and announcements?

Yes. The studio links to the original Classic workflow for existing bulk/pricing/announcement operations. These actions retain their own permissions and checks. Configured upload, recording and subscription pages remain linked when available. A modern layout does not change ownership or grant another user’s management access.

Do I need FansPaysite or a community plugin?

The public catalog and included workspaces run with compatible WordPress themes. FansPaysite and community plugins are optional. Media conversion, streaming and external payment features retain their own technical requirements.

Where can I get setup help?

Start with the Installation section and shortcode FAQ. For plugin questions, use the WordPress.org support forum. Include your versions, the workflow and steps to reproduce the problem; keep credentials and private content out of public reports.

Where do I report security bugs?

Please report security bugs through the Patchstack Vulnerability Disclosure Program. Patchstack assists with verification, CVE assignment and developer notification.

How do single-creator, multi-creator and multisite sites differ?

Single-creator and multi-creator catalogs both run within one WordPress site and use the same features. Multisite adds a separate site boundary: MicroPayments scopes internal balances and commerce records to each subsite, retains ambiguous historical network records for explicit review, and requires per-site approval before using a confirmed shared external wallet. An approved shared provider account still follows that provider’s own ledger model. Cold-subsite activation alone does not establish correct financial separation; use the documented site context, legacy review and provider approvals.

What happens to historical multisite balances and purchases?

The original records are retained. They are not used as an automatic fallback for an unrelated subsite. A network administrator must review the source, target site, user/content ownership, access terms and credit unit before adopting supported records. Ambiguous records stay held. The workflow does not globally clone balances, delete the retained source or automatically change roles. Existing single-site balances and purchases are unchanged.

Languages

This package is English-first. Spanish is retained separately as an incomplete review draft and is not bundled with the runtime plugin.

Where supplied, bundled translations may be generated or reviewed by AI agents. They are provided as a starting point and should be reviewed for your site before use, especially billing, access and consent wording. Translation coverage and terminology may need adjustment for your setup.

Existing WordPress community language packs and custom site translations are not removed or disabled, so some installations may continue to display translated or mixed-language text.

Optional credits and theme support

Public VideoWhisper credits are optional and disabled by default on a fresh installation. Existing explicitly saved credit-display choices are retained. A public credit link is not required to use the plugin.

Modern views include their own styles and work without FansPaysite. When that theme is active, version 2.7.10 supplies matching palette tokens and corrected additive RTL styling. Selecting a plugin layout does not change your global theme menus, page templates or archive layout.

Third-party assets and source

The bundled Fomantic UI 2.8.8 JavaScript/CSS is MIT-licensed. Human-readable source and build tools are available in the tagged upstream repository. The plugin removes its Google Fonts import and conditional Twemoji CDN image requests; typography uses available fallback fonts, and custom content can use native Unicode emoji text. Exact patch instructions, source links and hashes are included in interface/semantic/README.txt and asset-provenance.json.

Existing icon fonts are retained from the Semantic UI 2.3.3 distribution, with Font Awesome copyright notices and the SIL Open Font License 1.1 included alongside the font files. The UI code’s MIT license does not replace the font license. The bundled jQuery UI theme retains its MIT notice; the Plupload UI widget retains its GPL notice, readable JavaScript source and local text-rendering maintenance notice. Rebuild its matching minified file with the pinned Terser command in that source header.

Public text translations

With Agentic Multilingual Translator active and the relevant public text providers enabled, agents with Site Manager access can draft and separately publish translations of supported public fields. Enable drafting/publication in Translator and retain the appropriate Site Manager role, personal and connection permissions. Translating does not publish the original, change commercial access or unlock manual corrections.

Public creator profiles expose only the opted-in short introduction and biography on an unrestricted configured creator home. Authors choose a writing language from the site languages. Private account biographies, covers, offers and purchase details are excluded. The native profile publication choice and owner identity remain authoritative.

Can I sell one-time site memberships through WooCommerce?

Yes. Plans start paused. Create a published virtual simple product with individual sales enabled; preview its product, price, label and duration under Site membership plans before enabling sales. Use [videowhisper_site_memberships] for offers and [videowhisper_my_memberships] for private source history. Wallet memberships and creator tiers remain separate.

Explicitly select plans in the native Site membership access box. Selection offers an alternative paid route, or restricts otherwise free content; no selection changes nothing. Matching Video Share VOD and Picture Gallery adapters support their configured media types. Native visibility, passwords, channels, gallery/watch rules and protected-delivery requirements remain. Unknown external paid restrictions are not unlocked; public samples stay separate.

Each captured checkout grants its original fixed term. Repurchases are independent, without stacking or automatic renewal. Current order/item ownership, paid status, refunds and expiry control that source. Line refunds pause the affected source; unallocated order refunds pause membership sources on that order. Other valid purchases/grants remain, without role or approval changes.

Classic and Blocks checkout use WooCommerce APIs. Old/manual orders without captured pre-payment sources are not adopted. A native order action can recheck retained sources after storage failure. History has twenty entries per page and five hundred sources; new membership checkout stops at the ceiling without deleting history. Ordinary purchases remain available.

WooCommerce/gateways own credentials, taxes, coupons and payment/refund execution. This adapter makes no external request or wallet transfer. Back up orders, access records and the private signing option; rotating login/nonce salts does not invalidate sources. Privacy erasure retains minimum paid-access proof; pausing/deactivation retains records. Exclude personalized/protected pages from full-page caching.

Opt-in creator storefronts

Creators can publish a site-specific introduction from their studio or Public profile screen. Select a published item with an approved, independent public library poster for the cover; withdrawing poster approval also removes it from the storefront. Public profiles show existing membership offers and link to the native subscription confirmation flow. Browsing never processes a purchase or renewal.

Profile preferences are stored in user metadata separately for each WordPress site. Uncheck the public-profile option to hide the profile and remove its directory listing; this retains your saved draft fields and existing content. This feature adds no external service, telemetry or account registration.

The existing creator home supports a pinned single creator or an opt-in creator directory with mixed content. Single-creator sites retain the basic creator name and catalog before profile opt-in. Directory pages examine up to 12 indexed profiles and the latest 8 public candidates per profile; a creator whose recent candidates are all hidden may be omitted. The cover picker includes the latest 50 published items and the retained selection. Existing content, page assignments, wallet balances and access grants are unchanged.

Shortcodes: [videowhisper_creator_storefront creator="123"], [videowhisper_creators], [videowhisper_creator_storefront_edit]. The existing [videowhisper_creator_home] and navigation shortcodes remain supported. Optional FansPaysite mobile navigation uses a versioned read-only navigation contract; other themes work independently.

Reviewed native-wallet bundles

Open MicroPayments > Reviewed bundles as an authorized administrator. Select 1–200 existing published, password-free wallet-priced items from one seller, enter the full price and access duration, and review the exact item list and seller before approval. A duration of zero means lifetime access. Mixed sellers, coauthor allocations and additional role, creator-tier, site-plan or WooCommerce gates are excluded from new offers in this first contract.

Each approval creates a separate native purchase object with immutable scope, price, wallet unit and duration. Changed terms require a new reviewed offer. Free MicroPayments creates and manages these bundles independently; an extension may supply a compatible selection interface. Use [videowhisper_bundle id="123"] for the fixed offer summary or [videowhisper_bundle_offers item="456"] to list current offers for an item. Checkout remains on the native offer page.

Buyers review the full fixed price and acknowledge that already owned items do not reduce it or receive automatic credit. Checkout stops when every item is already available. A purchase retains its original timed or lifetime native receipt; it does not copy individual-item receipts, include future items or override current publication, password or other viewing requirements. Withdrawal stops new sales and retains purchased scope and expiry. Existing individual purchases, memberships, wallet settlement and originals remain separate. Refunds and wallet credits follow the site’s separately reviewed policy.

An expired wallet funding review

A funding review is valid for ten minutes and binds the current account, session, offer and original paid-through date. An authenticated expired submission explains the expiry and offers Review current wallet offer. Review again, then explicitly authorize the new unchecked confirmation. Reopening a review never enables funding or takes a payment automatically. Invalid credentials or changed evidence still require a fresh native review.

WooCommerce product, cart, checkout and account screens retain their native price, payment and access controls. A staff member’s ability to view the page does not make its product free; regular-content free-access badges are omitted from these purchase screens. Ordinary content notices and access restrictions remain.

Curated collections and returning readers

Build creator-owned ordered collections from existing videos, pictures, downloads and posts through Series editor or [videowhisper_series_editor]. Choose an approved public poster and review publication; contributors submit for review. Every item retains its own visibility, purchase, membership and provider checks. No file, product, price or entitlement is duplicated, and existing tags/URLs remain.

Embed [videowhisper_series id="123"] or [videowhisper_series_directory]. Collections hold up to two hundred creator-owned references with twenty rows per page; unavailable items get anonymous placeholders. Single- and multi-creator sites share the same model.

Fans can save public paid items before purchase without unlocking them. Use buyer-workspace links or [videowhisper_saved_content]. Each account/site retains up to five hundred bookmarks and five hundred positions; twelve-record pages may have gaps when access changes.

Playback memory requires explicit opt-in. Supported full native HTML5 video/audio can offer click-to-resume without autoplay. Public samples, hover previews, ads, embedded/foreign players and unqualified timelines are excluded. Unknown duration, changed media or expired access suppress resume. Throttled/pause/end saves may miss the final interval on navigation.

These private preferences remain in site-scoped WordPress metadata, without localStorage tracking or external registration. Turning memory off retains positions; explicit clears invalidate older writes. Native privacy export/erasure covers these records without changing purchases, wallets, subscriptions or originals. Deactivation retains data; WordPress controls account deletion.

Screenshots

Changelog

4.29.1

  • Keep an uncertain reminder handoff held when a mail provider throws, while continuing the native renewal batch for other fans. Do not repeat a reminder whose delivery outcome is unknown.
  • Qualify multiple native wallet cycles, insufficient funds, token replenishment, late funding, per-cycle reminders and cancellation with retained purchases, paid terms, approvals and originals. Genuine hosted multi-cycle acceptance remains a separate dated canary.

4.29.0

  • Recover authenticated expired credit reviews through an explicit audit check and fresh native preview. Confirmation is never carried forward; committed, held, used or unverifiable operations cannot be retried through recovery.
  • Show review expiry, a local expiry indicator and distinct warning, error and committed notices without changing the financial transaction path.
  • Present verified current membership terms before original order history, including independent wallet-funded terms after an initial order expires. Stopping future funding retains paid access.
  • Clarify original-debit proposal ceilings separately from partial credit amounts. Preserve source history, cumulative limits, purchases, approvals and originals.

4.28.0

  • Explain the ten-minute wallet funding review window and provide a native fresh-review action for authenticated expired submissions, retaining explicit consent and all payment guards.
  • Remove misleading regular-content free-access badges from WooCommerce product, cart, checkout and account screens, including cart/checkout blocks, without changing purchases or access.
  • Add independently usable administrator-reviewed immutable native wallet bundles, signed buyer quotes, explicit full-price partial-ownership acknowledgment and all-owned checkout protection.
  • Resolve fixed bundle scope through native site-scoped timed/lifetime purchase receipts. Withdrawal retains past purchases; individual receipts, other access gates and native financial settlement remain authoritative.

4.27.0

  • Read-only operation investigation distinguishes held intents, exact committed receipts, transaction candidates, incomplete or changing reads and retained original-debit limits.
  • Native account-scoped links and safe investigation steps never apply credit, clear a hold or change access; repeated GET/POST reads retain financial and source records.

4.26.0

  • Optional native administrator wallet credits require a current saved proposal, a fresh exact preview, native confirmation and a site-reviewed retention notice.
  • Partial and cumulative limits bind every committed or held credit to the original debit; durable operation identities, native ledger cross-checks and transactional receipts prevent blind retries or resetting a limit through another proposal.
  • Original access, paid dates, consent, purchases, approvals and media remain. Paginated audit and privacy handling retain minimum financial proof; no cash refund, package reversal, hold-clear or financial agent tool is included.

4.25.0

  • New native wallet renewals capture structured cycle/consent/transaction receipts atomically with the existing paid record; legacy access and original dates are retained.
  • Native administrators can preview and save proposal-only financial reviews, with exact amounts, original terms, fresh-evidence checks, session-bound expiry and idempotent history. No credit, refund, retry, access change or hold-clear is implemented.
  • Privacy export/erasure covers the new review records; bounded protected JSON storage preserves minimal evidence and removes optional notes/staff identifiers on erasure.

4.24.0

  • Native administrators can compare retained wallet-renewal references, ledger candidates and signed paid terms in a read-only Reconciliation evidence tab.
  • Distinguishes agreeing records, missing evidence, conflicting signatures/amounts, changed reads and bounded or failed comparisons without retrying payment, clearing holds or changing access.
  • Strict native account permissions, private output and paginated retained references; no new agent tool or financial correction action.

4.23.0

  • Read-only renewal health separates upcoming wallet funding, low balance, pending token orders, recorded credits and held attempts.
  • Native administrator account inspection and a private fan shortcode link existing order, wallet and membership tools without processing or retrying payments.
  • Bounded native WooCommerce order reads, site/account permissions and private-page headers retain access, purchases, approvals and originals.

4.22.0

  • Add separately opt-in native-wallet continuation for current paid site plans, with administrator-reviewed offers and explicit fan consent/cancellation.
  • Reuse completed native token-package funding and commit each renewal debit, ledger receipt, signed paid term and next due date together. Hold uncertain attempts for review; retain independent purchases and originals.
  • Add customizable low-funds warnings and optional fan-requested email reminders with a default seven-day lead, funding links, bounded jobs and native privacy export/erasure retention.
  • Link wallet setup from site plans, creator onboarding, plugin menus and the VideoWhisper toolbar. Preserve existing one-time and creator-subscription workflows.

4.21.0

  • Check the declared WooCommerce product type before new one-time site-plan checkout. A missing extension cannot silently turn a subscription product into a one-time offer; existing captured paid terms remain independent.
  • Add an optional handoff from editorial previews to Site Manager’s private native WordPress review. Review title and excerpt changes before applying; content body, publication, access, approvals and media stay native. Requires separately enabled Site Manager review/write tools; read-only tools do not gain write permission.
  • Recognize identical repeated member-access saves without rewriting the policy. Keep stale differing changes blocked, scope conflict notices to the matching editor and clarify the separate access save step.

4.20.0

  • Build pages with searchable native category controls and practical presentation presets. Public category search reaches beyond the initial choices and keeps a native fallback when search is unavailable.
  • Optional read-only Site Manager readiness and editorial-proposal tools, private native abilities and a guided administrator review screen. Existing role, personal and connection grants remain required.
  • Preserve existing shortcodes, access, purchases, content approval and original media.

4.19.0

  • Native fans-paysite catalog block with layout/filter controls and a read-only editor preview; existing shortcodes and native access retained.
  • Reviewed draft release calendar: preview up to 20 eligible new drafts, then apply site-plan calendar dates or paid-start delays atomically. Does not publish, approve or replace existing delayed policies.
  • Site-first presentation and updated banners explain single-/multi-creator use and self-hosted control.

4.18.0

  • Added a private first-publication guide and bounded read-only release-readiness timeline, linked from creator workspaces, setup and the VideoWhisper admin menu.
  • Links native editors and shows publication, recent shared preparation, selected site memberships and calendar/paid-start conditions without changing access, approvals, purchases or originals.
  • Added current workflow banners and a curated authentic screenshot tour.

4.17.0

  • Add opt-in elapsed-day release conditions for new site-plan content, evaluated against one current native paid source without age borrowing or term stacking.
  • Explain each plan’s configured duration, invalid delays, rejoining and overlapping purchases; keep original source terms, independent access and media intact.
  • Show a private own-membership timing explanation without publishing another fan’s schedule or changing native viewing rules.

4.16.0

  • Add opt-in calendar release dates on new site-plan content, enforced through native content and full-media access checks.
  • Retain existing purchases, creator subscriptions, roles, approvals, originals and issued membership terms; reject late restrictive edits and ambiguous local times.
  • Add independently approved local creator profile images, offer covers, clearer workflow help and calendar hints in catalogs.
  • Improve live theme-mode link contrast and retain native one-time WooCommerce payment/refund behavior.

4.15.0

  • Add explicit Video Share VOD and Picture Gallery site-plan adapters while retaining native media visibility/viewing, independent purchases and originals.
  • Add administrator-configurable brief/expanded purchase disclosures and public complete-terms fallback for native and WooCommerce purchases.
  • Add fan account/workspace plan discovery and current-access messages; keep native item/tier confirmation available beside site plans.
  • Guard retained media-plan bodies, excerpts and REST projections when the membership provider is absent; require compatible provider contracts.

4.14.0

  • Add optional paused-by-default one-time site plans, explicit native Woo product mapping and reviewed setup.
  • Capture checkout terms before payment and retain source-owned fixed access without global role changes or historical-order adoption.
  • Add explicit post/page/download membership rules, fan source history, local status/refund checks and native privacy/retention handling.
  • Preserve independent paid access, original media and separately approved public samples.

4.13.0

  • Add separate fixed-role fan signup and creator application pages with configurable introductions and reset-to-default choices.
  • Link creator model, account-page preview/apply/undo, readiness and read-only membership-source review as setup steps.
  • Preserve staff backend management, native network signup, existing page content, roles, publishing approvals, commerce and originals.

4.12.0

  • Add optional frontend registration, login, recovery and account pages with session-bound guest nonces, safe local returns and role-aware dashboard destinations.
  • Add reviewed creator applications, low-privilege role mapping and separately configurable public-profile eligibility.
  • Add public creative-focus/website fields, creator section navigation, shortcode follow buttons, private followed-creators feeds and follow management.
  • Add opt-in Google reCAPTCHA v3 with explicit visitor verification consent and server-side action/hostname/age/score checks.
  • Include site-scoped follows, profile fields and application records in native privacy export/erasure. Preserve content, originals, wallets and native access.

4.11.0

  • Add optional public creator bio/introduction translations with stored writing-language choices. Registered sources retain opt-in profile visibility, ownership and native publication rules.

4.10.0

  • Check destination requirements before the first save attempt, retain originals when setup needs attention, and retry after correcting settings without re-creating uncertain earlier attempts.

4.9.1

  • Find creator setup, media approval, preparation jobs and related integration settings from the VideoWhisper toolbar; contextual guidance explains workflow ownership.
  • Compact filter controls share a responsive row, dropdown menus stay above listing overlays, and decorative icons clarify navigation.

4.9.0

  • Creator storefront layout links, search forms and pagination retain the selected creator route.
  • Added native WordPress privacy export/erasure, reviewed retention settings and stopped-job safeguards. Originals, native content and existing purchase/access records are retained.
  • Added explicit site approval modes and revocable per-user approval for registered media destinations. Native publishing, seller and audience permissions remain required.
  • Added durable private audio preparation status, retry and native draft links through the optional Media Capture integration. Retained originals and separate public samples are preserved.
  • Added shared approval settings, reviewed changes before saving and native editor/user-profile controls.

4.8.0

  • Add optional private-origin audio intake and protected native download delivery, with retained originals and separate approved public samples.
  • Share Add media, Review and Save with recorder/video destinations, permission-checked previews and explicit storage choices.
  • Add private-storage and recorder WebM preparation status to quick setup.

4.7.0

  • Optional access-checked full-audio player for verified native downloads, disabled until a site administrator enables it.
  • Session-bound local GET/HEAD delivery and single byte ranges retain current purchase, membership, collection and paid-channel decisions. Existing source records and public samples stay separate.
  • Separate default-off audio playback memory, manual resume and mixed Continue playing library; existing video consent does not enable audio history.
  • Per-site privacy export/erasure, clear/reset generation checks and source/access revalidation retain native financial records.

4.6.0

  • Add creator-owned curated collections/series over existing content, with ordering, approved covers and native publication review.
  • Add private saved-content lists and explicit opt-in full-video playback memory through a versioned VOD adapter.
  • Recheck item/provider access and media identity; retain purchases, files and existing collection taxonomy behavior.
  • Add bounded private records, stale-writer invalidation and native privacy export/erasure callbacks.

4.5.0

  • Add opt-in, site-scoped creator profiles, approved promotional covers and a bounded creator directory.
  • Present existing membership offers with links to native confirmation; retain single/multi-creator catalogs and purchases.
  • Add a public-profile studio link and first buyer journey setup checklist.

4.4.0

  • Add a shared Create content workspace with optional Media Capture, Video Share VOD and Picture Gallery destinations, alongside native document uploads.
  • Add reviewed quick setup presets and separate review/direct publication settings for new unified-workflow audio. Preserve native creator and publication permissions.
  • Retain original media, create draft-first audio copies and resolve existing destinations on retries without changing prices, purchases, subscriptions or access.

4.3.1

  • Added a site-local administrator screen to review retained recorder-to-download draft attempts, with bounded pagination and a selected review before confirmation.
  • Added explicit reconciliation of a verified existing draft after an interrupted receipt update. Current object permissions, accepted ownership, matching audio and a fresh preview are required. No replacement draft, copy, publication, price or access grant is created.
  • Retain ambiguous attempts and all original/copy files; do not automatically retry or reset them.

4.3.0

  • Added a resumable single-/multi-creator setup wizard with concrete page previews, stale-change protection and non-destructive latest-change undo.
  • Added audio metadata and explicitly approved independent click-to-play samples in catalog, workspace and download detail views.
  • Added an owner-reviewed accepted-recorder-audio to download-draft workflow, retaining recordings and reusing confirmed draft receipts.
  • Preserved existing purchases, subscriptions, balances, seller policies, ownership and media access rules.

4.2.0

  • Add Justified mixed-content rows alongside Styled tiles, Cards, List and Creator feed for public catalogs and modern buyer/creator workspaces.
  • Use compact Fomantic layout/type/access buttons, category/order dropdowns, search fields and Edit buttons; reduce Styled tile spacing.
  • Add an enabled-by-default frontend layout selector switch, independent stars/likes switches and public video hover-preview switch under Listings.
  • Reuse Rate Star Review’s server-rendered listing controls and approved Video Share VOD promotional clips, with no private/full-video fallback and no automatic preview download.
  • Keep existing purchases, subscription inclusion checks, wallets and content-provider access behavior.

4.1.1

  • Serialize frontend donation and uploader settings as data, validate numeric slider values and reject malformed extension arrays.
  • Normalize legacy download-list identifiers consistently, preserve case, safely encode filter links and retain normal search, sorting and pagination.
  • Render uploader filenames, renamed titles and error details as text while retaining notification formatting. Refresh the matching readable/minified uploader build.
  • Keep existing purchases, subscriptions, balances, creator permissions and modern library behavior unchanged.

4.1.0

  • Add a separate Included with subscriptions source to modern buyer workspaces for native MicroPayments creator-tier entitlements, using the same model for one creator and multiple creators.
  • Apply current creator entitlement and complete content-provider checks before filling each library page. Preserve native Gallery decisions and require the qualified composed Video Share VOD authorizer for videos; Video Share VOD 3.1.10 or newer is required for this source; 3.1.9 is unsupported.
  • Add bounded, private navigation with an explicit Continue checking state when more candidates need review; retain ordinary links without JavaScript. Document the PHP OpenSSL requirement in setup guidance.
  • Add an explicit, authorized public-preview workflow for subscription cards, using small independent derivatives with placeholder fallback and no original/source/srcset fallback. Retain prior featured-preview behavior in existing catalog, purchase and creator views.
  • Reuse a proven empty native Gallery relationship cache only for the matching read query; retain complete provider checks, final vetoes and native custom-query fallback.
  • Show approved public previews or placeholders without adding player, source or download URLs. Keep purchase/order histories, existing grants, billing and creator-management workflows separate.
  • Clarify empty, unfinished and unavailable states with plain recovery messages. Keep the package English-first and the incomplete Spanish draft outside runtime.

4.0.0

  • Add included, opt-in Cards, List and Feed layouts for public catalogs and buyer/creator workspaces, alongside Styled tiles and Classic management.
  • Render catalogs on the server with shareable filters, ordinary pagination and optional AJAX/browser-history enhancement. Keep automatic refresh opt-in.
  • Support one creator or multiple creators with the same catalog and ownership model; show creator identity, the established featured-preview URL, media metadata, rating summaries and current offers.
  • Separate buyer content purchase records from completed WooCommerce orders. Retain expired/unavailable history without presenting current prices as historical payments or inventing new access grants.
  • Add a current-user creator studio with configured types/publication states and links to native editing, upload, subscription and bulk/announcement workflows.
  • Keep listing reads separate from purchases, subscription renewals, offer-marker maintenance and content-management mutations. Preserve existing records, page IDs, prices, roles and grants.
  • Add responsive light/dark styling, keyboard controls, RTL logical spacing and an optional FansPaysite 2.7.10 token bridge without requiring that theme.
  • Default optional public credits off on fresh installs, retaining existing explicit choices. Clarify optional external services, payment-provider dependencies and media-origin limits.
  • Make Classic workspace navigation reversible through native Cards, List and Feed links.
  • Harden frontend editing, public activity summaries, password/private download previews, CSS output and linked product ownership. Keep approved moderated media changes in the supplying plugin’s review workflow while allowing commerce edits.
  • Use unique core media uploads and retain shared image files when removing images from an item.
  • Require confirmed wallet debits before grants or recipient credits; correct coauthor recipients, coordinate internal balance writes and record failed settlement legs for manual reconciliation. Purchase and subscription changes require POST.
  • Check timed subscription grants at access time and process every creator’s renewal/termination independently.
  • Add per-subsite internal commerce data on multisite while leaving existing single-site data keys and purchases unchanged.
  • Retain ambiguous legacy network records for explicit network-administrator preview/adoption; do not clone balances across sites or automatically change roles.
  • Recognize native site-local myCRED and require site/account/unit approval for confirmed shared myCRED/TeraWallet configurations; keep unknown providers unavailable.
  • Ship English-first and preserve the Spanish PO/MO as a separate review draft; leave community language packs and custom translations untouched.
  • Remove bundled remote font/emoji requests and refresh asset cache versions so browsers request the reviewed local styles.
  • Require WordPress 6.9 and PHP 8.2 or newer.

3.2.14

  • Security: protect restricted content and excerpts in REST responses, feeds and listings.

3.2.13

  • Security: require a nonce-protected POST form for administrator membership removal.

3.2.12

  • Security: require a nonce and administrator capability to delete a membership from the admin users list; only update or delete the linked WooCommerce product when it is a product post.

3.2.11

  • Avoid uploader warnings and asset/activity links when the optional seller page has not been configured.
  • Security: isolate staged uploads by authenticated uploader and enforce the configured seller/upload policy on the upload endpoint.

3.2.10

  • Hardened server-side donation amount validation.

3.2.7

  • Moved screenshots to SVN assets and updated WordPress.org support metadata.
  • The generated Add Recording page now uses the selected VideoWhisper recorder
    app, so the bundled Free recorder is used by default and the legacy app stays
    available from recorder settings.

3.1

  • Creator stats with subscriptions and earnings
  • Code improvements

2.9

  • Guest upload shortcode [videowhisper_content_upload_guest] with reCaptcha, email notification, visitor support

2.8

  • Content listing tabs
  • Contet type tabs: All, Video, Picture
  • Access filter tabs: All, Subscription, Paid, Premium, Free

2.7

  • Coauthors: asset owner can add coauthors to share earnings, with custom percents for each, from asset edit page
  • List author and coauthors on content page (for set post types) with links to their BP or WP pages
  • Coauthors can access their content (similar to moderators)
  • Add/remove featured image when editing content (post)

2.6

  • Hide comments with paid content (option)
  • Limit comments per user (per post), except author

2.5

  • Separately customizable author earning ratio for donations, content sales, subscriptions
  • Minimum/maximum limits for subscription cost (that authors define)
  • Moderator roles can access content without paying

2.4

  • BuddyPress/BuddyBoss user tabs with author content
  • BuddyPress/BuddyBoss user tabs with author subscriptions
  • My Subscriptions page, shortcode for client to list and manage subscriptions

2.3

  • Author Subscription
  • Translation POT file
  • Integrate HTML5 recording
  • Integrate posting to BuddyPress/BuddyBoss/PeepSo with asset mentions
  • Micropayments paid content handler with custom access price and duration (hours), in addition to WooCommerce products and MyCred Sell Content

2.2

  • Donation goals
  • Crowdfunding

2.1

  • Content Upload page integrates Plupload to handle uploads as Documents (Downloads), Videos, Pictures
  • Quickly post to PeepSo activity stream

1.9

  • Paid content list aggregating multiple post types

1.8

  • Content dashboard for sellers and buyers

1.7

  • WooCommerce paid content integration

1.6

  • Downloads manager
  • Publishers can upload files
  • Files access can be restricted by membership
  • Pay per download

1.5

  • TeraWallet/WooWallet integration (with WooCommerce billing options)
  • Multi wallet support (MyCred + WooWallet)
  • Wallet user page with shortcode [videowhisper_my_wallet]
  • Semantic UI frontend interface integration

1.4

  • Control access to content by membership / role, from backend contend editor
  • Delete membership for user
  • Protect administrator accounts from changing role with membership

1.3

  • Edit content on a custom page /edit-content/?editID=[post id]
  • Set paid content with mycred plugin
  • Automatically detected and integrated for VideoShareVOD videos
  • Only owner and administrator can edit

1.2

  • Improvements

1.1

  • Original release