Hi, I changed the plugin slug to "domilocus".

You changed the plugin display name to "Domilocus".
Continuing with the plugin review for "consulinfolm". Let’s dive in!

Your plugin is not yet ready to be approved, you are receiving this email because the volunteers have manually checked it and have found some issues in the code / functionality of your plugin. 

Please check this email thoroughly, address any issues listed, test your changes, and upload a corrected version of your code if all is well. 
List of issues found


## Not permitted files

A plugin typically consists of files related to the plugin functionality (php, js, css, txt, md) and maybe some multimedia files (png, svg, jpg) and / or data files (json, xml). 

We have detected files that are not among of the files normally found in a plugin, are they necessary? If not, then those won't be allowed. 

Optionally, you can use the wp dist-archive command from WP-CLI in conjunction with a .distignore file. This prevents unwanted files from being included in the distribution archive. 

Example(s) from your plugin: 
domilocus/languages/domilocus-fr_FRmo
domilocus/languages/domilocus-es_ESmo
domilocus/languages/domilocus-it_ITmo
domilocus/languages/domilocus-en_GBmo
domilocus/languages/domilocus-de_DEmo



## Use wp_enqueue commands

Your plugin is not correctly including JS and/or CSS. You should be using the built in functions for this: 

When including JavaScript code you can use: 
•	wp_register_script() and wp_enqueue_script() to add JavaScript code from a file.
•	wp_add_inline_script() to add inline JavaScript code to previous declared scripts.

When including CSS you can use: 
•	wp_register_style() and wp_enqueue_style() to add CSS from a file.
•	wp_add_inline_style() to add inline CSS to previously declared CSS.

Note that as of WordPress 6.3, you can easily pass attributes like defer or async: https://make.wordpress.org/core/2023/07/14/registering-scripts-with-async-and-defer-attributes-in-wordpress-6-3/

Also, as of WordPress 5.7, you can pass other attributes by using this functions and filters: https://make.wordpress.org/core/2021/02/23/introducing-script-attributes-related-functions-in-wordpress-5-7/

If you're trying to enqueue on the admin pages you'll want to use the admin enqueues.
•	https://developer.wordpress.org/reference/hooks/admin_enqueue_scripts/
•	https://developer.wordpress.org/reference/hooks/admin_print_scripts/
•	https://developer.wordpress.org/reference/hooks/admin_print_styles/

Example(s) from your plugin:
includes/admin/booking-form.php:398 <style>
includes/admin/class-domilocus-dashboard-widget.php:143 <style>
includes/frontend/class-domilocus-frontend.php:693 <style type="text/css">



## Undocumented use of a 3rd Party / external service

Plugins are permitted to require the use of third party/external services as long as they are clearly documented. 

When your plugin reach out to external services, you must disclose it. This is true even if you are the one providing that service. 

You are required to document it in a clear and plain language, so users are aware of: what data is sent, why, where and under which conditions. 

To do this, you must update your readme file to clearly explain that your plugin relies on third party/external services, and include at least the following information for each third party/external service that this plugin uses: 
•	What the service is and what it is used for.
•	What data is sent and when.
•	Provide links to the service's terms of service and privacy policy.
Remember, this is for your own legal protection. Use of services must be upfront and well documented. This allows users to ensure that any legal issues with data transmissions are covered. 

Example: 
== External services ==

This plugin connects to an API to obtain weather information, it's needed to show the weather information and forecasts in the included widget.

It sends the user's location every time the widget is loaded (If the location isn't available and/or the user hasn't given their consent, it displays a configurable default location).
This service is provided by "PRT Weather INC": terms of use, privacy policy.


Example(s) from your plugin: 
# Domain(s) not mentioned in the readme file.
includes/frontend/class-domilocus-frontend.php:274 'https://js.stripe.com/v3/',
includes/frontend/class-domilocus-frontend.php:609 wp_enqueue_script('google-maps', 'https://maps.googleapis.com/maps/api/js?key=' . $google_maps_api_key . '&libraries=places', array(), '3.0', true);
# ↳ Found: 'https://maps.googleapis.com/maps/api/js?key=' . get_option('domilocus_manager_google_maps_api_key', '') . '&libraries=places'
includes/class-domilocus-events-manager.php:527 $url = 'https://api.predicthq.com/v1/events/';
includes/class-domilocus-eventbrite-api-validator.php:143 wp_remote_get($url, array('headers' => array('Authorization' => 'Bearer ' . $api_key, 'Content-Type' => 'application/json'), 'timeout' => 15, 'sslverify' => true));
# ↳ Found: 'https://www.eventbriteapi.com/v3/users/me/'
includes/class-domilocus-events-manager.php:434 $url = 'https://app.ticketmaster.com/discovery/v2/events.json';
... out of a total of 10 incidences.
# Domain(s) mentioned in the readme file. Links to service terms and/or privacy policy not found.
includes/admin/class-domilocus-dashboard-widget.php:292 wp_remote_get($feed_url, array('timeout' => 10, 'sslverify' => true));
# ↳ Found: 'https://consulinfo.it/wp-json/license-manager/v1/news'
includes/admin/class-domilocus-dashboard-widget.php:290 $feed_url = 'https://consulinfo.it/wp-json/license-manager/v1/news';

