Livid – Video Hosting

By Livid

★ 5.0/5 (3 ratings)300+ active installationsVersion 2.2.1

Embed Livid videos and migrate from Vimeo to Livid seamlessly.

Description

Livid is a video hosting platform. This plugin serves two purposes:

  1. Enable Livid embeds — Register Livid as an oEmbed provider so pasting Livid URLs into WordPress automatically creates video embeds, just like YouTube or Vimeo.

  2. Migrate from Vimeo — Scan your WordPress post content for Vimeo videos and replace them with equivalent Livid videos via the Livid platform.

Key Features

  • Automatic embeds — Paste any livid.com URL and it auto-embeds
  • Page builder ready — Native Livid Video elements for Elementor, WPBakery, Avada Builder, and Bricks, a Livid video type in Slider Revolution, plus a [livid_video] shortcode
  • Avada playback — Click-to-load previews, existing on-page iLightbox galleries, container video backgrounds, and playback controls for supported post/portfolio FlexSlider embeds
  • Divi playback — Native Video, Video Slider and Slide modules retain layouts, overlays and enabled responsive sources; native Text embeds receive Player.js lifecycle hooks. Saved Library, Theme Builder and Overlay sources are included in migration.
  • ACF scanning (opt-in) — Top-level text, textarea, URL, oEmbed and WYSIWYG values, preserving rich text and [embed] wrappers
  • Sensei LMS ready — Required-video completion, automatic lesson completion, and tab-away pausing; repeated required Livid embeds are tracked separately and mixed-provider lessons wait for all required videos
  • LearnDash ready — Livid lesson and topic embeds support LearnDash video progression, resume tracking, and completion
  • Supported-format scanning — Finds Vimeo iframes, Gutenberg embed blocks, bare URLs, [embed] and shortcodes, Elementor widgets, WPBakery elements, native Divi shortcode video fields, supported Avada elements and video fields, Bricks elements, and LearnDash lesson/topic progression URLs
  • Background processing — Scan and migration run as Action Scheduler jobs so they won’t time out on large sites
  • Safe replacement — Only replaces the specific videos you select through the Livid migration popup
  • Rollback data — Every changed source gets an immutable pre-write snapshot; main-content edits also retain tagged WordPress revisions when enabled
  • Permanent install — Keep the plugin active for continued Livid embed support

How It Works

The plugin registers Livid as an oEmbed provider, which is active immediately upon installation. For migration:

  1. Go to Settings > Livid, enable “Also check ACF custom fields” if needed, then click “Find Vimeo videos” (or “Search again”)
  2. The plugin scans supported post content, page-builder data, and LearnDash lesson/topic progression settings for Vimeo embeds
  3. A popup opens where you select which videos to migrate and map them to Livid video IDs
  4. The plugin rewrites the selected embeds in the background

Scope

Migration scans and rewrites post_content, supported page-builder data for Elementor (_elementor_data) and Bricks (_bricks_page_content_2), Avada’s _fusion.video_url, iframe sources in _fusion.video, active Slider vimeo_id fields and their verified legacy pyre_* equivalents, and LearnDash’s lesson_video_url setting for lessons/topics. It includes public post types, registered Divi Library, Theme Builder and Overlay sources, and registered Avada saved elements, templates, layout sections and Off Canvas records, in published, scheduled, draft, pending and private statuses. With “Also check ACF custom fields” enabled, it also scans top-level text, textarea, URL, oEmbed and WYSIWYG values using each post’s field reference. Iframe sources receive player URLs; links and [embed] URLs receive watch URLs, with HTML and closing shortcodes preserved. Number controls, nested/group/repeater fields, options-page, user and term fields are excluded. Global theme options, widget content and other post meta are not modified.

External Services

