👋 hitesh94 - Let’s improve your plugin!

Thank you for submitting your plugin, "Advanced Repeater Field for ACF".

Our volunteer reviewers, tools, and/or AI aids identified issues in your plugin that require your attention.

We’ve pended your submission to give you a chance to review and fix these common issues.

🤖 Please note that this message was generated using a combination of humans, algorithms, and AI in varying proportions. It may not have been reviewed by a human. All AI outputs are marked with the ✨ emoji. Pay attention to it, it's quite accurate.

Who are we?

The WordPress.org Plugins Directory is a service that the WordPress community offers to the world: free hosting, distribution and updates for more than 65,000 plugins, available to every WordPress site at no cost. This is made possible by the WordPress Foundation, the donated infrastructure that supports WordPress.org, and the volunteers who keep it running.

Being listed in the directory is not a commercial service and should not be taken for granted; it is an invitation to be part of this community, and it comes with the shared responsibility of keeping the directory safe and reliable for the millions of users who trust it.

We, the Plugins Team, 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 review is assigned to a single volunteer who will assist you throughout the entire process.

The review process

An email envelope.	1. Read this email carefully from start to finish. Review every issue, including the linked documentation and the provided examples. Then search your codebase for other occurrences of the same issues, even if they are not explicitly mentioned in this review. Take the time to understand each issue so you can apply what you learn to your plugin going forward.
A plugin author fixing the issues.	2. Address all identified issues, test your plugin thoroughly and upload a corrected version. If you have doubts about a specific issue, fix everything else and ask your questions alongside the update.

Note: The Plugins Team volunteers are not your developers or QA team. They are here to help you identify and understand issues so that you can improve and maintain your plugin in the future. Finding and fixing these issues remains your responsibility.
A volunteer reviewing the plugin.	3. Reply to this email thread (do not create a new email or reply to the submission confirmation). Your plugin will then be added to your reviewer's queue, and they will send you any remaining issues that are identified.
A new review of the plugin.	4. Once no further issues remain, your plugin will be approved 🎉

Fewer review cycles mean quicker approval, while multiple rounds can extend the process to weeks or months.

Before you reply

A warning.	Throughout the entire process, and before you reply, please ensure that:
You have addressed all reported issues and thoroughly tested your plugin. Make sure your updated version does not introduce new issues, such as fatal errors during activation.
You are replying to this email thread.
Your reply is brief and to the point. Include only information that is relevant for the next review; there is no need to describe every change you made, and please avoid unnecessary verbosity or AI-generated filler.
If you wish to alter your permalink (aka the plugin slug) "advanced-repeater-field-for-acf", you have explicitly stated your desired permalink in your reply. Changing the display name alone is not sufficient, and permalinks cannot be altered after approval.
You are making meaningful progress between review rounds. Updates that resolve only a small portion of the reported issues delay the review process, and the plugin may be rejected out of respect for the volunteers' time and other plugin authors waiting in the queue. Plugins rejected under these circumstances will not be reviewed again.
You treat the review as a learning opportunity and improve your knowledge of development practices and the directory guidelines accordingly.
Each volunteer may review hundreds of plugins every week. Following these indications and submitting a well-tested update makes the review process smoother for everyone.

Response times

Reviews are handled by volunteers alongside their own personal and job commitments, so response times depend entirely on their availability. You may receive a reply within a few days, after a week or two, or occasionally after a longer period. We appreciate your patience and understanding.

Please avoid requesting status updates unless you have been waiting an unusually long time (a month or more). Status requests do not accelerate the review; they slow it down by taking time away from the volunteers working through the queue. If you have replied to this email thread, you are in the queue. If you believe a reply went missing, check your spam folder and other inboxes first; if you have lost this email, write to us from the same address we sent it to and request that it be resent.

Guidelines

In addition to code quality, security and functionality, all plugins must adhere to the guidelines you accepted when submitting this plugin. Please keep them in mind when making changes: https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/.

Please note that failure to follow the Plugins Directory guidelines is taken seriously and may result in the loss of your WordPress.org plugin hosting privileges.


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 could 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(s) is/are "Advanced Repeater Field for ACF" and the slug is "advanced-repeater-field-for-acf" . The AI has detected ✨ "ACF" 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 begins with the generic descriptive phrase “Advanced Repeater Field” and does not include a distinctive identifier for the plugin or author. ACF is correctly placed after “for”, but the overall name remains insufficiently distinctive.
For example, for your plugin:
An alternative name may be: ✨ hitesh94 Advanced Repeater Field for ACF
An alternative slug may be: ✨ hitesh94-advanced-repeater-field-for-acf

ℹ️ 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 and/or uses a unique name, while respecting others’ trademarks and project names, (check for further details below) then:
Update the display name in both the readme file and plugin headers.
Update the slug in your plugin files, for example in the internationalization functions.
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.
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 hitesh94 and your display name.
The plugin contributor's username and display name.
hitesh94 - Hitesh Patel
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. Being granted permission is not enough. 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

In this context, by "similar" we mean something that goes beyond a letter-by-letter or word-by-word comparison. We also look into similar naming patterns, lookalike names or meanings.
You must ensure that the name of your plugin is distinctive and does not cause confusion with others.

How can you check this? Easy!
Perform a search engine query for the plugin name (Google, DuckDuckGo, Bing, ChatGPT) and parts of it.
If you find other plugins with "similar" names, change your plugin's name to something more distinctive and that won't cause confusion.
Go back to step 1 and check again, just in case.

❌ Changing the plugin name by adding a additional letter or a generic word (Advanced, Simple, etc) will probably not solve this problem at all.
✅ Your plugin name has to clearly stand out from other's plugins. You could try adding a coined term, your personal brand or a unique identifier at the beginning of the name. We rely on your creativity!

⚖️ Avoid Trademark / Project Names Confusion

Identify trademarks and project names mentioned in your plugin name "Advanced Repeater Field for ACF"and the slug "advanced-repeater-field-for-acf" . The AI has detected ✨ "ACF" 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.
❌ "Prices for WooCommerce by hitesh94". This plugin's distinguishing term shouldn't go at the end. It should be at the beginning.
❌ "AB Prices for WooCommerce". The term that distinguishes this plugin should be clearly differentiating, adding a few letters is not enough.
❌ "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.
❌ "Easy 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.
✅ "hitesh94 Prices Updater for WooCommerce" Ok! as it includes a unique identifier and clarifies unaffiliation (Ask ChatGPT)




👉 Your next steps

This is your checklist:
Is the name of this plugin descriptive and distinctive, and does it respect the trademarks and project names of others?

If there is something that needs to be fixed, please:
Take your time and fix it. Make sure that everything was addressed and the plugin works.
Update your plugin files at the "Add your plugin" page, while being logged in with your account "hitesh94".
Reply to this email.
Please keep your reply short, direct and clear. Avoid overly verbose and long AI responses. Do not list the changes made, we don't need that, we will review the entire plugin again, we won't compare the changes. However, please share any important context or clarifications that may help us during the review.

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 help 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) "advanced-repeater-field-for-acf", 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 advanced-repeater-field-for-acf/hitesh94/26Aug26/T1 26Aug26/4.2 (P0TDX359306HGN)