Hi Krystian. Sorry for the delay: there is a holiday this week in Germany and my client is on vacation.
But I want to thank you for your support: I was at least able to activate the basic payment and checkout options with the plugin without bothering the client. Shop is running, orders are processed and payments received. No advanced features, but that will do for now and we can do the onboarding to enable the advanced payment options later.
Thanks again, marking the thread as (partly) resolved, will open a fresh one if I run into more problems later on.
First: Yes, plugin is not activated for payment, still trying to setup the options. This is a live shop, so the old payment plugin is still in use before switching over to the new one and deactivating the old one. Would it in theory be possible to use a staging site under a different name for testing and later switch sites? I would normally test in a staging environment, but was afraid that then PP/payment plugin will need a reconnect again when switching to a different domain.
I’m intentionally using the legacy mode after unsuccessfully trying with modern UI first (could not find the API key setting for manual more in modern UI) – therefore trying to finalize the process before the new UI will be mandatory.
Regarding the activation of the advanced options: As mentioned, I see them, but the activation link for all of them leads to a German PayPal page offering to start a new business account. At the end of that page is a link to use an existing login – but using my “associated” developer login (which is my own PP merchant account) does not seem to work for activating the features. If I could copy the links and send them to the client to proceed, that would be a viable workaround.
I understand the translation problem, have worked as a community developer myself during a WordCamp years ago. Its just that when official advised to switch to an official plugin, it’s unsatisfying do be presented with an untranslated part in the backend and told by support that it is translated and German as language supported (of course it is for the frontend).
Regarding the main problem, guiding the client remotely might be the last option. But hopefully we may find more information with the data you requested.
Krystian, thank you very much for the feedback and clarification.
First regarding the translation to German (Formal): In the current stable release, nearly all of strings for the backend/setup/onboarding have no German translation, therefore german users might be overwhelmed. I can’t tell my client to go into the WordPress backend of a German WooCommerce shop, where everything is properly translated, and force him to complete an onboarding process for a payment solution in an untranslated plugin backend and in a language that is not his native. Perhaps my installation is broken, but I don’t think so, see the translation pages for yourself: https://translate.ww.wp.xz.cn/projects/wp-plugins/woocommerce-paypal-payments/stable/de/formal/
Regarding the necessary onboarding for all the advanced payment options, this is very unfortunate and I have to investigate my options. Reason I was asked to switch the payment plugin was that PayPal CSA called the client and told him that switching to this plugin is mandatory and done “in a handful of easy steps”, just requiring new API keys. Client wasn’t able/willing to do that themselves and tasked me with switching the plugin, for this added me with the special role “developer” to his merchant account, most likely instructed by CSA. But that role doesn’t seem to support new onboarding. Due to 2FA I’m unable to use his login, even if the client would be okay with that. So, I’m currently in a deadlock. Can the client add me temporary to his PP account with some other role? What is the suggested best practice is this regard? I can’t be the only external developer asked to switch an existing WC shop to the “new” plugin?
