I don’t see the connection right now, and I’m not aware of the rule you mentioned (despite very good experiences with WCS in the meantime).
Can you please name the specific error message you received?
And what did you test with? With WCS from the composer package, with the plugin checker plugin or is it the feedback from the plugin team about your plugin?
We are Using WCS but no error found in this.
We got feedback from the WordPress plugin team
We got message from wordpress team
## Generic function/class/define/namespace/option names
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 “woocommerce” for 43 element(s).
## Undocumented use of a 3rd Party or external service
We require plugins that reach out to other services to disclose this, in clear and plain language, so users are aware of where data is being sent. This allows them to ensure that any legal issues with data transmissions are covered. This is true even if you are the 3rd party service.
inc/classes/functions.php:1036 $sharing_url = ‘https://api.whatsapp.com/send?text=*‘. wp_strip_all_tags($args[‘text’]) .’%0a’. $args[‘url’];
I would recommend you to send a corresponding answer to the 1st point that your plugin uses WooCommerce hooks because you extend their functions. I don’t think this is something you can solve technically but should clarify with the plugin team.
And on the 2nd point, I think you should point out the use of this external service to your plugin user in your readme.txt and, if necessary, in other places where it makes sense.
Ok, Thank you!
Also, one thing we are not able to find prefixes below points using WCS. Is it possible to use the custom rule to find prefixes?
## 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 “Easy Custom Post Types” then you could use names like these:
- function ecpt_save_post()
- class ECPT_Admin{}
- namespace ECPT;
- update_option( ‘ecpt_settings’, $settings );
- define( ‘ECPT_LICENSE’, true );
- global $ecpt_options;
I’m not aware of any sniff, and I’d say it would be very difficult to do in terms of content. You have to make sure that all your functions are unique and cannot be used by other plugins, themes, WordPress itself or even PHP. I usually add the plugin slug as a prefix, sometimes completely, sometimes shortened, depending on the situation.