This plugin interacts with Livid in these ways:
1. Video migration
When you initiate a migration, the plugin sends a listing of Vimeo videos found on your site along with basic information about the pages they appear on. This is necessary so that Livid can match the Vimeo videos on your site to the ones you have uploaded to your Livid account. No data is sent unless you actively start a migration.
2. oEmbed provider
This plugin registers Livid as an oEmbed provider in WordPress. When a Livid video URL is embedded in a post or page, WordPress will make a request to Livid’s oEmbed endpoint to retrieve embed information (such as the video title and player HTML). This happens whenever a post containing a Livid embed is edited or its embed cache is refreshed.
3. Video playback and previews
The visitor’s browser loads Livid players and preview images where they are embedded. For Avada click-to-load facades, WordPress requests public oEmbed thumbnail metadata and caches successful lookups for an hour and failures for five minutes. The browser loads the returned preview image before the player is opened; the player iframe is created when the visitor clicks the play button. Live Builder preview lookups use an authenticated same-site endpoint.
These interactions are in line with Livid’s terms of service and privacy policy.

Installation

  1. Upload the plugin files to /wp-content/plugins/livid-video-hosting/
  2. Activate the plugin through the ‘Plugins’ screen in WordPress
  3. Go to Settings > Livid to run a migration (optional)

Livid embeds work immediately after activation. Migration requires a Livid account.

FAQ

Do I need a Livid account to use this plugin?

No. The plugin enables Livid embeds for everyone. You only need a Livid account if you want to migrate existing Vimeo embeds.

Will this break my existing Vimeo embeds?

No. The migration only replaces the specific Vimeo embeds you select. Anything you don’t select remains untouched.

Can I undo the migration?

Main-content edits create a WordPress revision tagged with the migration run ID. Builder and LearnDash fields are not revisioned by WordPress, so the plugin saves an immutable pre-write snapshot for those sources. Use the editor’s Revisions screen to restore pre-migration main content when available; this may also undo later post edits. There is no general one-click rollback UI for builder/setting snapshots, which require developer assistance to restore. Back up your database before running a large migration.

What embed formats are supported?

Gutenberg embed blocks, raw iframes, bare Vimeo URLs (auto-embeds), [embed] and shortcodes, Elementor widgets, WPBakery elements (both [vc_video] links and Vimeo iframes inside raw-HTML blocks), native Divi shortcode Video, Video Slider and Slide URLs, supported Avada static elements and post/portfolio video fields, Bricks elements (Video elements and Vimeo iframes inside rich-text elements), and LearnDash lesson/topic video-progression URLs.

Does Divi support Livid?

Paste a Livid URL into a native Divi Video module. Migration supports static shortcode Video and Video Slider src fields, Slide video_url fields, and their enabled tablet, phone and hover variants. Modules and design settings remain editable. Native fields in linked global-module instances are skipped; migrate the saved Library source and review selectively unsynced local overrides. Registered Library, Theme Builder header/body/footer and Overlay source content is scanned too. Player.js playback handles overlays, automatic slideshow timers, pause/end/seek/time updates, responsive reloads, hidden players and compatible Video Popup (vp-a / vp-s) close controls. Authored posters and supported URL privacy/playback options remain intact. Trusted Livid iframes in native Text modules also receive Player.js hooks, including when an opted-in ACF WYSIWYG field supplies the content. After successful content or ACF writeback, only the changed post’s derived Divi excerpt/date/first-image metadata is invalidated; rejected writes and no-op retries preserve caches. Keep Livid active after migration and clear external page caches.

Essential Grid 3 galleries and inline players can play trusted Livid URLs through their native interactions, including gallery groups, captions, navigation and close/filter cleanup. Custom-source Vimeo items in Essential Grid’s native table are scanned separately and selected by grid, with immutable backups and protection against concurrent edits. Shared grid changes affect every page using that grid. Post-based and alternate grid sources require separate review. Successful writes invalidate the changed grid’s native caches; clear external page caches after migration. Arbitrary dynamic sources, background videos, third-party module data, global presets and Divi 5 native blocks are not automatically migrated. Diagnostics include a Divi source-readiness audit so unhandled sources remain visible. Custom Vimeo SDK calls need review.

