Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter gcbrowne

    (@gcbrowne)

    You’re right. I’m on pro. I got referred here from a forum where the issue was being discussed. Didn’t notice the “Lite” part until after I posted.

    Sales sync not working for anyone. So this is still good info for someone on Lite who is considering Pro to see that when they spend money their paid version won’t work.

    If I was on Lite and I saw that the paid version wasn’t working I definitely would think twice about buying.

    Thread Starter gcbrowne

    (@gcbrowne)

    No I didn’t reach out to them. After having read all the posts with the identical problem and seeing the identical response from Yoast regarding said problems (this is over what looked to be months and years) there didn’t seem to be a point to adding myself to the roles of the people with the issue knowing full well all I’d get was a cut and paste reply used many times over. It was a quicker fix to uninstall and look for an alternative.

    But like I said, the free version works fine.

    This problem persists despite yoast marking this resolved. I am using the latest 16.2 version and get the same error – and the proposed resolution does not work. Sorry I spent money on this. I shall now go lament in the review section so other folk think twice about spending their own money.

    Thread Starter gcbrowne

    (@gcbrowne)

    Review modified. 5 Stars.

    Thread Starter gcbrowne

    (@gcbrowne)

    Noted. I see that now. In testing with Wordfence temporarily disabled I do not see the error message. (Maybe you could add an addendum to the documentation about Wordfence interaction with login and registration forms. If I had read that I would have known immediately where to go to fix it.)

    I will edit the review to reflect this if I can. If I can’t edit it I will ask moderators if it can be removed. Thank you.

    Thread Starter gcbrowne

    (@gcbrowne)

    This is not in the premium add-on. This is in the base plug-in.

    This isn’t expected behaviour and sounds like a bug. But to be clear, this is functionality from the User Verification premium addon – but you say you aren’t a paying customer?

    With respect to the <not a paying customer bit” isn’t the purpose of offering the product for free is the expectation that someone will either license it or buy the add-ons? Everyone starts free for evaluation. My point was in this evaluation bits of this were broken for me. If they were fixable I would not have a problem buying the product.

    The verification error appears inside a WPUM tag in the code:
    Screenshot 1

    Screenshot 2

    Any login by a “subscriber” or non-admin user gets this email verification thing – and it occurs for every login attempt.

    As for shortcodes, I had to use the code editor and paste in the shortcodes rather than use a short-code editor to do that for me. I can live with that. But the verification on every login is too much.

Viewing 6 replies - 1 through 6 (of 6 total)