Plugin profile · observed daily since 02 Aug 2026
Google Docs oEmbed
PluginPedia reports published data and observable changes. It does not rate plugin quality or safety, infer intent, or make recommendations. These are observations rather than a verdict. How this works
Ownership
Held by unknown throughout, with no change of ownership observed since daily tracking began on 02 Aug 2026.
Full observed history, including every field transition
Committing accounts
Read from the plugin’s public release log, so these predate this registry. A committing account is not an owner. Thirty accounts commit to WooCommerce and it has never changed hands.
| Account | Releases | First | Last |
|---|---|---|---|
| s3rgiosan | 11 | 21 Jun 2015 | 15 Oct 2016 |
This registry did not observe a transfer; it read these names off a public log. Whether that reflects a change of ownership is not something the directory publishes.
Adoption
How widely the plugin is installed, and what the people running it think of it. WordPress.org rounds install figures to one significant digit, so they describe an order of magnitude rather than a headcount.
Small but established: 100+ active installs. Enough sites to show it works in the wild, too few for adoption to say much on its own.
2 downloads a day over the last 7 days, falling 50% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
Install band fell to 100+ on 02 Sep 2026, from 200+. Both figures are rounded to one significant digit, so the size of the change is not knowable from them.
Daily record
Every field we record, one column per observation. Fields that never moved are named once rather than repeated across every column. A row of identical numbers would be padding.
| Field | 22 Aug | 23 Aug | 24 Aug | 25 Aug | 26 Aug | 27 Aug | 28 Aug | 29 Aug | 30 Aug | 31 Aug | 01 Sep | 02 Sep | 03 Sep | 04 Sep |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 0 | 11 | 0 | 11 | 0 | 0 | 11 | 0 | 0 | 0 | 0 | 0 | 0 |
| Active installs | 200+ | 200+ | 200+ | 200+ | 200+ | 200+ | 200+ | 200+ | 200+ | 200+ | 200+ | 100+ | 100+ | 100+ |
Unchanged throughout: ratings total (0) · version (1.0.10) · support threads (0) · threads resolved (0)
34 days of observation, most recent 14 shown.
Maintenance
When it was last released, and how far its declared compatibility has drifted from current WordPress.
Is anyone still maintaining this?
- No release in 3,612 days (9.9 years). The last was 15 Oct 2016.
- Declares compatibility only up to WordPress 4.6.30, while 7.1 is current. The author has not confirmed it runs on the last 25 releases.
- The same account maintains 2 other plugins, and none has been updated in over a year, the most recent on 14 Oct 2016.
A plugin that does one thing correctly may need no changes for years; a long gap is not, by itself, evidence of neglect.
History
Everything dated that this registry holds about the plugin, most recent first. Releases carry the author’s own release date; everything else is dated to when it was observed.
Entries marked from the release log predate this registry, and daily observation began 02 Aug 2026. They were read from the plugin’s public SVN history after the fact, not watched as they happened. Everything else was observed directly.
- 02 Aug 20261 month agoInstall band moved to 200+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 02 Aug 20261 month agoFirst observed by PluginPediaDaily snapshots of this plugin’s directory record begin here. Everything above this line is observed; anything before it comes from fields the API itself reports.
- 08 Apr 20188 years agoDormancy threshold crossed540 days since the last release (2016-10-15). Dormancy is a maintenance observation, not a judgement about the owner.
- 15 Oct 20169.5 years agoVersion 1.0.10 released
- 11 Oct 20169.5 years agoVersion 1.0.9 releasedfrom the release logCommitted by s3rgiosan.
- 10 Oct 20169.5 years agoVersion 1.0.8 releasedfrom the release logCommitted by s3rgiosan.
- 18 Mar 201610 years agoVersion 1.0.7 releasedfrom the release logCommitted by s3rgiosan.
- 21 Jan 201610 years agoVersion 1.0.6 releasedfrom the release logCommitted by s3rgiosan.
- 30 Nov 201510 years agoVersion 1.0.5 releasedfrom the release logCommitted by s3rgiosan.
- 28 Sep 201510 years agoVersion 1.0.4 releasedfrom the release logCommitted by s3rgiosan.
- 31 Jul 201511 years agoVersion 1.0.3 releasedfrom the release logCommitted by s3rgiosan.
- 28 Jun 201511 years agoVersion 1.0.2 releasedfrom the release logCommitted by s3rgiosan.
- 21 Jun 201511 years agoVersion 1.0.0 releasedfrom the release logCommitted by s3rgiosan.
- 21 Jun 201511 years agoVersion 1.0.1 releasedfrom the release logCommitted by s3rgiosan.
- 21 Jun 201511 years agoAdded to the WordPress.org directoryReported by the plugin API as the date this plugin was added.
What we know, and what we don’t
Everything on this page in one place, including the gaps, so that nothing here is mistaken for a clean bill of health.
What we know
- It has been held by unknown for all 34 days we have observed it.
- It was last released 9.5 years ago (15 Oct 2016).
- Its author declares it tested up to WordPress 4.6.30; WordPress is now on 7.1.
- WordPress.org reports 100+ active installs.
What we don’t know yet
- Nobody has rated it. The first rating that arrives shows up here.
- No forum threads were open in the two months we measure, so how responsive its support is cannot be said. One new thread starts answering that.
What can’t be known
- Whether the quiet is neglect or a finished plugin. That is the author’s intent, which no dataset records, and a stable plugin can need no changes for years.
Every record on this site, this one included, works under the same limits. We read what WordPress.org publishes about a plugin, never the plugin’s own code, so nothing here says whether a plugin is well built or safe. Install counts reach us already rounded; a change smaller than a band step doesn’t show. We don’t track security advisories yet. For anything older than our first observation we rely on the plugin’s public release log, where one exists. What this registry can and cannot see
Similar plugins
This plugin has not been updated in a long time. These carry the same tags and describe themselves in the same terms, so they are a starting point for a replacement, not a recommendation. Check them yourself.
Browse for Google Drive documents and embed directly in your posts/pages. Extends Google Apps Login plugin so no extra user auth required.
Embed a PDF from the Media Library or elsewhere via oEmbed or as a block into an iframe tag.
Documentation, FAQ & Knowledge Base plugin to create docs, FAQs, product FAQ, wikis & help center with MCP, AI writing, instant answers & AI Chatbot.
Embed a link and preview of Google Drive Documents by pasting a shared document link into the editor.
EmbedPress lets you embed videos, pages, social feeds, embed PDF 3D flipbooks & other content on WordPress without coding & enhance storytelling.
Build a powerful documentation hub with an AI-powered knowledge base, docs, wiki tools, changelogs and an AI chatbot to help users find answers instan …
Grouped from the tags each author chose for their own plugin, so the grouping is only as good as those tags.
Reach out about this record
Corrections, missing context, or anything else about Google Docs oEmbed: a person reads every submission, and corrections get a reply within 5 business days.