## Generic function/class/define/namespace/option names

All plugins must have unique function names, namespaces, defines, class and option names. This prevents your plugin from conflicting with other plugins or themes. We need you to update your plugin to use more unique and distinct names. 

A good way to do this is with a prefix. For example, if your plugin is called "Domilocus" then you could use names like these: 
•	function domilo_save_post(){ ... }
•	class DOMILO_Admin { ... }
•	update_option( 'domilo_options', $options );
•	register_setting( 'domilo_settings', 'domilo_user_id', ... );
•	define( 'DOMILO_PLUGIN_DIR', plugin_dir_path( __FILE__ ) );
•	global $domilo_options;
•	add_action('wp_ajax_domilo_save_data', ... );
•	namespace consulinfolm\domilocus;

Disclaimer: These are just examples that may have been self-generated from your plugin name, we trust you can find better options. If you have a good alternative, please use it instead, this is just an example.

The prefix should be at least four (4) characters long (don't try to use two- or three-letter prefixes anymore). We host almost 100,000 plugins on WordPress.org alone. There are tens of thousands more outside our servers. Believe us, you're likely to encounter conflicts. 

You also need to avoid the use of __ (double underscores), wp_ , or _ (single underscore) as a prefix. Those are reserved for WordPress itself. You can use them inside your classes, but not as stand-alone function. 

Please remember, if you're using _n() or __() for translation, that's fine. We're only talking about functions you've created for your plugin, not the core functions from WordPress. In fact, those core features are why you need to not use those prefixes in your own plugin! You don't want to break WordPress for your users. 

Related to this, using if (!function_exists('NAME')) { around all your functions and classes sounds like a great idea until you realize the fatal flaw. If something else has a function with the same name and their code loads first, your plugin will break. Using if-exists should be reserved for shared libraries only. 

Remember: Good prefix names are unique and distinct to your plugin. This will help you and the next person in debugging, as well as prevent conflicts. 

Analysis result: 
# This plugin is using the prefix "domilocus" for 196 element(s).

# Looks like there are elements not using common prefixes.
includes/class-domilocus-post-types.php:28 register_post_type('eb_apartment', array(
    'labels' => array('name' => __('Apartments', 'domilocus'), 'singular_name' => __('Apartment', 'domilocus'), 'menu_name' => __('Apartments', 'domilocus'), 'add_new' => __('Add New', 'domilocus'), 'add_new_item' => __('Add New Apartment', 'domilocus'), 'edit_item' => __('Edit Apartment', 'domilocus'), 'new_item' => __('New Apartment', 'domilocus'), 'view_item' => __('View Apartment', 'domilocus'), 'view_items' => __('View Apartments', 'domilocus'), 'search_items' => __('Search Apartments', 'domilocus'), 'not_found' => __('No apartments found', 'domilocus'), 'not_found_in_trash' => __('No apartments found in trash', 'domilocus'), 'all_items' => __('All Apartments', 'domilocus'), 'archives' => __('Apartment Archives', 'domilocus'), 'attributes' => __('Apartment Attributes', 'domilocus'), 'insert_into_item' => __('Insert into apartment', 'domilocus'), 'uploaded_to_this_item' => __('Uploaded to this apartment', 'domilocus'), 'featured_image' => __('Featured Image', 'domilocus'), 'set_featured_image' => __('Set featured image', 'domilocus'), 'remove_featured_image' => __('Remove featured image', 'domilocus'), 'use_featured_image' => __('Use as featured image', 'domilocus')),
    'description' => __('Tourist apartments for booking', 'domilocus'),
    'public' => true,
    'publicly_queryable' => true,
    'show_ui' => true,
    'show_in_menu' => false,
    // We'll add it to our custom menu
    'show_in_nav_menus' => true,
    'show_in_admin_bar' => true,
    'show_in_rest' => true,
    'rest_base' => 'apartments',
    'capability_type' => 'post',
    'hierarchical' => false,
    'supports' => array('title', 'editor', 'thumbnail', 'excerpt', 'custom-fields', 'revisions', 'page-attributes'),
    'has_archive' => true,
    'rewrite' => array('slug' => 'apartments', 'with_front' => false),
    'query_var' => true,
    'can_export' => true,
    'delete_with_user' => false,
    'menu_icon' => 'dashicons-building',
    'map_meta_cap' => true,
));
includes/class-domilocus-post-types.php:150 register_taxonomy('eb_apartment_category', 'eb_apartment', array('labels' => array('name' => __('Categories', 'domilocus'), 'singular_name' => __('Category', 'domilocus'), 'menu_name' => __('Categories', 'domilocus'), 'all_items' => __('All Categories', 'domilocus'), 'edit_item' => __('Edit Category', 'domilocus'), 'view_item' => __('View Category', 'domilocus'), 'update_item' => __('Update Category', 'domilocus'), 'add_new_item' => __('Add New Category', 'domilocus'), 'new_item_name' => __('New Category Name', 'domilocus'), 'parent_item' => __('Parent Category', 'domilocus'), 'parent_item_colon' => __('Parent Category:', 'domilocus'), 'search_items' => __('Search Categories', 'domilocus'), 'popular_items' => __('Popular Categories', 'domilocus'), 'separate_items_with_commas' => __('Separate categories with commas', 'domilocus'), 'add_or_remove_items' => __('Add or remove categories', 'domilocus'), 'choose_from_most_used' => __('Choose from the most used categories', 'domilocus'), 'not_found' => __('No categories found', 'domilocus')), 'description' => __('Apartment categories', 'domilocus'), 'public' => true, 'publicly_queryable' => true, 'hierarchical' => true, 'show_ui' => true, 'show_in_menu' => true, 'show_in_nav_menus' => true, 'show_in_rest' => true, 'show_tagcloud' => true, 'show_in_quick_edit' => true, 'show_admin_column' => true, 'capabilities' => array('manage_terms' => 'manage_categories', 'edit_terms' => 'manage_categories', 'delete_terms' => 'manage_categories', 'assign_terms' => 'edit_posts'), 'rewrite' => array('slug' => 'apartment-category', 'with_front' => false, 'hierarchical' => true), 'query_var' => true));
includes/class-domilocus-post-types.php:196 register_taxonomy('eb_apartment_amenity', 'eb_apartment', array('labels' => array('name' => __('Amenities', 'domilocus'), 'singular_name' => __('Amenity', 'domilocus'), 'menu_name' => __('Amenities', 'domilocus'), 'all_items' => __('All Amenities', 'domilocus'), 'edit_item' => __('Edit Amenity', 'domilocus'), 'view_item' => __('View Amenity', 'domilocus'), 'update_item' => __('Update Amenity', 'domilocus'), 'add_new_item' => __('Add New Amenity', 'domilocus'), 'new_item_name' => __('New Amenity Name', 'domilocus'), 'search_items' => __('Search Amenities', 'domilocus'), 'popular_items' => __('Popular Amenities', 'domilocus'), 'separate_items_with_commas' => __('Separate amenities with commas', 'domilocus'), 'add_or_remove_items' => __('Add or remove amenities', 'domilocus'), 'choose_from_most_used' => __('Choose from the most used amenities', 'domilocus'), 'not_found' => __('No amenities found', 'domilocus')), 'description' => __('Apartment amenities and features', 'domilocus'), 'public' => true, 'publicly_queryable' => true, 'hierarchical' => false, 'show_ui' => true, 'show_in_menu' => true, 'show_in_nav_menus' => true, 'show_in_rest' => true, 'show_tagcloud' => true, 'show_in_quick_edit' => true, 'show_admin_column' => true, 'capabilities' => array('manage_terms' => 'manage_categories', 'edit_terms' => 'manage_categories', 'delete_terms' => 'manage_categories', 'assign_terms' => 'edit_posts'), 'rewrite' => array('slug' => 'amenity', 'with_front' => false), 'query_var' => true));

👉 Continue with the review process.

Read this email thoroughly.

Please, take the time to fully understand the issues we've raised. Review the examples provided, read the relevant documentation, and research as needed. Our goal is for you to gain a clear understanding of the problems so you can address them effectively and avoid similar issues when maintaining your plugin in the future. 
Note that there may be false positives - we are humans and make mistakes, we apologize if there is anything we have gotten wrong. If you have doubts you can ask us for clarification, when asking us please be clear, concise, direct and include an example.
📋 Complete your checklist.

✔️ I fixed all the issues in my plugin based on the feedback I received and my own review, as I know that the Plugins Team may not share all cases of the same issue. I am familiar with tools such as Plugin Check, PHPCS + WPCS, and similar utilities to help me identify problems in my code. 
✔️ I tested my updated plugin on a clean WordPress installation with WP_DEBUG set to true.
⚠️ Do not skip this step. Testing is essential to make sure your fixes actually work and that you haven’t introduced new issues. 

✔️ I acknowledge that this review will be rejected if I overlook the issues or fail to test my code. 
✔️ I went to "Add your plugin" and uploaded the updated version. I can continue updating the code there throughout the review process — the team will always check the latest version. 
✔️ I replied to this email. I was concise and shared any clarifications or important context that the team needed to know.
I didn't list all the changes, as the team will review the entire plugin again and that is not necessary at all.

ℹ️ To make this process as quick as possible and to avoid burden on the volunteers devoting their time to review this plugin's code, we ask you to thoroughly check all shared issues and fix them before sending the code back to us. I know we already asked you to do so, and it is because we are really trying to make it very clear. 

While we try to make our reviews as exhaustive as possible we, like you, are humans and may have missed things. We appreciate your patience and understanding. 

Review ID: R domilocus/consulinfolm/19Nov25/T3 24Nov25/3.7B 


--
WordPress Plugins Team | plugins@wordpress.org
https://make.wordpress.org/plugins/ 
https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/
https://wordpress.org/plugins/plugin-check/ 
{#HS:3144103998-915737#}  
On Mon, Nov 24, 2025 at 12:32 PM UTC, WordPress.org Plugin Directory <plugins@wordpress.org> wrote: 
This is an automated message to confirm that we have received your updated plugin file.

File updated by consulinfolm, version 1.0.3.

https://wordpress.org/plugins/files/2025/11/24_12-32-00_domilocus.zip


--
WordPress Plugins Team | plugins@wordpress.org
https://make.wordpress.org/plugins/ 
https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/
https://wordpress.org/plugins/plugin-check/ 
On Sun, Nov 23, 2025 at 10:19 AM UTC, WordPress.org Plugin Directory <plugins@wordpress.org> wrote: 
Hi,
#. DISPLAY NAME
#. ✨ The name 'EasyBooking Manager' uses a generic construction ('Easy' + 'Booking') that is commonly used by other plugins and may be confused with existing plugins (e.g. 'Easy Hotel Booking'). Because it's a generic phrase, it lacks a distinctive element and could cause user confusion in the directory.
#.   ↳ Suggested name: Consulinfo Booking Manager for Vacation Rentals
#.   ↳ Suggested slug: consulinfo-booking-manager


--
WordPress Plugins Team | plugins@wordpress.org
https://make.wordpress.org/plugins/ 
https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/
https://wordpress.org/plugins/plugin-check/ 
On Sat, Nov 22, 2025 at 9:29 AM UTC, WordPress.org Plugin Directory <plugins@wordpress.org> wrote: 
This is an automated message to confirm that we have received your updated plugin file.

File updated by consulinfolm, version 1.0.3.

https://wordpress.org/plugins/files/2025/11/22_09-29-44_easybooking-manager.zip


--
WordPress Plugins Team | plugins@wordpress.org
https://make.wordpress.org/plugins/ 
https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/
https://wordpress.org/plugins/plugin-check/ 
On Wed, Nov 19, 2025 at 8:24 AM UTC, WordPress.org Plugin Directory <plugins@wordpress.org> wrote: 
👋 consulinfolm - let’s improve your plugin!

Thank you for submitting your plugin, "EasyBooking WP". 

Before your plugin reaches a human reviewer, our automated tools — which help the team handle around 1,000 plugin reviews per week — have flagged a few potential issues that you may need to address. To avoid delays and help streamline the manual review process, we’ve pended your submission to give you a chance to review and fix these common issues. 

🤖 This is an automated message generated using a combination of algorithms and AI. It hasn’t necessarily been reviewed by a human. Its purpose is to help you resolve potential common issues early, before manual review begins. All AI outputs are marked with the emoji ✨ and it's quite accurate.
Who are we?

We are a group of volunteers who help you identify common issues so that you can make your plugin more secure, compatible, reliable and compliant with the guidelines. 

For consistency and better communication, your plugin review will be assigned to a single volunteer who will assist you throughout the entire review. However, response times may vary depending on how much time the volunteer is able to contribute to the team and if whether they need to consult something with the rest of the team. 
The review process

 
Please read this email in full and check each issue, as well as the links to the documentation and the provided examples. Also, search for any other similar occurrences of the same issue that are not explicitly mentioned in the email.
Make sure you understand the issues so that you can incorporate them into your existing skillset.
 
If you decide to continue with the review process, you must fix any issues, test your plugin, upload a corrected version and then reply to this email.
In case of any doubt, please fix everything else and ask your questions alongside the update.
 
Your plugin is manually checked by a volunteer who sends you the remaining identified issues in the plugin.
We will be devoting our time to reviewing your plugin, we ask that you honor this by following the instructions.
Note: Volunteers are not your QA team. They are here to help you identify and understand issues so that you can improve and maintain your plugin in the future. Fixing the issues is your responsibility.
 
If there are no further issues, the plugin will be approved 🎉
 
Be brief and direct in your reply (please, avoid copy-pasting bloated AI responses, our AI is quite brief), be patient and make sure you have addressed all the issues and tested your plugin before responding.
It is disheartening to receive an updated plugin only to find that only a few issues have been resolved, or that it causes a fatal error upon activation.

When not making adequate progress in your review, it will be delayed and eventually rejected, for the sake of volunteers devoting their time and other plugin authors who correctly follow the review process.

Each volunteer can review up to 300 plugins per week, and they love to have life besides reviewing plugins, so please make things easier for us.

Understanding the Review Queue

When you reply, your plugin enters the review queue again. Fewer review cycles mean quicker approval, while multiple reviews can extend the process to weeks or months. 
Tip: Carefully fix all issues and test your plugin before resubmitting to speed up approval. 

This process is designed to help you improve your plugin while making the review experience faster and more efficient for everyone. 

Have you read the guidelines and this plugin complies with them?

Please confirm that you have read and complied with the WordPress.org Plugin Directory Guidelines. 

In particular, but not limited to, please check the following: 
•	Any included code must be GPL-compatible. This means, among others, that the users have to receive the four essential freedoms: (0) to run the program, (1) to study and change the program in source code form, (2) to redistribute exact copies, and (3) to distribute modified versions. (Guidelines 1 & 4)
•	Plugins must not restrict or lock functionality. (Guidelines 1, 5, & 9 — see clarification on SaaS in Guideline 6)
•	Plugins are permitted to require the use of third party/external services. The service itself must provide functionality of substance and be clearly documented (what the service is and what is used for + what data is sent and when + links to privacy and service terms) in the readme file submitted with the plugin. (Guideline 6)
•	Plugins must not track users without explicit consent. (Guidelines 7 & 9)

Is the name of this plugin descriptive and distinctive, and does it respect the trademarks and project names of others?

Choosing a name for a plugin can be challenging - it needs to be distinctive and meaningful, but also carefully chosen to avoid overlapping with existing plugins or inadvertently use someone else's trademark or project name in a way that could lead to confusion. 
📜 General plugin name/slug requirements
•	Plugin names and slugs must not be too generic; they should briefly describe what the plugin does.
•	Plugin names and slugs can be original and unique, even if they don’t describe the functionality directly — as long as they are recognizable and distinctive.
•	Plugin names and slugs must be distinguishable from those of other plugins to avoid confusion.
•	Plugin names and slugs must respect others' trademarks and project names. If your plugin includes a trademark or project name that you do not own, you must clearly mention it in a way that denotes that there is no affiliation.

This plugin display name is "EasyBooking WP" and the slug is "easybooking-wp" . The AI has detected ✨ "WP, Airbnb, Booking.com, Stripe, PayPal, Klarna, Apple Pay, Google Pay, GitHub" as potential trademark(s). 

We asked a trained AI about common issues with plugin names and it thinks there might be a problem. 
 ✨ The display name includes the term "WP" (EasyBooking WP) and the slug contains "wp". Using "WP" / "WordPress" in the plugin name/slug is discouraged/redundant for plugins in the WordPress.org directory and should be removed.
For example, for your plugin: 
•	An alternative name may be: ✨ Consulinfo EasyBooking — Booking & Property Manager 
•	An alternative slug may be: ✨ consulinfo-easybooking 

ℹ️ These suggestions were made by the AI. Bear in mind that a skilled human, either you or a volunteer from the Plugin Review Team, may spot issues with the new suggested name. 

⚠️ As with the rest of the review, you should address this issue and make any necessary changes. Simply changing the name without first checking what the issue is and how you can solve it won't help most of the time. Failure to address any of the issues raised will result in your submission being rejected for failing to demonstrate the expected level of effort in resolving the issues identified during the review process. 
☑️ Steps to resolve this issue

Choose a display name and slug that is distinctive, describes your plugin or uses a unique name, while respecting others’ trademarks and project names, (check for further details below) then: 
1.	Update the display name in both the readme file and plugin headers.
2.	Update the slug in your plugin files, for example in the internationalization functions.
3.	Reply to this email requesting a new slug reservation. 
In addition to the changes you have made to your code, we also need to reserve and allocate the new slug that you have chosen for your submission.
4.	Upload a new version via the "Add your plugin" page. 
If you are confident that the new name is suitable, there is no need to wait for confirmation of the new slug reservation. You may see a warning regarding the 'Text Domain', as we haven't changed the slug on our side yet. That's fine.

Also, please, don't check just this names, there are other places or resources where you may not use any trademarked (or commonly recognized) terms in a manner that that is likely to cause confusion. This includes (but is not limited to): 
•	Your username consulinfolm and your display name.
•	The plugin contributor's username and display name.
o	consulinfolm - consulinfolm
•	The URLs of this plugin.
•	Graphic resources such as this plugin icons and banners.

Are you the owner? If there are any issues with the trademark or project name and this is indeed an official plugin, it is likely that we have not been able to identify the current owner of the plugin as the trademark / project owner. 
Keep in mind, if you were hired as a freelance developer or a consultant specifically to create this plugin, then they must own the plugin. This is for their legal protection as well as yours. They can add you as a committer to the plugin so you can manage it from your account, but the owner must be them, not a temp-employee.

In order to solve this, you can do one of the following: 
•	Prove that you legally have the right to the original name/slug.
•	Change your user email to an official one or provide us with the user account for an official owner to whom we should transfer the plugin (they can create a new account if they need to)

Note: Should you have this plugin approved with the correct name and then go back to infringement of trademarks, we will close your plugin. Please don’t do this, even if you see other people ‘getting away with it.’ We have a lot of plugins and we’re contacting everyone in small batches to be manageable. They won’t get away with it forever, and they risk being banned from the directory. Which no one wants. 
ℹ️ Tips on choosing a suitable name (and avoiding back-and-forth in this process).

Choosing a name for a plugin can be challenging - it needs to be distinctive and meaningful, but also carefully chosen to avoid overlapping with existing plugins or inadvertently use someone else's trademark or project name in a way that could lead to confusion. 
🔍️ Avoid Name Similarity

Similarity is not only determined by letter-by-letter or word-by-word comparison; similar naming patterns or meanings also come into play. 
In short, anything that could lead to confusion.

You can verify the uniqueness of your plugin name the same way the review team does: 
1.	Perform a search engine query for the plugin name (Google, DuckDuckGo, Bing, ChatGPT) and parts of it.
2.	If you find other plugins with similar names, change your plugin’s name to something more distinctive—perhaps by adding a coined term, your personal brand, or a unique identifier.
3.	Go back to step 1 and check again, just in case.


Adding a generic word to the name to avoid similarity won't help. 
⚖️ Avoid Trademark / Project Names Confusion

Identify trademarks and project names mentioned in your plugin name "EasyBooking WP"and the slug "easybooking-wp" . The AI has detected ✨ "WP, Airbnb, Booking.com, Stripe, PayPal, Klarna, Apple Pay, Google Pay, GitHub" as potential trademark(s). 

To avoid potential misuse: 
•	If a trademark or project name is used at the beginning of your plugin name/slug and you are not the owner, it could imply false affiliation.
•	If the trademark appears elsewhere in the name/slug but is not part of a clear structure indicating unaffiliation, it may still be problematic.
•	Do not use any altered forms of a trademark, such as blend words or portmanteaus.

A safer naming pattern is to place the trademark at the end, following a phrase like "for" or "with". 
👀 Examples

Assuming you are creating a plugin that integrates with WooCommerce and you are not WooCommerce: 
•	❌ "WooCommerce Prices Updater" Trademarks issue as it implies affiliation with WooCommerce.
•	❌ "Prices Updater WooCommerce" Trademarks issue as it lacks a clear structure indicating no affiliation.
•	❌ "Prices for WooCommerce" It is too generic.
•	❌ "PricesPress for WooCommerce" This is considered portmanteau using the WordPress trademark.
•	❌ "Prices Updater for WooCommerce" Regarding trademarks it avoids indicating affiliation. However, there is a similarity issue, as there are other plugins with similar names.
•	❌ "Simple Prices Updater for WooCommerce" Similarity issue: Adding a generic word to avoid similarity won't make it sufficiently distinguishable.
•	✅ "Priconix Sync for WooCommerce" Ok! Original, distinguishable, unique name that is also not in use by others.
•	✅ "consulinfolm Prices Updater for WooCommerce" Ok! as it includes a unique identifier and clarifies unaffiliation (Ask ChatGPT)


Have you checked for common technical issues?

Please ensure that your plugin adheres to best practices, including the following: 
🔴 Proper sanitization of inputs

ℹ️ Why it matters: Sanitizing inputs is crucial for protecting against security vulnerabilities like SQL injection, handling invalid data, and ensuring that only safe, expected data is processed. 
Please check the official WordPress docs on sanitizing for details — this is a quick summary.

🔍 Identify unsanitized inputs: Check any input coming from sources such as: $_GET , $_POST , $_REQUEST , $_COOKIE , $_SERVER , $_SESSION 
If these inputs aren’t sanitized first, that’s a potential risk! 🕵️ 

🛠 Fix it: Always wrap any input with the right sanitization function, like: 
Content	Function
Plain text	sanitize_text_field() 
Email	sanitize_email() 
URL	esc_url_raw() 
Key	sanitize_key() 
Integer	absint() 

Refer to the official WordPress documentation for a complete list of sanitization functions.
👉 Use the most restrictive function that fits the expected content.
👉 Sanitize as early as possible — ideally as soon as the data is received.
👉 Only trust what you’ve cleaned yourself. 

Example:
$post_id = (int) $_GET['post_id']; // Sanitized as an integer
$email = sanitize_email( $_GET['email'] ); // Sanitized as an email
Your data is now sanitized! 🧼🍏 


Note: escape functions cannot be used to sanitize. They serve different purposes. Even if they seem to be perfect for this purpose, most of the functions are filterable and people expect to use them to escape. Therefore, another plugin may change what they do and make yours at risk and exploitable. 

If you are trying to echo the variable, you have to first sanitize it and then escape it, as for example: 
echo esc_html(sanitize_text_field($_POST['example']));
Example(s) from your plugin: 
includes/frontend/class-easybooking-shortcodes.php:1127 value="<?php echo esc_attr($_GET['min_price'] ?? ''); ?>" min="0" />
includes/frontend/class-easybooking-shortcodes.php:1070 value="<?php echo esc_attr($_GET['checkout'] ?? ''); ?>"
includes/frontend/class-easybooking-shortcodes.php:1130 value="<?php echo esc_attr($_GET['max_price'] ?? ''); ?>" min="0" />
includes/frontend/class-easybooking-shortcodes.php:1063 value="<?php echo esc_attr($_GET['checkin'] ?? ''); ?>"



Note: When checking a nonce using wp_verify_nonce you will need to sanitize the input using wp_unslash AND sanitize_text_field , this is because this function is pluggable, and extenders should not trust its input values. 

Example:
if ( ! isset( $_POST['easywp_nonce'] ) || ! wp_verify_nonce( sanitize_text_field( wp_unslash ( $_POST['easywp_nonce'] ) ) , 'easywp_nonce' ) )

Example(s) from your plugin: 
includes/admin/class-easybooking-admin-settings.php:687 if (empty($_POST['_wpnonce']) || !wp_verify_nonce($_POST['_wpnonce'], 'easybooking_settings_' . $tab)) {
includes/admin/class-easybooking-admin.php:319 if (empty($_POST['easybooking_resend_nonce']) || !wp_verify_nonce(wp_unslash($_POST['easybooking_resend_nonce']), 'easybooking_resend_confirmation_email')) {
includes/class-easybooking-calendar.php:29 if (!wp_verify_nonce($_POST['nonce'] ?? '', 'easybooking_nonce')) {
includes/class-easybooking-statistics-manager.php:677 if (!wp_verify_nonce($_POST['nonce'], 'easybooking_statistics')) {
... out of a total of 50 incidences.


Note: While the json_decode() function in PHP is useful for decoding JSON strings, it does not sanitize the input. Sanitization refers to the process of cleaning or filtering the input data to ensure that it is safe and secure to use. 

The json_decode() function simply transforms a JSON string into a PHP array or object. Any potentially malicious data or scripts may persist after json_decode(). 
Example(s) from your plugin: 
includes/class-easybooking-pricing-manager.php:590 $long_stay_discounts = json_decode(stripslashes($_POST['long_stay_discounts']), true);
includes/class-easybooking-pricing-manager.php:589 $pricing_rules = json_decode(stripslashes($_POST['pricing_rules']), true);


✔️ You can check this using Plugin Check.
🔴 Proper escaping of outputs

ℹ️ Why it matters: Escaping prevents common security issues like XSS (Cross-Site Scripting) and avoids breaking the HTML structure. 
Please check the official WordPress docs on escaping for details — this is a quick summary.

🔍 Identify unescaped outputs: Check any output ( echo , print , printf , etc. ) outputting a variable (like $title , $key ) or function result (like get_url() ) 
If the value is output without escaping, that’s a potential risk! 🕵️ 

🛠 Fix it: Always wrap any output with the proper escaping function depending on the context, like: 
Context	Function
URLs	esc_url() 
HTML attributes	esc_attr() 
Text inside HTML tags	esc_html() 
Raw HTML (careful!)	wp_kses() , wp_kses_post() 

Refer to the official WordPress documentation for a complete list of escaping functions.
👉 Use the most restrictive function that fits the context.
👉 Escaping should be applied as late as possible, ideally right before output. 

Example:
echo '<a href="' . esc_url( $profile_link ) . '" class="' . esc_attr( $username ) . '">' . esc_html( $display_name ) . '</a>';
Your output is now escaped! 


Note: The functions _e and _ex outputs the translation without escaping, please use an alternative function that escapes the output. 
•	An alternative to _e would be esc_html_e , esc_attr_e or simply using __ wrapped by a escaping function and inside an echo .
•	An alternative to _ex would be using _x wrapped by a escaping function and inside an echo .
Examples:
<h2><?php esc_html_e('Settings page', 'easybooking-wp'); ?></h2>

<h2><?php echo esc_html(__('Settings page', 'easybooking-wp')); ?></h2>

<h2><?php echo esc_html(_x('Settings page', 'Settings page title', 'easybooking-wp')); ?></h2>

Example(s) from your plugin: 
includes/admin/booking-form.php:296 <?php _e('Cancellata', 'easybooking-wp'); ?>
includes/class-easybooking-emails.php:384 <li><strong><?php _e('Check-out:', 'easybooking-wp'); ?></strong> <?php echo esc_html($check_out); ?></li>
 -----> _e('Check-out:', 'easybooking-wp')
includes/admin/class-easybooking-admin-settings.php:488 <p class="description"><?php _e('Nome visualizzato nel campo "Da".', 'easybooking-wp'); ?></p>
includes/class-easybooking-metaboxes.php:447 <label for="easybooking_country"><?php _e('Country', 'easybooking-wp'); ?></label>
 -----> _e('Country', 'easybooking-wp')
... out of a total of 470 incidences.


Note: The function __ retrieves the translation without escaping, please either: 
•	Use an alternative function that escapes the resulting value such as esc_html__ or esc_attr__ .
•	Or wrap the __ function with a proper escaping function such as esc_html , esc_attr , wp_kses_post , etc.
Examples:
<h2><?php echo esc_html__('Settings page', 'easybooking-wp'); ?></h2>

<h2><?php echo esc_html(__('Settings page', 'easybooking-wp')); ?></h2>

Example(s) from your plugin: 
includes/admin/class-easybooking-admin.php:514 echo '<span style="color: #999;">' . __('Apartment not found', 'easybooking-wp') . '</span>';
 -----> __('Apartment not found', 'easybooking-wp')
includes/class-easybooking-emails.php:462 <p><?php printf(__('Dear %s,', 'easybooking-wp'), esc_html($customer_name)); ?></p>
 -----> __('Dear %s,', 'easybooking-wp')
includes/class-easybooking-metaboxes.php:630 <li><?php printf(__('Free cancellation up to %d days before check-in', 'easybooking-wp'), (int) $applied_tariff_snapshot['free_cancellation_days']); ?></li>
 -----> __('Free cancellation up to %d days before check-in', 'easybooking-wp')
includes/frontend/class-easybooking-shortcodes.php:1238 <h3><?php printf(__('Search Results (%d apartments found)', 'easybooking-wp'), $apartments->found_posts); ?></h3>
... out of a total of 12 incidences.

✔️ You can check this using Plugin Check.
🔴 Nonces and User Permissions Before Processing Requests

ℹ️ Why it matters: Nonces and permissions checks ensure that the request comes from a trusted source, protecting against security threats like CSRF (Cross-Site Request Forgery) attacks. 
Please check the official WordPress docs on nonces and this article for details — this is a quick summary.

🔍 Spot it: Look for functions that interact with $_GET , $_POST , $_REQUEST and perform actions triggered by the user/browser that modify data or perform sensitive actions (e.g., privileged actions or data manipulation). For such actions, you should always check for a nonce. 
Additionally, verify user permissions if the action is restricted to certain roles (e.g., admin, editor). 
When in doubt, play it safe: always check. 

🛠 Fix it
1.	Create a nonce ( wp_nonce_field() , wp_nonce_url() , wp_create_nonce() ). If you need to pass the nonce to JavaScript you can make use of wp_localize_script() 
2.	Pass it with the request.
3.	Check the nonce ( check_admin_referer() , check_ajax_referer() , wp_verify_nonce() ) , and permissions if applicable ( current_user_can() ) .

Example (nonce check):
function easywp_save_email(){
    if ( !isset( $_POST['easywp_nonce'] ) || !wp_verify_nonce( sanitize_text_field( wp_unslash( $_POST['easywp_nonce'] ) ), 'easywp_save_email_action' ) ) {
        wp_send_json_error( 'Invalid nonce.' );
    }

    if ( !current_user_can( 'edit_posts' ) ) {
        wp_send_json_error( 'Insufficient permissions.' );
    }

    if ( isset( $_POST['post_id'] ) && isset( $_POST['price'] ) ) {
        update_post_meta( absint( $_POST['post_id'] ), 'price', floatval( $_POST['price'] ) );
    }
}
add_action( 'wp_ajax_easywp_save_email', 'easywp_save_email' );
⚠️ Without nonce and permissions checks, anyone could call this AJAX endpoint and change the price data for any post - risky! 
🔴 Use wp_enqueue commands

ℹ️ Why it matters: Because of performance and compatibility, please make use of the built in functions for including static and dynamic JS and/or CSS. 

🔍 Identify JS and CSS outputs: Look for any <script> or <style> HTML tags in your plugin. In the majority of cases you could enqueue them. 

🛠 Fix it: Make use of the specific function for enqueue them: 
Type of code	Functions
Static JS	wp_register_script() , wp_enqueue_script() , admin_enqueue_scripts() 
Inline JS	wp_add_inline_script() 
Static CSS	wp_register_style() , wp_enqueue_style() 
Inline CSS	wp_add_inline_style() 

👉 In the public pages you can enqueue them using the hook wp_enqueue_scripts() .
👉 In the admin pages you can enqueue them using the hook admin_enqueue_scripts() . You can also use admin_print_scripts() and admin_print_styles() .
👉 As of WordPress 6.3, you can easily pass attributes like defer or async, as of WordPress 5.7, you can pass other attributes by using functions and filters. 

Example:
function easywp_enqueue_script() {
    wp_enqueue_script( 'easywp_js', plugins_url( 'inc/main.js', __FILE__ ), array(), EASYWP_VERSION, true );
}
add_action( 'wp_enqueue_scripts', 'easywp_enqueue_script' );
Your JS/CSS is now enqueued! 

Possible cases from your plugin include: 
includes/admin/class-easybooking-admin-settings.php:586 <script>
includes/class-easybooking-metaboxes.php:272 <script>
includes/admin/class-easybooking-dashboard-widget.php:245 echo '<style>
includes/class-easybooking-metaboxes.php:859 <script>
includes/admin/class-easybooking-dashboard-widget.php:229 echo '<script>
includes/admin/class-easybooking-dashboard-widget.php:146 echo '<style>
includes/admin/class-easybooking-admin.php:168 <script>
includes/class-easybooking-metaboxes.php:236 <style>
... out of a total of 10 incidences.


👉 Your next steps

This is your checklist: 
1.	Have you read the guidelines and this plugin complies with them?
2.	Is the name of this plugin descriptive and distinctive, and does it respect the trademarks and project names of others?
3.	Have you checked for common technical issues?

If there is something that needs to be fixed, please take your time, fix it and update your plugin files at the "Add your plugin" page, while being logged in with your account "consulinfolm".
Please be concise and do not list the changes done — we will review the entire plugin again — but do share any clarifications or important context you want us to know.

If after checking the list and do the changes you feel that everything is right or need further clarification, please reply to this email and a volunteer will assist you. 

If you believe there is a requirement you cannot accomplish and choose not to make changes, your plugin submission will be rejected after three months. 
Thanks!

By taking these steps, you're helping the Plugin Review Team work more efficiently — meaning your plugin (along with the thousands of others in the queue) can be reviewed faster. 🚀 We really appreciate your contribution! 
Disclaimers

If, at any time during the review process, you wish to change your permalink (aka the plugin slug) "easybooking-wp", you must explicitly and clearly tell us what you would like it to be. Just changing it in your code and in the display name is not sufficient. Remember, permalinks cannot be altered after approval. 
This email was partially auto-generated, so please be aware that some information might not be entirely accurate. No personal data was shared with the AI during this process. If you notice any obvious errors or something seems off, feel free to reply — we’ll be happy to take a closer look and readjust this automation. 

REVIEW ID: AUTOPREREVIEW ❗TRM easybooking-wp/consulinfolm/19Nov25/T1 19Nov25/3.7B


--
WordPress Plugins Team | plugins@wordpress.org
https://make.wordpress.org/plugins/ 
https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/
https://wordpress.org/plugins/plugin-check/