Описание

glomex oEmbed connects your WordPress site to glomex Exchange. Paste a video or playlist URL into any editor and WordPress replaces it with the glomex player – no embed code to copy, no HTML to maintain.

The plugin registers glomex as a native WordPress oEmbed provider, so embedding works in the block editor, the classic editor and any editor that supports oEmbed. All you need is a glomex Exchange integration ID.

Once the integration ID is configured, embedding takes three steps:

Forge a URL from template: https://exchange.glomex.com/[video|videos|playlist|playlists]/VIDEO_OR_PLAYLIST_ID (integrationId parameter is optional)
Go to your post and paste the url into any editor (editor must support oEmbed)
You get an embedded player inside content!

Shortcodes

[glomex_integration]

You can use the shortcode [glomex_integration] to embed a player in your post.
Additional shortcode parameters (not required):
* playlist_id – ID of the playlist to embed
* integration_id – override default integration ID
* variant – player variant (default: ‘player-listicle’)
* width – player width in pixels (default: responsive width)
* height – player height in pixels (default: 16:9 aspect ratio)

If both width and height are not specified, the player will use responsive sizing with 16:9 aspect ratio.

URL

The supported URL scheme is https://exchange.glomex.com/[video|videos|playlist|playlists]/VIDEO_OR_PLAYLIST_ID

The placeholder variables are:
* VIDEO_OR_PLAYLIST_ID (mandatory) – the element id to embed
* [video|videos|playlist|playlists] (mandatory) – select one item to embed – it should exist in your account and be accessible with the given integration ID

Allowed parameters:

integrationId (optional) – allows overriding integration ID for this single embed

Plugin settings are used by default in all cases. Query strings will override the setting.

Configuration options

The plugin adds a settings page with two options: the global integration ID and custom script attributes.

You can set up the default integration ID using the GLOMEX_INTEGRATION_ID environment variable.

Custom script attributes

On the settings page you can add custom HTML data-* attributes to the glomex player script tags. This is useful for telling performance/optimization plugins to leave the player script alone – for example, add data-cfasync = false to exclude the script from Cloudflare Rocket Loader, or data-no-optimize = 1 to exclude it from WP Rocket. Only data-* attribute names are accepted; other names are ignored. The attributes are added to the player script tag of each embed.

Инсталиране

Uploading in WordPress Dashboard

Navigate to the ‘Add New’ in the plugins dashboard
Navigate to the ‘Upload’ area
Select the plugin archive from your computer
Click ‘Install Now’
Activate the plugin in the Plugin dashboard

Using FTP

Download plugin archive
Extract the archive to your computer
Upload the plugin directory to the plugins directory (it is usually /wp-content/plugins/ but sometimes it may vary)
Activate the plugin in the Plugin dashboard

ЧЗВ

What do I need on my server?

You need at least WP 5.3.14, PHP 7.4 with the mbstring and curl extensions enabled.

What do I need to operate the plugin?

You need an account at glomex Exchange and an integration ID from it. Custom script attributes are optional.

Where do I get my integration ID?

You need to navigate to your account at glomex Exchange.
Go to Manage => Players
Select one and copy Configuration ID
Paste the ID into the field on site or use to forge a link

Can I use more than one integration ID on the site?

Yes you can. You can have one „basic“ integration ID in your plugin configuration and any amount of integration IDs for embedded player.

Does the plugin output structured data (JSON-LD)?

No. Structured data is enabled in your glomex integration configuration and output by the player.

How do I stop my performance/optimization plugin from breaking the player?

Some optimization plugins (script deferring/combining, Cloudflare Rocket Loader, etc.) can interfere with the glomex player script. Use the „Custom script attributes“ setting to add the attribute your plugin uses to skip a script. For example:

Cloudflare Rocket Loader: data-cfasync = false
WP Rocket: data-no-optimize = 1

Only data-* attribute names are accepted; the attributes are added to the player script tags on the front end.

Отзиви

There are no reviews for this plugin.

Сътрудници и разработчици

“glomex oEmbed” е софтуер с отворен код. Към разширението са допринесли следните хора:

Glomex

Превеждане на “glomex oEmbed” на вашия език.

Имате интерес към разработване?

Преглеждане на кода, разглеждане на SVN хранилище, или абонамент към програмната история (log) чрез RSS.

Списък с промени

0.9.7

Fixed

PHP 8.2+ Creation of dynamic property deprecation notices reported by debugging plugins such as Query Monitor
the „Custom script attributes“ setting not applying to individual embeds
the settings page missing its tab layout and styling, because its stylesheet and script were never enqueued
the onboarding pointers never appearing
an Array to string conversion notice on oEmbed requests that pass url as an array instead of a string

Removed

the „Output structured data?“ setting and the includeStructuredData parameter – structured data is enabled in the glomex integration configuration and output by the player
the „Output general script?“ setting – it loaded glomex-player.js on every page and stripped the per-embed script tags, which the current embed markup no longer contains, so it only added an unused download

Other

tested with WordPress 7.0.2
optimized the bundled dependencies for a smaller download

0.9.6

added a „Custom script attributes“ setting to attach data-* attributes (e.g. data-cfasync="false") to the glomex player script tags, so they can be excluded from Cloudflare Rocket Loader and similar optimizers
fixed the missing „Settings“ link on the Plugins page (corrected the plugin file name and menu URL in the action-link hook)

0.9.5

tested with WordPress 7.0.1
fixed _load_textdomain_just_in_time notice on WordPress 6.7+ by no longer calling translation functions before the init hook
hardened the activation/deactivation hooks against being invoked with a null argument (e.g. by older WP-CLI versions)
updated bundled dependencies (upstream i18n loading improvements)
reduced package size by removing development files (VCS/CI metadata) from bundled dependencies

0.9.4

improved security by adding proper escaping for shortcode attributes

0.9.3

improved code quality to align with WordPress Coding Standards
improved security by adding proper sanitize for shortcode attributes

0.9.2

improved security by adding proper escaping for shortcode attributes
updated/tested with WP 6.7.1

0.9.1

created glomex_integration shortcode to embed a player in your post

0.9.0

created functionality for the prefixing video ID in the URL
updated/tested with WP 6.4.3

0.8.5

updated vendor requirements

0.8.4

removed internal update checker
renamed functions/namespaces/constants names with new prefix

0.8.3

updated vendor requirements

0.8.2

fixed the problem with embedding URL decoding in popular page builders

0.8.1

fixed the problem with embedding URL decoding in older WP versions

0.8

fixed files headers
fixed grumphp config
refactored main oEmbed code to be better quality
implemented custom codestyle based on CodeatCS

0.7

used 2 different vendor directories and composer files

0.6

loaded only single glomex-player.js on frontend

0.5.5

fixed a bug in the oEmbed URL generation function

0.5.4

updated documentation

0.5.3

implemented update checker with support for GitHub repo

0.5.0

initial release with basic functions