Enable “Also check ACF custom fields (advanced)” to include supported top-level WYSIWYG and other text-like post fields. Scan results distinguish unique Vimeo videos from source placements. Unsupported or malformed grid values remain unchanged and are reported for review. Nested/repeater/group, options, user and term contexts need separate review.

Tested native baselines are Divi 4.27.4, Essential Grid 3.0.14, Video Popup 1.1.4, ACF 6.5.0 and Divi Machine 8.2.15. Native desktop Chrome checks cover playback hooks, slider/gallery navigation, popup close/reopen, fullscreen and hidden-player cleanup. These checks do not establish support for every version, live editor or consent configuration, physical mobile browsers, or real cloud imports. Divi Machine and other licensed integrations are installed separately and are not bundled. See the plugin README’s support matrix for setup and limits.

Are there known playback limitations?

Very narrow hosted embeds (observed at 204px wide) can clip fullscreen, picture-in-picture and settings controls when More controls is expanded or after resizing from desktop to a narrow viewport. Core playback still works. This hosted-player issue is not corrected by the WordPress plugin.

Divi slider transitions may replace the outgoing iframe before its player sends a pause reply. Playback stops, but custom integrations must not require a pause event before iframe replacement or removal.

Does Avada Builder support Livid?

Add a Livid Video element in Avada Builder or use [fusion_livid_video url="https://livid.com/watch/VIDEO_ID" /]. The element supports a Live Builder preview, native layout settings, accessible title, start time, autoplay, mute and loop. Video Facade follows the element’s on/off setting or Avada’s default and shows a Livid thumbnail with a play button before loading the iframe.

Migration covers static [fusion_vimeo] elements, Lightbox video URLs, button/column links, container video URLs and numeric Vimeo IDs, supported sources in encoded Code Blocks, modern _fusion post/portfolio and active Slider video fields, and the verified legacy pyre_* equivalents when still active. Existing on-page iLightbox galleries keep their groups, captions and navigation; background videos keep the container layout, cover sizing, mute and loop controls. Supported post/portfolio FlexSlider embeds use Player.js for playback and slide changes. Registered fusion_element, fusion_template, fusion_tb_section and awb_off_canvas content is scanned too. Metadata edits have an immutable pre-write snapshot.

Native dynamic Vimeo elements and container backgrounds can render a Livid URL returned by Avada’s resolver while retaining the source binding. Diagnostics reports all Vimeo-bearing option records and Avada dynamic video bindings, with exact field paths and known owners; private tokens and full setting values are omitted. Legacy pyre video fields are excluded and audited when a content layout or override filter could suppress them; the background scanner does not execute Avada’s context-dependent layout resolver or metadata promotion. Global options, widgets, arbitrary dynamic source fields/callbacks, malformed encoded blocks and unrelated private post types are not automatically migrated. Templates may resolve a different source on each page and need inspection of that actual source. Native programmatic iLightbox URL/array calls are supported. Modal/Off Canvas close events pause playback immediately, with visibility checks for hidden content. Vimeo-specific structured data, animations and arbitrary API options are not reproduced. The integration was checked against Builder 3.16.2 and Core 5.16.2 and does not claim complete Avada parity. Keep the plugin active and verify the surfaces used by your site after migration.

Custom bound iLightBox galleries using global smartRecognition: true must initialize after window.LividAvadaNative is available, or reapply the setting through the adapter-wrapped instance.setOption({ smartRecognition: true }). The native API cannot expose a custom gallery’s earlier recognition setting.

How do I enable Sensei video completion?

In the course editor, open Course Settings > Video. Enable Required to block completion until required videos end, Autocomplete lesson to complete automatically, and optionally Autopause. These settings affect the whole course; per-block required/optional overrides are respected. Completion requires the player’s ended event. This does not enforce watching every second or prevent seeking. Looping and unavailable required videos cannot complete the lesson. Tested with Sensei LMS 4.26.4.

