WP Hotel Booking Woocommerce Plugin - Support paying for booking of WP Hotel Booking plugin with the payment system provided by WooCommerce.
Prioritized issue groups from the latest Plugin Check scan
Maintainability
99
11 issue groups
Security
82
4 issue groups
I18n
8
2 issue groups
Repo Compliance
3
3 issue groups
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$adult_qty'.
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$_product".
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "HB_WC_Booking".
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "'hotel_booking_admin_setting_fields_' . $this->id".
Sample message
Global constants defined by a theme/plugin should start with the theme/plugin prefix. Found: "HB_WC_ENABLE".
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "hb_wc_admin_view".
Sample message
A function call to __() 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
Mismatched text domain. Expected 'wp-hotel-booking-woocommerce' but got 'woocommerce'.
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "WP Hotel Booking WooCommerce" - contains the restricted term "woocommerce" which cannot be used within in your plugin name, unless your plugin name contains one of the allowed patterns: "for woocommerce", "with woocommerce", "using woocommerce", or "and woocommerce". The term must still not appear anywhere else in your name.
Sample message
wp_redirect() found. Using wp_safe_redirect(), along with the "allowed_redirect_hosts" filter if needed, can help avoid any chances of malicious redirects within code. It is also important to remember to call exit() after a redirect so that no other unwanted code is executed.
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
error_log() found. Debug code should not normally be used in production.
Sample message
Processing form data without nonce verification.
Sample message
parse_url() is discouraged because of inconsistency in the output across PHP versions; use wp_parse_url() 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
Tested up to: 6.9 < 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
Missing "License" in Plugin Header. Please update your Plugin Header with a valid GPLv2 (or later) compatible license.
Sample message
The "Domain Path" header in the plugin file must point to an existing folder. Found: "lang"
Potential connections found in static code analysis.
Outbound calls
3
External assets
0
Incoming endpoints
0
No external asset domains detected.
No public endpoints detected.
First score snapshot
v2.0.3
36
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 36 | 192 | 93 | 99 | v2.0.3 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.