Title: Code Embed
Author: David Artiss
Published: Igbe 5, 2009
Last modified: Igbe 20, 2026
---
Ṣàwárí àwọn plugin
# Code Embed
Láti ọwọ́ [David Artiss](https://profiles.wordpress.org/dartiss/)
[Ṣe ìgbàsílẹ̀](https://downloads.wordpress.org/plugin/simple-embed-code.2.6.zip)
[Àkọ́kọ́wò Láaye](https://yor.wordpress.org/plugins/simple-embed-code/?preview=1)
* [Àwọn àlàyé](https://yor.wordpress.org/plugins/simple-embed-code/#description)
* [Àwọn àgbéyẹ̀wò](https://yor.wordpress.org/plugins/simple-embed-code/#reviews)
* [Ìgbéwọlẹ̀](https://yor.wordpress.org/plugins/simple-embed-code/#installation)
* [Ìdàgbàsókè](https://yor.wordpress.org/plugins/simple-embed-code/#developers)
[Ìrànlọ́wọ́](https://wordpress.org/support/plugin/simple-embed-code/)
## Àpèjúwe
Code Embed allows you to embed code (JavaScript, CSS and HTML Ìtumọ̀ Yorùbá: – it
canÌtumọ̀ Yorùbá: ’t be used for server-side code, such as PHP) in a post, without
the content being changed by the editor. This is incredibly useful for embedding
third-party scripts, etc. The plugin is used by many large sites, including Mozilla.
Key features include…
* Add HTML or JavaScript to posts or pages Ìtumọ̀ Yorùbá: – particularly useful
for embedding videos!
* Embed in widgets using the [Widget Logic](https://wordpress.org/plugins/widget-logic/)
plugin.
* Global embedding allows you to set up some code in one post or page and then
access it from another.
* Modify the keywords or identifiers used for embedding the code to your own choice.
* Search for embedding code via a simple search option.
* Add a simple suffix to the embed code to convert videos to responsive output.
* Embed an external script directly using just the URL.
* Conforms to WCAG 2.1 AA standards.
* And much, much more!
Iconography is courtesy of the very talented [Janki Rathod](https://www.fiverr.com/jankirathore).
**Please visit the [Github page](https://github.com/dartiss/code-embed) for the
latest code development, planned enhancements and known issues.**
### Getting Started
To use this plugin, you need to have custom fields enabled on your site. If youÌtumọ̀
Yorùbá: ’re using the block editor, you may need to switch this on first Ìtumọ̀
Yorùbá: – please scroll down to the next section to learn how to do this. If youÌtumọ̀
Yorùbá: ’re using the classic editor, then youÌtumọ̀ Yorùbá: ’ll find the custom
fields at the bottom of the editor screen.
Although this plugin works for both posts and pages, for simplicity I will simply
refer to posts Ìtumọ̀ Yorùbá: – bear in mind that pages work in the same way.
Once you have custom fields switched on, hereÌtumọ̀ Yorùbá: ’s how easy it is to
use…
1. Once you have the plugin installed, start a new post.
2. Scroll down to the bottom of the screen and look for the “Custom Fields” section.
3. Under “Add New Custom Field”, enter a name of `CODE1` and your embed code as the
value.
4. In your post content, add `{{CODE1}}` where you wish the embed code to appear.
And thatÌtumọ̀ Yorùbá: ’s it Ìtumọ̀ Yorùbá: – when the post is viewed or previewed,`{{
CODE1}}` will be replaced with the code that you asked to be embedded.
This should get you started Ìtumọ̀ Yorùbá: – for more information and advanced options,
please see below. Alternatively, thereÌtumọ̀ Yorùbá: ’s a fantastic guide at [Elftronix](http://www.elftronix.com/free-easy-plugin-add-javascript-to-wordpress-posts-pages/)
which I would recommend.
### Using this plugin with the block editor (aka Gutenberg)
By default, custom fields are hidden inside the block editor but can be revealed.
1. Edit or create a post.
2. Click the settings button (three dots) in the top right-hand corner.
3. Go to Preferences.
4. Click the Panels tab.
5. You will find a button to toggle the ‘Custom Fields’ meta box Ìtumọ̀ Yorùbá: –
make sure this is toggled to “on”.
6. A button should appear titled “Enable & Reload” Ìtumọ̀ Yorùbá: – youÌtumọ̀ Yorùbá:’
ll need to click on that and wait for the page to reload before the custom fields
will appear.
Check out the screenshots for how the custom fields should look.
### I canÌtumọ̀ Yorùbá: ’t find the custom fields
For block editor users, IÌtumọ̀ Yorùbá: ’m assuming youÌtumọ̀ Yorùbá: ’ve done the
above. For classic editor users, the custom fields should be present by default.
In all cases they should appear at the bottom of the editor screen.
From version 2.4, anyone without the “unfiltered HTML” capability wonÌtumọ̀ Yorùbá:’
t be able to use custom fields, for added security. Please see the section “Custom
Field Security”, below, for more details.
If none of the above applies, then you may have a theme or plugin that removes this
or may have a problem with your WordPress installation Ìtumọ̀ Yorùbá: – you will
need to try the usual diagnostics to try and resolve this, including requesting
help on [the WordPress support forum](https://wordpress.org/support/forum/how-to-and-troubleshooting/).
### The Code Embed Options Screen
While in WP Admin, if you go to Settings -> Code Embed, youÌtumọ̀ Yorùbá: ’ll be
able to access the options that are available for this plugin.
Code embedding is performed via a special keyword that you must use to uniquely
identify where you wish the code to appear. This consists of an opening identifier(
something that goes at the beginning), a keyword and then a closing identifier.
You may also add a suffix to the end of the keyword if you wish to embed multiple
pieces of code within the same post.
From this options screen, you can specify the above identifier that you wish to
use. By default, the opening and closing identifiers are double braces and the keyword
is `CODE`. During these instructions these will be used in all examples.
The options screen is only available to those with a capability to manage options
or greater. All the other Code Embed menu options are available to users with a
capability to edit posts or greater.
### How to Embed Code
To embed in a post, you need to find the meta box under the post named “Custom Fields”.
If this is missing, you may need to add it by clicking on the “Screen Options” tab
at the top of the new post screen.
Now create a new custom field with the name of your keyword Ìtumọ̀ Yorùbá: – e.g.`
CODE`. The value of this field will be the code that you wish to embed. Save this
custom field.
Now, wherever you wish the code to appear in your post, simply put the full identifier(
opening, keyword and closing characters). For example, `{{CODE}}`.
If you wish to embed multiple pieces of code within a post, you can add a suffix
to the keyword. So we may set up 2 custom fields named `CODE1` and `CODE2`. Then
in our post we would specify either `{{CODE1}}` or `{{CODE2}}` depending on which
you wish to display.
DonÌtumọ̀ Yorùbá: ’t forget Ìtumọ̀ Yorùbá: – via the options screen you can change
any part of this identifier to your own taste.
### How to Embed Code from an External URL
If you specify a URL within your post, surrounded by your choice of identifiers,
then the contents of the URL will be embedded within your post.
Obviously, be careful when embedding a URL that you have no control over, as this
may be used to hijack your post by injecting, for example, dangerous JavaScript.
For example, using the default options, you could embed the contents of a URL using
the following method…
```
{{http://www.example.com/code.php}}
```
or
```
{{https://www.example.com/code.html}}How to Use Global Embedding
```
You can also create global embeds Ìtumọ̀ Yorùbá: – that is, creating one piece of
embed code and using it in multiple posts or pages.
To do this, simply make reference to an already defined (but unique) piece of embed
code from another post or page.
So, letÌtumọ̀ Yorùbá: ’s say in one post you define a custom field named `CODE1`.
You can, if you wish, place `{{CODE1}}` not just in that post but also in another
and it will work.
However, bear in mind that the embed code name must be unique Ìtumọ̀ Yorùbá: – you
canÌtumọ̀ Yorùbá: ’t have defined it in multiple posts, otherwise the plugin wonÌtumọ̀
Yorùbá: ’t know which one youÌtumọ̀ Yorùbá: ’re referring to (although it will report
this and list the posts that it has been used in).
In the administration menu, there is a sidebar menu named “Tools”. Under this is
a sub-menu named “Code Search”. Use this to search for specific embed names and
it will list all the posts/pages that theyÌtumọ̀ Yorùbá: ’re used on, along with
the code for each.
### Embedding in Widgets
Natively, you cannot use the embed facilities within sidebar widgets. However, if
you install the plugin [Widget Logic](https://wordpress.org/extend/plugins/widget-logic/),
then Code Embed has been set up to make use of this and add the ability.
* Install [Widget Logic](https://wordpress.org/extend/plugins/widget-logic/) and
activate.
* In Administration, select the Widgets page from the Appearance menu. At the bottom
there will be a set of Widget Logic options.
* Ensure ‘Use widget_content filter’ is ticked and press Save.
Although you cannot set up embed code within a widget, you can make reference to
it, for example by writing `{{CODE1}}` in the widget.
### Responsive Output Conversion
Responsive output is where an element on a web page dynamically resizes depending
upon the current available size. Most video embeds, for instance, will be a fixed
size. This is fine if your website is also of a fixed size; however, if you have
a responsive site then this is not suitable.
Code Embed provides a simple suffix that can be added to an embed code and will
convert the output to being responsive. This works best with videos.
To use, when adding the embed code onto the page, simply add `_RES` to the end,
before the final identifier. For example, `{{CODE1_RES}}`. The `_RES` should not
be added to the custom fields definition.
This will now output the embedded code at full width, dynamically resizing as required.
If you donÌtumọ̀ Yorùbá: ’t wish the output to be full width, you can specify a
maximum width by adding an additional `_x` on the end, where `x` is the required
width in pixels. For example, `{{CODE1_RES_500}}` will output `CODE1` as responsive
but with a maximum width of 500 pixels.
**It should be noted that this is an experimental addition and will not work in
all circumstances.**
### Embedding in excerpts
By default, embed code will not appear in excerpts. However, you can switch this
ability on via the Code Embed options screen. If you do this, then the standard
rules of excerpts will still apply but only once the code embed has been applied.
For example, excerpts are just text, a specific length, etc.
### Filtering of code
By default, WordPress allows unfiltered HTML to be used by users in post custom
fields, even if their role is set up otherwise. This opens up the possibility of
leaving a site vulnerable, if any plugins that use this data donÌtumọ̀ Yorùbá: ’
t check it appropriately.
“Out of the box,” neither the contributor nor author roles have unfiltered HTML
capabilities but can access custom post fields.
As this plugin requires the use of unfiltered HTML, we need to ensure that only
authorized users can use it. From version 2.5, any users without this permission
that update a post containing embeds from this plugin will cause the code to be
filtered.
### Reviews & Mentions
“Works like a dream. Fantastic!” Ìtumọ̀ Yorùbá: – Anita.
“Thank you for this plugin. I tried numerous other iframe plugins and none of them
would work for me! This plugin worked like a charm the FIRST time.” Ìtumọ̀ Yorùbá:–
KerryAnn May.
[Embedding content](http://wsdblog.westbrook.k12.me.us/blog/2009/12/24/embedding-content/)
Ìtumọ̀ Yorùbá: – WSD Blogging Server.
[Animating images with PhotoPeach](http://comohago.conectandonos.gov.ar/2009/08/05/animando-imagenes-con-photopeach/)
Ìtumọ̀ Yorùbá: – Cómo hago.
## Àwọn àwòrán ìbòjú
* [[
* The options screen
* [[
* The custom field meta box with a Code Embed field set up to show some YouTube
embed code
* [[
* Example embed code in a post
* [[
* The block editor Settings screen showing the Custom field switch at the bottom
* [[
* The search screen showing the results of a search for {{CODE1}}
## Ìgbéwọlẹ̀
Code Embed can be found and installed via the Plugin menu within WordPress administration(
Plugins -> Add New). Alternatively, it can be downloaded from WordPress.org and
installed manually…
1. Upload the entire `simple-embed-code` folder to your `wp-content/plugins/` directory.
2. Activate the plugin through the ‘Plugins’ menu in WordPress administration.
Voila! ItÌtumọ̀ Yorùbá: ’s ready to go.
## FAQ
### My code doesnÌtumọ̀ Yorùbá: ’t work
If your code contains the characters `]]>`, then youÌtumọ̀ Yorùbá: ’ll find that
it doesnÌtumọ̀ Yorùbá: ’t Ìtumọ̀ Yorùbá: – WordPress modifies this itself.
Also, check to see if the post has been modified by a user without `unfiltered_html`
permissions Ìtumọ̀ Yorùbá: – if it was, they may have caused the code to have been
modified (see the “Filtering of code” section above).
Otherwise, itÌtumọ̀ Yorùbá: ’s likely to be your code and not this plugin. The best
way to confirm this is to look at the source of the page and compare the code output
with what you embedded. Does it match? If it does, then your code is at fault.
### WhatÌtumọ̀ Yorùbá: ’s the maximum size of the embed code that I can save in a custom field?
WordPress stores the custom field contents in a MySQL table using the `longtext`
format. This can hold over 4 billion characters.
### Can I use the same embed name on multiple pages?
Yes, you can. If you wish to share one set of embed code across multiple posts,
though, then you need to give it a unique name (see “How to Use Global Embedding”,
above).
### Is this GDPR compliant?
It is, in that it doesnÌtumọ̀ Yorùbá: ’t save any data that could be at odds with
GDPR compliance (i.e. itÌtumọ̀ Yorùbá: ’s compliant by design). However, if you
use this to embed third-party scripts, then those scripts may not be and you will
need to speak to the providers for further details.
### Do you support this plugin on forks of WordPress?
No. It was developed for WordPress, and so forks remain unsupported. I have no intention
of developing and testing this on any other version.
### Where do I report security bugs found in this plugin?
Please report security bugs found in the source code of the Code Embed plugin through
the [Patchstack Vulnerability Disclosure Program](https://patchstack.com/database/vdp/9e5fb3d8-2b30-4f96-919c-ecbc8308eda4).
The Patchstack team will assist you with verification, CVE assignment, and notify
the developers of this plugin.
## Àwọn àgbéyẹ̀wò
### [Not Helpful](https://wordpress.org/support/topic/not-helpful-6/)
[nick0488](https://profiles.wordpress.org/nick0488/) Agẹmọ 30, 2024 1 ìdáhùn
I was working on a client site and I can someone had installed code embed previously
but somehow it got forgetten about. Its putting in code even when deactivated.But
I have no way of adding code nevermind removing old code. There is no useful information,
even the FAQ didnÌtumọ̀ Yorùbá: ’t help. Theres no way to see what code has been
added or where. Except from a code search but you still need to type in something
Ìtumọ̀ Yorùbá: – without knowing the suffix its pointless.I couldnÌtumọ̀ Yorùbá:’
t even add new code to see how it works. Absolutely no option, no custom fields
nothing. Its nothing but clutter.
### [No FAQ Ìtumọ̀ Yorùbá: – not able to use it](https://wordpress.org/support/topic/no-faq-not-able-to-use-it/)
[kimberean](https://profiles.wordpress.org/kimberean/) Agẹmọ 31, 2023 2 àwọn ìdáhùn
Although page says “see FAQ” there is NO FAQ. Wasted a lot of time trying to get
this to work. Someone raised this a year ago and no change has been made. Clearly
no support or interest in helping users. Useless.
### [useful plugin](https://wordpress.org/support/topic/useful-plugin-938/)
[ritadevine](https://profiles.wordpress.org/ritadevine/) Ṣẹrẹ 24, 2023
I have good experience with it. Nice plugin.
### [Great plugin](https://wordpress.org/support/topic/great-plugin-35780/)
[David](https://profiles.wordpress.org/davidkaur/) Ọ̀pẹ 19, 2022
It is very useful plugin
### [Great plugin](https://wordpress.org/support/topic/great-plugin-34466/)
[Dylan H.](https://profiles.wordpress.org/dylan011001/) Òkúdù 28, 2022 2 àwọn ìdáhùn
ItÌtumọ̀ Yorùbá: ’s great to have a plugin to display code on your website integrated
with the block editor. IÌtumọ̀ Yorùbá: ’ve struggled to find one that is so stable
but Code Embed has everything I need. Highly recommended!
### [Awesome support!](https://wordpress.org/support/topic/awesome-support-703/)
[justin27](https://profiles.wordpress.org/justin27/) Èbìbí 31, 2022
I wasnÌtumọ̀ Yorùbá: ’t able to use this plugin due to my theme but the plugin developer
is awesome and provides great support for this FREE plugin!
[ Ka gbogbo àwọn àgbéyẹ̀wò 45 ](https://wordpress.org/support/plugin/simple-embed-code/reviews/)
## Àwọn Olùkópa & Olùgbéejáde
“Code Embed” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí
plugin yìí.
Àwọn Olùkópa
* [ David Artiss ](https://profiles.wordpress.org/dartiss/)
A ti túmọ̀ “Code Embed” sí àwọn èdè agbègbè 8. Ọpẹ́lọpẹ́ fún [àwọn atúmọ̀ èdè](https://translate.wordpress.org/projects/wp-plugins/simple-embed-code/contributors)
fún àwọn ìkópa wọn.
[Túmọ̀ “Code Embed” sí èdè rẹ.](https://translate.wordpress.org/projects/wp-plugins/simple-embed-code)
### Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè?
[Ṣàwárí koodu](https://plugins.trac.wordpress.org/browser/simple-embed-code/), ṣàyẹ̀wò
[ibi ìpamọ́ SVN](https://plugins.svn.wordpress.org/simple-embed-code/), tàbí ṣe
àgbékalẹ̀ sí [àkọsílẹ̀ ìdàgbàsókè](https://plugins.trac.wordpress.org/log/simple-embed-code/)
nípasẹ̀ [RSS](https://plugins.trac.wordpress.org/log/simple-embed-code/?limit=100&mode=stop_on_copy&format=rss).
## Àkọsílẹ̀ àwọn àyípadà
I use semantic versioning, with the first release being 1.0.
#### 2.6
* Enhancement: A massive review of the code means that it now conforms to WCAG
2.1 AA standards, and is more secure and performant than ever before.
* This is not the end to improvements, however, and expect 2.7 to drop soon with
even more quality-of-life enhancements, as well as all the bugs squashed that
have been reported to me.
#### 2.5.2
* Security: Fixed CVE-2026-2512, as reported by [Muhammad Yudha](https://www.wordfence.com/threat-intel/vulnerabilities/researchers/yudha)
via [WordFence](https://www.wordfence.com/r/26c227ba3ee33458/).
#### 2.5.1
* Security: Changed `wp_remote_get` to `wp_safe_remote_get` to improve security.
#### 2.5
* Enhancement: This release is a revised version of 2.4, with less impact on other
plugins and users. See the README for more details, but this undoes the changes
in 2.4 and adds in filtering of code embed fields for users without the correct
permissions.
* Bug: Fixed a long-standing bug that could cause an infinite loop to occur in
rare situations.
#### 2.4
* Security: A vulnerability was reported to me but is actually an issue with Core.
IÌtumọ̀ Yorùbá: ’ve implemented a fix that protects not just this plugin but
any others you may have installed. Please read the section in the README titled“
Custom Field Security” for more details.
* Enhancement: Tweaked a few bits of code here. No visible changes, just quality
improvements.
#### 2.3.9
* Enhancement: So, let me tell you a story. To make the output look neat, I was
adding carriage returns to the embeds. Except, if you want to embed something
partway through a line it can look… well… wrong. And all for it looking clean.
Remember, kids, cleanliness isnÌtumọ̀ Yorùbá: ’t always next to Godliness. Needless
to say, those rogue carriage returns are gone.
* Enhancement: While I was at it, I updated some of the settings code to a brand-
spanking new version, which IÌtumọ̀ Yorùbá: ’m sharing across all my plugins.
* Enhancement: Tidied up some of the assets, including adding a blueprint for WordPress
Playground.
#### 2.3.8
* Bug: You know that vulnerability I fixed in 2.3.7? It fixed that but broke something
else. That should now be resolved. Apologies for that.
#### 2.3.7
* Bug: Fixed a bug that created a potential vulnerability.
* Enhancement: Improved code quality, using the latest version of PHPCS and WordPress
sniffs.
#### 2.3.6
* Bug: Fixed a variable that was incorrectly assigned. It happens. I guess.
#### 2.3.5
* Enhancement: Cleared up a big batch of code quality issues. Now it ticks all
the boxes for both the WordPress and VIP rulesets in PHPCS.
* Enhancement: A new, richer, header has been added to the plugin file.
* Enhancement: The plugin version number is now used as a revision for the script
queueing Ìtumọ̀ Yorùbá: – this means that it will be cached by the browser until
the plugin release changes.
* Enhancement: Lots of changes made to the README Ìtumọ̀ Yorùbá: – hopefully it
should read more easily than before!
#### 2.3.4
* Bug: Fixed a minor error that occurred due to the removal of the debug code in
the last release. Sorry about that.
#### 2.3.3
* Enhancement: IÌtumọ̀ Yorùbá: ’ve removed the debug code. I allowed it to be switched
off but IÌtumọ̀ Yorùbá: ’ve never used it and it may not have switched off properly
anyway. So itÌtumọ̀ Yorùbá: ’s gone.
* Enhancement: Added some additional plugin meta.
#### 2.3.2
* Bug: Fixed another pesky bug that was affecting embedded URLs. My code to do
this was years old and I couldnÌtumọ̀ Yorùbá: ’t understand why IÌtumọ̀ Yorùbá:’
d written it the way I had. So IÌtumọ̀ Yorùbá: ’ve rewritten it from scratch.
#### 2.3.1
* Bug: Fixed a variable naming issue that I may, or may not (I did), have created
in the latest release.
#### 2.3
* Enhancement: All the code is now compliant with the full-fat VIP coding standards.
It was no mean feat but, as a result, the plugin is more secure than ever before.
* Enhancement: The default is to now use double braces around your embed name,
which is essentially the universal default for template tags such as this. If
youÌtumọ̀ Yorùbá: ’re an existing user, your current configuration wonÌtumọ̀
Yorùbá: ’t change, though Ìtumọ̀ Yorùbá: – this only affects new users.
* Enhancement: Improved translation output, including where IÌtumọ̀ Yorùbá: ’d
accidentally added an extra character to the text domain.
* Enhancement: Using the `checked` function on fields, rather than the form parameter.
* Enhancement: Added a useful links sidebar to the Help for both screens.
* Maintenance: Throughout, use Yoda conditions I now do.
* Maintenance: Added links to the sparkly new Github repo.
* Bug: When updating the options you sometimes didnÌtumọ̀ Yorùbá: ’t get a confirmation
message. You do now!
* Bug: Fixed a weird one where I was referencing a variable that I was never using.
#### 2.2.2
* Maintenance: Updated README to work better with new plugin directory format.
Also, now converting all text to US English, which is the WordPress standard.
Snazzy.
* Maintenance: Updated all links to artiss.blog and removed donation links. Clickable.
* Maintenance: Minimum WordPress level is now 4.6 for this plugin, meaning I could
remove various pieces of code. Strong and stable.
* Maintenance: Lots of language updates, many of which are a consequence of the
move to WordPress 4.6 (including removal of language files and links, etc.).
Verbose.
#### 2.2.1
* Maintenance: Updated branding, including adding donation links.
#### 2.2
* Enhancement: Added support for embedding code in excerpts.
* Enhancement: Validated, sanitized and escaped the admin screen data.
* Maintenance: Overhauled the way default options are fetched and/or generated.
Now a lot more efficient.
* Maintenance: Updated the admin screens so they are formatted in a similar way
to the default WordPress screens.
* Maintenance: Removed hardcoding of plugin folder.
* Maintenance: Updated author and removed donation links.
* Maintenance: Renamed files and file functions Ìtumọ̀ Yorùbá: – removed prefix
from files and updated it on functions.
* Maintenance: Added a domain path for translations.
#### 2.1.2
* Maintenance: Added missing text domain, ready for automatic translation.
#### 2.1.1
* Maintenance: Updated help text.
* Maintenance: Modified admin screen headings so theyÌtumọ̀ Yorùbá: ’re compatible
with WP4.3.
* Enhancement: Added options to suppress debug output.
* Enhancement: Added donation link to plugin meta. Go on, you know you want to!
#### 2.1
* Maintenance: Updated plugin branding.
* Maintenance: Removed feature pointer Ìtumọ̀ Yorùbá: – no longer required.
* Enhancement: Removed support screen and moved remaining admin screens.
* Bug: Fixed issues with translations.
#### 2.0.2
* Enhancement: Fixed a [minor XSS vulnerability](https://bugzilla.mozilla.org/show_bug.cgi?id=771315)(
kindly reported by Mozilla).
* Enhancement: Shows README appropriate to the current installed version, instead
of the latest.
#### 2.0.1
* Enhancement: Removed restriction on embed code length.
#### 2.0
* Maintenance: Removed dashboard widget.
* Maintenance: Further code tidying.
* Maintenance: Added new code for contextual help to use new WP 3.3 elements.
* Enhancement: New admin menu option, under which existing option screens now exist
along with a support screen. If you have the [README Parser plugin](https://wordpress.org/extend/plugins/.wp-readme-parser/)
installed, then it will also add a sub-menu displaying README instructions.
* Enhancement: Added internationalization to code.
* Enhancement: Will now work with widgets if you install the plugin [Widget Logic](https://wordpress.org/extend/plugins/widget-logic/).
* Enhancement: Added experimental ability to convert to responsive output.
* Enhancement: Added option to specify a URL instead of an embed code.
* Enhancement: Added feature pointer for when plugin is activated.
#### 1.6.1
* Bug: Fixed bug where name of plugin folder was incorrect.
#### 1.6
* Maintenance: Improved code further from 1.5, including separating code into separate
includes.
* Enhancement: Added global embeds option.
* Enhancement: New tools option in the administration menu that allows you to search
for code embeds.
#### 1.5.1
* Enhancement: Added form security.
#### 1.5
* Maintenance: Renamed plugin to bring in line with new plugin conventions.
* Maintenance: Plugin rewrite to create more efficient code Ìtumọ̀ Yorùbá: – can
now also completely personalize the embed code used in the post.
* Maintenance: PHPDoc used throughout for documentation purposes, plus new coding
standards.
* Maintenance: Instructions completely rewritten.
* Enhancement: Support information improved, including contextual help on the settings
screen (if supported).
#### 1.4.1
* Bug: Version details as HTML comments were being output whether an embed existed
or not Ìtumọ̀ Yorùbá: – corrected.
#### 1.4
* Enhancement: Option screen that allows you to specify the maximum number of possible
embeds per post and the embed word.
#### 1.3
* Enhancement: Increased limit of number of code embeds from 5 to 20.
#### 1.2
* Maintenance: Simplification of code.
#### 1.1
* Maintenance: The instructions have been corrected. Thanks to John J. Camilleri
for pointing it out!
* Maintenance: Plugin has been tested with version 2.8 of WordPress. No code changes
have been made.
#### 1.0
* Initial release.
## Plugin àwùjọ
Àwùjọ ni ó ṣe ìdàgbàsókè àti àtìlẹ́yìn fún plugin yìí. [Ṣe ìkópa sí plugin yìí](https://github.com/dartiss/code-embed)
## Àkójọpọ̀ Meta
* Ẹ̀yà **2.6**
* Ìgbàgbọ́hùn tó kẹ́yìn **ọ̀sẹ̀ 4 sẹ́yìn**
* Àwọn ìgbéwọlẹ̀ tó ṣiṣẹ́ **10,000+**
* Ẹ̀yà WordPress ** 4.6 tàbí ju bẹ́ẹ̀ lọ **
* Dánwò dé **6.9.4**
* Ẹ̀yà PHP ** 7.4 tàbí ju bẹ́ẹ̀ lọ **
* Àwọn èdè
* [English (Canada)](https://en-ca.wordpress.org/plugins/simple-embed-code/), [English (UK)](https://en-gb.wordpress.org/plugins/simple-embed-code/),
[English (US)](https://wordpress.org/plugins/simple-embed-code/), [Romanian](https://ro.wordpress.org/plugins/simple-embed-code/),
[Russian](https://ru.wordpress.org/plugins/simple-embed-code/), [Spanish (Chile)](https://cl.wordpress.org/plugins/simple-embed-code/),
[Spanish (Spain)](https://es.wordpress.org/plugins/simple-embed-code/), [Spanish (Venezuela)](https://ve.wordpress.org/plugins/simple-embed-code/),
àti [Swedish](https://sv.wordpress.org/plugins/simple-embed-code/).
* [Túmọ̀ sí èdè rẹ](https://translate.wordpress.org/projects/wp-plugins/simple-embed-code)
* Àwọn àmì
* [code](https://yor.wordpress.org/plugins/tags/code/)[css](https://yor.wordpress.org/plugins/tags/css/)
[embed](https://yor.wordpress.org/plugins/tags/embed/)[html](https://yor.wordpress.org/plugins/tags/html/)
[javascript](https://yor.wordpress.org/plugins/tags/javascript/)
* [Ìwòye Tó Péye](https://yor.wordpress.org/plugins/simple-embed-code/advanced/)
## Àwọn ìbò
4.4 lára àwọn ìràwọ̀ 5.
* [ 38 5-star reviews ](https://wordpress.org/support/plugin/simple-embed-code/reviews/?filter=5)
* [ 0 4-star reviews ](https://wordpress.org/support/plugin/simple-embed-code/reviews/?filter=4)
* [ 0 3-star reviews ](https://wordpress.org/support/plugin/simple-embed-code/reviews/?filter=3)
* [ 1 2-star review ](https://wordpress.org/support/plugin/simple-embed-code/reviews/?filter=2)
* [ 6 1-star reviews ](https://wordpress.org/support/plugin/simple-embed-code/reviews/?filter=1)
[Your review](https://wordpress.org/support/plugin/simple-embed-code/reviews/#new-post)
[See all reviews](https://wordpress.org/support/plugin/simple-embed-code/reviews/)
## Àwọn Olùkópa
* [ David Artiss ](https://profiles.wordpress.org/dartiss/)
## Ìrànlọ́wọ́
Nǹkan wà tí o fẹ́ sọ? Ṣé o nílò ìrànlọ́wọ́?
[Wo àpéjọ ìrànlọ́wọ́](https://wordpress.org/support/plugin/simple-embed-code/)
## Ṣe ìtọrẹ
Ṣé o fẹ́ ṣe àtìlẹ́yìn fún ìlọsíwájú plugin yìí?
[ Ṣe ìtọrẹ sí plugin yìí ](https://artiss.blog/donate)