For a safe trial, use a temporary draft course and lesson with a Livid embed and Sensei lesson-action blocks. Use Preview as Student, verify completion is blocked before the ending, then verify Completed persists after playback. Exit preview and move the temporary content to Trash. Sensei interactive-video overlays and Sensei-specific custom video fields are not supported by this integration.

Does the scan find every Vimeo reference?

The migration scans supported content sources, including standard embeds in Sensei lessons. It does not search server files, arbitrary custom fields, widgets, or options. Download diagnostics report under Settings > Livid for a broader read-only database check; the report indicates skipped tables, errors, and truncation.

Can migration progress overcount after a retry?

Re-executing an already-completed rewrite can count it again in migration progress, while leaving the content unchanged. Verify saved content and run a fresh scan after recovering interrupted jobs.

What happens to LearnDash learner progress after replacing a video?

Lesson and course completion records are not changed. LearnDash derives partial playback resume data from the video URL, so an in-progress playback position resets when that URL changes from Vimeo to Livid.

Changelog

2.2.1

  • Fix missing fullscreen controls on Livid URLs pasted into Avada text elements. Preserve the real iframe source through Avada’s lazy loader for oEmbed and rendered Livid embeds, using browser-native lazy loading while retaining existing permissions, sizing, and playback behavior.

2.2.0

  • Add Divi 4 shortcode Video, Video Slider and Slide migration, including enabled responsive sources and registered Library, Theme Builder and Overlay layouts. Preserve selected occurrences, native modules, playback flags, draft dates, existing slugs and GUIDs. Add Essential Grid custom Vimeo item migration with source-qualified selections, immutable backups, concurrent-edit protection and targeted cache invalidation. Retain large grouped jobs by verified payload reference. Add Player.js playback support for native Divi Video/Text/sliders, compatible Video Popup dialogs, Essential Grid 3 gallery/inline players and supported Divi Machine ACF Item contexts. Preserve layout, manual pause, source flags and explicit iframe permissions; cancel outgoing, hidden and removed players. Deliver bubbling playback events before teardown callbacks so page-level listeners receive inline-player completion. Include top-level ACF WYSIWYG fields under the existing opt-in, preserving rich text and adjacent [embed] wrappers. Clear only the changed post’s derived Divi caches after successful content or ACF writes. Clarify unique-video and placement counts, ACF scope and source-review warnings. Document tested integration versions and retain unsupported dynamic contexts, Divi 5 blocks and alternate grid sources for review. Gate packaging and publishing on repeatable PHP, JavaScript and production-package checks; keep optional native fixture coverage explicit. Document two known playback limits: very narrow hosted players can clip secondary controls after expanding More controls or resizing; Divi slider iframe replacement stops playback but can precede the player’s pause reply. Core playback remains functional; custom integrations must account for iframe removal without a pause event.

2.1.0

  • Add an editable Livid Video element for Avada Builder with native layout controls, title/start settings, inherited click-to-load facades and Live Builder previews. Add Player.js playback handling for hidden/dynamic content and supported post/portfolio FlexSlider embeds, plus adapters for existing on-page iLightbox galleries and container backgrounds. Migrate static Avada Vimeo elements, native lightbox/button/column/background URLs and numeric background IDs, encoded Code Block sources, and the modern _fusion post/portfolio and active Slider video fields. Support verified legacy pyre_* video fields only while Avada still reads them. Carry supported URL playback flags and start offsets. Include registered Avada library elements, saved templates, layout sections and Off Canvas records in scans. Preserve selected-occurrence locators, safe retries and immutable metadata backups. Keep the shared Vimeo SDK script while the rewritten source still contains unselected Vimeo iframes. Render native dynamically bound Vimeo elements and container backgrounds when Avada resolves their source to a trusted Livid URL, preserving bindings and dynamic layout/title settings. Add unsampled, redacted audits of every Vimeo-bearing option record, Avada dynamic source binding and legacy video field excluded because a content layout may suppress it. Global options and arbitrary dynamic source fields remain audit-only; do not infer a template source owner from a rendered fallback. This adds the documented Avada surfaces, not complete Vimeo-provider parity. Preserve saved URL playback options, skip inactive dynamically replaced fallback content, and protect encoded Code Block selections against content changes and reordering. Handle delayed player events and slider transitions without overriding a visitor’s pause, replay completed videos on return, and respect disabled slideshow rotation. Custom bound lightboxes using global smart recognition must initialize after the adapter or reapply their recognition setting through its wrapped API.

