The infamous Plugin Rejection!

Envato Authors CodeCanyon
1

Hey Y’all
I know it’s a boring topic, but according to the Envato Quality Team, here is still the best option!
I recently submitted a WordPress plugin, “One Tap Sign-in (OTSI)”, which is an authentication plugin that provides seamless sign-in options using Google One Tap, Facebook, LinkedIn, and traditional email login/registration. It can be a lightweight and easy-to-use authentication plugin that works with every theme, and relies on CloudFlare Turnstile for spam prevention and security.

It also provides many small but useful functionalities for the whole user management workflow, including:

  • User-Friendly Interface: Modern, responsive modals and buttons with customizable styling
  • Email Management System: Customizable HTML email templates for verification, welcome, and password reset
  • Security Features: CloudFlare Turnstile integration (CAPTCHA alternative), advanced email verification
  • User Tracking: Track user registration sources and login methods
  • User Dashboard: Creates user user-friendly user dashboard, which is customizable through the plugin, with a custom banner
  • WordPress Login Customization: Customize the default WordPress login page
  • Shortcode Support: Easy integration with any theme using shortcodes

I know it’s not an invention, but many themes won’t handle the registration process seamlessly, and this plugin let users have a simple all-in-one solution (instead of having many small plugins)

Now the real question is why we don’t get clear feedback?
is this the topic and usage of the plugin that got rejected?
Or does the technical implementation/documentation need improvement?

One possible area might be the licensing. I implemented a method where I need my plugin to get listed first, so that I can have the Item ID to make the license activation part work. (which I didn’t have before getting approved). What’s the workaround?

Here is the plugin landing page (no live demo yet):

I appreciate your feedback!

2

@AllSeen - The rejection could be due to one of these common issues:

  1. Licensing Implementation:
    The Item ID dependency is problematic. Envato typically requires licensing to work before approval. Consider using a temporary license key system that converts to Item ID post-approval.

  2. Feature Overlap:
    With existing auth plugins like Social Login, yours needs clearer USP differentiation. Highlight what makes OTSI unique (e.g., CloudFlare Turnstile integration + user tracking combo).

  3. Documentation:
    Ensure your documentation clearly shows:

  • Installation workflow
  • Customization options
  • Conflict resolution with major themes/plugins
1 Like
3

Hey, thanks for sharing this — the plugin sounds really useful, especially for themes that lack proper user registration flows. Regarding the rejection, it’s often not about the idea but more about polish. I’d recommend double-checking the documentation, code structure, and making sure everything follows Envato’s submission guidelines. Licensing can be tricky too — maybe consider using a temporary key system until your item gets an ID, or explain the logic clearly in your docs for reviewers. Sometimes, even a small UX issue or unclear setup can lead to a soft rejection. Hope you get it approved soon!

4

You cannot have license expiry. CodeCanyon’s license is lifetime access to updates etc.

It’s fine to require users to need to subscribe/extend for support but not updates etc.