Adds an oEmbed field type to Advanced Custom Fields.
Prioritized issue groups from the latest Plugin Check scan
Security
24
6 issue groups
I18n
16
2 issue groups
Maintainability
8
4 issue groups
Repo Compliance
1
1 issue group
Sample message
Mismatched text domain. Expected 'advanced-custom-fields-oembed-field' but got 'acf'.
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$dimensions['height']'.
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
Missing $domain parameter in function call to __().
Sample message
Processing form data without nonce verification.
Sample message
Detected usage of a possibly undefined superglobal array index: $_POST['height']. Check that the array index exists before using it.
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "Advanced Custom Fields: oEmbed Field" - contains the restricted term "advanced-custom-fields" and cannot be used to begin your plugin name. We disallow the use of certain terms in ways that are abused, or potentially infringe on and/or are misleading with regards to trademarks. You may use the term "advanced-custom-fields" elsewhere in your plugin name, such as "... for advanced-custom-fields".
Sample message
In footer ($in_footer) is not set explicitly wp_register_script; It is recommended to load scripts in the footer. Please set this value to `true` to load it in the footer, or explicitly `false` if it should be loaded in the header.
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Detected usage of a non-sanitized input variable: $_POST['oembed_url']
Sample message
$_POST['oembed_url'] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
Tested up to: 4.0 < 7.0. The "Tested up to" value in your plugin is not set to the current version of WordPress. This means your plugin will not show up in searches, as we require plugins to be compatible and documented as tested up to the most recent version of WordPress.
Sample message
Incorrect Stable Tag. It's recommended not to use "Stable Tag: trunk". Your Stable Tag is meant to be the stable version of your plugin and it needs to be exactly the same with the Version in your main plugin file's header. Any mismatch can prevent users from downloading the correct plugin files from WordPress.org.
Potential connections found in static code analysis.
Outbound calls
4
External assets
0
Incoming endpoints
1
No external asset domains detected.
No public endpoints detected.
wp_ajax
First score snapshot
v1.0.3
44
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 44 | 49 | 36 | 13 | v1.0.3 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.