2.0.3

  • Fix disappearing dynamic Elementor videos when migrated ACF values contain iframe embed code. Render through a runtime skin before Elementor’s empty-output check, preserving shared template bindings and nested section rendering. Preserve escaped ACF field values during writeback so successful migrations are not incorrectly reported as failed. Resolve ACF fields using each post’s reference, verify complete URL tokens, migrate multiple video occurrences independently, and use player URLs for iframe sources. Reject changed field definitions and exclude numeric controls from alphanumeric ID replacement. Keep the latest completed migration summary and conflict reasons visible after reloading the admin page. Dynamic Elementor videos render inline; Vimeo-specific image overlays and lightboxes are not preserved. Real Elementor and ACF integration tests cover nested sections and per-course sources; Elementor Pro’s ACF tag and WPML translation settings still require site-specific staging verification. To migrate bare IDs from an ACF Number field, first change that field to Text while keeping its name and key; the plugin does not change field definitions automatically.

2.0.2

  • Support migrated Livid URLs in Elementor Video widgets whose Vimeo URL comes from a dynamic field such as ACF. Preserve each course or lesson’s dynamic binding and skip static fallback URLs during scanning. Handle escaped iframe values without damaging attribute quotes, and clear Elementor and oEmbed caches after ACF migration. Dynamic players render inline with autoplay, mute, loop, start time and aspect ratio; Elementor’s Vimeo overlay and lightbox are not used. Enable ACF field scanning to migrate the source values.

2.0.1

  • Fix legacy Vimeo detection for protocol-relative URLs, plain links, and Elementor video widgets with missing or incorrect video types. Migrate Elementor backgrounds and HTML-widget lightbox links, converting unsupported video lightboxes to Livid watch-page links. Preserve HTTP status and server error codes in migration notices. Add diagnostics v3 with local pickup and queue health, plus warnings about Vimeography, collections, and disabled cron.

2.0.0

  • Fix Sensei mixed-provider lessons whose completion buttons remained blocked by stale click handlers.
  • Track repeated required Livid embeds independently so each block must finish.
  • Add local integration tests and document Sensei completion setup, draft testing, recovery, and migration limitations.

1.9.1

  • Bricks’ native Video element with a Livid link as its File URL or dynamic-data source now matches Bricks’ YouTube/Vimeo behaviour more closely: the video previews in the builder canvas instead of showing a broken player; the iframe carries the element’s “Iframe title” or, failing that, the video’s own title from Livid, for screen readers; and when the element has a poster image, the poster is shown and the Livid player is only loaded when clicked, as Bricks does with its provider preview images.
  • Support Livid embeds in Sensei LMS lesson video progression, including required videos, automatic completion, and tab-away pausing. Preserve other required videos and completion filters; accept playback messages only from the matching Livid iframe.

