Doesn’t stop feeds from processing

  • Resolved swinggraphics

    (@swinggraphics)


    3 months, 4 weeks ago

    It runs too late. It allows credit card information to be processed, then stops only the entry from being created in the database and notification emails.

    2024-07-25 11:24:18.812467 – DEBUG –> GFAuthorizeNet::get_payment_transaction(): Initializing new AuthorizeNetAIM object based on feed #197

    …

    2024-07-25 11:24:20.171147 – DEBUG –> GF_No_Duplicates::validate_token(): POST request from [form url] using GND Token 20240725103733-a4bb1597a253f5ac105ec977bb89cd4e818708d9 Existing entries using this token: 1 2024-07-25 11:24:20.171220 – DEBUG –> GF_No_Duplicates::validate_token(): GND Token 20240725103733-a4bb1597a253f5ac105ec977bb89cd4e818708d9 was saved to a previous entry!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Samuel Aguilera

    (@samuelaguilera)

    It’s not running late, it’s just not running, because stopping feed processing is not a feature of this plugin.

    For most feeds, which need the entry to be saved first in order to be able to process the feed, preventing the entry from saving will also prevent the feed processing. But this is not the case for feeds which run before saving the entry, like Authorize.net feeds.

    I’ll look into this as a feature request.

    Thread Starter swinggraphics

    (@swinggraphics)

    I understand. That would be a good feature. Gad knows why GF doesn’t fix this themselves to prevent duplicate payments.

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