newshop

Hello @mrclayton
ok, thanks.
I’ve since discovered that the cause of the error message wasn’t the renaming of the fields at all, but the Flexible Checkout Fields plugin itself (it just made the required fields optional via css, so Klarna complained anyway altough the other payment methods worked, dont really understand that but when I disable the plugin everything works fine). So I will uninstall the plugin and change the order via functions.php.

So that means I could theoretically return to my original plan and rename the company field to “additional address” – not sure if that really makes sense though. Because then Stripe would get the information “Company: additional address data”, right? And if I add a whole new field instead of modifying the company field, Stripe probably wouldn’t get that info at all since my custom field isn’t a standard field, right?

Bottom line: if I need an Additional Address field, it would be the safest way to leave all the fields as they are and just rename “Street address” to “Street address and house number”, hoping that the customers notice it, right?

• This reply was modified 4 years, 9 months ago by newshop.

Hi @mrclayton
thank you very much for your fast reply.
The problem is that I wanted to have a seperate field for house number because by default street and housenumber are one single field – this is very confusing for Germany and leads to people forget to enter the house number.

So, I could try to add the house number as an additional field instead of modifiying the existing ones but I guess that will have unintended consequences too, right? Because Klarna & Co. only grab the information from the default Woocommerce fields?
If so, I think I have to go back to the default fields and hoping that Woocommerce will introduce the seperate house number field one day…

Kind regards from Germany

Hello? This is still not resolved..

Hi @stoyangeorgiev
ok I see, thank you. Although for onlineshops with customer login it would be a good feature. Guess it’s hard to combine good security with good user experience 🙂

Ok, danke. Ich lasse den Thread mal geöffnet, wäre super wenn du hier das Entwickler-Feedback teilen könntest.

• This reply was modified 4 years, 9 months ago by newshop.

Es kommt eindeutig von PayPal Plus. Es verschwindet sobald ich PayPal Plus deaktiviere und ist wieder da wenn ich es aktiviere.
Außerdem liegt der Code dazu in eurem Plugin (\woo-paypalplus\src\Assets\AssetManager.php ab Zeile 162):

private function enqueuePayPalFrontEndScripts()
    {
        list($assetPath, $assetUrl) = $this->assetUrlPath();

        wp_register_script(
            'bluebird',
            'https://cdn.jsdelivr.net/npm/bluebird@3.5.3/js/browser/bluebird.js',
            []
        );

Jetzt nochmal extra ein Plugin zu installieren nur um die unnötig geladenen Skripte von PayPal Plus zu deaktivieren (zumal ich den Bluebird Bezahlservice nirgends aktiviert habe da ich ihn nicht brauche) erscheint mir nicht besonders sinnvoll. Dann lieber per Action über die functions.php.
Aber eigentlich sollte es doch von Plugin-Seite aus so konfigurierbar sein dass es
1. Überhaupt erst aktiviert wird wenn dieser Bezahlservice angeboten wird und
2. Nur auf den Seiten geladen wird, wo es auch benötigt wird.

Hello,
just updated to version 3.0.2, cleared the cache and noticed that the closing div for “nv-product-image” class is still missing although it should be fixed due to the changelog (“div tag isn’t closed for products on the shop page”). 🙁
Could you please fix this and release it as a patch?
That would be really appreciated.

• This reply was modified 4 years, 9 months ago by newshop.