1.9.0

  • Bricks’ native Video element now plays a Livid link given as its “File URL” source, including one pulled from dynamic data such as an ACF field inside a template or popup. Bricks treated the link as a media file and rendered a <video> the browser rejected; the plugin now swaps it for the Livid embed on the frontend, keeping the element’s overlay and play icon, and carrying over autoplay, loop and mute.
  • Migrations now use Livid’s V2 popup: the whole scan is reviewed in one window and confirmed once, however many videos it holds. The plugin feeds the popup its scan in pages, receives the confirmed selection back in pages, and stores each page on the site before telling Livid it arrived, so a lost acknowledgement never causes duplicate work. Replacement jobs only start once the complete selection is stored, and a crash between storing it and scheduling the jobs is repaired automatically. Reopening the popup and confirming again replaces an unfinished transfer; a scan that has already been sent refuses a second transfer until a new search is run. If Livid does not offer the V2 popup yet, the admin page offers the classic flow as an explicit choice. Manifest post groups are now keyed by post id.
  • Large scans are now handed to Livid in batches sized to Livid’s request limits, instead of one manifest that failed to confirm above roughly 3,000 videos. The Livid window is reused for each batch, every batch’s selection is queued into the same run so one progress bar covers the whole migration, and a batch with nothing to confirm can be skipped. Scan results are stored one batch per option rather than in one growing option, and the manifest primes post caches so building it no longer issues a query per video.
  • Embeds are now verified before they are rewritten. Each embed found by a scan records where it sits among all embeds of its kind (every iframe, block or shortcode, not just the Vimeo ones) plus a fingerprint of its original source. A migration job rewrites an embed only when the saved position still holds that exact original, recognises its own replacement if it is re-run, and otherwise reports a conflict and leaves the post untouched. This fixes two bugs: when a post held the same Vimeo video twice and only one was chosen, the first occurrence was rewritten regardless; and a YouTube iframe ahead of a Vimeo one inside an Elementor or Bricks HTML widget could make the wrong iframe get rewritten. Conflicts are listed on the completion screen with a link to each post. Scans made by earlier plugin versions keep migrating exactly as before.

1.8.0

  • Migrate Vimeo videos stored in Advanced Custom Fields. Tick “also check ACF custom fields” when moving from Vimeo to include links found in text, textarea, URL, oEmbed, and number fields, with an optional mode for matching plain video IDs. Every change is backed up so it can be rolled back.
  • Livid video embeds now preview as the video in the block editor on WordPress.com-hosted sites, matching how they already display on the published page.

1.7.0

  • Add LearnDash video progression support for Livid embeds, including bulk replacement of lesson and topic Vimeo progression URLs through the existing Livid migration flow. Preserve Vimeo-compatible resume, focus-pause, replay, and completion behavior for LearnDash and Video Resume for LearnDash, including bounded resume-seek recovery and reliable completion at the playback endpoint.

1.6.5

  • The Elementor, WPBakery, and Bricks video widgets now default to matching each video’s real aspect ratio automatically. The fixed ratio options (16:9, 4:3, 9:16, and the rest) are still available when you want to set one explicitly.

1.6.4

  • Video blocks now display at each video’s true aspect ratio automatically, so portrait, square, and widescreen videos are all sized correctly.

1.6.3

  • Improved video display in centered and auto-width columns, so embeds are always sized correctly.

1.6.2

  • Improved compatibility with page builders and block themes (including Stackable), so videos display reliably inside columns and flexible layouts, in the editor and on the front end.

1.6.1

  • More reliable video blocks: the video URL is saved as you type, and a block added without a URL now shows a helpful notice in the editor.

1.6.0

  • WPBakery background video: Livid URLs pasted into a row, section, or column’s native “Video background” control now play as chromeless, cover-fit background videos. WPBakery gates its background markup on YouTube URLs server-side (and its own script removes any background container it doesn’t recognise), so the plugin emits its own Livid-owned container into the rendered wrapper and a frontend handler fills it with a cover-fit embed — WPBakery’s script never touches it. The control is relabelled “YouTube/Livid link” with matching help text.

