VidFlow AI

By Vidflow-AI

0+ active installationsVersion 1.1.1

Create, embed, and publish AI videos in WordPress with Google or Hailuo. Bring your own API key; provider usage is billed separately.

Description

Create AI videos, manage them in WordPress, embed them in posts and pages, and publish them to YouTube.

Connect your own Google AI Studio or Hailuo AI / MiniMax account. The plugin is free; your chosen provider bills you for API usage or credits.

Kling is deprecated and closed to new connections. Free-only sites with an existing saved Kling API 2.0 key can continue using it while Pro is deactivated. Activating Pro disables new Kling generation, regardless of license status. Current live Kling compatibility is unverified.

Free features

  • Create from text or images: Use a prompt and optional Start or End Frames, depending on the model.
  • Manage your video library: Search and filter videos, preview and download completed results, and review failed jobs before retrying.
  • Embed in posts and pages: Add completed videos with the VidFlow Gutenberg block or a shortcode.
  • Publish to YouTube: Upload completed videos in the background and review their publishing status and links.
  • Video storage: Hailuo videos stay with the provider by default; protected Media Library copies are optional. Google videos are always saved locally. Local files use short-lived playback and download URLs.

Provider and OAuth secrets are encrypted in WordPress. Settings include completion audio, privacy controls, and uninstall cleanup options.

VidFlow AI Pro

Pro is a separate paid add-on that requires Free and an active Pro license. Update Free before installing Pro.

  • WooCommerce Product Videos: Create or assign videos on product pages. Requires WooCommerce 8.0 or later.
  • Product video styles: Choose a built-in style or describe your own. Custom prompt mode uses prompts and images you supply.
  • AI storyboards and opening images: Prepare product-video scenes and Google Gemini opening images in Auto mode, then review them in Create Video.
  • Camera presets: Choose camera movements for supported Google and Hailuo models.
  • Projects and reusable assets: Keep related clips and source assets together.
  • Batch runs: Submit and track multiple generations, retry failures, or cancel a run.
  • Video merging: Combine project clips in a supported browser, then embed or publish the result.
  • Prompt templates: Save prompts to use again.
  • Generation history: Review prompts and settings from earlier generations.
  • Library tools: Mark favorites and use advanced filters.

Pro does not include provider credits. Auto can incur text and opening-image charges before video review. Video generation and image regeneration are billed separately by your provider.

See Pro features and plans.

External Services

The plugin contacts external services when you configure or use the related feature. Requests go directly from your WordPress site to the selected service.

Kling AI (Kuaishou) — deprecated connector

New Kling connections are closed. Sites with a previously saved API 2.0 key can use the deprecated connector while Pro is deactivated. Activating Pro hides Kling from Settings and blocks new Kling generation, regardless of license status. Deactivating Pro restores saved-key access. Removing the key after existing jobs settle prevents reconnection through this version. Existing jobs, media, and embeds are preserved; legacy AK/SK credentials support only existing-job polling. Completed videos stay with Kling unless protected Media Library storage is enabled. Current live compatibility is unverified, and provider-hosted media depends on provider availability.

Used to validate credentials, read remaining resource-package usage on the Settings page, submit generations, poll status, and retrieve generated media URLs. New requests use https://api-singapore.klingai.com; legacy jobs may continue polling at https://api.klingai.com.

Opening Settings or choosing Refresh sends your saved API key and an account-usage date range. Connection tests send your key and a one-day usage range. Neither action generates a video. Generations send your key, prompt, model/settings, and supplied frame data. Status checks send credentials and the saved task ID. Kling may return usage data, task status, errors, and hosted media URLs.

Terms: https://kling.ai/docs/user-policy | Privacy: https://kling.ai/docs/privacy-policy | API terms: https://kling.ai/document-api/protocols/paidServiceProtocol | API privacy: https://kling.ai/document-api/protocols/privacyPolicy

Hailuo AI / MiniMax

Used to validate credentials, submit generations, poll status, and retrieve media URLs through https://api.minimax.io. Requests may send your credential, prompt, model/settings, supplied frame URL or data, and saved task ID. MiniMax may return task status, errors, and hosted media URLs.

