Query re cron & recurring payments

  • Resolved nm001

    (@nm001)


    3 months, 3 weeks ago

    Your plugin has a very sensible check if the site appears to be a duplicate (presumably for staging or CDN). If it detects a duplicate, then you require the payment mode to be switched to test mode and back to avoid duplicate payments being triggered.

    We have wp cron set to be run via a conventional cron. ie. in wp-config.php disable_wp_cron is set to true

    So in fact there is no risk of duplicate payments.

    Despite this, in order to get renewals to work we have to manually switch to test mode and back.

    Is there a way around this? Is there a function we can use to do the switch in code or clear the duplicate site flag?

    We found the test mode flag in the options table in the database, but fiddling directly with that – eg. inserting then removing – looks risky + we suspect that probably won’t work anyways.

    Many thanks.

    • This topic was modified 3 months, 3 weeks ago by nm001.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Georgian Cocora

    (@raster02)

    3 months, 3 weeks ago

    Hello @nm001,

    Is the URL of your website changing constantly and triggering that failsafe? If you reset it once after you change the URL, it shouldn’t trigger again.

    To reset it, simply enable the opposite operation mode -> save -> activate back the mode you want -> save.

    Also, we expose a filter that you can use to simply bypass that check: 

    add_filter( 'pms_disable_cloned_website_check', '__return_true' );

    Hope this helps!

    Best Regards.

    Thread Starter nm001

    (@nm001)

    3 months, 2 weeks ago

    That’s really helpful. Presumably the filter belongs in functions.php

    We’re using a CDN so consistently two URLs but cron only runs on the origin server.

    Plugin Author Georgian Cocora

    (@raster02)

    3 months, 2 weeks ago

    Hello @nm001,

    Yes, child theme functions.php or a custom plugin.

    You can use it as long as you’re aware that your website is bypassing that restriction. The main problem appears when cloning the website to another server

    Best Regards.

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

You must be logged in to reply to this topic.