• I’ve just installed the plugin and am getting things set up. When I am on the membership level checkout page, and click on select and confirm, it goes to a white page. I turned on debugging, and get this error:

    Notice: load_plugin_textdomain was called with an argument that is deprecated since version 2.7 with no alternative available. in /home/XXX/public_html/blog/wp-includes/functions.php on line 3008

    Notice: load_plugin_textdomain was called with an argument that is deprecated since version 2.7 with no alternative available. in /home/XXX/public_html/blog/wp-includes/functions.php on line 3008

    Notice: add_option was called with an argument that is deprecated since version 2.3 with no alternative available. in /home/XXX/public_html/blog/wp-includes/functions.php on line 3008

    https://www.ads-software.com/plugins/paid-memberships-pro/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter TraciBunkers

    (@tracibunkers)

    I deactivated all of my plugins except the ones for PMPro, and this is the error:

    Fatal error: Call to undefined method Stripe::setApiKey() in /home/XXX/public_html/blog/wp-content/plugins/paid-memberships-pro/classes/gateways/class.pmprogateway_stripe.php on line 12

    Thread Starter TraciBunkers

    (@tracibunkers)

    I’m not exactly sure what the problem was. I ended up having to deactivate PMPro and it’s “helpers”, restore the database to before I installed it. Then I reinstalled it and had the same problems. I deactivated the plugins and the debugging error was gone. Then I reactivated them one-by-one, and the error never came back . . . and it looks like that page works fine now. Go figure!

    Plugin Author Jason Coleman

    (@strangerstudios)

    Traci, sounds like another plugin on your site might have been loading an older version of the Stripe API. And depending on which plugin loaded first, the error would show up or not.

    You can try to upgrade any other plugin that might be using the Stripe API and see if that fixes things. Or sometimes when more than one plugin wants to load or use a third party library like that, some manually updates need to be made to one or both plugins to get them to play nice together. We and most other developers try to avoid these issues, but it’s really impossible without coding for every possible combination, etc.

    So if you know which other plugin might have been causing the conflict, let us know and we can try to address it for you and everyone else who might be using them together.

    Thread Starter TraciBunkers

    (@tracibunkers)

    I’m not sure which plugin was causing the problem. I do use Stripe with my Shopp plugin, but I use the plugins organizer plugin to filter out what loads/doesn’t load on specific pages, and had it set up to not load Shopp when in my “membership” area. So I’m not exactly sure what caused the problem/fixed it since it’s not happening now (fingers crossed it stays that way).

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘check out/confirm error’ is closed to new replies.