Terms: https://www.minimax.io/terms-of-service-v2.html | Privacy: https://www.minimax.io/privacy-policy-v2.html | Hailuo terms: https://hailuoai.video/doc/terms-of-service.html | Hailuo privacy: https://hailuoai.com/doc/privacy-policy.html

Google (Gemini API)

Used for video generation, status checks, recovery of earlier jobs, and result downloads through https://generativelanguage.googleapis.com. Saving the Google API key does not contact Google.

A generation sends your key, prompt, model/settings, and supported Start/End Frame images. Gemini Omni 1.1 Flash produces one 3–10-second video with native audio in landscape or portrait at 360p, 720p (default), 1080p (upscaled), or 4K (upscaled). Use text, a Start Frame, or a Start Frame with an optional End Frame. An End Frame requires a Start Frame; matching images do not guarantee seamless motion or product fidelity.

Google stores background interactions for status recovery. Paid interaction retention defaults to 55 days and can be shortened in AI Studio; generated files generally expire after 48 hours. VidFlow saves completed videos to protected local Media Library storage before marking them complete. Downloads may redirect to Google media hosts without forwarding your API key. Google’s billing, quota, region, and access rules apply.

Gemini API terms: https://ai.google.dev/gemini-api/terms | Google privacy: https://policies.google.com/privacy

Google OAuth and YouTube

Used only when you configure and connect YouTube or queue a completed video for publishing. OAuth uses https://accounts.google.com and https://oauth2.googleapis.com; channel checks and uploads use https://www.googleapis.com.

Connection sends your OAuth client details, authorization code, redirect URI, requested scopes, and tokens as required by Google. Publishing sends the video’s bytes, title, description, tags, category, and visibility. Google may return channel details, tokens, upload status, errors, and video URLs.

YouTube terms: https://www.youtube.com/t/terms | Google privacy: https://policies.google.com/privacy | YouTube API terms: https://developers.google.com/youtube/terms/api-services-terms-of-service

Provider-hosted media and remote frames

Preview, download, validation, thumbnail, or import actions may request provider media or remote frame URLs from your WordPress server. The receiving host sees your server IP, requested URL, and normal HTTP metadata. VidFlow does not add WordPress account data or plugin settings to these requests.

Provider media is governed by the selected provider’s terms and privacy policy above. No analytics, tracking, or VidFlow-hosted telemetry request is sent by the plugin.

Installation

PHP security requirements: 8.2.35+, 8.3.36+, 8.4.27+ or 8.5.12+ within the same PHP branch. Startup and activation are blocked on unsupported PHP. Credentials, history and recovery data are retained; processing resumes after PHP is patched. Unknown future PHP branches and prereleases require review. Disable session.upload_progress.enabled in the web-server PHP configuration; VidFlow does not use PHP session upload progress. This supplements, and does not replace, PHP patching.

  1. Install VidFlow AI through WordPress or upload it to /wp-content/plugins/vidflow-ai/.
  2. Activate the plugin.
  3. Open VidFlow AI > Settings and save credentials for a supported provider.
  4. Open Create Video, choose a model, enter a prompt, and add any supported frames. Submit the generation.
  5. Open Video Library to preview, download, or embed the completed video. For YouTube publishing, connect your channel in Settings first.

FAQ

Is VidFlow AI Free really free?

Yes. Video creation, the library, embeds, and YouTube publishing are included. You need your own provider account and pay that provider for API usage or credits.

How do I embed a video?

Add the VidFlow block in the WordPress editor and select a completed video, or use [vidflow id="123"] in a Shortcode block. Replace 123 with the video’s VidFlow record ID, not a Media Library attachment ID.

What do I need to publish to YouTube?

You need a Google OAuth client ID and client secret for your site, then authorize access to your channel. Follow the setup guidance in VidFlow AI > Settings. Your AI provider connection does not connect YouTube automatically.

Do I need WooCommerce?

No. Only Pro’s WooCommerce Product Videos feature requires it.

Does work continue after I leave the page?

