Cron action not working when manually triggered

  • Resolved Michael Ott

    (@mikeyott)


    6 months ago

    Firstly, love this plugin. And love the fact it’s actively supported. Kudos.

    I discovered an issue by chance just now. I had a stack of spam registrations (I’m not sure how but I’ll look into that further) and of course they are all unverified, which is expected.

    The Problem

    I have the setting enabled to Delete unverified users with a 360 delay, once daily. But I wanted to delete them all now, so I resorted to the trusty Cronjob Scheduler plugin which I often use for debugging and testing during development. I found the cron action called user_verification_delete_unverified_user which I am pretty certain is instigated by your plugin. The problem is that when I manually trigger the action, I see my users count go down, so some unverified users must be getting deleted, but I also still see a stack of unverified users that didn’t get deleted.

    Am I misunderstanding something? Or is this a bug?

    PS: Any chance we can have an Unverified view in the users page like this mockup?

    • This topic was modified 6 months ago by Michael Ott. Reason: Title change
Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Michael Ott

    (@mikeyott)

    Update: I also just noticed that when I manually trigger the action, it only ever deletes 20 unverified users at a time. I can constantly replicate this.

    Plugin Support pickpluginswporgrep

    (@pickpluginswporgrep)

    Hi Michael,
    Thank you for using our plugin. We really appreciate your support.

    Any chance we can have an?Unverified?view in the users page like this mockup?

    Sure! That’s a great feature request. Our developer agreed to implement this feature in our next update.

    We have set a limit on each cron execution because there may be thousands of spam users, and it is not a good idea to delete all of them in a single execution.

    You can schedule a server cron job to automatically delete unverified users, so you don’t have to run the cron manually.

    For guidance, refer to this article –?https://www.hostinger.com/tutorials/how-to-fix-wordpress-missed-schedule
    Start reading from “Set Up a Cron Command.”

    Thread Starter Michael Ott

    (@mikeyott)

    Thanks, that’s great news about the unverified view.

    I am aware of the existing function to schedule the cron to delete unverified users, and agree it would be problematic if it tried to delete too many at once.

    But there could easily be a situation where the website is acquiring more spam registrations at a rate greater than the number of unverified registrations that are deleted when the cron action runs, which means you can never actually clean up all unverified registrations.

    With this in mind, may I cheekily also suggest an option to let us specify how many are deleted when the cron action fires, and put a hard limit on the field so it can’t be abused. I realise this isn’t something casually implemented, so no worries if not possible. The new unverified view will still offer an easy way to bulk delete unverified registrations.

    Thanks – love your work.

    Plugin Support pickpluginswporgrep

    (@pickpluginswporgrep)

    I forwarded your feedback to our developers, and they completely understand the logic behind your request. They’ve agreed to implement this feature in a future update!

    Since our development team is currently focused on creating a Gutenberg block-based plugin called “Combo Blocks,” this update for the user verification plugin might take a few days to finalize.

    I’ll be sure to follow up here as soon as the update with your requested feature is available.

    Thread Starter Michael Ott

    (@mikeyott)

    Totally awesome! Take your time. We’ve all gone this long without the feature, waiting a bit longer won’t hurt.

    Talk soon.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.