jloosli

I’m planning on testing out the various options above…it probably won’t be until next week (when things are a little quieter), but I’ll report back to you anything useful that I discover.

I didn’t realize that was what that does…I guess I’ve got two concerns:

• I’m worried about it being confusing for people if their account is created automatically (although I see some benefits for that as well).
• They access the things they have purchased through “Groups” plugin with the “Groups WooCommerce” plugin handling adding them to a group when the purchase is complete. This brings on more questions:

• Would everything just work (new account created, assigned to the correct group(s)), or would I need to jump through some hoops to make sure everything lined up?
• Will the purchase be attributed to the correct account if they have one, but aren’t logged in?

I’m not expecting you to know how the Groups thing works out, but it’s something I want to test out to get a better answer to my questions. There’s a big sale going on tomorrow, so I’m just going to leave the Payments API turned off for now. I’ll probably dig into this more sometime next week.

Thanks!

Here’s the checkout settings:

https://drive.google.com/file/d/1OQw9AuX8qSRWUOVV94XMxWGo-SaYYP7T/view?usp=sharing

Here’s the accounts settings:

https://drive.google.com/file/d/164Xj6MQmrrjUsoS7NC1Cw5NBUoSnVg9W/view?usp=sharing

Sorry…added that comment before seeing your comment. If the person isn’t logged in, on the checkout form, it won’t let them checkout unless they either create an account or log in. If you just made it so the Payments API wasn’t used unless they are currently logged in, that should fix the issue.

Just updated to the 4.0 version of the plugin. Same issue, but now someone gets an error saying the password field is empty. It would be great if this could just be conditional to only use the Payments/Apple Pay API if the person is currently logged in.

@jwineman,

Do you know when the next release will be coming?

I have a similar issue. Here’s the console information:

compiled.js?ver=3.1.1:28 action @ 14:44:31.163 CONFIG_FETCH
compiled.js?ver=3.1.1:28 action @ 14:44:31.502 CONFIG_FETCH_SUCCESS
compiled.js?ver=3.1.1:28 action @ 14:44:31.504 CONFIG_UPDATE_BY_KEY
compiled.js?ver=3.1.1:28 action @ 14:44:31.506 INTL_FETCH_TRANSLATIONS
compiled.js?ver=3.1.1:28 action @ 14:44:31.509 USER_LOGIN_SUCCESS
compiled.js?ver=3.1.1:28 action @ 14:44:31.512 ZONES_FETCH
compiled.js?ver=3.1.1:28 action @ 14:44:31.516 @@router/TRANSITION
compiled.js?ver=3.1.1:28 action @ 14:44:31.517 @@router/UPDATE_LOCATION
compiled.js?ver=3.1.1:28 action @ 14:44:32.071 INTL_FETCH_TRANSLATIONS_SUCCESS
compiled.js?ver=3.1.1:28 action @ 14:44:32.073 APPLICATION_INIT
compiled.js?ver=3.1.1:28 action @ 14:44:32.943 ZONES_FETCH_ERROR
compiled.js?ver=3.1.1:28 action @ 14:44:32.954 NOTIFICATION_ADD
compiled.js?ver=3.1.1:28 Uncaught Error: Minified exception occurred; use the non-minified dev environment for the full error message and additional helpful warnings.
at r (compiled.js?ver=3.1.1:28)
at s (compiled.js?ver=3.1.1:27)
at u (compiled.js?ver=3.1.1:27)
at Object.instantiateChildren (compiled.js?ver=3.1.1:24)
at y._reconcilerInstantiateChildren (compiled.js?ver=3.1.1:26)
at y.mountChildren (compiled.js?ver=3.1.1:26)
at y._createContentMarkup (compiled.js?ver=3.1.1:25)
at y.mountComponent (compiled.js?ver=3.1.1:24)
at Object.mountComponent (compiled.js?ver=3.1.1:26)
at y.mountChildren (compiled.js?ver=3.1.1:26)

Wordpress: 4.7.2
PHP: 7.0.15

• This reply was modified 8 years ago by jloosli. Reason: Added wordpress and PHP versions

I was receiving the same error, but I after changing:

&$this

to

$this

on lines 645 and 994, it worked

Ran into this problem as well…have you come across anything to resolve this?