Yes. Status checks and queued uploads continue through WordPress scheduled tasks. If progress stops updating, check that those tasks are running.

What limits local video storage?

The default download/import limit is 128 MB per video when no valid saved limit exists. Existing saved limits, including 256 MB, are preserved. Change the limit in Settings > Media. Google results must finish saving to protected local storage before they are complete. Hailuo and retained Kling results may remain provider-hosted unless local storage is selected. Browser upload and host limits are separate. Provider media URLs can expire; keeping a library record does not guarantee that its remote video remains available.

Can editors embed videos?

Administrators manage generation, settings, the shared library, and publishing. Users who can edit posts can use the VidFlow embed block or shortcode with shared completed videos.

What happens if generation fails?

Video Library shows the provider error when available. Check your credentials, credits, model settings, source images, and scheduled tasks before retrying. A retry may consume provider credits.

Why does an embedded video stop playing on a cached page?

Signed playback URLs expire and must refresh when the page loads. Exclude /vidflow-video/*, /wp-json/vidflow/v1/public-video-url*, and ?rest_route=/vidflow/v1/public-video-url* from page, CDN, and firewall caching. If you use JavaScript optimization, do not delay assets/js/embed-refresh.js until user interaction.

What happens if I uninstall VidFlow AI?

By default, uninstalling keeps plugin data and files. Enable “Delete plugin records on uninstall” in Settings to remove VidFlow records, related settings, caches, and logs. Media Library files, provider-hosted videos, published uploads, and post content remain. On multisite, each site’s setting applies separately.

Screenshots

Changelog

1.1.1

  • Log redacted Google API error explanations when WordPress debugging and debug logging are enabled.
  • Added 64 MB, 100 MB, and 128 MB options for the maximum downloaded video size.
  • Added a Create Video and Video Library warning when background generation status checks appear stalled.
  • Added optional Google Omni End Frames to Create Video, with image validation and protection against changed frame pairs before submission.
  • Added faster status checks on Create Video and a Library refresh that checks all generating videos.
  • Added Google API key security guidance beside Google settings, with exact restriction steps, stolen-key protection limits, and instructions for a compromised website.
  • Added Google video generation with maintained model choices, text or Start Frame input, background status checks, and required protected local storage.
  • Added one encrypted Google API key shared by video generation and compatible Pro Gemini prompt and image tools.
  • Added resolution, orientation, and duration details to Video Library previews when generation metadata is available.
  • Added compact remaining-balance status to connected generation providers, with details on demand, manual refresh, stale-data fallback, and a MiniMax billing link.
  • Removed fixed Product Video style totals from Pro feature descriptions.
  • Updated the tested WordPress version to 7.1.
  • Discourage browser autofill, password suggestions, and writing predictions in Settings API key and publishing destination credential fields.
  • Clarified Google End Frame data sharing, the 128 MB storage default, provider retention limits, and current Pro documentation.
  • Show the available Pro add-on, its feature list, and a link to VidFlow AI on Free admin screens.
  • Show only the elapsed clock while a new video is being created.
  • Shortened End Frame guidance in Single Create.
  • Matched the Start and End Frame selection buttons with “Choose image” on Create Video.
  • Check generation status every minute in the background, with a 30-minute timeout and recovery of saved provider jobs from the Library.
  • Lowered the default video import size limit to 128 MB while preserving saved limits and larger size options.
  • Clarified required Google storage, optional provider imports, and per-video download limits; separated download diagnostics from optional browser upload configuration examples.
  • Raised the minimum supported WordPress version to 7.0.
  • Raised the minimum supported PHP to 8.2.35, with patched releases required in each supported PHP branch.
  • Corrected the bundled privacy notice: activating Pro blocks new Kling generation, while saved credentials, history and accepted-job recovery remain preserved.
  • Shortened readme feature and setup guidance, removed repeated explanations, and moved uninstall guidance into the FAQ.
  • Clarified Pro Auto preparation charges and browser requirements for merging, matching the Pro feature guide.
  • Expanded Pro feature guidance with product-video prompt and opening-image tools, camera presets, batch controls, merged-video workflows, and separate provider charges.
  • Kept legacy Kling generation on saved-key Free-only sites. Activating Pro hides Kling from Settings and Create and blocks new submissions; deactivation restores Free access without changing saved data or task recovery.
  • Clarified GPL rights, consumer protections, Freemius-based business liability limits, proportionate suspension, limited business indemnity and advance notice of material Terms changes; the first-purchase refund guarantee is unchanged.
  • Updated bundled legal notices with email-only support, privacy disclosures and a 14-day, no-questions-asked refund for the first Pro purchase; provider charges remain separate and mandatory consumer rights are preserved.
  • Placed the Kling warning directly below the platform buttons on Create Video.
  • Deprecated Kling for new connections; retained saved-key sites with notices, protected pending-job recovery, and ended reconnection after explicit key removal. Current live Kling compatibility is unverified.
  • Kept upload results bound to the queued media revision and actual transferred bytes; refused changed resumable sources and prevented stale workers from restoring current publication status.
  • Renewed typed published players in cached embeds without treating platform iframe URLs as downloadable video files.
  • Grouped Library card actions in a keyboard-accessible gear menu with clear labels and larger touch targets; kept Publish and configured inline actions visible beside it.
  • Standardized Google platform identifiers, API fields, job metadata, and generated video filenames before release.
  • Maintained bundled Google video price estimates through plugin updates instead of a calendar expiry.
  • Kept extension-provided generation details beside the Generate video button.
  • Corrected the bundled privacy policy to describe Support email and forum links after removal of the website Contact form.
  • Expanded Gemini Omni video output to 360p, 720p, 1080p (upscaled), and 4K (upscaled), with 3–10-second clips at every size and 720p as the default.
  • Standardized the video provider name as Google across settings, help, recovery messages, documentation, and readmes.
  • Opened published external links directly from block previews instead of loading them as embedded players.
  • Updated Google video generation to Gemini Omni 1.1 Flash through the Interactions API, with text/image video, 3–10-second choices, protected local saving and saved-job recovery.
  • Required explicit replacement of removed model selections; preserved accepted legacy Google operation recovery and prevented incompatible older add-ons from submitting new Google images.
  • Reduced optional YouTube player clutter in frontend blocks and shortcodes while retaining playback controls and required YouTube features.
  • Kept video-list cache revisions stable until source changes, allowing add-ons to retain cached lists for longer.
  • Kept shared video-list filters consistent for add-on queries and treated a search for zero as a record-ID search.
  • Kept Create Video’s handoff screen visible until an add-on acknowledges its loaded controls and restored draft.
  • Used maintained video model lists without model-access checks or expiry; saving a Google key stays local and provider errors never trigger automatic resubmission.
  • Kept sidebar extension controls synchronized with the current video settings.
  • Allowed add-ons to match frame-action labels, appearance, and placement while preserving native frame-selection locks.
  • Allowed add-on Create workflows to place supported settings inside their own item controls while preserving Single settings.
  • Supported compact outlined frame actions and add-on action ordering while preserving the default Free frame controls.
  • Allowed add-ons to submit a reviewed Single draft through a queued receipt and display its real video in the normal generation view; requires matching updated Free and Pro versions.
  • Kept add-on frame actions beside selected Start Frame previews and honored protected frame selections.
  • Kept storyboard planning, Gemini text catalogs, merged-video publishing notices, and project asset selection in the Pro add-on while preserving shared Free workflows.
  • Made Free settings and Google key-removal guidance describe the features available in Free.
  • Allowed a Create Video handoff to provide its own settings review without saved Create preferences changing that workflow’s effective settings.
  • Standardized API-key fields, connection actions, removal confirmation, and billing guidance across generation provider connectors.
  • Used one shared Google key for video generation and Gemini, removing the pre-release key migration step.
  • Simplified Google connector setup, shared the API-key guide with Gemini, and kept connection status in sync.
  • Kept an add-on’s processing view visible until its Create Video draft is ready for review.
  • Allowed Create Video handoffs to resume an add-on workflow and keep its requested creation mode selected.
  • Renamed the beauty-product starter example to “Beauty product video” in Create Video prompt help.
  • Clarified generation timing, provider credentials, publishing, storage, and uninstall guidance; improved interface labels and translated video counts.
  • Collapsed connector cards by default, made each card resize independently, grouped provider balances inside their expandable setup areas, and replaced text refresh actions with compact icons.
  • Allowed add-ons to validate complete Create Video requests before provider submission.
  • Clarified when saved provider credentials are sent for connection, credit, generation, and status requests.
  • Renamed the Settings page heading and broadened its introduction so licensing, connections, notifications, media, and privacy share one clear settings home.
  • Removed the “Latest” tag from Kling and Hailuo model selector labels.
  • Reduced WordPress.org download size by excluding development-only frontend source and Node build files from release packages.
  • Scaled video-library and publishing-activity lists with stable cursor pagination, optional totals, bounded maintenance queries, and resumable database upgrades.
  • Moved generation status checks out of browser requests into a bounded, leased background coordinator with site and provider concurrency caps, queue health, and a small WP-Cron fallback.
  • Isolated generation, publishing, Media Library import, and maintenance work into dedicated background queues.
  • Correct Video Library ages across browser timezones and display creation timestamps in the WordPress site’s timezone, including daylight-saving changes.
  • Clarify Google video errors, direct users to review existing requests in Google AI Studio, and advise trying later when generation continues to fail.
  • Recover successful Google URI videos when optional result metadata is absent, and keep checking accepted tasks after temporary result or download failures without submitting another generation.
  • Explain Google video submission failures with specific connection, access, quota, or response guidance while preventing automatic resubmission.
  • Restored the Pro teaser’s desktop columns, with its introduction and link on the left and features filling the right panel.
  • Keep saved credential indicators and connection checks synchronized after saving, replacing, or removing a provider key.
  • Preserve unsaved API keys and YouTube credentials during unchanged Settings refreshes and after local credential saves or removals.
  • Keep the last known provider balance when a refresh returns a temporary error, including concurrent settings requests.
  • Renew protected embed playback when a video source fails before loading.
  • Restored Free package builds with Google Start and End Frame support.
  • Kept local generating-modal previews out of production bundles and release packages.
  • Restored validated add-on diagnostic context while retaining secret and provider-payload redaction.
  • Updated the Google API key security link to open Google’s current restriction guidance section.
  • Preserved locked Product Video frames when applying another saved draft.
  • Restored keyboard focus to the frame controls after choosing or removing an image.
  • Fixed literal count and link placeholders in standalone and WooCommerce-bundled Action Scheduler past-due warnings.
  • Restored the visible Generating video title and elapsed-time label in the Create Video progress modal.
  • Kept credentials, provider messages, media URLs, and request details out of debug logs and PHP exception traces.
  • Prevented concurrent VidFlow database upgrades from trying to add the same table column twice.
  • Disable Generate immediately after a click and keep setup, submission, or status-check errors visible in the video modal.
  • Blocked new provider requests when status polling cannot be scheduled, and kept saved tasks recoverable when scheduling fails.
  • Cleared old provider cooldowns when resuming a saved task and applied polling timeouts even when provider check slots are full.
  • Matched the Single Create frame Remove buttons to Batch and hid extra frame selection actions after choosing an image.
  • Kept the Create Video elapsed timer moving while status checks run.
  • Started the Create Video elapsed timer when the request begins, so it counts from the first second shown in the modal.
  • Fixed Google video saving when a background request had not loaded the WordPress file helpers.
  • Fixed provider-hosted video thumbnail generation on sites using plain permalinks.
  • Recovered video downloads from valid provider URLs when saved local files are missing, and returned a clear error when a file becomes unreadable before streaming.
  • Served saved local videos without an HTTPS loopback, preventing local development certificate errors when fetching video files.
  • Kept shortcode copy feedback visible below its Library action, matched keyboard focus to VidFlow styling, and made action menus narrower with dark popover edges.
  • Kept admin screen headings within WordPress’s existing page landmark for assistive navigation.
  • Updated admin screens to use the current WordPress React mounting API, removing legacy React warnings.
  • Restored authenticated video downloads for editing and merging clips stored in protected local media.
  • Kept embedded-video URL renewal working on sites using plain permalinks.
  • Renewed signed thumbnail and playback URLs after cached video reads, including editor and public-token lookups.
  • Restored saved local reference images after protected-storage moves and read protected references locally instead of requiring an HTTP download.
  • Allowed protected thumbnails to renew independently when their video remains provider-hosted.
  • Preserved admin icon shapes and colors with both filled and stroke-based WordPress icons.
  • Preserved all stored records, caches, recovery state and logs on uninstall unless the site’s deletion preference is enabled; honored separate multisite preferences and retained consent for dependent plugins removed later.
  • Applied consistent side and bottom spacing to the publishing dialog footer.
  • Prevented duplicate publishing jobs and kept queue limits intact when database reads fail.
  • Kept video and publishing migrations retryable after database read failures.
  • Updated the privacy policy to describe maintained Google models and local key storage accurately.
  • Made connector save confirmations translatable and clarified the Google API key guidance for server requests.
  • Restored the saved uninstall preference and showed an error when a setting change could not be saved.
  • Kept incomplete database setup and upgrades retryable until all required tables, columns, and indexes are available.
  • Reported failed publishing-details saves and stopped queueing until the details can be saved.
  • Prevented concurrent Google connection changes, video imports, private media repairs, and balance refreshes from replacing another worker’s lock.
  • Kept provider credentials unchanged when active generation jobs could not be read from the database.
  • Preserved authenticated protected-thumbnail identity across refreshed preview links for integrations, without extending link expiry or bypassing revocation.
  • Restored legacy publishing history and active-job recovery through a bounded, retryable upgrade repair, including sites that finished the earlier migration.
  • Prevented simultaneous requests from creating duplicate background polling coordinators, with automatic recovery after interrupted scheduling.
  • Kept Library filters visible and keyboard reachable on narrow screens.
  • Prevented overlapping generation retries and preserved accepted or uncertain Kling and Hailuo jobs through recovery.
  • Recovered failed Media Library imports without duplicating owned files.
  • Preserved videos and media after failed deletion, and allowed interrupted cleanup to resume when deletion is tried again.
  • Honored valid byte ranges extending beyond the video’s end.
  • Used 1080p for Kling 2.6 End Frames and native audio while preserving the selected audio setting.
  • Checked final Kling prompts against the selected model’s character limit before submission.
  • Kept confirmed publications successful when local status updates fail, with bounded local repair that never uploads the video again.
  • Recovered YouTube upload sessions from acknowledged bytes when a progress response omits its Range header.
  • Fixed repeated existing-media protection failures on Windows, preserved interrupted repairs and attachment metadata, and cleared the repair notice only after protection completes.
  • Kept late responses from replacing current Library filters, embed previews, or publishing status after changing videos.
  • Stopped YouTube uploads when chunk acknowledgements stall, rewind, or exceed the sent bytes, while preserving the saved upload session for recovery.
  • Stopped Hailuo connection checks from reporting success for failed HTTP requests or malformed provider responses.
  • Kept development test polyfills out of production ZIP packages even when absent from Composer metadata.
  • Kept reviewed add-on drafts current after cancelling generation confirmation.
  • Kept supported Google model choices visible on Create Video without a provider access check.
  • Prevented generation or batch submission while provider fields are still loading.
  • Kept the Create Video settings panel visible with a loading indicator while switching platforms.
  • Added missing Google AI Studio balance guidance and a direct billing link to the Google settings card.
  • Kept connector action buttons on the same line when their loading indicator appears.
  • Added a three-second confirmation tooltip when a Video Library shortcode is copied.
  • Prevented API-key removal while Kling or Hailuo jobs still need their credentials, and let legacy Kling credentials be removed explicitly.
  • Refreshed Create Video connection status after shared Google key changes without clearing the video draft.
  • Kept accepted Google jobs on their original operation during recovery, blocked uncertain resubmissions, and rechecked access and credentials before safe retries.
  • Preserved unsaved Google API keys when returning to connector settings.
  • Required renewed approval to abandon Google recovery when the affected jobs change.
  • Prevented ambiguous Google submissions from being resubmitted automatically and kept generated results incomplete until their authenticated local copy is saved.
  • Corrected Pro feature wording in the Free readme so release packaging completes.
  • Restored background generation status checks so accepted videos no longer remain stuck generating when polling jobs run.
  • Loaded the shared VidFlow AI admin palette on hidden license and billing pages.
  • Cleared argument-bearing WP-Cron fallback jobs when VidFlow is deactivated.
  • Fell back to WP-Cron when Action Scheduler is loaded but not initialized yet, preventing early one-off and recurring background jobs from being dropped.
  • Aligned saved connector labels and values consistently in Settings.
  • Rejected Hailuo requests whose final prompt exceeds the provider limit before any provider request is sent.
  • Restored frontend embeds for provider-hosted videos when Media Library storage is disabled.
  • Restored resumable publishing-status database upgrades so existing video libraries no longer retry malformed aggregate queries.
  • Kept the last known provider balance visible after a failed refresh and prevented older credit checks from replacing results after credentials change.
  • Reset every Create Video request field only after a completed generation while preserving the full draft after submission, polling, or provider failures.
  • Let extensions clean up related records immediately after a video is permanently deleted.
  • Kept Video Library status polling active when an in-progress check returns no change, so completed cards update without a manual refresh.
  • Kept large-site database upgrades resumable when an individual migration query fails or a large schema change needs explicit approval.
  • Refreshed public-token, pending-import, and attachment lookups immediately after video changes.
  • Reported publish-state projection failures instead of confirming stale library status.
  • Stopped partial Publishing Activity pages from offering an empty follow-up page.
  • Cleared deleted Media Library attachment references with bounded memory while immediately refreshing cached videos.
  • Removed per-video publishing-status queries and total-library ID loading from filtered library requests.
  • Kept Publishing Activity source labels and open-action wording accurate when the original source record is no longer available.
  • Stopped retrying rejected YouTube credentials, failed overdue background jobs, and added a safe way to stop queued retries so videos no longer remain locked in Publishing.
  • Reported and retried publishing-summary persistence failures instead of confirming recovery while the source could remain locked in Publishing.
  • Restored missing recurring background actions automatically and cleared all plugin-owned queues on deactivation.
  • Protect sensitive arguments and transport failures without changing other plugins’ PHP tracing or error handlers.
  • Kept Google API keys out of video retrieval exception traces and retained uncertain provider jobs for recovery.
  • Blocked startup and activation on PHP releases below the required branch-specific security patches, preserving credentials, history and recovery data until PHP is updated.
  • Validated reference-image types from their contents before video generation and returned safe errors for malformed images.
  • Rejected invalid YouTube upload destinations before transferring or resuming video data.
  • Validated downloaded video content before proxying it, rejected unsupported or incomplete responses, and prevented browser MIME sniffing.
  • Rejected unsupported playback URL schemes and preview types while preserving signed links and safe fallback playback.
  • Prevented provider credentials, OAuth secrets, and video upload data from being forwarded through HTTP redirects.
  • Rejected oversized local reference images before loading their contents into memory.
  • Kept imported generation prompts out of attachment titles, restricted VidFlow media metadata and edits, and stored generated thumbnails with protected originals and signed previews. Preserved authorized previews on the native Edit Media screen.
  • Added a retryable background repair for existing VidFlow media files and image sizes, preserving user-edited titles and reporting incomplete protection.
  • Guarded uploads file writes, moves, and log appends against symlink destinations, and kept case-distinct Unix directories outside the uploads boundary.
  • Kept HTTPS certificate verification enabled when proxying videos from the same site.
  • Rechecked the initiating administrator’s permissions before completing a YouTube connection.
  • Cleaned up rejected YouTube upload downloads and stopped automatic retries for sources above the upload limit.
  • Restricted Google model checks, Google operations, and authenticated result downloads to bounded trusted endpoints without forwarding credentials to media redirects.