Seamlessly integrates FancyBox lightbox into your WordPress blog: Upload, activate, and you're done. Additional configuration optional.
Prioritized issue groups from the latest Plugin Check scan
I18n
145
6 issue groups
Maintainability
47
10 issue groups
Security
15
3 issue groups
Repo Compliance
1
1 issue group
Sample message
Mismatched text domain. Expected 'fancybox-for-wordpress' but got 'mfbfw'.
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$current_settings".
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$ajax_nonce'.
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
strip_tags() is discouraged. Use the more comprehensive wp_strip_all_tags() instead.
Sample message
Missing $domain parameter in function call to esc_html_e().
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "FancyBox for WordPress" - contains the restricted term "wordpress" which cannot be used at all in your plugin name.
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "fancy_check_if_woocommerce".
Sample message
Processing form data without nonce verification.
Sample message
Resource version not set in call to wp_enqueue_script(). This means new versions of the script may not always be loaded due to browser caching.
Sample message
load_plugin_textdomain() has been discouraged since WordPress version 4.6. When your plugin is hosted on WordPress.org, you no longer need to manually include this function call for translations under your plugin slug. WordPress will automatically load the translations for you as needed.
Sample message
Found call to wp_enqueue_style() with external resource. Offloading styles to your servers or any remote service is disallowed.
Sample message
Sanitization missing for register_setting().
Sample message
Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "Fancybox_Review".
Sample message
Global constants defined by a theme/plugin should start with the theme/plugin prefix. Found: "PLUGIN_NAME".
Sample message
The parameter "FBFW_URL . 'languages'" at position #2 of load_plugin_textdomain() has been deprecated since WordPress version 2.7.0. Use "" instead.
Sample message
In footer ($in_footer) is not set explicitly wp_enqueue_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
A function call to esc_html__() with texts containing placeholders was found, but was not accompanied by a "translators:" comment on the line above to clarify the meaning of the placeholders.
Sample message
Tested up to: 6.8 < 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
The "Text Domain" header in the plugin file does not match the slug. Found "mfbfw", expected "fancybox-for-wordpress".
Not analyzed yet.
First score snapshot
v3.3.7
60
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 60 | 208 | 175 | 33 | v3.3.7 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.