1.5.0

  • Slider Revolution support: add Livid as a video type in Slider Revolution 7. A “Livid” tab in the video-layer settings and a “Livid” entry in the Add-layer menu let you place Livid videos in layers and slide backgrounds, rendered as chromeless embeds. Layers are driven over the embed’s Player.js API, so Slider Revolution’s playback options work — autoplay, loop, start/end trim, volume, mute, next-slide-when-ends, pause-module-timer, stop-other-media, and cover-fit slide backgrounds.

1.4.1

  • Fix the scan job’s candidate-post query to include Bricks pages: it only looked at post_content and Elementor meta, so Bricks pages with empty post_content were never scanned. Meta keys are now derived from the registered strategies.

1.4.0

  • Bricks Builder support: a first-class Livid Video element (registered from the plugin — no child theme needed), Livid URLs work in the background Video URL control (chromeless background videos) and in the link control’s lightbox video option, and the migration scanner finds and converts Vimeo embeds inside Bricks pages (Video elements and iframes in rich-text elements).

1.3.0

  • Livid URLs pasted into Elementor’s background Video Link field now play as chromeless background videos on sections, columns, and containers. Note: previously pasted (non-functional) Livid background URLs will start playing after this update.

1.2.0

  • Add WPBakery Page Builder support. A new “Livid Video” element and a general-purpose [livid_video] shortcode let you place Livid videos in WPBakery, and the migration now converts WPBakery Vimeo embeds — both [vc_video] links and Vimeo iframes inside [vc_raw_html]/[vc_raw_js] blocks. Livid oEmbed output is also hardened so embeds render correctly inside host wrappers such as WPBakery’s responsive video box.

1.1.1

  • Detect Elementor Video widgets whose Vimeo embed was pasted as a full <iframe> into the URL field (the vimeo_url or youtube_url setting), and widgets where video_type isn’t set to “vimeo”. Previously these were skipped because we required a clean Vimeo URL — now we extract the ID from the embed like Elementor itself does. Elementor’s stock placeholder video is ignored so YouTube/Dailymotion widgets aren’t migrated by mistake. Also tightens the diagnostics report: Elementor’s derived stats/cache meta are excluded from the results, and excerpts of structured fields are longer so the full widget is captured.

1.1.0

  • Add a one-click diagnostics report (Settings → Livid) that scans the whole site for Vimeo references and downloads a JSON report you can send to support. It pinpoints where each video lives — including page builders, widgets, custom fields, and other plugins’ data the migration doesn’t reach — so we can track down videos the migration misses. The report is read-only, takes excerpts from live content only (never revisions, trash, or drafts), and excludes passwords and customer data.

1.0.13

  • chore: tidy the wp.org listing metadata — drop the Contributors line from readme.txt (it linked to an unrelated livid account) and correct the manual-install path to /wp-content/plugins/livid-video-hosting/ to match the shipped slug.

1.0.12

  • Published to the WordPress.org plugin directory. The self-hosted download now installs to wp-content/plugins/livid-video-hosting/ to match the wp.org slug, so a site can switch to the listing and keep updating in place.

1.0.11

  • Fix: WordPress admin now displays the correct plugin version.

1.0.10

  • Fix: migrated Gutenberg embeds no longer inherit stale aspect-ratio classes that made them render at roughly double height.

1.0.6

  • Fix: the Livid Video block toolbar and outline now appear when hovering anywhere over the player, not just its outer edge.

1.0.5

  • New: Elementor support — a first-class Livid Video widget, plus Vimeo migration for Elementor pages (Vimeo Video widgets convert in place; HTML and Text Editor widgets keep their type with iframe sources swapped).

1.0.4

  • New: Livid Video Gutenberg block.

1.0.3

  • Fix: corrected Livid API URLs.

1.0.0

  • Initial release.
  • Livid oEmbed provider registration.
  • Vimeo embed scanning (raw iframes, Gutenberg embed blocks, bare URLs, [embed] shortcodes, and shortcodes).
  • Background migration via Action Scheduler.
  • Livid API integration with signed manifests.