• Resolved alfredo1216

    (@alfredo1216)


    Hi,

    I really like the way your plugin works, it’s great.

    However, I have the following problems:

    On the woocommerce checkout page, when loading the page it sends a verification request, and if I reload it 5 times, it sends it 5 times. When it should only be when the order is going to be processed by clicking on the “Place Order” button.

    How could I solve it?

    And also, isn’t it possible to have a .log to see where some requests are coming from?

    Thanks

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author IsTempMail

    (@istempmail)

    Hi Alfredo,
    sorry for the delayed answer. We currently use functionality that is built into WordPress to trigger the email verification. We do this for maximum compatibility with plugins built on top of WP.

    We are aware this creates extra API requests in WooCommerce. Unfortunately at the moment we do not have specialized support for WC in our plugin. We will likely add it in the future, though.

    A log is available from your IsTempMail dashboard, under “API statistics”.

    In WooCommerce, do you want to use disposable email detection to prevent fraud? Or are you using it to prevent users from getting free products with a fake email? Or something else?

    Thread Starter alfredo1216

    (@alfredo1216)

    Hi,

    It would be great if this problem could be solved in a future update.

    Regarding the log, I checked “API Statistics” and I see that I am receiving a recurring request with domain example.com that I believe is being generated by a plugin. I was wondering if there was a possibility of knowing or having a .log with the path from where the request originated or if they could integrate it in the future and thus exclude it.

    Regarding your question, I use your plugin mainly to avoid the purchase of free products with temporary emails, and then to avoid fraud.

    Thanks

    Plugin Author IsTempMail

    (@istempmail)

    Hi Alfredo,

    Regarding example.com – I can’t see your stats but this could also be from our plugin itself. We currently do a test API call using example.com to verify the tpoken provided. This happens when you activate the plugin or save settings. So it should only be very few calls. This is obviously not ideal and we’ll solve this with the next version of our API. We also know that users sometimes enter example.com addresses instead of an actual email to try and game email verification. This might also account for some of the API calls you saw.

    Adding a log is a great suggestion. It would provide better insight and control for installations with many plugins. We’ll keep that in mind for the next major release of the plugin.

    Thanks for letting us know about your use case. We agree that IsTempMail is a great way to prevent abuse of free product offers and can be a good layer of protection against fraud.

    Thank you for your feedback. I’ll close this for now. Feel free to send us an email to [email protected] if you want to stay in touch regarding upcoming releases of the plugin.

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